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.

DimensionAgent Skills MCPMCP server that exposes the Agent Skills catalog to AI coding agents via progressive disclosureMartinLoop MCP ServerAn independent control layer that gives AI coding agents budgets, brakes, and receipts
FMRS59 / 100 · C79 / 100 · B
Reliability6 / 2012 / 20
Security and permissions12 / 2018 / 20
Maintenance15 / 2016 / 20
Documentation13 / 2018 / 20
Setup experience13 / 2015 / 20
Best for
  • Developers already using the tech-leads-club/agent-skills catalog who want to search and invoke skills directly from an MCP-enabled coding assistant
  • Workflows that benefit from progressive, on-demand loading of skill content rather than pulling the whole catalog at once
  • 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
  • Teams requiring an MCP implementation maintained directly by an official product or protocol owner (this is a community project from Tech Leads Club, not an Anthropic or other official offering)
  • Use cases needing the server itself to execute code, access the filesystem, or call external cloud services (the README does not document such tools)
  • 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
  • Running via npx requires network access to download and execute the @tech-leads-club/agent-skills-mcp package
  • The MCP server needs access to the skills catalog data (via CDN or local cache) to support listing, searching, and reading
  • 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 README notes that roughly 13% of skills in open marketplaces contain critical vulnerabilities; while this project claims static analysis and scanning of its skills, running third-party packages via npx -y still requires trusting the published package
  • The repository's license field is NOASSERTION, and some skills come from community or third-party authors retaining their own original licenses — verify individual skill licensing before commercial or compliance-sensitive use
  • The README does not provide detailed input/output parameters or error codes for the tools, so full integration requires consulting packages/mcp/README.md
  • 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 Code, Cursor, VS CodeClaude Code, Codex, Gemini CLI, Cursor, VS Code, GitHub Copilot, Continue
Tools40