MCP Server Config Audit

Audits mcp.json for the mistakes AI-written agent configs carry: inline API keys, unpinned npx launches, plaintext remote servers, shell wrappers, auto-approved tools and filesystem roots. Runs entirely in your browser — nothing is uploaded.

Same engine as the VS Code extension, byte for byte.

Get the complete version $29

This page is the working piece. The full pack has everything below.

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

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.

Buy the full version — $29

Questions people ask

What does MCP Server Config Audit actually do?

It reads one mcp.json and reports every server entry that leaks a credential or grants more machine than it needs: an API key in env or headers, npx or uvx launching a package with no version, an untagged Docker image, a plaintext endpoint, a bash -c wrapper, an auto-approval list, a filesystem root of slash. On the shipped sample it returns 14 findings, 8 blocking, each with a line number.

Who is this for?

Developers who run AI coding agents in VS Code, Cursor, Windsurf or Claude Desktop and keep an mcp.json beside the code, platform engineers who review the configs their teams commit, and security reviewers who are handed an agent config and asked whether it is safe to merge. It assumes you wrote the file quickly, possibly with an assistant.

Why is a free tool not enough here?

A JSON linter or a schema check says the file is valid, and it is. Nothing in valid JSON knows that npx without a version resolves the newest published package at every launch, that alwaysAllow removes the confirmation step, or that a filesystem root of slash reaches your SSH keys. Secret scanners run after you have already pushed the file.

What is free and what costs money?

Free covers one file completely: all 18 rules, every line number, every replacement, in the editor and in the browser, with nothing withheld and no watermark. The paid version changes scope rather than depth. It audits every agent config in a repository and in user-scope locations at once, fails CI with a non-zero exit code, and exports a dated evidence report.

What would this cost done by hand?

Freelance application-security engineers commonly bill $100 to $200 an hour. Reading one mcp.json against credential hygiene, package pinning, transport and least-privilege questions takes a careful reviewer most of an hour the first time, and the file changes again the next time somebody adds a server to it.

Ask about this tool

One question, answered by the person who built it. Your email only if you want the answer sent.

Want the full version?
Enter your email and we send the download link.
ENDEJAESPT

Find a tool