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.

DimensionGitGuardian MCP ServerBring GitGuardian secret detection and incident management into your AI agentNPM Sentinel MCP ServerAI-powered NPM package analysis MCP server
FMRS52 / 100 · D79 / 100 · B
Reliability8 / 2012 / 20
Security and permissions12 / 2016 / 20
Maintenance11 / 2018 / 20
Documentation13 / 2018 / 20
Setup experience8 / 2015 / 20
Best for
  • Teams already using GitGuardian SaaS (US/EU) or a self-hosted instance
  • Developers who want secret scanning, incident triage, and remediation inside their IDE or chat client
  • Teams that want to automate secret remediation via pull requests
  • Users of MCP clients that support type: http and can complete an OAuth flow
  • CI/CD, scripts, or airgapped environments that need local stdio with a PAT
  • 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 GitGuardian and do not want to connect to its API
  • Users limited to older MCP clients without type: http support who cannot use the local stdio fallback
  • Users expecting the server to work with no authentication or scope configuration
  • Hosted-service users who do not want requests to transit mcp.gitguardian.com (they should self-host instead)
  • 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
  • Requires a GitGuardian access token (OAuth or PAT); the exposed tool set is determined by the token's OAuth scopes
  • Local stdio mode uses the GITGUARDIAN_PERSONAL_ACCESS_TOKEN environment variable
  • Self-hosted OAuth proxy mode proxies /authorize, /token, and /register to your GitGuardian dashboard
  • PAT lifetime defaults to 30 days and is configurable via GITGUARDIAN_TOKEN_LIFETIME
  • The server defaults to read-only-leaning permissions
  • 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
  • MCP servers are an emerging technology; agents act on your behalf and under your responsibility
  • In hosted mode, requests transit mcp.gitguardian.com in addition to api.gitguardian.com
  • Token scopes determine which tools the agent can use; overly broad scopes increase blast radius
  • Code-fix automation opens pull requests, so agent actions should be reviewed
  • Browser-driven OAuth in stdio mode is deprecated and stores the PAT on disk; that code path will be removed in a future release
  • 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 clientsCursor, Claude Desktop, Claude.ai, Windsurf, ZedClaude Desktop, VS Code, Cursor
Tools419