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.

DimensionMastercard Developers MCPAccess Mastercard Developers APIs, documentation, and API specifications through MCP.MartinLoop MCP ServerAn independent control layer that gives AI coding agents budgets, brakes, and receipts
FMRS53 / 100 · D79 / 100 · B
Reliability9 / 2012 / 20
Security and permissions13 / 2018 / 20
Maintenance10 / 2016 / 20
Documentation12 / 2018 / 20
Setup experience9 / 2015 / 20
Best for
  • Developers building AI assistants or agents that need to integrate with Mastercard Developers APIs.
  • Teams looking for quick access to Mastercard API documentation within their development environment.
  • 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
  • Not suitable for users needing actual API calls or transactions; this server only provides information retrieval.
  • Not for generic documentation searches unrelated to Mastercard Developers.
  • 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
  • No authentication or API keys required for the server itself, as it accesses only public documentation and API specifications.
  • Client requires ability to execute `npx` command.
  • 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
  • Documentation and API specs may not be the most up-to-date since information comes from the public developer portal.
  • Dependent on network connectivity; server may not work if Mastercard developer portal is unreachable.
  • As a third-party extension, there could be undiscovered bugs or limitations.
  • 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
Tools90