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.

DimensionMCPOExpose MCP tools as OpenAPI services instantly.NPM Sentinel MCP ServerAI-powered NPM package analysis MCP server
FMRS53 / 100 · D79 / 100 · B
Reliability8 / 2012 / 20
Security and permissions8 / 2016 / 20
Maintenance11 / 2018 / 20
Documentation13 / 2018 / 20
Setup experience13 / 2015 / 20
Best for
  • LLM applications and developers that need MCP tools over HTTP
  • Teams using OpenAPI tools, SDKs, or UIs
  • Deployments requiring multi-server configuration, hot reload, or OAuth 2.1
  • Developers auditing NPM dependencies within AI workflows
  • Teams performing supply chain security assessments
  • Users of Claude Desktop, Cursor, or VS Code
Not for
  • Clients that only need direct native MCP stdio communication
  • Deployments unwilling to manage API keys, network ports, or proxy security
  • Other protocols or integrations not documented in the source
  • 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
  • It must execute the specified MCP server command or connect to the specified SSE or Streamable HTTP endpoint
  • It must listen on the configured HTTP port
  • OAuth 2.1 may require browser authorization, a callback port, and, with file storage, write access to ~/.mcpo/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
  • The exposed HTTP service should use an API key; the README demonstrates API keys as startup arguments
  • The proxy makes MCP tools available to callers that can reach the HTTP service, so port and reverse-proxy settings require care
  • OAuth tokens may be stored under ~/.mcpo/tokens/; protect that directory in deployment
  • Commands, endpoints, and headers in the configuration affect proxy targets and credentials
  • 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 clientsOpen WebUIClaude Desktop, VS Code, Cursor
Tools019