
FilingPulse MCP server
Which MCP servers are FilingPulse's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.
read 2026-10-21
- Registry nameio.filingpulse/filingpulseverified in the MCP registry
The registry name sits under filingpulse.io. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.
- Stateanswerschecked 2026-10-21
- Tools7
- Server calls itselffilingpulse
- Server version0.1.0
- Protocol version2025-06-18
On 2026-10-21 the server answered initialize and tools/list without a sign-in. First answer in 208 ms.
- Its tools do track S-1 IPO registration filings by SEC file number, but not receive signed webhooks when matching insider filings arrive.
Once connected
- Parameters are untyped or undescribed in 2 of 7 tools: check arguments before calling.
Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.
- INITE MCP score85 of 100answers 100 · does the job 50 · definitions 95 · context 100 · connects 100
- What an agent can do with it1 of 2 use cases
- Answered100% of days7 of 7 daily checks
- Median first answer229 ms
- Space in an agent's context≈ 1,611 tokensthe definitions of all its tools (7), which an agent carries on every turn
- Tool definitionsA · 95 of 100
- Typed results0 of 7 toolsdeclared outputSchema: results come typed, read once
- Parameters without a description: in 2 of 7
What an agent can do with it
- not sure · query insider trades by ticker through the REST API
- cannot · receive signed webhooks when matching insider filings arrive
- can do · track S-1 IPO registration filings by SEC file number
Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?
Worth a look
None of the five warning signs in these definitions.
A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →
get_insider_tradesList normalized SEC insider ownership filings (Form 4 transactions, plus Form 3 initial statements and Form 5 annual statements — 3/5 live-forward since 2026-09-23), newest first: non-derivative and derivative transaction legs, holdings…
get_insider_filingFetch one insider ownership filing (Form 3/4/5) by SEC accession number (e.g. 0001653558-26-000110), with all transaction legs, holdings, and footnotes.
get_corporate_eventsList SEC 8-K corporate events classified by official item code, newest first — e.g. 2.02 results of operations, 5.02 executive/director changes, 1.01 material agreements, 7.01 Reg FD. Filter by item code, issuer ticker or CIK, or…
get_ipo_registrationsList S-1/F-1 registration lifecycle events, newest first: registration statements, amendments, notices of effectiveness, and priced prospectuses (424B1/424B4), threaded across stages by SEC file number (e.g. 333-297472). Issuer objects…
get_registration_eventFetch one S-1/IPO registration lifecycle event by SEC accession number.
get_dataset_statusRow counts, latest ingest timestamps, and earliest covered filing date for each dataset (Form 4, 8-K, registrations). Call this to learn what date range a query can be answered from.
get_schemaThe frozen schema-v1 contract for FilingPulse objects: field-by-field documentation for form4 / event_8k / registration_event, the list envelope, design rules (strings-as-filed, null-never-missing, additive-only), and the Form 4…
How to connect
Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:
{
"mcpServers": {
"filingpulse": {
"type": "http",
"url": "https://mcp.filingpulse.io/mcp"
}
}
}Add it
Claude Code, in a terminal
claude mcp add --transport http filingpulse https://mcp.filingpulse.io/mcpclaude.ai, ChatGPT and other clients: add https://mcp.filingpulse.io/mcp as a custom connector in the settings.
Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.
Cookies
Before we count this visit
Analytics and ad measurement tell us which pages and which of our ads do their job: Google Analytics and Google Ads, the Meta pixel, Yandex Metrica, and one first-party id of our own. Nothing is stored until you answer, and declining changes nothing about the site.