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.

DimensionHermes Atlas MCP ServerBring the Hermes Atlas ecosystem catalog to any MCP client.BioMCPOne binary. One grammar. Evidence from the biomedical sources you already trust.
FMRS43 / 100 · D75 / 100 · B
Reliability6 / 2010 / 20
Security and permissions10 / 2016 / 20
Maintenance8 / 2018 / 20
Documentation7 / 2017 / 20
Setup experience12 / 2014 / 20
Best for
  • Developers and teams using Hermes Agent who want to discover community tools and integrations.
  • Users who want to access live catalog information through MCP clients like Claude Desktop, Cursor, etc.
  • Users who need up-to-date ecosystem data, as data is fetched live and cached briefly.
  • Biomedical researchers
  • Clinicians
  • AI agents that need efficient access to biomedical literature and data analysis
Not for
  • Users needing offline catalog access independent of the internet (data is fetched live from hermesatlas.com).
  • Users who want long-term caching or to avoid external API dependencies (optional Redis provides longer caching, but default is in-memory only).
  • Users needing official oversight or support, as this server is maintained by a contributor, not the official Hermes project.
  • 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
  • Network access: fetch live catalog data and API requests from hermesatlas.com.
  • File system access: for the installer, read and write client config files (e.g., claude_desktop_config.json).
  • Optional: access to Redis if REDIS_URL is set.
  • 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
  • Data is sourced from a third-party API (hermesatlas.com), which could affect reliability if the site or API changes.
  • The installer modifies client config files, which could break existing MCP setups if done incorrectly; use --print for a dry run.
  • Since the server is experimental (0.x), breaking changes may occur.
  • 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 Desktop, Cursor, Continue, WindsurfClaude Desktop, Claude Code, Codex, Other MCP stdio clients
Tools611