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

SEC Filings & Earnings

REMOTE · FILING.MEMORYAPI.ORG

SEC filings, insider trades, and earnings data

0 this week 75 Trust /100

Last scanned (20 hours ago)

Scores higher than 62% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Finance and Payments

Trust breakdown (7 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 → Why this is hard to score →

Endpoint Security57
Transport & Reachability100
Schema Quality & AI Usability76
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 473 tokens (~94/item across 5 items; 5 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 Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
  • Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
What we tested

Checks we ran (12)

  • TLS certificate
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 5 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

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.

  • 11 Nov 26 0
    • Stability: 0.97 → pass security
  • 10 Nov 26 0
    • Stability: pass → 0.97 functional
  • 9 Nov 26 0
    • Stability: 0.97 → pass security
  • 8 Nov 26 0
    • Stability: pass → 0.97 functional
  • 6 Nov 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
  • 21 Oct 26 0
    • HSTS header: unverified → fail ▼ security
    • Transport: fail → pass ▲ security
    • Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 5 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
  • 20 Oct 26 0
    • HSTS header: fail → unverified ▼ security
    • Transport: pass → fail ▼ security
    • Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
  • 28 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
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 21 Nov 2026 · Probed https://filing.memoryapi.org/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=memoryapi.org CN=WE1,O=Google Trust Services,C=US 21 Oct 2026 19 Jan 2027 ECDSA 256 ECDSA-SHA256 bb55c575430a74a7139fb9fc2e710a7a
SANs: memoryapi.org, *.memoryapi.org
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of filing.memoryapi.org. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
org. DS published 725 8 Verified
memoryapi.org. No DS 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://filing.memoryapi.org/mcp Verified 200
http (plaintext) http://filing.memoryapi.org/mcp HTTPS enforced 301 https://filing.memoryapi.org/mcp
MCP tools · 5 exposed · ~473 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. 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 →

Tool Tokens
get_earnings_data ~95

Get structured financial data from SEC XBRL filings. Returns revenue, net income, EPS, assets, and more with historical data and YoY growth.

NameTypeReqDescription
cikstring–SEC CIK number
conceptstring–Financial concept: revenue, net_income, eps, assets, liabilities, equity, operating_income, gross_profit, cash, debt
tickerstring–Stock ticker symbol

No output schema declared.

No examples provided.

get_fda_data ~101

Get FDA drug recalls and adverse event reports from openFDA. Search 17,000+ recalls and 20M+ adverse events by drug name or company.

NameTypeReqDescription
companystring–Company/manufacturer name
drugstring–Drug name to search (e.g. aspirin, Tylenol)
limitnumber–Number of results (max 25)
typestring–recalls (default) or adverse_events

No output schema declared.

No examples provided.

get_insider_trades ~72

Get insider trading activity from SEC Form 4 filings. Shows when executives and directors buy or sell company stock — a key alpha signal for trading agents.

NameTypeReqDescription
cikstring–SEC CIK number
limitnumber–Number of trades
tickerstring–Stock ticker symbol

No output schema declared.

No examples provided.

get_material_events ~67

Get Form 8-K material event filings — M&A announcements, CEO changes, earnings releases, and other events requiring immediate SEC disclosure.

NameTypeReqDescription
cikstring–SEC CIK number
limitnumber–Number of events
tickerstring–Stock ticker symbol

No output schema declared.

No examples provided.

get_recent_filings ~138

Get recent SEC EDGAR filings for any public company. Filter by form type (10-K annual, 10-Q quarterly, 8-K events, 4 insider trades, DEF 14A proxy).

NameTypeReqDescription
cikstring–SEC CIK number (alternative to ticker)
formstring–Form type: 10-K, 10-Q, 8-K, 4, DEF 14A, S-1, 13F
limitnumber–Number of results (max 25)
tickerstring–Stock ticker (e.g. AAPL, MSFT, TSLA)

No output schema declared.

No examples provided.

Install

How do I install the SEC Filings & Earnings MCP server?

SEC Filings & Earnings is a hosted endpoint at https://filing.memoryapi.org/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 · filing.memoryapi.org

# add to Claude Code
claude mcp add --transport http org-memoryapi-filing 'https://filing.memoryapi.org/mcp'
Common questions

What is the SEC Filings & Earnings MCP server?

SEC Filings & Earnings is an MCP server listed in the public MCP registry as org.memoryapi/filing. SEC filings, insider trades, and earnings data. This page covers its hosted endpoint (https://filing.memoryapi.org/mcp).

Is the SEC Filings & Earnings MCP server safe to use?

SEC Filings & Earnings 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 SEC Filings & Earnings MCP server expose?

SEC Filings & Earnings exposes 5 tools: get_recent_filings, get_insider_trades, get_earnings_data, get_material_events, get_fda_data. Their descriptions and schemas cost roughly 473 tokens of context every time the server is loaded.

Does the SEC Filings & Earnings MCP server require authentication?

No. We connected to SEC Filings & Earnings without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the SEC Filings & Earnings MCP server still maintained?

SEC Filings & Earnings is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the SEC Filings & Earnings MCP server?

VerifyMCP ran 12 checks on SEC Filings & Earnings, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about SEC Filings & Earnings: Authorization. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.