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.

DimensionMCP HandlerEasily spin up an MCP server on Next.js, Nuxt, Svelte, and moreNPM Sentinel MCP ServerAI-powered NPM package analysis MCP server
FMRS57 / 100 · C79 / 100 · B
Reliability9 / 2012 / 20
Security and permissions11 / 2016 / 20
Maintenance12 / 2018 / 20
Documentation13 / 2018 / 20
Setup experience12 / 2015 / 20
Best for
  • Developers working in JavaScript/TypeScript with Fetch-compatible frameworks
  • Teams wanting one handler that serves both new and legacy MCP clients
  • Stateless, per-request deployments that do not need Redis sessions
  • Projects needing RFC 9728 / RFC 8414 compliant authorization surfaces
  • Developers auditing NPM dependencies within AI workflows
  • Teams performing supply chain security assessments
  • Users of Claude Desktop, Cursor, or VS Code
Not for
  • Frameworks built on Node.js IncomingMessage/ServerResponse such as Express without a Web Request adapter
  • Projects still on @modelcontextprotocol/sdk 1.x (use mcp-handler 1.x instead)
  • Deployments requiring the HTTP+SSE (2024-11-05) transport, removed in 2.x
  • Environments running Node.js below 20
  • 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
  • Access to the exposed HTTP route
  • Access to the authorization server that issues bearer tokens
  • Ability to configure protected resource metadata endpoints
  • Network access from the deployment to the authorization server when verifying tokens
  • 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
  • Exposing the MCP handler publicly without auth can let arbitrary callers invoke registered tools
  • Tool return content flows into the model context, so sensitive data could leak
  • 2.x is stateless, so GET/DELETE session operations return 405 and session-dependent clients may misbehave
  • Migrating from 1.x is a breaking change (full Standard Schema for inputSchema, removal of variadic methods, ctx.http?.authInfo), and improper upgrades cause runtime errors
  • 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, Cursor, WindsurfClaude Desktop, VS Code, Cursor
Tools119