Edgar Entity MCP Server

edgar-entity-mcp

Source: https://github.com/pgeneralpl/edgar-entity-mcp · Issues: https://github.com/pgeneralpl/edgar-entity-mcp/issues · MCP Registry: io.github.pgeneralpl/edgar-entity-mcp

US company research for AI agents, from official public data. One MCP server that covers SEC EDGAR (filings, XBRL financials, Form 4 insider trades, cross-company comparisons) and state Secretary of State business-entity registries (NY, CO, OR, CT, PA). Responses are compact JSON with source URLs, sized to keep token use low.

• Analysts: "Compare TSLA, F and GM revenue for CY2023", "What did insiders sell at Apple this month?", "Summarize the latest 10-K risk factors."
• Founders / sales / diligence: "Is Acme Widgets LLC an active Colorado entity? Who is its registered agent?"
• Researchers: clean 10-K/10-Q sections as text, normalized financial time series with the XBRL tag used for each metric.

No API keys are needed for the data. SEC asks you to identify yourself with a User-Agent (see SEC User-Agent).

Hosted endpoint (no install): https://edgar-entity-mcp.vercel.app/mcp. See Install.

The npm package edgar-entity-mcp (0.1.0) is deprecated and no longer maintained. Use the hosted endpoint, or run the server from this repository's source.

---

Tools

Also included: a company_research_brief prompt that runs the whole workflow, and an edgar-entity://data-sources resource (licenses).

Every tool takes company as a ticker (AAPL), CIK (320193) or unambiguous name. Errors come back as {"error":{"code","message","hint"}} with isError: true. Ambiguous names return candidate CIKs; a typo (Microsfot) is never resolved silently: it returns AMBIGUOUS with the likely candidate, and an unknown name returns NOT_FOUND with did_you_mean, a pointer to lookup_business_entity and an EDGAR company-search link (current and former names, filers without a ticker).

Every tool declares an outputSchema, and successful results carry the same JSON twice: as structuredContent (for clients that use structured output) and as a JSON text block (for clients that don't). The schemas are deliberately permissive (few required fields, nullable values, extra fields allowed) so an unusual upstream record never turns a good answer into a validation error. Error results have only the text block.

Example calls and real outputs (live data, trimmed)

get_financials {"company":"AAPL","limit":1}

{"cik":"0000320193","name":"Apple Inc.","period_type":"annual","currency":"USD",
 "periods":[{"fy":2025,"fp":"FY","period_end":"2025-09-27","period_start":"2024-09-29","form":"10-K","filed":"2025-10-31",
   "accession":"0000320193-25-000079","revenue":416161000000,"gross_profit":195201000000,"operating_income":133050000000,
   "net_income":112010000000,"eps_basic":7.49,"eps_diluted":7.46,"operating_cash_flow":111482000000,"capex":12715000000,
   "total_assets":359241000000,"total_liabilities":285508000000,"stockholders_equity":73733000000,"cash":35934000000,
   "long_term_debt":78328000000,"shares_outstanding":14776353000,"free_cash_flow":98767000000}],
 "tags_used":{"revenue":["us-gaap:RevenueFromContractWithCustomerExcludingAssessedTax"],"net_income":["us-gaap:NetIncomeLoss"],"...":[]},
 "source_url":"https://data.sec.gov/api/xbrl/companyfacts/CIK0000320193.json"}

period_type:"quarterly" returns 3-month values. 10-Q cash-flow lines are year-to-date, so quarters are derived by differencing, and Q4 is derived as FY minus 9M. For example, MSFT FY25 Q4 revenue comes out at $76.441B, which matches the reported figure. Each derived value is listed in notes.

get_insider_trades {"company":"TSLA","limit":5}

{"cik":"0001318605","name":"Tesla, Inc.","filings_returned":5,
 "summary":{"open_market_buys":{"count":0,"shares":0,"value":0},"open_market_sales":{"count":19,"shares":34620.25,"value":13321733}},
 "code_legend":{"F":"Shares withheld to pay exercise price or taxes","M":"Exercise or conversion of derivative (exempt)","S":"Open market or private sale"},
 "filings":[{"form":"4","filed":"2026-09-09","accession":"0001104659-26-106432","reporter":"Taneja Vaibhav","roles":"Officer",
   "officer_title":"Chief Financial Officer","transactions":[
     {"security":"Common Stock","date":"2026-09-08","code":"S","shares":2605.75,"price":360.134,"value":938419.17,
      "acquired_disposed":"D","shares_owned_after":25972.25,"ownership":"D"}],
   "url":"https://www.sec.gov/Archives/edgar/data/1318605/000110465926106432/tm2625055d1_4seq1.xml"}],"has_more":true}

get_filing_document outline first {"url":"https://www.sec.gov/Archives/edgar/data/320193/000032019325000079/aapl-20250927.htm","mode":"outline"} (no text, ~2 KB for a 208k-character 10-K):

{"url":"…/aapl-20250927.htm","cik":"0000320193","accession":"0000320193-25-000079","index_url":"…/0000320193-25-000079-index.htm",
 "kind":"html","mode":"outline","total_chars":208531,
 "outline":[{"id":"1","title":"Business","offset":8637,"chars":16040},{"id":"1A","title":"Risk Factors","offset":24677,"chars":68120},
            {"id":"7","title":"Management's Discussion and Analysis (MD&A)","offset":104372,"chars":18232},
            {"id":"8","title":"Financial Statements and Supplementary Data","offset":125643,"chars":62027}, "…"],
 "hint":"Read an item with section: '<id>', or page through it with offset = the item's offset and max_chars ≤ its chars."}

then read only the item you need, 10,000 characters at a time by default (offset is relative to the section when section is set, else to the whole document):

get_filing_document {"url":"https://www.sec.gov/Archives/edgar/data/320193/000032019325000079/aapl-20250927.htm","section":"1A","max_chars":3000}

{"url":"…/aapl-20250927.htm","kind":"html","section":{"id":"1A","title":"Risk Factors"},"total_chars":68118,"offset":0,"next_offset":3000,
 "text":"Item 1A.  Risk Factors\nThe following summarizes factors that could have a material adverse effect on the Company’s business…"}

compare_companies {"tag":"Revenues","period":"CY2023","companies":["TSLA","F","GM"]}

{"concept":"us-gaap:Revenues","unit":"USD","period":"CY2023","companies_reporting":2679,"results":[
 {"rank":12,"cik":"0000037996","name":"Ford Motor Co","val":176191000000,"end":"2023-12-31"},
 {"rank":13,"cik":"0001467858","name":"GENERAL MOTORS COMPANY","val":171842000000,"end":"2023-12-31"},
 {"rank":23,"cik":"0001318605","name":"Tesla, Inc.","val":96773000000,"end":"2023-12-31"}],
 "source_url":"https://data.sec.gov/api/xbrl/frames/us-gaap/Revenues/USD/CY2023.json"}

Balance-sheet (instant) concepts need an I suffix, e.g. {"tag":"Assets","period":"CY2024Q4I"} (with metric the suffix is added for you: {"metric":"total_assets","period":"CY2024"} reads CY2024Q4I).

compare_companies by metric {"metric":"revenue","period":"CY2023","companies":["MSFT","AMZN","F"]}: many filers (MSFT, AMZN, AAPL) report revenue as RevenueFromContractWithCustomerExcludingAssessedTax, not Revenues, so metric tries up to 3 tags per company (Revenues, then RevenueFromContract…, then SalesRevenueNet for periods ≤ 2018) and reports the tag used:

{"metric":"revenue","period":"CY2023","period_basis":"calendar","results":[
 {"rank":1,"cik":"0001018724","name":"AMAZON.COM, INC.","val":574785000000,"start":"2023-01-01","end":"2023-12-31","tag":"us-gaap:RevenueFromContractWithCustomerExcludingAssessedTax"},
 {"rank":2,"cik":"0000789019","name":"MICROSOFT CORPORATION","val":211915000000,"start":"2022-07-01","end":"2023-06-30","tag":"us-gaap:RevenueFromContractWithCustomerExcludingAssessedTax","fiscal_period_differs":true},
 {"rank":3,"cik":"0000037996","name":"Ford Motor Co","val":176191000000,"start":"2023-01-01","end":"2023-12-31","tag":"us-gaap:Revenues"}],
 "tags_tried":["us-gaap:Revenues","us-gaap:RevenueFromContractWithCustomerExcludingAssessedTax"],"notes":["…"]}

Fiscal vs calendar periods. get_financials and get_xbrl_concept report fiscal periods as filed (fy/fp; Apple's FY2025 ended 2025-09-27). compare_companies uses SEC calendar frames: CY2023 holds, for each filer, the ~365-day period that best fits calendar 2023 (Microsoft's FY ending 2023-06-30). Rows whose period is more than 14 days off the calendar period get fiscal_period_differs: true; for a company's own fiscal years use get_financials. accn in a frame row is the latest filing that reported the value (often the next year's 10-K), not necessarily the original filing.

lookup_business_entity {"name":"Newmont Corporation","states":["CO"]}

{"results":[{"state":"CO","entity_id":"20021056790","name":"Newmont Corporation","status":"Good Standing",
  "type":"Foreign Profit Corporation (FPC)","formed":"2002-03-08","jurisdiction":"DE",
  "principal_address":"6900 East Layton Ave, Suite 700, Denver, CO, 80237, US",
  "registered_agent":{"name":"CORPORATION SERVICE COMPANY","address":"1900 W Littleton Blvd, Littleton, CO, 80120"},
  "details_url":"https://www.coloradosos.gov/biz/BusinessEntityDetail.do?masterFileId=20021056790",
  "source_url":"https://data.colorado.gov/resource/4ykn-tg5h.json?entityid=20021056790"}],
 "count":1,"offset":0,"has_more":false,"total":1,
 "by_state":{"CO":{"count":1,"offset":0,"has_more":false,"total":1,"query_url":"…"}}}

lookup_business_entity {"name":"Tiffany & Co.","states":["NY"],"include_total":true} (exact spelling variants rank first; TIFFANY AND COMPANY matches Tiffany & Co.)

{"results":[{"state":"NY","entity_id":"22220","name":"TIFFANY AND COMPANY","status":"Active", "…":"…"},
            {"state":"NY","entity_id":"5329856","name":"TIFFANY 1, INC.","status":"Active", "…":"…"}, "…"],
 "count":5,"offset":0,"has_more":true,"next_offset":5,"total":489,
 "by_state":{"NY":{"count":5,"offset":0,"has_more":true,"next_offset":5,"total":489,"active_only_dataset":true,"query_url":"…"}}}

Pagination is per state (limit 1–25 per state, offset 0–500; pass next_offset). total is exact with include_total: true (one extra count request per state) and is also filled in once the last page is reached. Oregon lists one row per associated name, so its pages are computed over the first 300 rows (a note says when that window is exhausted).

Other quick examples:

• search_company {"query":"berkshire"} → BERKSHIRE HATHAWAY INC, CIK 0001067983, tickers BRK-B, BRK-A
• search_company {"query":"Microsfot"} → MICROSOFT CORP (score 69, a typo match); {"query":"facebook"} → Meta Platforms, Inc. with matched_former_name: "Facebook Inc"
• list_filings {"company":"AAPL","forms":["10-K"],"date_to":"2010-12-31","limit":2} → the 2010 10-K and 10-K/A, read from older history pages
• get_xbrl_concept {"company":"TSLA","tag":"ResearchAndDevelopmentExpense","forms":["10-K"],"framed_only":true}
• lookup_business_entity {"entity_id":"0783036","states":["CT"]} → THE TRAVELERS COMPANIES, INC. (Active, foreign stock corp, MN)

---

Install

Use the hosted endpoint (recommended; no install), or run the server yourself from this repository's source. The server is also listed in the official MCP Registry as io.github.pgeneralpl/edgar-entity-mcp (remote endpoint).

The npm package edgar-entity-mcp (0.1.0) is deprecated and no longer maintained; do not install it.

Remote (Streamable HTTP), recommended

Hosted endpoint (free, no key needed): https://edgar-entity-mcp.vercel.app/mcp · health: https://edgar-entity-mcp.vercel.app/health. The hosted instance uses a shared cache, stays well below the SEC fair-access rate, and applies per-client quotas (see Hosted limits).

{ "mcpServers": { "edgar-entity": { "url": "https://edgar-entity-mcp.vercel.app/mcp" } } }

• Claude Code: claude mcp add --transport http edgar-entity https://edgar-entity-mcp.vercel.app/mcp
• Cursor: ~/.cursor/mcp.json (global) or .cursor/mcp.json (project).
• VS Code: .vscode/mcp.json using "servers" in place of "mcpServers".

For clients that only speak stdio: "command": "npx", "args": ["-y", "mcp-remote", "https://edgar-entity-mcp.vercel.app/mcp"] (mcp-remote is a third-party bridge, not part of this project).

Run locally from source (stdio)

git clone https://github.com/pgeneralpl/edgar-entity-mcp.git
cd edgar-entity-mcp
npm ci && npm run build
SEC_USER_AGENT="Your Name you@example.com" node dist/stdio.js --version

Then point your client at the built file (use the absolute path of your clone):

{
  "mcpServers": {
    "edgar-entity": {
      "command": "node",
      "args": ["/absolute/path/to/edgar-entity-mcp/dist/stdio.js"],
      "env": { "SEC_USER_AGENT": "Your Name or Company you@example.com" }
    }
  }
}

• Claude Desktop: ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows).
• Claude Code: claude mcp add edgar-entity -e SEC_USER_AGENT="Your Name you@example.com" -- node /absolute/path/to/edgar-entity-mcp/dist/stdio.js

Node.js version (local use): use a patched Node.js — 22.23.4+ (22.x) or 24.22.1+ (24.x, recommended), or 26.12.1+. These releases (2026-10-21) fix CVE-2026-111497, a Brotli decoder out-of-bounds write that a malicious server response decoded by fetch() could trigger, plus TLS hostname-verification bypasses. Node.js 20 is end-of-life and will not get the fix. Check with node -v; the server prints a warning on stderr when started on an unpatched Node.js. The hosted endpoint runs on Vercel's managed Node.js 24.x runtime, which Vercel patches itself. engines.node is 24.x (it pins the Vercel runtime), so npm ci prints an EBADENGINE notice on 22.x — that is expected and harmless on 22.23.4+.

Self-host the HTTP server

npm run build && PORT=3000 SEC_USER_AGENT="Acme you@acme.com" npm run start:http   # → http://127.0.0.1:3000/mcp

The node server binds 127.0.0.1 by default and only answers requests whose Host is localhost (DNS-rebinding protection) and whose Origin, if any, is local. To expose it, set HOST=0.0.0.0, ALLOWED_HOSTS=mcp.example.com, optionally ALLOWED_ORIGINS, and TRUST_PROXY=1 only when a reverse proxy sets X-Forwarded-For/X-Real-IP. All settings are listed under Environment variables.

Deploy to Vercel

The repo already contains api/mcp.ts and api/health.ts (Vercel Functions with a Web-standard handler built on mcp-handler) and vercel.json, which runs npm run build and rewrites /mcp to /api/mcp and /health to /api/health. It also sets X-Content-Type-Options: nosniff, X-Frame-Options: DENY and Referrer-Policy: no-referrer on every response, and a strict Content-Security-Policy (default-src 'none'; style-src 'unsafe-inline'; frame-ancestors 'none'; base-uri 'none'; form-action 'none') on the static HTML pages only (/, /privacy, /terms, /abuse), not on /mcp or /health. public/llms.txt (a plain-text summary for LLM tools and crawlers) is served at /llms.txt as text/plain; charset=utf-8. npm run smoke:remote -- https://<project>.vercel.app/mcp runs a live check against a deployment.

1. vercel link then vercel env add SEC_USER_AGENT (plus HEALTH_SECRET, IP_HASH_SALT, optionally SOCRATA_APP_TOKEN; full list in Production configuration).
2. Strongly recommended: add the Upstash Redis integration. The cache, the SEC/state rate budgets and the per-client quotas then become fleet-wide; without it they are per instance. Keep eviction off in the Upstash console and enable usage alerts: the cache bounds itself (see Redis memory budget).
3. vercel deploy --prod. Point clients at https://<project>.vercel.app/mcp.

---

Hosted limits

The hosted endpoint is a free beta with low limits. Anonymous clients get up to 60 units per day per IP (shared networks may get less) and 30 per minute, within shared daily budgets per network and for all anonymous use; most calls cost 1–3 units and a call answered from cache usually costs 1. Over-quota calls return a RATE_LIMITED error with retry_after_seconds. Running the server locally from source over stdio has no quota. Higher limits on the hosted endpoint may be requested by a person via the GitHub issue form (reviewed manually, may be declined; please do not file automatically).

Other limits on the HTTP endpoint: 64 KB request bodies, no JSON-RPC batches (one message per request), at most 20 Form 4 filings per insider call and 5 states / 25 results per state per entity lookup, filing documents up to 15 MB.

Environment variables and their defaults, unit costs per tool, quotas, Redis settings and the deployment configuration are documented for operators and self-hosters in docs/OPERATIONS.md.

Privacy and personal data

The hosted server's Privacy Policy (source), Beta terms (source) and Contact & Abuse (source) pages are served from public/. The only contact is patryk.general@mail.grokbot.com.

• Registered agents and service-of-process contacts are treated as individuals unless the name ends with a legal-form suffix (Inc, Corp, LLC, LLP, LP, Ltd, Company, "& Co", Bank, N.A., …) or is a known registered-agent service (CT Corporation, CSC, Cogency Global, …). "JOHN CHURCH", "JUDE LAW", "DAVID CO" and "JOHN SMITH PA" are individuals; ambiguous CO/PA/PC endings count as individual.
• Individual agents are returned as { "kind": "individual", "withheld": true }, and the entity's principal/mailing addresses (and NY location name) are withheld too (addresses_withheld: true), since for one-person businesses these are often a home address. The hosted endpoint always withholds them (include_agent_details is ignored there and the response carries a privacy note). The person/organization split is an automated classification; contact us to suppress any we miss. include_agent_details: true reveals them only in local stdio use, or on a self-hosted HTTP server whose operator opts in with ALLOW_PERSON_AGENT_DETAILS=1 (ignored on Vercel; see Environment variables). Organizational agents are always shown.
• Erasure/objection requests: add entity:<STATE>:<id> or agent:<name> with npx tsx scripts/suppress.ts add ... (Redis set, picked up within 10 minutes), SUPPRESSION_FILE, or src/states/suppression-list.ts. Entity ids are normalized (case, punctuation, leading zeros). A suppressed name is matched as whole words in agent names and addresses and in the entity name, NY location name and principal/mailing addresses; any hit removes every personal field of that record, and a hit in the entity name (also matched with spaces removed, e.g. "JANEDOE HOLDINGS LLC") replaces the name with [withheld]. If Redis is configured but the suppression list cannot be loaded on a cold instance, state lookups are refused (before any registry request) rather than served without it.
• Form 4 reporting-owner names are statutory public disclosures and are returned by get_insider_trades.

What the hosted server stores, and for how long

• Rate limiting keeps only integer counters in Redis, under identifiers hashed with a salt that rotates daily, expiring 25 h after the UTC day they count; per-minute limits are never written to Redis.
• Not stored anywhere in Redis: raw IPs, user agents, request paths, tool arguments, per-tool usage history. Shared cache entries hold public SEC and state data under hashed key names and expire after at most 24 h.
• Aggregate usage statistics (per-day counts per tool, outcome and error code, allowlisted client-software labels, an approximate unique-client count) are kept for 30 days after each UTC day; no per-client records. They are on by default on production and self-hosted HTTP servers with Redis (STATS_ENABLED=0 turns them off) and readable only through GET /stats with STATS_SECRET.
• Logs (errors, and optional per-call usage lines with a daily-rotating hash) go to Vercel runtime logs under Vercel's plan retention; tool arguments and raw IPs are never logged by this server.

The full Redis key list, TTLs and hashing scheme are in docs/OPERATIONS.md.

Security notes

• Filing text from get_filing_document is untrusted, filer-authored content. It is returned between <<<BEGIN UNTRUSTED SEC FILING TEXT id=<nonce>>>> / <<<END UNTRUSTED SEC FILING TEXT id=<nonce>>>> markers, where the nonce is random per response and repeated in untrusted_marker_id, so filer text cannot fake a closing marker. Zero-width, bidi control, Unicode tag characters (U+E0000–E007F) and variation selectors (U+FE00–FE0F, U+E0100–E01EF) are stripped. Other third-party text (entity names and addresses, Form 4 reporter names, remarks and footnotes, XBRL labels and descriptions) is cleaned the same way and listed in each response's untrusted_fields. Agents should treat all of it as data, never as instructions.
• Only https://www.sec.gov/Archives/edgar/data/<CIK>/<accession>/<file> URLs are accepted as document input; redirects are followed manually and re-checked against the host allowlist.
• Error messages returned to clients are generic; details go to server logs with a reference id.

SEC User-Agent and rate limits

SEC's fair-access policy caps clients at 10 requests/second and requires a declared User-Agent. SEC may block clients without one (HTTP 403 "Undeclared Automated Tool"). This server sends SEC_USER_AGENT on every SEC request, stays at 6 req/s by default (fleet-wide with Redis), retries 429/5xx with backoff, and caches responses for at most 24 h. Limiter and cache details: docs/OPERATIONS.md.

Data sources & licenses

The code is MIT-licensed. The server ships no data and fetches everything live. Full details are in DATA_SOURCES.md and LICENSES/.

Colorado disclaimer: The data made available here has been modified for use from its original source, which is the State of Colorado. THE STATE OF COLORADO MAKES NO REPRESENTATIONS OR WARRANTY AS TO THE COMPLETENESS, ACCURACY, TIMELINESS, OR CONTENT OF ANY DATA MADE AVAILABLE THROUGH THIS SITE. THE STATE OF COLORADO EXPRESSLY DISCLAIMS ALL WARRANTIES, WHETHER EXPRESS OR IMPLIED, INCLUDING ANY IMPLIED WARRANTIES OF MERCHANTABILITY, OR FITNESS FOR A PARTICULAR PURPOSE. The data is subject to change as modifications and updates are complete. It is understood that the information contained in the Web feed is being used at one's own risk.

Delaware, the most common state of incorporation, has no open bulk dataset, so it is not covered. CA and FL are on the roadmap (see list_supported_states). This server provides informational data only and is not investment, legal or credit advice. It is not a consumer reporting agency, and its output must not be used for FCRA-regulated decisions.

Architecture

src/
  core/      names (normalisation, bounded edit distance), config, cache (memory LRU | Upstash | tiered), rate limiter, fetch+retry, usage hooks, errors
  sec/       tickers (fuzzy, did-you-mean), formerNames (curated former names), submissions, documents (HTML→text, item extraction), financials, xbrl (concept/frames), insider (Form 4)
  states/    registry (per-state dataset config + normalizers), socrata (SoQL builder, spelling variants, ranking, pagination)
  tools.ts   zod schemas + tool handlers (transport-agnostic)
  server.ts  registers tools/prompt/resource on an McpServer (shared by both transports)
  stdio.ts   stdio entry point (node dist/stdio.js) → serveStdio()
  http/      handler.ts (mcp-handler + auth/quotas) · node-server.ts (local/self-host)
api/mcp.ts   Vercel Function

Built on the official MCP TypeScript SDK v2 (@modelcontextprotocol/server, the successor to the @modelcontextprotocol/sdk v1 package, and a requirement of mcp-handler 2.x). It serves the 2026-07-28 protocol and falls back automatically for 2025-era clients, over both stdio and HTTP.

Development

npm install
npm run check        # typecheck + eslint + vitest (offline unit tests)
npm run smoke:e2e    # build + live smoke over stdio (all tools, real SEC/state data) + HTTP + Vercel-function e2e
npm run validate:registry   # validate server.json against the MCP Registry schema
npx @modelcontextprotocol/inspector --cli node dist/stdio.js --method tools/list

Roadmap

• More states: FL (Sunbiz bulk files), CA (bizfile API, needs a key), WA/TX where open data allows; NY inactive entities (the "All Filings" dataset)
• Officers/directors (CT principals dataset; PA officer rows; DEF 14A)
• EDGAR full-text search (efts.sec.gov) and 8-K item-level event feed
• 13F holdings, 13D/G ownership, S-1/IPO tracking
• Webhooks/subscriptions for new filings and insider trades (MCP events)
• Segment and geographic revenue (XBRL dimensions via the Financial Statement datasets)
• MCPB bundle for one-click Claude Desktop install (a manifest.json is included and validated)

License

MIT for the code (see LICENSE). Use of the hosted server is subject to the Beta terms. Data remains subject to each source's terms (see DATA_SOURCES.md).