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.

DimensionKindly Web Search MCP ServerWeb search plus robust content retrieval for AI coding tools and agentsNPM Sentinel MCP ServerAI-powered NPM package analysis MCP server
FMRS59 / 100 · C79 / 100 · B
Reliability9 / 2012 / 20
Security and permissions13 / 2016 / 20
Maintenance11 / 2018 / 20
Documentation14 / 2018 / 20
Setup experience12 / 2015 / 20
Best for
  • Users of AI coding tools who need full discussion/documentation context rather than just URLs
  • Clients that support MCP, such as Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI and Claude Desktop
  • Teams deploying a remote MCP service via Docker and Streamable HTTP
  • Environments that must egress through a proxy (HTTP/SOCKS5)
  • Developers auditing NPM dependencies within AI workflows
  • Teams performing supply chain security assessments
  • Users of Claude Desktop, Cursor, or VS Code
Not for
  • Users who cannot install a Chromium-based browser on the MCP client machine and mainly need arbitrary-site page_content extraction
  • Users who want to expose the remote HTTP port directly to the public internet (it is unauthenticated and unencrypted by default)
  • Users unwilling to provide any search provider API key
  • 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
  • Reads a search provider API key from the environment (one of Serper/SerpBase/Tavily/SearXNG/Sofya/You.com)
  • Optional GITHUB_TOKEN (can be read-only and limited to public repositories) for GitHub Issues/Discussions extraction
  • Launches a local headless Chromium browser process to fetch arbitrary web pages
  • Optional outbound network access via proxy env vars (HTTP_PROXY/HTTPS_PROXY/ALL_PROXY) or KINDLY_CHROME_PROXY
  • 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
  • HTTP transports are unauthenticated and unencrypted by default; exposing the port publicly is risky
  • get_content fetches any URL it is given and runs from the server's network location, which can reach internal resources
  • Browser reuse shares cookies, local storage, cache and user-agent state across requests
  • API keys stored in client config files may leak
  • Failed or timed-out fetches may return partial content or an error message
  • 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 Code, Codex, Gemini CLI, Claude Desktop, Cursor, OpenClaw, Antigravity, VS CodeClaude Desktop, VS Code, Cursor
Tools219