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.

DimensionHonchoReasoning memory for stateful agents.BioMCPOne binary. One grammar. Evidence from the biomedical sources you already trust.
FMRS55 / 100 · C75 / 100 · B
Reliability8 / 2010 / 20
Security and permissions9 / 2016 / 20
Maintenance11 / 2018 / 20
Documentation14 / 2017 / 20
Setup experience13 / 2014 / 20
Best for
  • Stateful agents that need cross-session memory
  • Applications requiring personalization and long-term context
  • Developers using MCP-compatible clients
  • Teams choosing between a managed or self-hosted memory service
  • Biomedical researchers
  • Clinicians
  • AI agents that need efficient access to biomedical literature and data analysis
Not for
  • One-off conversational applications that do not retain history
  • Integration reviews requiring a documented list of MCP tool names and parameters
  • Workloads where messages or documents must not be sent to an external memory service
  • 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 an Authorization request header to mcp.honcho.dev
  • Requires a valid OAuth access token or Honcho API key
  • May optionally require a default workspace ID
  • The service may receive and process session messages, events, documents, or tool traces
  • 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
  • Content sent to Honcho may contain sensitive personal or application data
  • Background reasoning is asynchronous, so newly added messages may not immediately appear in chat or representation results
  • The managed service depends on network access, credentials, and Honcho availability
  • The AGPL-3.0 license may affect self-hosting and redistribution plans
  • 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 Code, Cursor, Cline, Windsurf, OpenCode, OpenClaw, HermesClaude Desktop, Claude Code, Codex, Other MCP stdio clients
Tools011