Tools
Read-only tools across News, Markets, Signals, SEC datasets, and Account — search news, resolve assets and markets, pull Oracle signals, and query every SEC filing dataset.
MCP server overview
The Model Context Protocol (MCP) is an open standard that lets an AI agent discover and call external tools, read resources, and run prompt templates through a uniform interface — instead of hand-wiring HTTP calls into the model. The QuantConomy MCP server speaks that protocol, so any MCP-capable client can use the QuantConomy API as a first-class set of tools.
What it gives an agent
Section titled “What it gives an agent”The server wraps the QuantConomy REST API and exposes it as MCP primitives, so an agent can answer market questions directly from the data without you writing any glue code:
Resources
Stable URIs the agent can attach as context: quantconomy://account (plan, credits, limits)
and quantconomy://stats (system-wide counts and last-update times).
Prompts
Parameterised research playbooks — market-brief and company-due-diligence — that chain
the tools into a single workflow.
See the full list on the Tools & resources page.
Hosted and stateless
Section titled “Hosted and stateless”The server is hosted at https://mcp.quantconomy.com/mcp and speaks Streamable HTTP. It is
fully stateless: every request builds a fresh session from its own
Authorization: Bearer mtk_... header, handles the request, and disposes — so your API key is
supplied per request and is never stored between calls. There is also a GET /health
endpoint. Any MCP client that can connect to a remote server URL can use it.
A thin read-only proxy
Section titled “A thin read-only proxy”The MCP server adds no data of its own. Every tool forwards to the REST API at
https://api.quantconomy.com/api/v1 using your API key, so all of the platform’s rules
apply identically whether you call REST directly or go through MCP:
- The same plan tier gates (SEC datasets require Starter or higher).
- The same credit cost per request, charged against your balance.
- The same rate limits and validation.
Every tool is a GET, so the agent can only read — it can never create, modify, or delete.
Who it’s for
Section titled “Who it’s for”Any MCP-capable client that can connect to a remote server URL — including Claude Desktop, Claude Code, Cursor, and ChatGPT. See Connect a client for per-client setup.
Next steps
Section titled “Next steps” Connect a client Concrete config for Claude, Cursor, ChatGPT, and other remote-MCP clients.
Tools & resources Every tool, resource, and prompt the server exposes, with arguments.