MCP server inspector
Paste an MCP tools/list answer and review the whole server at once. Finds what checking one schema at a time cannot: two tools described the same way, names that collide once case is ignored, one enum spelled two ways.
Your input is processed in this browser. It is not uploaded. A file or pasted rows go nowhere. A URL is fetched by your browser directly from the address you give it. Sharing creates a link containing the data you choose to include.
This link will contain
Anyone with the link can read this. Compression is not encryption.
What it does
A tool schema can be faultless on its own and still break the server it belongs to. Two tools whose descriptions say the same thing leave a model guessing which one to call. Two names that differ only by an underscore look like one name to anything that matches loosely. An enum spelled open in one tool and OPEN in the next teaches a model one spelling and fails the calls that expected the other.
This page reads a tools/list answer, JSON-RPC envelope and all, and reports in two layers: what is wrong between tools first, then each tool on its own under the same ten rules as the tool-schema linter.
What it does not do
It never scores how similar two descriptions are. Every description finding is an exact match after a stated amount of normalising, and the sentence says what was ignored, so you can read the pair and check the claim yourself. Safety annotations are optional in the MCP specification, so a server that declares none gets one note rather than one fault per tool. A clean run says what was checked and that nothing was found, which is a different and more honest claim than saying the server is fine.