Signal Nodus SEC Filings

What Signal Nodus SEC Filings MCP server does

Signal Nodus SEC Filings MCP server exposes SEC filing analysis through an HTTP MCP endpoint at https://mcp.signalnodus.ai/. Its main use is working with US 10-K, 10-Q, and 8-K filings without requiring an agent to parse long, inconsistently formatted EDGAR documents itself.

The service can identify a company from a ticker or name, list recent filings, retrieve individual filing sections as cleaned text, and compare one item across two filings at sentence level. It can also check a numeric statement against as-filed XBRL and turn 8-K item codes into filing events. The data is limited to US SEC filings; it does not provide market prices, news, forecasts, sentiment scores, or coverage of non-US-listed companies.

How it works

Connect an MCP client to the hosted HTTP URL. The lookup_company tool is free and can confirm that the connection works before any paid request is made. Other tools charge per call, with prices declared in their tool descriptions so an agent can inspect the cost before calling them.

Responses derived from filings include the accession number, filing date, source URL, and parser version. Calls pinned to an accession number remain tied to that specific filing, including an amendment. Unpinned calls warn when a later amendment is available. Returned filing text also includes provenance guidance identifying issuer text as data rather than instructions.

The Signal Nodus SEC Filings MCP server sanitizes returned text by removing control characters, zero-width characters, bidirectional overrides, and Unicode tag characters. Paying customers can retrieve their own 30-day usage audit log, including the accession number associated with each call.

Setup and configuration

The hosted connection requires only this MCP configuration:

{
  "mcpServers": {
    "signalnodus": {
      "type": "http",
      "url": "https://mcp.signalnodus.ai/"
    }
  }
}

Paid access is available through a free trial key, prepaid API keys, or per-request payment over the service's HTTP API. A prepaid key is sent as Authorization: Bearer <key> on the MCP endpoint. MCP calls return HTTP 200 with a structured payment refusal when payment is needed, allowing clients that do not handle HTTP 402 responses to receive the payable URL.

The repository also documents self-hosting as a Cloudflare Worker backed by D1. That deployment uses Wrangler and can be configured with Stripe, x402 facilitator, dashboard, Turnstile, and deposit-address settings. Payment credentials are optional for a degraded deployment; without the relevant Stripe or CDP credentials, machine-payment routes return 503 machine_payments_unavailable while prepaid-key MCP access remains available.

Tools and capabilities

• lookup_company: resolve a ticker or company name to its CIK, exchange, SIC, and fiscal year end.
• recent_filings: list company filings with accession numbers and dates.
• latest_filings: read the live, market-wide filing feed, including 8-K item codes.
• filing_section: extract a requested 10-K or 10-Q item such as 1A, 7, or 7A.
• compare_filings: produce a sentence-level comparison for one item across two filings.
• verify_financial_claim: check a numeric claim against as-filed XBRL.
• filing_events: decode 8-K filings into events by item code.

Limitations and notes

Figures are as filed and are not adjusted or restated. Pricing is metered per call, and tools outside the SEC workflow are described as experimental in the broader catalog. The project publishes evaluation results for extraction and diffing against a public set of real filings, including amended and difficult layouts. Reports of incorrect parsing should include the relevant accession number.