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.

DimensionMCPJam InspectorOpen-source testing and evaluations platform for MCP server developersNPM Sentinel MCP ServerAI-powered NPM package analysis MCP server
FMRS58 / 100 · C79 / 100 · B
Reliability8 / 2012 / 20
Security and permissions13 / 2016 / 20
Maintenance11 / 2018 / 20
Documentation13 / 2018 / 20
Setup experience13 / 2015 / 20
Best for
  • Developers building or maintaining MCP servers who need to verify consistent behavior across many clients
  • Teams wanting to add MCP conformance and regression testing to their CI/CD pipeline
  • Developers debugging OAuth/DCR/CIMD authorization flows
  • Developers previewing and iterating on Apps SDK / MCP app widget UIs locally
  • Developers auditing NPM dependencies within AI workflows
  • Teams performing supply chain security assessments
  • Users of Claude Desktop, Cursor, or VS Code
Not for
  • End users who just want to plug an MCP server into an assistant client (this is a developer debugging tool, not an end-user MCP server)
  • Users needing hosted-only features like skill sync or tasks in a fully offline environment, since the hosted app is HTTPS-only and some features are local-only
  • Users looking for an MCP server implementation that exposes tools to an AI assistant
  • Projects outside the NPM ecosystem (e.g., pure Python/Go)
  • Environments without network access to deps.dev, OSV.dev, and the npm registry
  • Scenarios requiring maintenance by an official upstream vendor
Required permissions
  • Network access to connect to target MCP servers (local STDIO process or remote HTTP/S endpoint)
  • The local/desktop build launches and communicates with local STDIO subprocesses, i.e. it can execute local commands
  • The OAuth debugger accesses and handles authorization credentials and token exchanges
  • A self-built Docker image binds to a local port (127.0.0.1 by default) requiring local port access
  • Network access to the NPM registry and external services (deps.dev, OSV.dev, OpenSSF, npms.io, GitHub)
  • Read access to workspace lockfiles (pnpm-lock.yaml, package-lock., yarn.lock) for cache invalidation
Risks and side effects
  • As a debugging tool it logs and displays full JSON-RPC messages and OAuth exchange details, so logs may contain sensitive tokens or credentials
  • Docker deployments that use `-p 6274:6274` instead of `-p 127.0.0.1:6274:6274` could expose the debugging port publicly
  • The hosted web app cannot be used for STDIO-only servers since it only supports HTTPS endpoints
  • The repository's license field is listed as NOASSERTION even though the README states Apache 2.0 — verify actual license terms before relying on this project
  • Third-party READMEs and changelogs are untrusted external content; they are wrapped in tags with _meta flags but should still be handled cautiously
  • Depends on availability and accuracy of external services
  • Batch requests are capped at 25 packages to prevent registry enumeration; larger sets require batching
  • Third-party open source project, not officially maintained by NPM or Anthropic
Supported clientsClaude Desktop, VS Code, Cursor
Tools019