Papertrade Analytics docs

Agent discovery

Everything an agent needs to find and use this project is served as real files at stable paths. They are generated at build time from the same tool registry the server runs, so they cannot drift from the code.

PathContent-TypePurpose
/.well-known/mcp/server-card.jsonapplication/jsonMCP server card: server info, the streamable-http endpoint, capabilities and the full tool list.
/.well-known/mcp.jsonapplication/jsonAlias of the server card.
/.well-known/agent-card.jsonapplication/jsonA2A agent card: name, description, skills mapped from the MCP tools, input and output modes, provider.
/.well-known/agent.jsonapplication/jsonAlias of the agent card.
/.well-known/api-catalogapplication/linkset+jsonRFC 9727 API catalog linking the OpenAPI document, the MCP endpoint, the docs and llms.txt.
/openapi.jsonapplication/jsonOpenAPI 3.1 for /api/metrics, /api/snapshots and /mcp.
/llms.txttext/plainShort index for language models, with links to every docs page as raw markdown.
/llms-full.txttext/plainEvery docs page inlined in one file.
/robots.txttext/plainContent-Signal and explicit allow for GPTBot, ClaudeBot, Claude-User, OAI-SearchBot, Google-Extended and PerplexityBot.
/sitemap.xmlapplication/xmlEvery page, including each docs page.

Every docs page also exists as raw markdown at the same path plus .md, for example https://papertrade-analytics.pages.dev/docs/mcp.md.

The home page sends Link response headers with rel="service-desc" (OpenAPI), rel="api-catalog" and rel="mcp" (the server card), so a client that only does a HEAD / can find the rest.

Registry listing#

server.json at the repository root describes the server for the official MCP registry under io.github.nirholas/papertrade-analytics with a streamable-http remote at the live /mcp. glama.json supports Glama. Publishing to the registry is a manual step by the maintainer.

Unofficial, not affiliated with Papertrade. High leverage can lose your whole margin. Not financial advice. Edit this page.