MCP config checker

Short answer: paste your Claude Desktop, Cursor or VS Code MCP config and this page matches each server against our test results (299 listings, data as of 2026-11-11): status, last test date, tool-call test, deprecation and published advisories.

Privacy. Your config is read in this browser tab only. It is never uploaded, logged or sent anywhere. The page makes one request: it downloads our public directory file (/data/config-check.json) before you paste anything. You can check this in your browser's network tab, or load the page and then go offline.

Building a new config instead? Use the MCP config generator. Checking one npm package? Use the freshness checker.

Loading our directory file...

Your MCP config (JSON or JSONC)

Remove API keys and tokens before pasting. Values under env and headers are never shown here, only their names.

Check config

How matching works

• npm: npx, bunx or pnpm dlx plus the exact package name (version pins are compared with the version we tested).
• PyPI: uvx, pipx run or uv tool run, including --from.
• Remote: the url / serverUrl field or mcp-remote <url>, matched to the endpoint we probed. Shown as remote, not tested from your config.
• GitHub repo references, and ghcr.io Docker images (probable match).
• Exact matches only. When several listings share a package or repo, all of them are shown and none is picked.