sec-edgar-mcp — Watchlist

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Monitor exact implementation activity, MCP interface, permission and setup changes.

Reviewed Oct 10, 2026 · Documentation review; complete setup workflow not independently tested

Best fit

SEC EDGAR filings and finance research

What we know

A SEC EDGAR MCP (Model Context Protocol) Server Public Radar listing describes capability; verify precise runtime setup and privilege boundaries upstream.

Maintenance / activity evidence

GitHub exact repo pushed_at 2026-10-03T09:11:21Z

Tracking evidence observed Oct 10, 2026. These dated signals do not establish current maintenance. Reviewed enrichment confidence: medium.

Verification gaps / watch-outs

Installation and comprehensive security have not been independently audited.
Primarily public SEC EDGAR filing data; rate limits and interpretation/attribution should be explicit. Complete write authority is not verified.
Refer to first-party setup documentation; do not infer authorization from package existence.
Sensitive access: public regulatory filings

Primarily public SEC EDGAR filing data; rate limits and interpretation/attribution should be explicit.
Public tracking suitability is not an installation safety audit.

Full authority, access and evidence limits are available in Review context and Access & risk.

Popularity

368 repository stars

Stars observed Oct 10, 2026.

Repository total for stefanoamorelli/sec-edgar-mcp.

All limitations / Review context

Has sec-edgar-mcp changed its documented MCP interface, authentication or privilege boundaries, and does it merit promotion?

Limited editorial listing; known permission implications disclosed, no independently established publication blocker.

Primarily public SEC EDGAR filing data; rate limits and interpretation/attribution should be explicit.
Public tracking suitability is not an installation safety audit.
Refer to first-party setup documentation; do not infer authorization from package existence.
public regulatory filings
Sensitive access: public regulatory filings
Complete write authority is not verified.
Installation, client compatibility and comprehensive security have not been independently audited. Authentication and access depend on the configured services.
Upstream credential and permission scopes must be validated before runtime use.
Precise setup/auth/permissions not verified
Write actions/tool inventory not confirmed against exact tool documentation; listed action classes remain illustrative or context-dependent. Empty inventory does not establish read-only.
Some integration/runtime instructions are not confirmed from a first-party install guide and therefore intentionally omitted.
Exact GitHub pushed_at 2026-10-03T09:11:21Z

Original activity observations

GitHub exact repo pushed_at 2026-10-03T09:11:21Z

Technical identity

github.com/stefanoamorelli/sec-edgar-mcp

Exact implementation source: https://github.com/stefanoamorelli/sec-edgar-mcp ↗
Reviewed resource type: MCP Server
Repository identity: stefanoamorelli/sec-edgar-mcp

Evidence & Sources

Evidence basis: Recorded source evidence
Setup runtime verification: Not independently runtime-tested by MCP100 for this setup workflow.

Reviewed Oct 10, 2026 · Latest source observation Oct 10, 2026

GitHub repository ↗
stefanoamorelli/sec-edgar-mcp
Recorded repository material and project history.

Setup · Watchlist

Install & Agents

Publisher instructions.

Source evidence observed Oct 14, 2026.

Additional setup details required — see the specific gaps below.

Install / connect
Publisher instructions
SEC EDGAR MCP provides public regulatory data via an MCP server.
publisher documented · Publisher instructions
uvx sec-edgar-mcp
Configure / authenticate
MCP100 setup guide
Register `uvx sec-edgar-mcp` as a stdio MCP server in the selected client. Alternative `pip install sec-edgar-mcp` in your own virtual environment. `npm install` in repo evals is NOT the MCP server install.
Previously reviewed Docker configuration; alternative to uvx: In a compatible JSON-based MCP client use command `docker` and args ["run","-i","--rm","-e","SEC_EDGAR_USER_AGENT=Your Name (your@email.com)","stefanoamorelli/sec-edgar-mcp:latest"]. Replace the user agent with a truthful contact identity; for Codex use client-specific configuration format.
Check connection
Suggested check
Confirm MCP tools/list and invoke a read-only issuer or filing search on a public-company test fixture.
Remove / uninstall / revoke
MCP100 setup guide
Remove the SEC EDGAR MCP client entry by actual registration name; if installed with pip, `python -m pip uninstall sec-edgar-mcp` in same environment. uvx needs no global uninstall.
Client unregistration, program uninstall, persistent-data deletion, and credential revocation must be treated separately.
Remove client registration · Claude Code only · MCP100 composed guide
claude mcp remove sec-edgar

Official Documentation & Sources

What it does

A SEC EDGAR MCP (Model Context Protocol) Server Public Radar listing describes capability; verify precise runtime setup and privilege boundaries upstream.

Capability: Finance & Payments
Resource type: MCP Server
Industry: Financial Services & Investing
Best fit: SEC EDGAR filings and finance research

Representative uses

SEC EDGAR filings and finance research

Limitations

Primarily public SEC EDGAR filing data; rate limits and interpretation/attribution should be explicit.
Some integration/runtime instructions are not confirmed from a first-party install guide and therefore intentionally omitted.
Exact GitHub pushed_at 2026-10-03T09:11:21Z

Reviewed access

Access & risk

Review the exact access boundary before connecting this MCP to accounts, credentials, or sensitive data.

Authentication: Refer to first-party setup documentation; do not infer authorization from package existence.
Permissions: Primarily public SEC EDGAR filing data; rate limits and interpretation/attribution should be explicit.
Data handling: public regulatory filings
Cost: Provider or usage fees possible; verify current pricing
Risk and cautions: Primarily public SEC EDGAR filing data; rate limits and interpretation/attribution should be explicit.

Access scope and cautions

Write actions: Not verified
Sensitive access: public regulatory filings
Risk level: low
Security notes: Primarily public SEC EDGAR filing data; rate limits and interpretation/attribution should be explicit. Public tracking suitability is not an installation safety audit.

The reviewed evidence does not establish the complete write authority of this MCP. Consult the unresolved evidence before granting write access.

FAQ

Based on reviewed evidence as of 2026-10-10T03:38:00Z. Watchlist tracking is not a recommendation or a security certification.

Which tasks are documented for this implementation?

The reviewed tasks include: SEC EDGAR filings and finance research.

What setup and authentication are documented?

A complete connection procedure is not verified. Client notes: Installation command omitted unless verified or clearly package-specific; do not infer npx/uvx entrypoints. These facts do not supply missing installation commands, credentials or a verified authentication procedure. Authentication: Refer to first-party setup documentation; do not infer authorization from package existence.

Can it modify data or perform write operations?

Not verified. The available evidence does not establish the complete write authority. Recorded permission context: Primarily public SEC EDGAR filing data; rate limits and interpretation/attribution should be explicit.

What data-handling boundary should I consider?

public regulatory filings Recorded sensitive-access context: public regulatory filings.

What limitations and risks should I check before use?

Primarily public SEC EDGAR filing data; rate limits and interpretation/attribution should be explicit. Some integration/runtime instructions are not confirmed from a first-party install guide and therefore intentionally omitted. Exact GitHub pushed_at 2026-10-03T09:11:21Z. Public tracking suitability is not an installation safety audit. Upstream credential and permission scopes must be validated before runtime use.