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 EDGAR Filings

PYPI · MCP-SERVER-EDGAR

Latest SEC filing and calendar-year filing history for a stock ticker, with official EDGAR links.

Available components

64 Trust /100

Last scanned (7 hours ago)

Scores higher than 61% of PyPI servers

Category Finance and Payments

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security50
  • Malware scan not yet available for this package.Unverified
  • No known CVEs affecting this package version or its production dependencies.Pass
  • Runs uv_build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
  • 1 of 31 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to SudiptoHaldar/mcp_server_edgar). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 0 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability72
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 1647 tokens (~411/item across 4 items; 3 tools + 1 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management10
  • Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
  • 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
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 3 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
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
What we tested

Checks we ran (15)

  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • 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 package. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Malware scan in Supply Chain SecurityMalware scan not yet available for this package.

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

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.

  • 4 Nov 26 +12
    • Provenance: fail → pass ▲ security
    • The attested source repository moved: SudiptoHaldar/mcp_server_edgar security
    • Stability: unverified → 0.07 ▲ functional
    • Package version: 0.1.0 → 0.1.2 functional
    • Package version: 0.1.0 → 0.1.1 functional
  • 2 Nov 26 52

    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 5 Nov 2026 · Analysed pypi/mcp-server-edgar@0.1.2

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem pypi
Reason Verified
Discovered via Registry attestation endpoint
Source repo SudiptoHaldar/mcp_server_edgar
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/SudiptoHaldar/mcp_server_edgar/.github/workflows/release.yml@refs/tags/v0.1.2
Rekor log index 3691670890
Predicate type PyPI publish attestation https://docs.pypi.org/attestations/publish/v1
Subject digest sha256:ebfe1827333cac30745e25b32fd93cb0362cace0d386a96f52df4c2ac9976ac2

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend Known build tool uv_build

Background: Why install scripts are a supply-chain risk →

Dependencies 31 packages
Packages resolved 31
No linked repository 1
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 3 exposed · ~1,402 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_latest_filing ~448

Newest SEC filing for a stock ticker, with official EDGAR links. Resolves the ticker to its SEC CIK and returns the filing with the latest `filing_date` (the date the SEC received it). `forms` restricts the search to exact form types, case-insensitive: `["10-K"]` matches `10-K` but not `10-K/A`; omit it to consider every form. `report_date` (the period the filing covers) is returned as context only, so a 10-K filed in January 2026 for the fiscal year ending September 2025 has a 2026 `filing_date`. Args: ticker: Stock ticker symbol, e.g. `"AAPL"`. Case and surrounding whitespace are ignored; `BRK.B` and `BRK-B` are equivalent. forms: Optional list of SEC form types, e.g. `["10-K", "10-Q"]`. cik: Optional SEC CIK (1-10 digits, string or integer) to pick one issuer when a previous call returned `"ambiguous"`; it must be listed under `ticker`. Returns: A JSON object with `status` and a one-line `message`. On `"ok"`: `company` {cik, name, ticker, exchange}, `forms` (normalised list or null) and `filing` {form, filing_date, report_date, accession_number, filing_url, primary_document_url}, or `filing` null when the company has no filing of those forms; `filing_url` (the filing index page) is always present, `primary_document_url` may be null. The other statuses (`not_found`, `ambiguous` with `candidates`, `invalid_input` with `field`, `upstream_error` with `retryable`) are defined in the server instructions. Example: `get_latest_filing("AAPL", ["10-K"])` returns Apple's most recent annual report.

NameTypeReqDescription
cik–––
forms–––
tickerstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

list_filings_by_year ~548

Filings a company submitted to the SEC during one calendar year, newest first, paged. `year` selects filings by `filing_date`, the date the SEC received the filing, not by `report_date` (the period the filing covers): a 10-K for the fiscal year ending September 2025 that was filed in January 2026 belongs to `year=2026`. `forms` restricts the list to exact form types, case-insensitive (`["10-K"]` matches `10-K` but not `10-K/A`). Older years are served from the SEC's history files automatically. Args: ticker: Stock ticker symbol, e.g. `"AAPL"`; case and surrounding whitespace are ignored. year: Calendar year of the filing date, 1993 or later; a future year returns an empty list. forms: Optional list of SEC form types, e.g. `["10-K", "10-Q"]`; omit it for every form. limit: Page size (default 100); larger values are clamped to the server's cap. offset: Filings to skip, for paging; pass the previous result's `next_offset`. cik: Optional SEC CIK (1-10 digits, string or integer) to pick one issuer when a previous call returned `"ambiguous"`; it must be listed under `ticker`. Returns: A JSON object with `status` and a one-line `message`. On `"ok"`: `company` {cik, name, ticker, exchange}, `year`, `forms`, `limit` (the effective page size), `offset`, `total_count`, `returned_count`, `next_offset` (null on the last page) and `filings` (newest first; each has form, filing_date, report_date, accession_number, filing_url, primary_document_url); an empty year is `"ok"` with `total_count` 0. Page with `offset=next_offset` until null. The other statuses (`not_found`, `ambiguous` with `candidates`, `invalid_input` with `field`, `upstream_error` with `retryable`) are defined in the server instructions. Example: `list_filings_by_year("AAPL", 2025, ["10-K", "10-Q"])` lists Apple's 2025 reports.

NameTypeReqDescription
cik–––
forms–––
limitinteger––
offsetinteger––
tickerstringyes–
yearintegeryes–

Structured output declared, but exposes no named fields.

No examples provided.

list_form_types ~406

EDGAR form types (submission-type codes) filed in recent quarters, most common first. Use this to learn which values the `forms` argument of `get_latest_filing` and `list_filings_by_year` accepts: `form` is exactly the code EDGAR uses (`10-K`, `10-K/A`, `SCHEDULE 13G/A`, `424B2`, `NPORT-P`). The list is a snapshot bundled with the server (see `catalogue.generated_on` and `catalogue.quarters`); `filings` counts filings of that type over those quarters; `description` and `topics` come from the SEC Forms List when the form number is known, otherwise null. Amendments end with `/A`. No request is made to the SEC. Args: query: Optional case-insensitive text matched against the code and description (`"10-K"` lists `10-K`, `10-K/A`, `10-KT`, ...; `"/A"` lists amendments). limit: Maximum entries per page (default 100; clamped to the server's cap). offset: Entries to skip, for paging; pass the previous result's `next_offset`. Returns: A JSON object with `status` and a one-line `message`. On `"ok"`: `query`, `limit`, `offset`, `total_count`, `returned_count`, `next_offset` (null on the last page), `catalogue` {generated_on, quarters, sources} and `form_types` (each: form, description, amendment, filings, topics). `"invalid_input"` carries `field`, as defined in the server instructions; no other status occurs. Example: `list_form_types("13G")` lists the Schedule 13G submission types and their counts.

NameTypeReqDescription
limitinteger––
offsetinteger––
query–––

Structured output declared, but exposes no named fields.

No examples provided.

Install

How do I install the SEC EDGAR Filings MCP server?

SEC EDGAR Filings runs locally as a PyPI package, launched with uvx mcp-server-edgar. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · mcp-server-edgar

# add to Claude Code
claude mcp add sudiptohaldar-mcp-server-edgar -- uvx mcp-server-edgar
Common questions

What is the SEC EDGAR Filings MCP server?

SEC EDGAR Filings is an MCP server listed in the public MCP registry as io.github.SudiptoHaldar/mcp-server-edgar. Latest SEC filing and calendar-year filing history for a stock ticker, with official EDGAR links. This page covers its PyPI package (mcp-server-edgar).

Is the SEC EDGAR Filings MCP server safe to use?

SEC EDGAR Filings scores 64 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. Its build provenance is signed and verified. 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 EDGAR Filings MCP server expose?

SEC EDGAR Filings exposes 3 tools: get_latest_filing, list_filings_by_year, list_form_types. Their descriptions and schemas cost roughly 1,402 tokens of context every time the server is loaded.

Is the SEC EDGAR Filings MCP server still maintained?

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

What licence is the SEC EDGAR Filings MCP server under?

SEC EDGAR Filings declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

What did VerifyMCP test on the SEC EDGAR Filings MCP server?

VerifyMCP ran 15 checks on SEC EDGAR Filings, covering Known CVEs, Install scripts, Dependency health, Source repository and 11 more. One item could not be completed, a gap on our side rather than a finding about SEC EDGAR Filings: Malware scan. Endpoint Security and Transport & Reachability do not apply to a PyPI package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.