Financial data your agent can cite, back to the filing it came from.

Connect with OAuth (no key needed)

mcp.evidinvest.com is a full OAuth 2.1 authorization server (MCP authorization spec 2025-06-18, with RFC 7591 dynamic client registration and PKCE). Add the URL, sign in with your browser, approve once — the client holds the token and you never handle a key. Credits, tools and limits are identical to key auth, and the first connection carries the same free allowance.

curl -sI https://mcp.evidinvest.com/mcp -X POST
# HTTP/1.1 401 Unauthorized
# WWW-Authenticate: Bearer resource_metadata="https://mcp.evidinvest.com/.well-known/oauth-protected-resource"

curl -s https://mcp.evidinvest.com/.well-known/oauth-protected-resource
curl -s https://mcp.evidinvest.com/.well-known/oauth-authorization-server

What $20 buys

List prices, Sept 2026, from each vendor's pricing page. Check them before you buy. The full nine-provider table — history depth, filing citations, MCP, free tiers and non-US coverage, each cell sourced and dated — is on the September 2026 comparison.

Coverage

Options data policy. Options positioning is served for the previous trading session only. Under the OPRA plan, options data becomes historical — furnishable to any person and exempt from OPRA’s Redistribution Fee — at the opening of trading on the next trading session; data from the session in progress is delayed data whatever the delay, and redistributing it requires a Vendor Agreement we do not hold. So get_options_positioning returns an as_of date that is always a completed session, and no same-day options data is served on any surface. The guard is server-side, identical for the API, the MCP server and the site.

No analyst estimates. For US listings, rows from fiscal 2009 on link to their SEC filing; older rows are EvidInvest’s standardized historical statements without a filing link. The 40,000+ listings outside the US on 60+ exchanges — London, Tokyo, Zurich, Milan, Frankfurt, Paris, Stockholm and others — are standardized by EvidInvest, with end-of-day prices: no SEC filing behind them, no filing link, and less history than the US set.

Full inventory with per-dataset coverage and refresh times: what the financial data API actually has. How filing search returns cited passages from 10-K, 10-Q, 8-K and earnings calls: SEC EDGAR API and filing search.

Two ways to connect

Same key, same tools, same credits. Create the key at /settings/api-keys (sign in, “Create New Key”, copy it once).

import os, requests

r = requests.post(
    "https://mcp.evidinvest.com/v1/tools/get_income_statement",
    headers={"Authorization": f"Bearer {os.environ['EVIDINVEST_API_KEY']}"},
    json={"arguments": {"symbol": "NVDA", "period": "annual"}},
    timeout=30,
)
r.raise_for_status()
data = r.json()["result"]      # metered against your credit balance; HTTP 402 when it is 0

claude mcp add --transport http evidinvest https://mcp.evidinvest.com/mcp \
  --header "Authorization: Bearer YOUR_API_KEY"

{
  "mcpServers": {
    "evidinvest": {
      "type": "streamable-http",
      "url": "https://mcp.evidinvest.com/mcp",
      "headers": { "Authorization": "Bearer YOUR_API_KEY" }
    }
  }
}

One-click install

Every route below points at the same endpoint and bills the same credits. The deeplinks carry a YOUR_API_KEY placeholder — the editor opens its MCP settings pre-filled and you paste your real key there, so the secret never travels in a URL.

claude mcp add --transport http evidinvest https://mcp.evidinvest.com/mcp \
  --header "Authorization: Bearer YOUR_API_KEY"

{
  "model": "sonar-pro",
  "messages": [{ "role": "user", "content": "What does NVDA's latest 10-K say about supply concentration? Cite the filing." }],
  "mcp_servers": [
    {
      "name": "evidinvest",
      "server_url": "https://mcp.evidinvest.com/mcp",
      "headers": { "Authorization": "Bearer YOUR_API_KEY" },
      "defer_loading": true
    }
  ]
}

59 tools

Each is one REST endpoint and one MCP tool. Full schemas in the OpenAPI spec.

Credits

The same credit packs as the website — prepaid credits, metered by usage. AI analyses draw credits by the tokens they use, so connecting your own LLM through MCP or the REST API draws far less from a pack than an AI analysis on the site does.

One balance per account, shared by all your API keys. Free to start: your first API key carries a free allowance, once per account, no card. No subscription. Credits never expire.

Questions developers ask

What is free, and what costs credits?

The website is free. Your first API key starts with a free allowance, once per account, no card. After that, usage is metered against the same credit balance as the site — prepaid credits, from $10, metered by usage over both REST and MCP. Connecting your own model draws far less than an AI analysis on the site, which spends credits by the tokens it uses. Credits never expire and there is nothing to cancel.

Rate limits?

60 requests per minute per API key. When your balance hits 0 the API returns HTTP 402 with a top-up link; nothing is charged for the refused call.

REST or MCP — does billing differ?

No. Same key, same 59 tools, same credit balance over either transport. Use REST from scripts and pipelines, MCP from Claude, Cursor or any MCP client.

Where does the data come from, and can I show it to users?

For US listings, fundamentals are extracted from SEC EDGAR filings (10-K, 10-Q, 20-F, 40-F), which are public records, and prices are Cboe, delayed 15 minutes. The 40,000+ listings outside the US on 60+ exchanges have no SEC filing behind them: those fundamentals are EvidInvest-standardized and their prices are end-of-day. Every price-bearing response carries an attribution field naming the source and the delay — keep both if you display prices.

How would I know a number is right?

search_sec_filings, search_earnings_transcripts and the sec_* tools return the filing text with accession numbers and sec.gov URLs, so you can check the passage yourself. Valuation tools return every method, the assumptions it ran on and the filing behind them, not a single number.