FilingPulse runs a hosted Model Context Protocol server, so AI agents — Claude, ChatGPT, Cursor, anything that speaks MCP — can query normalized SEC EDGAR filings directly:
https://mcp.filingpulse.io/mcpStreamable HTTP, read-only, no key and no install required. The 32-odd EDGAR MCP servers on the registries run locally against raw EDGAR; this one is hosted and serves the same already-normalized schema-v1 objects as our REST API — full transaction legs, footnotes, owner roles, item codes, file-number threading — from a pipeline that ingests continuously. FilingPulse is data infrastructure: tools report what was filed with the SEC, never signals or advice.
claude mcp add --transport http filingpulse https://mcp.filingpulse.io/mcpSettings → Connectors → Add custom connector → paste
https://mcp.filingpulse.io/mcp. No authentication.
Settings → Connectors → Advanced → enable Developer mode, then add a connector with the same URL and no authentication. Requires a plan with Developer Mode access.
// .cursor/mcp.json
{"mcpServers": {"filingpulse": {"url": "https://mcp.filingpulse.io/mcp"}}}// .vscode/mcp.json
{"servers": {"filingpulse": {"type": "http", "url": "https://mcp.filingpulse.io/mcp"}}}Seven read-only tools over the same tables the REST API serves. List tools return the
standard {"data": […], "total": n, "limit": n, "offset": n} envelope, newest
filed first; numeric values are strings exactly as filed (schema v1).
| Tool | What it returns |
|---|---|
get_insider_trades | Form 4 insider transactions — filter by ticker, CIK, form type (4 / 4/A), or since-date. |
get_insider_filing | One Form 4 by accession number, with all transaction legs, holdings, and footnotes. |
get_corporate_events | 8-K events classified by official item code (2.02 results, 5.02 leadership changes, …). |
get_ipo_registrations | S-1/F-1 registration lifecycle events, threaded across stages by SEC file number. |
get_registration_event | One registration lifecycle event by accession number. |
get_dataset_status | Row counts, freshness, and the covered date range per dataset. |
get_schema | The frozen schema-v1 contract, section by section, including the transaction-code table. |
Three ready-made task prompts (MCP prompts/list — most clients surface
them as slash commands or prompt pickers). Each renders a concrete task over the tools
with the date window already computed server-side:
| Prompt | Arguments | What it does |
|---|---|---|
insider_activity | ticker, days (90) | Summarize Form 4 insider transactions for one issuer: buys vs sells, distinct insiders, largest priced transactions, amendments. |
events_digest | ticker, days (30) | Digest recent 8-K filings grouped by official item code, with accession numbers and links to the original filings. |
ipo_pipeline | days (14) | Report new S-1/F-1 registration statements and freshly priced prospectuses, threaded per offering by SEC file number. |
Every prompt reports what was filed with the SEC — none produce investment advice,
signals, or recommendations. The full API docs are also served in-band as MCP resources
(resources/list: llms.txt + llms-full.txt).
The anonymous MCP endpoint is a discovery tier: 20 tool calls per minute per
IP, at most 25 rows per list call. That is deliberately enough to
explore the data and answer real questions in a chat, and deliberately not enough to run a
sync pipeline. For programmatic access — bigger pages, monthly quotas, incremental
since= sync, HMAC-signed webhooks — get a free API
key (no card) and use the REST API. Coverage note: Form 4 and 8-K data extend backward
continuously as our backfill runs; registration events are tracked live since Aug 1, 2026
with no backfill. get_dataset_status reports the exact current window.
The endpoint speaks standard MCP JSON-RPC over streamable HTTP (protocol
2025-06-18; stateless — no session ids). To see the tool list without an MCP
client:
curl -s https://mcp.filingpulse.io/mcp \
-H "Content-Type: application/json" \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'