MCP CheckCheck an MCP config before you run it
Paste an mcpServers block, one server object, or an install command. Each static check comes back as pass, warn or fail, with why it matters and how to fix it.
Result
Nothing scanned yet. Below is the result for the example in the box, so you can see the format.
files
0 fail, 3 warn, 1 pass, 0 info.
| Result | Check | Why | How to fix |
|---|---|---|---|
| Warn | Version is not pinned | @modelcontextprotocol/server-filesystem has no version, so the newest release is fetched and run at every launch. | Pin an exact version, for example @modelcontextprotocol/server-filesystem@X.Y.Z. Look up the current one on the package page and re-check it when you update. |
| Warn | -y skips the install prompt | With -y, npx downloads and runs the package without asking, every time. | Pin the version first; then -y is only auto-confirming a version you chose. |
| Warn | Gives access to a whole disk or home folder | A path of "/", "~" or a drive root lets the server read and usually write everything you can. | Pass only the specific project folder. |
| Pass | No secrets found in the config | No env values, headers or arguments matched a key pattern. This is a pattern check and can miss unusual keys. | Nothing to fix |