Audit one mcp.json for what an agent config gives away — inline API keys, unpinned npx launches, p
144
Audit one mcp.json for what an agent config gives away — inline API keys, unpinned npx launches, plaintext remote servers, shell wrappers, auto-approved tools, whole-machine filesystem roots — with line numbers. The shipped sample config _fixtures/dirty.mcp.json (33 lines, five servers) returns 14 findings, 8 of them blocking.
docker run --rm -v "$PWD":/work getreadystack/mcp-config-audit /work/file
The same 18 rules as the VS Code extension, in a container. Mount a folder on /work.
--rules lists every ruledocker run --rm -e READYSTACK_LICENSE=<key> -v "$PWD":/work getreadystack/mcp-config-audit --dir /work --ci
Freelance application-security engineers commonly bill $100-$200 an hour; a single review hour costs more than three licences, and the config changes every time somebody adds a server.
Claude Code · Cursor · Windsurf · any MCP client - add to your MCP config:
{ "mcpServers": { "mcp-config-audit": { "command": "npx", "args": ["-y", "@readystack/mcp-config-audit", "--mcp"] } } }
Tools: check_text and check_file (free) · check_dir (licence; the full sweep is free for 7 days). The agent gets every finding with the line number.
- name: MCP Server Config Audit
run: npx -y @readystack/mcp-config-audit --dir . --ci
(container: docker run --rm -v "$PWD:/work" getreadystack/mcp-config-audit --dir /work --ci)
Try the full run free for 7 days — no key needed. Then one licence, 7-day refund, no questions. Set READYSTACK_LICENSE=<key> or run --license <key> once.
Content type
Image
Digest
sha256:ad52d4cc0…
Size
46.1 MB
Last updated
4 days ago
docker pull getreadystack/mcp-config-audit