io.github.jethrokirk-sudo/filingapi
REMOTE · MCP.FILINGAPI.DEV · SCANNED SEP 25
SEC filings, earnings transcripts, guidance signals & macro calendar for S&P 500. 11 MCP tools.
Available components
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 → Why this is hard to score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 10 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
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 Management100
- No destabilizing schema changes in the last 30 days.Pass
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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the io.github.jethrokirk-sudo/filingapi MCP server?
io.github.jethrokirk-sudo/filingapi is a hosted endpoint at https://mcp.filingapi.dev/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.filingapi.dev
claude mcp add --transport http jethrokirk-sudo-filingapi 'https://mcp.filingapi.dev/mcp'
{
"mcpServers": {
"jethrokirk-sudo-filingapi": {
"url": "https://mcp.filingapi.dev/mcp"
}
}
} {
"servers": {
"jethrokirk-sudo-filingapi": {
"type": "http",
"url": "https://mcp.filingapi.dev/mcp"
}
}
} [mcp_servers.jethrokirk-sudo-filingapi] url = "https://mcp.filingapi.dev/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"jethrokirk-sudo-filingapi": {
"type": "remote",
"url": "https://mcp.filingapi.dev/mcp",
"enabled": true
}
}
} openclaw mcp add jethrokirk-sudo-filingapi --url 'https://mcp.filingapi.dev/mcp' --transport streamable-http
mcp_servers:
jethrokirk-sudo-filingapi:
url: "https://mcp.filingapi.dev/mcp" {
"McpServers": {
"jethrokirk-sudo-filingapi": {
"Transport": "http",
"Url": "https://mcp.filingapi.dev/mcp"
}
}
} assistant mcp add jethrokirk-sudo-filingapi -t streamable-http -u 'https://mcp.filingapi.dev/mcp'
{
"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.
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.
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 7 Aug 26 0
- The server no longer declares the “experimental” capability functional
- 5 Aug 26 0
- HSTS header: unverified → fail ▼ security
- TLS certificate: unverified → pass ▲ security
- Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 10 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
- Schema quality: unverified → fail ▼ functional
- Tool coverage: unverified → 100 ▲ functional
- Schema quality: unverified → pass ▲ functional
- Schema quality: unverified → good ▲ functional
- Stability: fail → 0.33 functional
- New tool “get_company_info” functional
- New tool “get_earnings_calendar” functional
- New tool “get_filing_detail” functional
- New tool “get_filings” functional
- New tool “get_guidance” functional
- New tool “get_sector_filings” functional
- New tool “get_signals” functional
- New tool “get_transcript” functional
- New tool “list_sectors” functional
- New tool “search_filings” functional
- 4 Aug 26 0
- HSTS header: fail → unverified ▼ security
- TLS certificate: pass → unverified ▼ security
- Stability: 0.27 → fail ▼ security
- A breaking change shipped without a version bump: still 1.28.1 ▼ security
- Tool “get_company_info” was removed ▼ security
- Tool “get_earnings_calendar” was removed ▼ security
- Tool “get_filing_detail” was removed ▼ security
- Tool “get_filings” was removed ▼ security
- Tool “get_guidance” was removed ▼ security
- Tool “get_sector_filings” was removed ▼ security
- Tool “get_signals” was removed ▼ security
- Tool “get_transcript” was removed ▼ security
- Tool “list_sectors” was removed ▼ security
- Tool “search_filings” was removed ▼ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- Schema quality: fail → unverified ▼ functional
- Schema quality: good → unverified ▼ functional
- Schema quality: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
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 25 Sept 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=YE1,O=Let's Encrypt,C=US | 29 Aug 2026 | 27 Nov 2026 | ECDSA 256 | ECDSA-SHA384 | 5219aec248b8d2d55bae8d84954ec5370b3 |
| SANs: mcp.filingapi.dev | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| 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 |
Background: What to check on a remote MCP endpoint →
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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
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 |
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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
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.
| Name | Type | Req | Description |
|---|---|---|---|
| ticker | string | yes | – |
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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.
| Name | Type | Req | Description |
|---|---|---|---|
| accession_number | string | yes | – |
| ticker | string | yes | – |
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.
| Name | Type | Req | Description |
|---|---|---|---|
| filing_type | – | – | – |
| ticker | string | yes | – |
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.
| Name | Type | Req | Description |
|---|---|---|---|
| ticker | string | yes | – |
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).
| Name | Type | Req | Description |
|---|---|---|---|
| event_type | – | – | – |
| sector | string | yes | – |
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.
| Name | Type | Req | Description |
|---|---|---|---|
| hours | integer | – | – |
| limit | integer | – | – |
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.
| Name | Type | Req | Description |
|---|---|---|---|
| ticker | string | yes | – |
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.
| Name | Type | Req | Description |
|---|---|---|---|
| date_from | – | – | – |
| date_to | – | – | – |
| query | string | yes | – |
| ticker | – | – | – |
No output schema declared.
No examples provided.
What is the io.github.jethrokirk-sudo/filingapi MCP server?
io.github.jethrokirk-sudo/filingapi is an MCP server listed in the public MCP registry as io.github.jethrokirk-sudo/filingapi. SEC filings, earnings transcripts, guidance signals & macro calendar for S&P 500. 11 MCP tools. This page covers its hosted endpoint (https://mcp.filingapi.dev/mcp).
Is the io.github.jethrokirk-sudo/filingapi MCP server safe to use?
io.github.jethrokirk-sudo/filingapi scores 75 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.jethrokirk-sudo/filingapi MCP server expose?
io.github.jethrokirk-sudo/filingapi exposes 10 tools: get_filings, get_guidance, get_filing_detail, search_filings, get_transcript, and 5 more. Their descriptions and schemas cost roughly 882 tokens of context every time the server is loaded.
Does the io.github.jethrokirk-sudo/filingapi MCP server require authentication?
No. We connected to io.github.jethrokirk-sudo/filingapi without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.github.jethrokirk-sudo/filingapi MCP server still maintained?
io.github.jethrokirk-sudo/filingapi is still listed as active in the MCP registry. We last reached this channel on 25 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.