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.

DimensionTradeMemory ProtocolTamper-evident decision audit trail and outcome-weighted memory for AI trading agents.BioMCPOne binary. One grammar. Evidence from the biomedical sources you already trust.
FMRS69 / 100 · C75 / 100 · B
Reliability11 / 2010 / 20
Security and permissions14 / 2016 / 20
Maintenance13 / 2018 / 20
Documentation16 / 2017 / 20
Setup experience15 / 2014 / 20
Best for
  • Individual traders who want persistent memory and a decision audit trail for their AI trading agent.
  • Developers building autonomous trading agents that need to query prior context before trading.
  • Compliance or risk teams that need verifiable, exportable decision records.
  • Researchers studying the outcome-weighted memory (OWM) framework.
  • Biomedical researchers
  • Clinicians
  • AI agents that need efficient access to biomedical literature and data analysis
Not for
  • Users expecting the MCP server to place orders, manage funds or touch wallets — it does not execute trades.
  • Teams needing a rich hosted service or a fast-moving feature roadmap (the project is in maintenance mode).
  • Anyone treating its outputs as trade signals or investment advice.
  • Users requiring capabilities not yet shipped, such as external TSA anchoring or zkML proof of inference.
  • 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
  • Reads the trade decision context and trade records passed in by your agent.
  • Writes and maintains memory-layer and audit-chain data locally.
  • By default makes one outbound call to an RFC 3161 trusted timestamping service, sending only the 32-byte daily audit root with no trade data; disable with TRADEMEMORY_TSA=off.
  • Does not access API keys, wallets or broker credentials.
  • 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
  • Audit-chain maturity is limited: v0.5 does not yet include TSA timestamping and external anchoring, which the docs list as roadmap items.
  • OWM empirical validation is ongoing (n=40; target n>=100 for statistical significance), so conclusions should be treated cautiously.
  • The evolution engine is in a research phase, with statistical gate pass rate still being optimised.
  • The default outbound timestamping call contacts a third-party service, which must be disabled for fully offline environments.
  • Memory and audit data live locally, so disk tampering or loss affects verifiability and historical retention.
  • 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, Claude Code, CursorClaude Desktop, Claude Code, Codex, Other MCP stdio clients
Tools2011