Scan, lock, and gate your MCP servers — npm audit + lockfile + CI drift gate for the MCP era
Drift inferred · capture-to-capture
No drift recorded — single capability capture; advisories appear once its surface changes.
transport stdio · http counts 0 tools · 0 res
· 0 prompts
permission surface via code analysis
No tools enumerated yet for this server.
evidence-backed
findings quoted directly from the published source artifact — not inferred
code files: 30
filesystem 8
- fs package/dist/commands/config.js :1
import fs from 'node:fs'; - fs package/dist/commands/deps.js :1
import fs from 'node:fs'; - fs package/dist/commands/diff.js :1
import fs from 'node:fs'; - fs package/dist/commands/lock.js :1
import fs from 'node:fs'; - fs package/dist/commands/scan.js :1
import fs from 'node:fs'; - fs package/dist/context.js :1
import fs from 'node:fs'; - fs package/dist/oauth/store.js :1
import fs from 'node:fs'; - fs package/dist/version.js :1
import fs from 'node:fs';
shell / exec 1
- shell package/dist/commands/auth.js :1
import { spawn } from 'node:child_process';
network 1
- net package/dist/commands/auth.js :2
import http from 'node:http';
declared dependencies 10
- @modelcontextprotocol/sdk@^1.30.0
- cli-table3@^0.6.5
- commander@^15.0.0
- picocolors@^1.1.1
- mcp-agentgate-core@0.67.61
- mcp-agentgate-config-convert@0.14.0
- @types/node@^22.20.1
- typescript@^5.9.3
- vitest@^4.1.10
- zod@^4.4.3