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.

DimensionEmilia Protocol MCP ServerExact-action approval and verifiable signed receipts for consequential agent actions.BioMCPOne binary. One grammar. Evidence from the biomedical sources you already trust.
FMRS49 / 100 · D75 / 100 · B
Reliability8 / 2010 / 20
Security and permissions9 / 2016 / 20
Maintenance11 / 2018 / 20
Documentation12 / 2017 / 20
Setup experience9 / 2014 / 20
Best for
  • Teams building autonomous agents on MCP that need an authority control plane
  • Security and platform engineering teams that need exact-action approval and verifiable evidence
  • Enterprise deployments that bind human or institutional authorization to one exact executable action
  • Biomedical researchers
  • Clinicians
  • AI agents that need efficient access to biomedical literature and data analysis
Not for
  • Projects expecting a replacement for OAuth/OIDC, workload identity, or policy engines
  • Users expecting the server itself to be an auditor, accredited certifier, or settlement rail
  • Deployments that do not place Gate on the credential-owning path yet expect preventive control
  • 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
  • EP_API_KEY is the key needed for write and live action-guard operations (optional; public receipt lookup may work without it)
  • The server runs as a local stdio process and can read the environment variables configured for it
  • Enabling EP_INCLUDE_REGISTRY_TOOLS exposes additional registry and reputation tool interfaces
  • 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
  • Preventive control holds only under complete mediation; paths that bypass the enforcement point are unconstrained
  • Without EP_API_KEY, write operations and live action guarding may be unavailable
  • Admission is not execution and execution is not effect; unknown results must be reconciled, not blindly retried
  • Environment switches that broaden the advertised tool set widen the exposed surface
  • The referenced IETF documents are individual Internet-Drafts, not RFCs or IETF endorsement
  • 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 clientsClaude DesktopClaude Desktop, Claude Code, Codex, Other MCP stdio clients
Tools011