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.

DimensionAxion Planetary MCPThe world's first virtual satellite you can connect with MCP — Earth observation as easy as conversation.BioMCPOne binary. One grammar. Evidence from the biomedical sources you already trust.
FMRS50 / 100 · D75 / 100 · B
Reliability9 / 2010 / 20
Security and permissions3 / 2016 / 20
Maintenance10 / 2018 / 20
Documentation15 / 2017 / 20
Setup experience13 / 2014 / 20
Best for
  • Farmers, city planners, NGOs, and students without GIS expertise
  • Developers who want natural-language satellite data analysis
  • Teams wanting zero-credential self-hosting
  • Biomedical researchers
  • Clinicians
  • AI agents that need efficient access to biomedical literature and data analysis
Not for
  • Users needing high-resolution commercial imagery
  • Users unwilling to self-host but wary of the free hosted tier
  • Production remote-sensing workflows requiring sub-meter real-time data
  • 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
  • API key (for hosted server authentication)
  • Optional AWS credentials (only for GeoTIFF exports to S3)
  • Local network access to reach the SSE server
  • 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 hosted server runs on Render's free tier and may take ~30 seconds to wake when idle
  • The starter API key is published in the README and may be abused or revoked
  • Exports over 10MB require an S3 setup
  • AWS credentials for S3 exports must be kept secure
  • 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
Tools611