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 ServerGive AI assistants access to SEC EDGAR filings.BioMCPOne binary. One grammar. Evidence from the biomedical sources you already trust.
FMRS59 / 100 · C75 / 100 · B
Reliability10 / 2010 / 20
Security and permissions11 / 2016 / 20
Maintenance13 / 2018 / 20
Documentation12 / 2017 / 20
Setup experience13 / 2014 / 20
Best for
  • Researchers who need AI-assisted access to U.S. public-company filings
  • Users analyzing company, financial, or insider-trading data
  • Financial research workflows that require precise numbers and source links
  • Biomedical researchers
  • Clinicians
  • AI agents that need efficient access to biomedical literature and data analysis
Not for
  • Users requiring an SEC-maintained or SEC-endorsed server
  • Public HTTP deployments requiring built-in authentication
  • Other data sources or financial-service capabilities not described in the source material
  • Users needing to write to upstream databases (read-only)
  • Users requiring direct access to closed datasets (e.g., COSMIC is not directly integrated)
  • Users expecting all advanced features without API keys
Required permissions
  • Requires access to the SEC EDGAR API
  • Requires the non-secret SEC_EDGAR_USER_AGENT environment variable
  • HTTP mode should run on a controlled network because authentication is not included
  • Requires internet access to query public biomedical APIs
  • Optional API keys (NCBI, Semantic Scholar, OpenFDA, etc.) to improve rate limits or unlock features
  • Local read/write access for skills, cache, and local study data (e.g., `~/.local/share/biomcp`)
Risks and side effects
  • The project states that it is not affiliated with or endorsed by the U.S. Securities and Exchange Commission
  • HTTP transport has no authentication and should not be exposed to untrusted networks
  • SEC API access may depend on correct user-agent configuration and external service availability
  • Financial and insider-trading information should be verified through the returned SEC filing URLs
  • Upstream API rate limits may affect performance
  • Some data sources (e.g., KEGG) have licensing terms that restrict non-academic use
  • Features requiring API keys (e.g., OncoKB) may be incomplete without them
  • Local binary installations need regular updates for compatibility
Supported clientsDifyClaude Desktop, Claude Code, Codex, Other MCP stdio clients
Tools011