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.

DimensionStock Trade MCP ServerMCP server exposing Tiingo API endpoints for stock prices, news, forex, and fundamentals.MartinLoop MCP ServerAn independent control layer that gives AI coding agents budgets, brakes, and receipts
FMRS42 / 100 · D79 / 100 · B
Reliability6 / 2012 / 20
Security and permissions10 / 2018 / 20
Maintenance4 / 2016 / 20
Documentation10 / 2018 / 20
Setup experience12 / 2015 / 20
Best for
  • Developers and quantitative analysts needing programmatic access to Tiingo financial data.
  • Users who want to integrate financial data into MCP clients like Claude Desktop.
  • Workflows that require automated retrieval of stock, news, forex, and fundamentals data.
  • 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 without a Tiingo API key (must register and obtain a token).
  • Users needing real-time streaming quotes (the server provides REST endpoints only).
  • Users requiring data sources other than Tiingo.
  • 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
  • Network access to call Tiingo API endpoints.
  • Environment variable `TIINGO_API_TOKEN` for authentication.
  • Local file system access to read the built JavaScript file (typically `build/index.js`).
  • 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
  • Risk of exposing your Tiingo API key; handle it securely.
  • API usage may incur costs depending on Tiingo's pricing.
  • Dependence on third-party service: Tiingo's availability and data accuracy may vary.
  • Error handling might not be robust; invalid API keys or request failures may result in errors.
  • 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 DesktopClaude Code, Codex, Gemini CLI, Cursor, VS Code, GitHub Copilot, Continue
Tools110