SE SEC Event Intelligence

MCP server

SEC Filing MCP Server

A hosted Model Context Protocol API endpoint for the live SEC Event Intelligence API. Run two public setup tools first, then add an API key for production filing watchlists, company lookup, and filing summaries in Claude-style, Cursor, VS Code, and other Streamable HTTP MCP client workflows.

MCP API endpoint Remote Streamable HTTP Claude-style MCP workflows Cursor and VS Code setup Public demo tool call Subscription info tool Evaluation workflow Prompt request payloads Official registry listing
Subscribe on RapidAPI Run browser demo Tool-call quickstart Evaluation runner Access routes Security profile Python first-call runner Evaluation workflow Curl runner Demo tool call Subscription info call
Streamable HTTP endpoint 
{
  "name": "sec-event-intelligence-mcp",
  "transport": "streamable-http",
  "remoteServer": "https://api.data-apis.com/mcp",
  "publicSetupTools": [
    "sec_demo_latest_filings",
    "sec_subscription_info"
  ],
  "productionToolsRequire": "x-api-key or Authorization: Bearer",
  "productionTools": [
    "sec_watchlist_changes",
    "sec_company_search",
    "sec_filing_summary"
  ],
  "recommendedSetup": [
    "Run initialize and tools/list on the remote MCP URL.",
    "Call sec_demo_latest_filings without a key to verify connectivity.",
    "Call sec_subscription_info for REST checkout and hosted MCP direct-access links.",
    "Add a Data APIs key as x-api-key or Authorization: Bearer before using hosted MCP production data tools."
  ],
  "clientWorkflows": [
    "Claude-style MCP workflows through a Streamable HTTP-capable client or gateway.",
    "Cursor and VS Code MCP setup with the downloadable client config.",
    "Terminal evaluation with the curl runner before sending credentials."
  ],
  "clientConfig": "https://api.data-apis.com/downloads/sec-event-intelligence-mcp-client-config.json",
  "registry": "com.data-apis.api/sec-event-intelligence"
}

No-key MCP tool-call quick check

Run these two public tools/call requests before sending credentials. The first verifies live sample data, and the second returns RapidAPI REST checkout, hosted MCP access, pricing, and client configuration links.

Run browser demo Open quickstart Open evaluation runner Download Python runner Download curl runner Download evaluation workflow Demo call JSON Subscription call JSON
Public tools/call checks 
curl -sS https://api.data-apis.com/mcp \
  -H "Content-Type: application/json" \
  --data '{"jsonrpc":"2.0","id":"demo-latest-filings","method":"tools/call","params":{"name":"sec_demo_latest_filings","arguments":{"limit":3}}}'

curl -sS https://api.data-apis.com/mcp \
  -H "Content-Type: application/json" \
  --data '{"jsonrpc":"2.0","id":"subscription-info","method":"tools/call","params":{"name":"sec_subscription_info","arguments":{}}}'

Recommended MCP setup path

Use the public setup tools to confirm the remote endpoint before sending an API key. This keeps the first integration test small and gives buyers the exact checkout and configuration links from inside their MCP client.

What this MCP server does

This remote MCP server exposes SEC filing data tools through JSON-RPC tools/list and tools/call. It gives MCP-capable clients a small no-key demo first, then routes production SEC filing workflows to RapidAPI REST access or hosted MCP direct access with a buyer-controlled API key.

Claude, Cursor, and VS Code client workflows

Use this as a remote MCP server for client environments that support Streamable HTTP directly or through a gateway. The same no-key setup calls work for Claude-style MCP workflows, Cursor projects, VS Code Copilot MCP configuration, and terminal verification before production credentials.

Download VS Code MCP config Download generic MCP config Download curl runner MCP server setup Claude-style setup Cursor setup Remote MCP client setup

MCP access routes

RapidAPI is the marketplace checkout path for REST endpoint usage. Hosted MCP production tool calls use the remote MCP URL directly and need a Data APIs key for x-api-key or Authorization: Bearer. The public setup tools stay open so buyers can verify the server before choosing an access route.

Remote MCP trust boundary

The public MCP methods are limited to discovery, setup prompts, demo data, and access handoff. Production data tools are read-only, require a buyer-controlled API key, and do not expose OAuth dynamic client registration.

Available MCP tools

The endpoint supports initialize, tools/list, and tools/call. Tool calls use the same paid SEC data layer as the REST API, with public demo and subscription-info tools available for setup checks.

Public demo tool call

Use this JSON-RPC request to confirm remote MCP connectivity without an API key. The response is intentionally limited and includes subscription links for full data access.

POST /mcp tools/call 
{
  "jsonrpc": "2.0",
  "id": "demo-latest-filings",
  "method": "tools/call",
  "params": {
    "name": "sec_demo_latest_filings",
    "arguments": {
      "limit": 3
    }
  }
}

Public subscription-info tool call

Use this JSON-RPC request to return pricing, checkout, documentation, and API-key setup links from the MCP endpoint without an API key.

POST /mcp tools/call 
{
  "jsonrpc": "2.0",
  "id": "subscription-info",
  "method": "tools/call",
  "params": {
    "name": "sec_subscription_info",
    "arguments": {}
  }
}

Connect

MCP discovery methods, sec_demo_latest_filings, and sec_subscription_info are public. Production hosted MCP data-returning tool calls require a Data APIs key sent as x-api-key or Authorization: Bearer.

Directory submission

Use these stable public fields when submitting the remote MCP server to third-party MCP directories or API catalogs.

Data infrastructure only. MCP tools expose public SEC filing metadata only, require buyer-controlled API keys for data calls, and do not perform trade actions, ratings, recommendations, or personalized financial guidance.