# io.filingpulse/filingpulse (remote · mcp.filingpulse.io)

Hosted SEC EDGAR filings: Form 4 insider trades, 8-K events, S-1/IPO registrations. Read-only.

- Trust score: 77/100 (medium)
- Change this week: −4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-23

## Components

- remote · `mcp.filingpulse.io`: 77/100 (this document), [markdown](https://verifymcp.io/servers/io-filingpulse-filingpulse/mcp.md), [page](https://verifymcp.io/servers/io-filingpulse-filingpulse/mcp)

## Channel facts

- Endpoint: `https://mcp.filingpulse.io/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-23.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 50/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - Instruction-quality not yet verified: the AI judgement didn't run.
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 100/100
  - No destabilizing schema changes in the last 30 days.
- **Tool Coverage**: 97/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 92% of tool parameters carry a description.
- **Tool Safety**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - 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.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add --transport http io-filingpulse-filingpulse 'https://mcp.filingpulse.io/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "io-filingpulse-filingpulse": {
      "url": "https://mcp.filingpulse.io/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "io-filingpulse-filingpulse": {
      "type": "http",
      "url": "https://mcp.filingpulse.io/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.io-filingpulse-filingpulse]
url = "https://mcp.filingpulse.io/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-filingpulse-filingpulse": {
      "type": "remote",
      "url": "https://mcp.filingpulse.io/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add io-filingpulse-filingpulse --url 'https://mcp.filingpulse.io/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  io-filingpulse-filingpulse:
    url: "https://mcp.filingpulse.io/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "io-filingpulse-filingpulse": {
      "Transport": "http",
      "Url": "https://mcp.filingpulse.io/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add io-filingpulse-filingpulse -t streamable-http -u 'https://mcp.filingpulse.io/mcp'
```

### Other

```json
{
  "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.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-23 (score 77, −7)

- [security regression] Judged manipulation: pass → unverified
- [security] Stability: 0.97 → pass
- [security] The server rewrote its instructions, which are the text every model session reads
- [functional regression] Schema quality: good → unverified
- [functional] New prompt “events_digest”
- [functional] New prompt “insider_activity”
- [functional] New prompt “ipo_pipeline”

### 2026-09-22 (score 84, +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.

### 2026-09-20 (score 83, 0)

- [security] Tool “get_insider_trades” rewrote its description, which is the text the model reads
- [functional] Schema quality: excellent → good
- [cosmetic] “get_insider_trades” added an optional parameter “owner_cik”

### 2026-09-19 (score 83, +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.

### 2026-09-17 (score 82, +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.

### 2026-09-15 (score 81, +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.

### 2026-09-13 (score 80, +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.

### 2026-09-11 (score 79, 0)

- [security] Tool “get_corporate_events” rewrote its description, which is the text the model reads
- [cosmetic] “get_corporate_events” added an optional parameter “ticker”

## MCP tools (7)

### `get_insider_trades` (~338 tokens)

Form 4 insider transactions

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.

Input parameters:

- `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.

### `get_insider_filing` (~74 tokens)

One Form 4 filing

Fetch one Form 4 insider-transaction filing by SEC accession number (e.g. 0001653558-26-000110), with all transaction legs, holdings, and footnotes.

Input parameters:

- `accession` (string, required): SEC accession number, e.g. 0001653558-26-000110.

### `get_corporate_events` (~275 tokens)

8-K corporate events

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.

Input parameters:

- `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.

### `get_ipo_registrations` (~255 tokens)

S-1/IPO registration lifecycle

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.

Input parameters:

- `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.

### `get_registration_event` (~34 tokens)

One registration event

Fetch one S-1/IPO registration lifecycle event by SEC accession number.

Input parameters:

- `accession` (string, required): SEC accession number.

### `get_dataset_status` (~49 tokens)

Dataset coverage and freshness

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.

### `get_schema` (~72 tokens)

Normalized schema reference

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.

Input parameters:

- `section` (string)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/io-filingpulse-filingpulse/mcp#diagnostics

## Score history

- 2026-09-23: 77
- 2026-09-22: 84
- 2026-09-21: 83
- 2026-09-20: 83
- 2026-09-19: 83
- 2026-09-18: 82
- 2026-09-17: 82
- 2026-09-16: 81
- 2026-09-15: 81
- 2026-09-14: 80
- 2026-09-13: 80
- 2026-09-12: 79
- 2026-09-11: 79
- 2026-09-10: 79
- 2026-09-09: 78
- 2026-09-08: 78
- 2026-09-07: 77
- 2026-09-06: 77
- 2026-09-05: 76
- 2026-09-04: 76
- 2026-09-03: 75
- 2026-09-02: 75
- 2026-09-01: 74
- 2026-08-31: 74
- 2026-08-30: 74
- 2026-08-29: 73
- 2026-08-28: 73
- 2026-08-27: 72
- 2026-08-26: 72
- 2026-08-25: 69

## Common questions

### 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.

## Links

- Remote endpoint: https://mcp.filingpulse.io/mcp
- Website: https://filingpulse.io/mcp.html
- Changelog RSS feed: https://verifymcp.io/servers/io-filingpulse-filingpulse/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-filingpulse-filingpulse/mcp.json
- HTML version of this page: https://verifymcp.io/servers/io-filingpulse-filingpulse/mcp