mcpField
A
AgentFilings

AgentFilings

Remote
api.agentfilings.comFinance0Updated 2w ago

About AgentFilings

AgentFilings serves structured SEC/EDGAR filings, XBRL earnings, and Form 4 insider data for US filers as JSON. It is for agents and applications needing filing data, with restatement and period-label reconciliation and a free coverage probe before paid calls.

Key features

  1. 01Search SEC filings by company
  2. 02Retrieve XBRL-derived earnings data
  3. 03Access Form 4 insider transactions
  4. 04Reconcile restated period values
  5. 05Preserve fiscal period provenance
  6. 06Check endpoint coverage before payment

Use cases

  1. 01Retrieve recent filings for a US filer
  2. 02Review earnings periods and restated figures
  3. 03Look up insider transactions in Form 4
  4. 04Check whether a ticker has data before a paid request

MCP support

Exposes paid data tools through an MCP endpoint over streamable HTTP, alongside an HTTP API. Calls use x402 payments in USDC on Base; a Stripe subscription implementation is not enabled in the live deployment.

Configuration

Remote servers need no local install. Pick your client, then copy the config or install in one click.

Endpointhttps://api.agentfilings.com/mcp
Copy install command
Claude CodeTerminal
Cursor.cursor/mcp.json
VS Code.vscode/mcp.json
Claude Desktopclaude_desktop_config.json
Windsurf~/.codeium/windsurf/mcp_config.json

Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.

Tools

4
ParameterTypeRequiredDescription
tickerstringNoTicker to check, e.g. AAPL. Omit for service-wide coverage.

Details

From the project README

AgentFilings

Structured US SEC/EDGAR filing data for AI agents — filings index, XBRL-derived earnings, and Form 4 insider transactions as clean JSON, over both HTTP and MCP.

Paid per call with x402 (USDC on Base mainnet, no account required). A flat Stripe subscription rail — API-key issuance, subscription gate, checkout and webhook — is implemented in apps/api/src/billing/ but not switched on in the live deployment.

Live at api.agentfilings.com · OpenAPI · llms.txt · MCP at https://api.agentfilings.com/mcp, listed in the official MCP registry as com.agentfilings/mcp, with an MCP Server Card, an AI Catalog and an x402 manifest for discovery.

# Free. Tells you what data exists before you spend anything.
curl "https://api.agentfilings.com/probe?ticker=AAPL"

What's actually interesting in here

Most of the work went into three things that are easy to get wrong with SEC data, and one that's easy to get wrong with agent payments.

Restatements. companyfacts returns the same period once per filing that reported it. When a company restates a figure, the superseded value is still in the API. Each period here reconciles to its most recently filed value rather than the first one encountered.

Fiscal period provenance. The fy/fp fields on a fact describe the filing, not the period. A 10-Q showing last year's quarter as a comparative stamps that older period with the newer filing's fiscal year. Each period here keeps the labels from the filing that originally reported it. benchmark/ is a runnable measurement of how often those disagree.

Entity identity. SEC's ticker map can point at a post-reorganization shell that holds the ticker and files no financial data. Resolution is CIK-authoritative, with a guard that refuses to record coverage for an entity reporting no us-gaap facts.

Payment replay. Every x402 payment proof is bound to the specific resource it paid for, so a proof issued for one endpoint or MCP tool cannot be replayed against another. Settlement is idempotent, and EIP-712 domains are read per-network from the USDC contracts rather than hardcoded.

Honest coverage

/probe is free, and it will tell you not to pay:

{
  "ticker_coverage": {
    "covered": true,
    "endpoints_with_data": ["/filings/latest", "/earnings/summary"],
    "empty_endpoints": ["/insiders"],
    "hint": "Partial coverage. /filings/latest and /earnings/summary will return data. /insiders would return an empty result, so do not pay for those."
  }
}

A company can be covered for filings and empty for earnings — foreign issuers filing under IFRS, pre-revenue companies. Charging for a call that returns nothing is the fastest way to lose an automated buyer permanently, so the service says so before taking money.

Layout

apps/api/          TypeScript / Hono — HTTP API + MCP server
  src/payments/    x402 v2: routes config, replay guard, idempotency, discovery
  src/billing/     Stripe rail: key issuance, subscription gate, checkout, webhook
  src/mcp/         MCP over streamable HTTP, paid tools
  src/repo/        Corpus access (Postgres in prod, local JSON in tests)
apps/ingest/       Python 3.12 — SEC ingestion, XBRL + Form 4 parsers
packages/shared/   Pricing table, x402 constants, response types
infra/migrations/  SQL schema
benchmark/         Standalone, runnable SEC XBRL correctness measurement
tests/             Cross-cutting, including the payment-security spec

packages/shared/src/pricing.ts is the single source of truth for the API surface. The payment middleware, /probe, the MCP tool list and the OpenAPI document all derive from it.

Development

pnpm install
pnpm test        # vitest — api + shared
pnpm typecheck
pnpm lint
pnpm dev         # http://localhost:8080

curl localhost:8080/health
curl "localhost:8080/probe?ticker=AAPL"

Payments are gated off by default, so paid routes serve openly in development. Ingestion requires SEC_CONTACT_EMAIL — the SEC requires a contact in the User-Agent and blocks requests without one. See .env.example and infra/DEPLOY.md.

Principles

  • The free surface is honest. /health and /probe are always free, and /probe never overstates coverage.
  • Never charge for what cannot be served. An unimplemented endpoint is never payment-gated — the middleware would otherwise take payment and then 404.
  • Public domain only. SEC EDGAR. No licensed datasets, no scraped transcripts.
  • Merchant only. The service never holds, routes, or forwards third-party funds.

Licence

MIT. Data is SEC EDGAR, public domain.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.