← Registry

Data Collection

filingpulse.io

Provides access to SEC corporate filings including insider trades, corporate events, and IPO registrations.

1 endpoint7 known toolsFirst detected August 24, 2026Last detected August 24, 2026

ENDPOINT 1

https://mcp.filingpulse.io/mcp

No auth detected

MCP server metadata

Name
filingpulse
Version
0.1.0
Capabilities
tools
Server instructions

FilingPulse serves normalized SEC EDGAR filings as one stable JSON schema: Form 4 insider transactions, 8-K corporate events classified by item code, and S-1/IPO registration lifecycle events threaded by SEC file number. All tools are read-only. This anonymous endpoint is rate-limited per IP and caps list responses at 25 rows; for programmatic access, higher limits, incremental sync, and HMAC-signed webhooks, get a free API key (no card) at https://filingpulse.io/signup.html and use the REST API at https://api.filingpulse.io (reference: https://filingpulse.io/docs.html). FilingPulse is data infrastructure: it reports what was filed with the SEC and provides no investment advice, signals, or recommendations.

Known tools 7

get_insider_trades

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.

Potential side effects
get_insider_filing

Fetch one Form 4 insider-transaction filing by SEC accession number (e.

Inferred read-only
get_corporate_events

List SEC 8-K corporate events classified by official item code, newest first — e.

Inferred read-only
get_ipo_registrations

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.

Inferred read-only
get_registration_event

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

Inferred read-only
get_dataset_status

Row counts, latest ingest timestamps, and earliest covered filing date for each dataset (Form 4, 8-K, registrations).

Inferred read-only
get_schema

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.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.filingpulse]
url = "https://mcp.filingpulse.io/mcp"
enabled = true
Claude Code

.mcp.json

{
  "mcpServers": {
    "filingpulse": {
      "type": "http",
      "url": "https://mcp.filingpulse.io/mcp"
    }
  }
}
Claude Desktop

Settings → Connectors → Add custom connector

Name: filingpulse
Remote MCP URL: https://mcp.filingpulse.io/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "filingpulse": {
      "url": "https://mcp.filingpulse.io/mcp"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code
{
  "servers": {
    "filingpulse": {
      "type": "http",
      "url": "https://mcp.filingpulse.io/mcp"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "filingpulse",
  "transport": "streamable-http",
  "url": "https://mcp.filingpulse.io/mcp"
}
MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.