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.

DimensionGEML MCP ServerAn MCP server for GEML documents, enabling block-at-a-time edits with validation.NPM Sentinel MCP ServerAI-powered NPM package analysis MCP server
FMRS68 / 100 · C79 / 100 · B
Reliability12 / 2012 / 20
Security and permissions14 / 2016 / 20
Maintenance13 / 2018 / 20
Documentation16 / 2018 / 20
Setup experience13 / 2015 / 20
Best for
  • Documentation workflows that have adopted GEML.
  • Collaborative authoring with AI agents or scripts where safety is required.
  • Software development workflows that rely on documentation or code skeletons.
  • Developers auditing NPM dependencies within AI workflows
  • Teams performing supply chain security assessments
  • Users of Claude Desktop, Cursor, or VS Code
Not for
  • Repositories that don't use GEML.
  • As a general-purpose file system tool.
  • Use cases requiring a network-accessible MCP server.
  • 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 and write access to files under the directory specified by --root, and only that directory.
  • Fetching packages on demand via npm/npx.
  • Ability to create and write .gemlhistory sidecar files inside the root.
  • 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
  • Misconfigured --root may cause unexpected changes, but writes outside the directory are explicitly refused.
  • Invalid document modifications are refused, but network access is needed for package installation.
  • History files may grow over time; tracking quotas is outside the root.
  • Vulnerable to misconfiguration of clients or tools; ensure the --root path is correct.
  • 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, Claude Code, Generic MCP clientClaude Desktop, VS Code, Cursor
Tools1219