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.Firecrawl MCP ServerFirecrawl's official MCP server for web search, scraping, and structured extraction for AI agents
FMRS69 / 100 · C75 / 100 · B
Reliability11 / 2013 / 20
Security and permissions14 / 2012 / 20
Maintenance13 / 2016 / 20
Documentation16 / 2017 / 20
Setup experience15 / 2017 / 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.
  • Scenarios needing clean, structured web context fed to an AI assistant
  • Users already on the Firecrawl platform who want to call its scraping capability directly via MCP
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.
  • Simple static-page scraping where you don't want to depend on a third-party API and incur call costs
  • Sites that explicitly disallow automated access (robots.txt)
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 a Firecrawl API key to call; cost and quota are governed by the Firecrawl account
  • firecrawl_agent/firecrawl_interact perform automated browser interaction, which may trigger login or form-submission flows on the target site
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.
  • Bulk crawl/map tools can generate significant request volume against a target site — respect the site's rate limits and terms of service
  • firecrawl_agent's interactive action chain is longer — define task boundaries clearly before running it to avoid accidentally triggering actions on a sensitive site
Supported clientsClaude Desktop, Claude Code, CursorClaude Desktop, VS Code, Cursor, Windsurf, Zed, Amp
Tools2011