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.

DimensionVictoriaMetrics MCP ServerOfficial VictoriaMetrics MCP server for seamless integration with VictoriaMetrics API and documentation.NPM Sentinel MCP ServerAI-powered NPM package analysis MCP server
FMRS69 / 100 · C79 / 100 · B
Reliability10 / 2012 / 20
Security and permissions15 / 2016 / 20
Maintenance16 / 2018 / 20
Documentation15 / 2018 / 20
Setup experience13 / 2015 / 20
Best for
  • Developers and SREs using VictoriaMetrics for monitoring and observability.
  • Engineers who want to leverage AI assistants to simplify metric queries and operations.
  • Teams needing quick access to documentation and troubleshooting guides.
  • 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 do not use VictoriaMetrics; this server is not suitable for other monitoring systems.
  • Scenarios requiring write or modify operations, as the server only supports read-only APIs.
  • Environments sensitive to resource consumption, as the embedded documentation vector database may increase memory and CPU usage.
  • 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
  • Read access to VictoriaMetrics instance APIs (query, list metrics, export data, etc.).
  • If using Cloud mode, access to VictoriaMetrics Cloud API key.
  • Network access to connect to the VictoriaMetrics instance or Cloud service may be required.
  • 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
  • Need to carefully manage API tokens to avoid leaking sensitive data.
  • AI-generated queries and configurations may contain errors; should be verified before use in production.
  • The server may consume significant resources, especially when loading the documentation vector database; can save resources by disabling the documentation tool.
  • 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, Claude Code, Codex, VS Code, Zed, JetBrains IDEs, WindsurfClaude Desktop, VS Code, Cursor
Tools3019