M
MCP Directory CURATED DIRECTORY
911 MCP servers indexed
中文
← Back to directory
COMPARE UP TO 4 SERVERS

Compare MCP servers

Compare scores, permissions, risks, and fit in one decision-focused table.

DimensionSEC EDGAR MCP ServerQuery SEC EDGAR filings, XBRL financials, and company data through MCP. STDIO & Streamable HTTP.MCP Toolbox for DatabasesGoogle's official database MCP toolbox — define AI-accessible database tools via config
FMRS68 / 100 · C74 / 100 · B
Reliability11 / 2013 / 20
Security and permissions15 / 2013 / 20
Maintenance11 / 2017 / 20
Documentation17 / 2016 / 20
Setup experience14 / 2015 / 20
Best for
  • Financial analysts and researchers needing fast, structured access to SEC filings.
  • Developers wanting to run SQL queries on SEC data directly within MCP clients.
  • Regtech and data scientists interested in XBRL data.
  • Teams that want precise control over which database operations an AI can perform, rather than open arbitrary SQL execution
  • Scenarios needing a unified MCP setup across multiple database engines
Not for
  • Users requiring totally offline access to historical filings (though a local mirror option exists).
  • Scenarios needing real-time streaming or very low latency (SEC has rate limits and publication lag).
  • Users who want to avoid setting up their own EDGAR_USER_AGENT (but can use the hosted instance).
  • Lightweight cases that just want to run a few ad-hoc SQL queries without maintaining a tools.yaml config (a simpler single-database MCP may be a better fit)
Required permissions
  • Access to SEC EDGAR public API (no API key, but valid User-Agent required).
  • When self-hosting locally, runs a local server process that needs a Node/Bun runtime.
  • Optional: when using the local SQLite mirror, stores data and caches on disk.
  • Database credentials (username/password/connection string) are supplied via env vars or config
  • A tool's actual permission is whatever SQL statement is defined in tools.yaml — designed for least privilege, but misconfiguration can still over-expose access
Risks and side effects
  • SEC requires a valid User-Agent like 'YourAppName [email protected]'; otherwise IP blocks could occur.
  • The tool accesses public APIs and may be rate-limited if too many requests are made.
  • As a non-official server, validate reliability and maintenance status before using in production.
  • If tools.yaml defines SQL statements that allow unconstrained writes or deletes, the AI could accidentally modify data
  • The prebuilt toolsets (--prebuilt) favor convenience and may expose broader query capability than a specific business actually needs — use a custom tools.yaml in production
Supported clientsClaude Desktop, Cursor, VS CodeClaude Code, Gemini CLI, Zed, Antigravity
Tools170