MCP Toolset Analyzer
Inspect a pasted MCP tools/list response for protocol issues, documentation gaps, potential overlap, and serialized footprint.
MCP toolset input
Paste JSON or YAML. Analysis stays in this browser. The local limit is 768.0 KiB and 100 tools.
MCP definitionsToolset analysis
Ready to analyze
Paste MCP tools or load an example, then choose Analyze locally.
What a tools/list response contains
MCP servers expose their available tools through tools/list. This page accepts the result, a JSON-RPC envelope, a tools object, a bare array, and YAML equivalents. A continuation cursor marks the pasted result as partial; no server connection or next-page request occurs.
Protocol checks and quality suggestions
The analyzer validates each input and optional output schema with Draft 2020-12, checks tool names and duplicates, and checks declared annotations. For Streamable HTTP it reports invalid x-mcp-header annotations as errors; with unknown transport it explains the conditional impact. Internal documentation and overlap heuristics are labeled separately and never treated as MCP violations.
Overlap and footprint
Potential overlap uses shared action families, entity names, description tokens, and parameter names. Similar wording can be intentional, so findings invite review rather than automatic merging. Footprint uses minified JSON serialization of each pasted definition and exact UTF-8 byte counts; it does not claim provider-neutral token counts.
Privacy, source, and limits
Analysis runs in a browser worker. Definitions are not uploaded, stored, executed, or used to fetch icon or reference URLs. The page targets MCP 2026-07-28 and shows rule-pack version and source links alongside results. Toolsets are limited to 768 KiB, 100 tools, 60,000 parsed nodes, and a 20-second worker timeout.