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.

DimensionDreamGraphA graph-governed architecture cognition layer for MCP-enabled software projects.NPM Sentinel MCP ServerAI-powered NPM package analysis MCP server
FMRS58 / 100 · C79 / 100 · B
Reliability8 / 2012 / 20
Security and permissions8 / 2016 / 20
Maintenance14 / 2018 / 20
Documentation16 / 2018 / 20
Setup experience12 / 2015 / 20
Best for
  • Developers whose codebases have grown beyond short-term memory, seeking AI that understands the system and explains changes.
  • Architects, system engineers, and product builders needing an architecture intelligence layer.
  • Projects using MCP clients like Claude Desktop or VS Code that benefit from persistent graph memory.
  • Developers auditing NPM dependencies within AI workflows
  • Teams performing supply chain security assessments
  • Users of Claude Desktop, Cursor, or VS Code
Not for
  • Users seeking a lightweight chat assistant rather than a complex knowledge graph system.
  • Projects preferring simple tooling without persistent state or architecture governance.
  • Environments without Node.js 20+ or a compatible shell.
  • 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 project files to build the knowledge graph (scan, enrich).
  • Read and write instance configuration and database (SQLite by default, optional PostgreSQL).
  • Execute `dg` CLI commands to manage daemon lifecycle.
  • VS Code extension permissions: file access, editor integration, daemon connection.
  • Potential network access (via HTTP daemon) and LLM API or local model server connections.
  • 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
  • Cognitive outputs are advisory until backed by governed evidence or explicit review; expired or rejected ideas remain inspectable but not authoritative.
  • Ensure instance configuration is secured, especially when using HTTP transport; do not expose the daemon on untrusted networks.
  • Plugins (when enabled) must be trusted; untrusted plugins may pose risks, but mechanisms for gating and trust banners exist.
  • Backup data before major upgrades, as migration scripts may be needed for older versions (e.g., pre-v8.2.6).
  • 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 CodeClaude Desktop, VS Code, Cursor
Tools019