hindcast

MCP servers

MCP server for SEC filings — EDGAR tools for agents

An agent with a browser can read one filing. An agent with tools can answer a question that spans ten thousand of them. The difference is whether EDGAR arrives as HTML to be parsed on the fly or as typed tool calls that return resolved values with citations attached.

Hindcast exposes SEC coverage as an MCP server: tools for full-text filing search, XBRL fact lookup by concept and period, holdings and insider transactions, each returning the accession number and filing timestamp alongside the value. The agent does not manage rate limits, taxonomy quirks or amended-filing precedence — those are the server's problem, which is the entire reason to have a server.

MCP means no SDK and no integration branch in your codebase. Point a compatible client at the endpoint and the tools appear. The endpoint opens to the waitlist first.

hindcast — session

preview

hindcast> which filings mention a specific risk factor this year?

→ tool: filings_search { query:"...", forms:["10-K"], period:"..." }

matching passages with company, form type and accession number

source: SEC EDGAR — every hit links back to the filed document

Preview of the shape of an answer — endpoints open to the waitlist first.

What's covered

Join the waitlist — this page's dataset is already selected.

Need this one?votes for SEC & EDGAR
Optional — helps us build in the right order. All skippable.

Role

Company

Datasets you need

Questions

Which clients can connect to it?

Any client that speaks the Model Context Protocol — chat assistants, IDE agents and custom frameworks alike. The server is remote, so a client only needs the URL rather than a local install.

Can the agent trust what comes back?

It can check it, which is better. Every returned value carries the identifiers needed to open the underlying filing, so an answer can be verified rather than taken on faith.

Join the waitlist. Vote the roadmap. First in, first served.

← Back to the data catalog