Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, email [email protected] and we’ll put it right.

io.github.jethrokirk-sudo/filingapi

REMOTE · MCP.FILINGAPI.DEV · SCANNED AUG 3

SEC filings, earnings transcripts, guidance signals & macro calendar for S&P 500. 11 MCP tools.

+5 this week 63 Trust /100
Trust breakdown (6 categories)

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. How we score →

Endpoint Security57
Transport & Reachability100
Schema Quality & AI Usability71
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 882 tokens (~88/item across 10 items; 10 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
  • Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

remote · mcp.filingapi.dev

# add to Claude Code
claude mcp add --transport http jethrokirk-sudo-filingapi https://mcp.filingapi.dev/mcp
# ~/.codex/config.toml
[mcp_servers.jethrokirk-sudo-filingapi]
url = "https://mcp.filingapi.dev/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "jethrokirk-sudo-filingapi": {
      "type": "remote",
      "url": "https://mcp.filingapi.dev/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add jethrokirk-sudo-filingapi --url https://mcp.filingapi.dev/mcp --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  jethrokirk-sudo-filingapi:
    url: "https://mcp.filingapi.dev/mcp"
// mcp.json
{
  "mcpServers": {
    "jethrokirk-sudo-filingapi": {
      "type": "http",
      "url": "https://mcp.filingapi.dev/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 3 Aug 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

  • 1 Aug 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

  • 31 Jul 26 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 30 Jul 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

  • 29 Jul 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

  • 27 Jul 26 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 26 Jul 26 57

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 3 Aug 2026 · Probed https://mcp.filingapi.dev/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=mcp.filingapi.dev CN=YE2,O=Let's Encrypt,C=US 30 Jun 2026 28 Sept 2026 ECDSA 256 ECDSA-SHA384 52ddf3a2d58b0636cbd74cadc135cbdf152
SANs: mcp.filingapi.dev
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd
DNSSEC insecure

Validation of mcp.filingapi.dev. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
dev. present 60074 8 Verified
filingapi.dev. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.filingapi.dev/mcp Verified 200
http (plaintext) http://mcp.filingapi.dev/mcp HTTPS enforced 301 https://mcp.filingapi.dev/mcp
MCP tools — 10 exposed · ~882 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.

Tool Tokens
get_company_info ~50

Get sector, industry, and data coverage info for a company. Returns the company's GICS sector and industry classification, plus counts of available filings and transcripts.

NameTypeReqDescription
tickerstringyes

No output schema declared.

No examples provided.

get_earnings_calendar ~79

Get upcoming earnings announcement dates with EPS and revenue estimates. Defaults to the next 7 days if no dates specified. Use this when asked about upcoming earnings, who reports this week, or when a specific company's next earnings date is.

NameTypeReqDescription
date_from
date_to
ticker

No output schema declared.

No examples provided.

get_filing_detail ~89

Get the full detail of a single SEC filing by ticker and accession number (the unique SEC filing ID, e.g. '0000320193-26-000011'). Use this after get_filings or get_guidance has identified a specific filing you want to inspect in full.

NameTypeReqDescription
accession_numberstringyes
tickerstringyes

No output schema declared.

No examples provided.

get_filings ~79

Get SEC filings (8-K, 10-Q, etc.) for a company by ticker symbol. Use this to see what filings are available for a company, with dates and accession numbers. Does not include guidance extraction - use get_guidance for that.

NameTypeReqDescription
filing_type
tickerstringyes

No output schema declared.

No examples provided.

get_guidance ~102

Get forward-looking guidance language extracted from a company's SEC filings, by ticker symbol. Use this when asked what a company said about future performance, revenue outlook, margin expectations, or other forward-looking statements. Note: results are keyword-matched sentences from filings and may include both forward guidance and recent reported results - read each sentence carefully to distinguish actual forward guidance from historical figures.

NameTypeReqDescription
tickerstringyes

No output schema declared.

No examples provided.

get_sector_filings ~93

Get recent SEC filings for all companies in a given sector. Sector names are case-insensitive, e.g. "Technology", "Energy", "Healthcare". Use list_sectors first if unsure of exact names. Optionally filter by event_type (earnings_release, acquisition, executive_change, restructuring, dividend, guidance_update).

NameTypeReqDescription
event_type
sectorstringyes

No output schema declared.

No examples provided.

get_signals ~135

Get real-time AI sentiment signals derived from SEC 8-K filings. Each signal includes: ticker, bullish/bearish/neutral classification, confidence score (-100 to 100), a one-line summary, and key factors. Signals are generated by Claude Haiku within minutes of EDGAR publication. Use this when asked which companies have recently filed bullish or bearish 8-Ks, or to screen for sentiment shifts across the S&P 500. Default window is 30 days; set hours=24 for today only.

NameTypeReqDescription
hoursinteger
limitinteger

No output schema declared.

No examples provided.

get_transcript ~107

Get all available earnings call transcripts for a company by ticker. Returns a list of transcripts (each with fiscal_quarter, fiscal_year, date, and speakers). If asked about a specific quarter, look for it within the returned list rather than expecting a single result - this endpoint does not currently filter server-side. Use this when asked what was said on an earnings call, as opposed to in written SEC filings.

NameTypeReqDescription
tickerstringyes

No output schema declared.

No examples provided.

list_sectors ~62

List all available sectors with the number of tickers in each. Use this when asked about sectors, industries, or to find which sector a type of company falls under. Returns 11 GICS sectors covering the S&P 500.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

search_filings ~86

Search across all SEC filings in the database by keyword, optionally filtered by ticker and date range (YYYY-MM-DD format). Use this for open-ended questions like "which companies mentioned supply chain issues" rather than looking up one known ticker.

NameTypeReqDescription
date_from
date_to
querystringyes
ticker

No output schema declared.

No examples provided.