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.

DimensionAlpaca MCP ServerAlpaca's official MCP server for trading stocks, ETFs, crypto, and options via natural language.MartinLoop MCP ServerAn independent control layer that gives AI coding agents budgets, brakes, and receipts
FMRS62 / 100 · C79 / 100 · B
Reliability10 / 2012 / 20
Security and permissions12 / 2018 / 20
Maintenance10 / 2016 / 20
Documentation16 / 2018 / 20
Setup experience14 / 2015 / 20
Best for
  • Developers who want to automate trading
  • Users who want to use AI assistants for investment research and trade execution
  • Traders familiar with Alpaca brokerage services
  • Engineering teams scaling AI coding agents while controlling spend
  • Platform teams that need auditable, rollback-aware agent execution records
  • Organizations using multiple agents (Claude, Codex, Gemini) under one governed flow
Not for
  • Users who need a hosted remote MCP server (Alpaca does not provide hosted service)
  • Users who want to trade mutual funds or futures (not supported)
  • Users who need to view Broker API docs (server excludes Broker API endpoints)
  • Developers who just want a simple code-completion helper without run governance
  • Teams unwilling to accept local JSONL run records with HMAC signing
  • Environments without a supported adapter (Claude/Codex/Gemini CLIs, direct provider, or verifier-only)
Required permissions
  • Access Alpaca account information (balances, positions, orders)
  • Place orders on behalf of the user (buy, sell, cancel)
  • Read market data and news
  • Read Alpaca documentation
  • Read/write access to the configured repo root (writable scope restrictable via --allow-path/--deny-path)
  • Ability to invoke the chosen agent CLI (Claude/Codex/Gemini, etc.) and its underlying model account
  • Local disk writes for run records, receipts, and share outputs (share/run-receipt., etc.)
  • Execution of user-configured verifier commands (e.g. npm test)
Risks and side effects
  • The server can execute real trades, potentially leading to financial loss
  • API keys are sensitive credentials and should be handled securely
  • Options and crypto trading carry high risk and are not suitable for all investors
  • Algorithmic outputs are based on historical data and may not predict future markets
  • Verifier commands are executed; poorly chosen verifier commands carry security risk despite preflight policy checks
  • Cost and token figures may be estimates (labeled with provenance) and should not be treated as settled accounting
  • Receipt integrity must be verified before use as trustworthy evidence; missing rollback evidence is flagged as EVIDENCE_BOUNDARY
  • Policy defaults come from martin.config.yaml and can be overridden by CLI flags; misconfiguration can loosen safety boundaries
Supported clientsClaude Desktop, Cursor, VS Code, Claude Code, PyCharm, Antigravity CLI, ChatGPT, Claude MobileClaude Code, Codex, Gemini CLI, Cursor, VS Code, GitHub Copilot, Continue
Tools740