Claude-style MCP workflow

SEC Filing MCP Server for Claude-Style Workflows

Use SEC Event Intelligence as a remote MCP server in Claude-style client workflows that support Streamable HTTP directly or through a gateway. The public setup tools let a buyer confirm connectivity and pricing links before adding production credentials.

Claude-style MCP workflows Streamable HTTP-capable client or gateway No-key tool-call checks Read-only SEC filing data Buyer-controlled API key

Run no-key tool calls Request hosted MCP access Subscribe on RapidAPI Open browser demo Download MCP config Remote client setup

Remote MCP setup

{
  "remoteServer": "https://api.data-apis.com/mcp",
  "transport": "streamable-http",
  "publicSetupTools": [
    "sec_demo_latest_filings",
    "sec_subscription_info"
  ],
  "productionTools": [
    "sec_watchlist_changes",
    "sec_company_search",
    "sec_filing_summary"
  ],
  "auth": "x-api-key or Authorization: Bearer for production tools",
  "clientConfig": "https://api.data-apis.com/downloads/sec-event-intelligence-mcp-client-config.json"
}

First no-key MCP checks

Confirm the remote server before sending credentials. The demo call returns a small public SEC filing sample, and the subscription-info call returns pricing, checkout, documentation, and hosted MCP access links.

Open tool-call quickstart Download demo tool call Download subscription-info call Download curl runner

initializeConfirm protocol metadata and tool capability.
tools/listConfirm SEC filing tools are visible before production auth.
sec_demo_latest_filingsRun a no-key public sample response through tools/call.
sec_subscription_infoReturn pricing, REST checkout, hosted MCP access, and configuration links.

Client setup path

Use the hosted MCP endpoint in a Streamable HTTP-capable client or gateway. Production SEC data tools are read-only and require a buyer-controlled API key in request headers.

Client pathRegister the remote MCP URL through a Streamable HTTP-capable client or gateway.
Credential boundaryKeep production API keys in the client or gateway secret store, not in prompts.
First checksUse sec_demo_latest_filings and sec_subscription_info to verify the workflow without credentials.

When this MCP server fits

The server is designed for filing-monitoring workflows that need normalized public SEC EDGAR metadata without operating a separate ingestion pipeline.

FitClaude-style research workflows that need SEC filing context
FitGateway setups where credentials should stay under buyer control
FitEvaluations that need a public demo before paid production calls

Production SEC filing tools

After setup checks, authenticated MCP tool calls use the same SEC Event Intelligence data layer as the REST API. Buyers can choose hosted MCP direct access for client tool calls or RapidAPI for REST snippets and marketplace billing.

sec_watchlist_changesPoll grouped ticker watchlists for newly observed filings.
sec_company_searchResolve public companies by ticker, CIK, or company name.
sec_company_filingsFetch issuer filing history and source filing links.
sec_filing_summaryRetrieve one normalized filing record by accession number.
sec_insider_tradesReview public Forms 3, 4, and 5 metadata by ticker.

Data infrastructure only. MCP tools expose public SEC filing metadata only, require buyer-controlled API keys for production data calls, and do not provide trading, rating, recommendation, or personalized financial guidance.