io.filingpulse/filingpulse
REMOTE · MCP.FILINGPULSE.IO · SCANNED SEP 23
Hosted SEC EDGAR filings: Form 4 insider trades, 8-K events, S-1/IPO registrations. Read-only.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability50
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- Instruction-quality not yet verified: the AI judgement didn't run.Unverified
- Context-footprint check failed: tool/resource definitions use about 1370 tokens (~152/item across 9 items; 7 tools + 2 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage97
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 92% of tool parameters carry a description.Partial
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- Manipulation not yet verified: only 8 of 9 captured unit(s) of tool text has been judged so far, so we will not certify text no model has read as clean.Unverified
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
How do I install the io.filingpulse/filingpulse MCP server?
io.filingpulse/filingpulse is a hosted endpoint at https://mcp.filingpulse.io/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.filingpulse.io
claude mcp add --transport http io-filingpulse-filingpulse 'https://mcp.filingpulse.io/mcp'
{
"mcpServers": {
"io-filingpulse-filingpulse": {
"url": "https://mcp.filingpulse.io/mcp"
}
}
} {
"servers": {
"io-filingpulse-filingpulse": {
"type": "http",
"url": "https://mcp.filingpulse.io/mcp"
}
}
} [mcp_servers.io-filingpulse-filingpulse] url = "https://mcp.filingpulse.io/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"io-filingpulse-filingpulse": {
"type": "remote",
"url": "https://mcp.filingpulse.io/mcp",
"enabled": true
}
}
} openclaw mcp add io-filingpulse-filingpulse --url 'https://mcp.filingpulse.io/mcp' --transport streamable-http
mcp_servers:
io-filingpulse-filingpulse:
url: "https://mcp.filingpulse.io/mcp" {
"McpServers": {
"io-filingpulse-filingpulse": {
"Transport": "http",
"Url": "https://mcp.filingpulse.io/mcp"
}
}
} assistant mcp add io-filingpulse-filingpulse -t streamable-http -u 'https://mcp.filingpulse.io/mcp'
{
"mcpServers": {
"io-filingpulse-filingpulse": {
"type": "http",
"url": "https://mcp.filingpulse.io/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 23 Sept 26 −7
- Judged manipulation: pass → unverified ▼ security
- Stability: 0.97 → pass security
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: good → unverified ▼ functional
- New prompt “events_digest” functional
- New prompt “insider_activity” functional
- New prompt “ipo_pipeline” functional
- 22 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Sept 26 0
- Tool “get_insider_trades” rewrote its description, which is the text the model reads security
- Schema quality: excellent → good functional
- “get_insider_trades” added an optional parameter “owner_cik” cosmetic
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 0
- Tool “get_corporate_events” rewrote its description, which is the text the model reads security
- “get_corporate_events” added an optional parameter “ticker” cosmetic
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 23 Sept 2026 · Probed https://mcp.filingpulse.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.filingpulse.io | CN=YE2,O=Let's Encrypt,C=US | 10 Aug 2026 | 8 Nov 2026 | ECDSA 256 | ECDSA-SHA384 | 63efd539b356214e8a04c5d21d4eeff383f |
| SANs: mcp.filingpulse.io | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.filingpulse.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 57355 | 8 | Verified |
| filingpulse.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.filingpulse.io/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.filingpulse.io/mcp | HTTPS enforced | 308 | https://mcp.filingpulse.io/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_corporate_events 8-K corporate events ~275
List 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 since-date. Returns a {data, total, limit, offset} envelope.
| Name | Type | Req | Description |
|---|---|---|---|
| cik | string | – | SEC CIK number, digits only (leading zeros optional). |
| item | string | – | Official 8-K item code, e.g. 2.02 or 5.02. |
| limit | integer | – | Rows to return (max 25 on this endpoint). |
| offset | integer | – | Rows to skip — page through 'total' with limit+offset. |
| since | string | – | Only filings filed on/after this date (YYYY-MM-DD). |
| ticker | string | – | Issuer ticker symbol, e.g. KMI. 8-K headers carry no ticker, so it is resolved to a CIK via this dataset's Form 4 filings — an issuer with no Form 4 yet needs 'cik' instead. |
| until | string | – | Only filings filed on/before this date (YYYY-MM-DD) — with since, a fixed reproducible window. |
No output schema declared.
No examples provided.
get_dataset_status Dataset coverage and freshness ~49
Row 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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_insider_filing One Form 4 filing ~74
Fetch one Form 4 insider-transaction filing by SEC accession number (e.g. 0001653558-26-000110), with all transaction legs, holdings, and footnotes.
| Name | Type | Req | Description |
|---|---|---|---|
| accession | string | yes | SEC accession number, e.g. 0001653558-26-000110. |
No output schema declared.
No examples provided.
get_insider_trades Form 4 insider transactions ~338
List normalized SEC Form 4 insider-transaction filings, newest first: non-derivative and derivative transaction legs, post-transaction holdings, owner roles (director/officer/10% owner), footnotes, and amendment (4/A) links. Numeric values are strings exactly as filed; every object carries 'accession' and 'filed_date'. Filter by issuer ticker, issuer CIK, reporting-owner CIK (owner_cik — one insider's filings across every issuer), form_type, or since-date. Returns a {data, total, limit, offset} envelope for paging. Hosted and already normalized — no EDGAR crawling, parsing, or local install needed.
| Name | Type | Req | Description |
|---|---|---|---|
| cik | string | – | SEC CIK number, digits only (leading zeros optional). |
| form_type | string | – | 4 = original filing, 4/A = amendment. |
| limit | integer | – | Rows to return (max 25 on this endpoint). |
| offset | integer | – | Rows to skip — page through 'total' with limit+offset. |
| owner_cik | string | – | Reporting owner (insider) CIK, digits only — one person or entity's filings across every issuer. Owner CIKs appear in each filing's reporting_owners[]. |
| since | string | – | Only filings filed on/after this date (YYYY-MM-DD). |
| ticker | string | – | Issuer ticker symbol as filed, e.g. KMI. Case-insensitive exact match. |
| until | string | – | Only filings filed on/before this date (YYYY-MM-DD) — with since, a fixed reproducible window. |
No output schema declared.
No examples provided.
get_ipo_registrations S-1/IPO registration lifecycle ~255
List 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 include SIC code, state of incorporation, and former names. Coverage is live-forward since 2026-08-01. Returns a {data, total, limit, offset} envelope.
| Name | Type | Req | Description |
|---|---|---|---|
| cik | string | – | SEC CIK number, digits only (leading zeros optional). |
| file_number | string | – | SEC file number, e.g. 333-297472 — follows one offering across stages. |
| form_type | string | – | – |
| limit | integer | – | Rows to return (max 25 on this endpoint). |
| offset | integer | – | Rows to skip — page through 'total' with limit+offset. |
| since | string | – | Only filings filed on/after this date (YYYY-MM-DD). |
| stage | string | – | Lifecycle stage to filter on. |
| until | string | – | Only filings filed on/before this date (YYYY-MM-DD) — with since, a fixed reproducible window. |
No output schema declared.
No examples provided.
get_registration_event One registration event ~34
Fetch one S-1/IPO registration lifecycle event by SEC accession number.
| Name | Type | Req | Description |
|---|---|---|---|
| accession | string | yes | SEC accession number. |
No output schema declared.
No examples provided.
get_schema Normalized schema reference ~72
The 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 transaction-code table.
| Name | Type | Req | Description |
|---|---|---|---|
| section | string | – | – |
No output schema declared.
No examples provided.
What is the io.filingpulse/filingpulse MCP server?
io.filingpulse/filingpulse is an MCP server listed in the public MCP registry as io.filingpulse/filingpulse. Hosted SEC EDGAR filings: Form 4 insider trades, 8-K events, S-1/IPO registrations. Read-only. This page covers its hosted endpoint (https://mcp.filingpulse.io/mcp).
Is the io.filingpulse/filingpulse MCP server safe to use?
io.filingpulse/filingpulse scores 77 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.filingpulse/filingpulse MCP server expose?
io.filingpulse/filingpulse exposes 7 tools: get_insider_trades, get_insider_filing, get_corporate_events, get_ipo_registrations, get_registration_event, and 2 more. Their descriptions and schemas cost roughly 1,097 tokens of context every time the server is loaded.
Does the io.filingpulse/filingpulse MCP server require authentication?
No. We connected to io.filingpulse/filingpulse without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.filingpulse/filingpulse MCP server still maintained?
io.filingpulse/filingpulse is still listed as active in the MCP registry. We last reached this channel on 23 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.