Skip to main content
Astreus is an MCP server: AI assistants can connect to it and work directly with the platform’s structured, traceable financial data — statements, segments, filings, decks, transcripts, guidance, events, news, ownership, macro and the claim graph, across the US, the Gulf, Japan, Taiwan, Korea and Europe. Once connected, you don’t write API calls — you ask questions:
“Did NVIDIA beat its data-center guidance last quarter? Cite the filings.”
The assistant chains the tools itself (resolve the company → pull segment revenue → pull the guidance scorecard → trace the numbers to their filings) and answers with accession numbers next to every figure. The shared source release covers financials, source documents, calendars, ownership, management, macro catalogs, government, assets and other licensed research data. The hosted server and installed CLI can run different releases: use tools/list on the connected server for the actual tool names and schemas. Account administration and billing are outside the public MCP data surface.

Connect your client

No API key needed — you approve the connection with your Astreus sign-in (OAuth).
1

Add the connector

In Claude, open Settings → Connectors → Add custom connector and paste:
2

Approve access

Claude sends you to Astreus. Sign in (or you already are), review what’s being granted — read-only data access, metered on your plan — and click Approve.
3

Ask something

Back in Claude, enable the connector in the chat’s tools menu and ask a question. The connection works on Claude mobile too, and you can revoke it anytime from Claude’s connector settings.
Good first prompts: “What was Apple’s gross margin trend over the last 8 quarters? Cite each figure.” · “Summarize the newest 8-K from Tesla.” · “What did NVIDIA’s management promise on the last earnings call, and what’s their guidance hit rate?” · “Show US unemployment as it was known in March 2020.”

The tools

The current source release defines 64 public data tools. Four experimental tools remain local-only and are omitted here. A connected server’s tools/list is authoritative for the version it runs. Use the generated tool reference for exact endpoint mappings. Tool descriptions document units, coverage, licensing, pagination and source anchors. Some tools filter or reshape REST responses to satisfy their bounds and redistribution rules; do not assume every tool returns the entire corresponding REST payload. get_document_text reads a listed filing or document as bounded text, using the company identifier and accession/doc_ref from list_filings (an SEC accession alone also works, without the company). Page/character windows retain provenance. Scans without stored OCR can return text_unavailable; follow the returned source or page-image path rather than guessing the missing text.

Metering, auth and limits

  • A tool call is metered like the REST request(s) it makes — the same per-minute and monthly counters as the REST API. Most tools make one request; get_transcript (index + text) and get_guidance (commitments + scorecard) make two, and get_event_text makes two when it has to look the item code up first. Protocol plumbing (initialize, tools/list) is free. MCP calls appear in the usage dashboard as /api/mcp#<tool>.
  • get_financials takes the same period_type (including semiannual), reporting_basis and accounting basis as the REST route, and get_company returns the company’s accounting_bases so an assistant can ask for the right one.
  • Two credentials work: API keys (pk_live_..., as a Bearer or X-API-KEY header) and OAuth tokens from the connector flow. Both are data-scoped — key management, billing and account routes reject them by design.
  • When you’re rate limited, the tool result says how many seconds to wait; assistants honour it.

Availability and boundaries

The public tools omit local-only experiments. Prices, benchmarks, tracking, geometry, photos and other third-party data may be withheld or filtered by the tool’s license rules even when a REST route exists. Absence of a tool or a returned value is not zero. The data catalog and tool reference map each interface; check the tool’s own schema and returned limitations before relying on coverage. Current API keys remain data-scoped. Workspace storage, account news rules, billing and key management are not available through public MCP. The signed-in Agent mode uses the user’s existing account session for its news-monitor controls.

Rules the server enforces on itself

The server’s own instructions carry the contract from agents.md: cite accession numbers next to figures, respect vintages (/financials is latest-restated and names its filing; macro is the current vintage, not what was known at the time), treat null as “not available” — never zero — and present data without investment advice.