MCP RELEASE CHECK — GET YOUR CATALOG FILES

WHAT ARE THESE FILES?
They are JSON snapshots of the tool definitions advertised by your MCP server through tools/list. They describe names, descriptions, input/output schemas and behavior hints. They are not your server configuration, source code, API credentials, tool-call results or conversation history.

1. SAVE THE BASELINE
Connect to the previously approved release using your MCP client or MCP Inspector. Request tools/list and save the complete JSON response as baseline.json. Keep this snapshot before deploying changes. If the previous release is already gone and you have no saved catalog, run its old version in a suitable test environment; this app cannot reconstruct it.

2. SAVE THE CURRENT RELEASE
Connect to the candidate release using the same client identity, permissions and configuration. Request tools/list again and save its complete JSON response as current.json. Differences in permissions or feature flags can change discovery even when the code has not changed.

3. UPLOAD BOTH FILES
Use the baseline picker for baseline.json and the current-release picker for current.json. Verify your purchase email for a paid comparison. Download the HTML and JSON reports afterwards. The free synthetic sample is available without purchase.

MCP INSPECTOR: LOCAL STDIO SERVER
With Node.js installed, replace the example path with your actual server entry point:

npx @modelcontextprotocol/inspector node path/to/server/index.js

Open the URL printed by Inspector, connect, and use the Tools tab to inspect the tools exposed by your server. Save the complete tools/list JSON using the response/raw-JSON view available in your client version. A screenshot or a list of tool names is not enough. If your UI does not expose complete JSON, use Inspector CLI below. Do not click tools/call just to export definitions; listing does not require executing tools.

CLI EXPORT: LOCAL STDIO
Run in a terminal that can start your server:

npx @modelcontextprotocol/inspector --cli node path/to/server/index.js --method tools/list --format json > baseline.json

Repeat against the candidate release, changing the output filename to current.json. These are shell examples; use your actual server command and arguments. First-time npx execution can download Inspector from npm. Review the tool before running it. Keep server diagnostic logs on stderr so stdout remains JSON.

CLI EXPORT: REMOTE HTTP
For a server you are authorized to inspect:

npx @modelcontextprotocol/inspector --cli https://your-server.example/mcp --transport http --method tools/list --format json > baseline.json

Replace the example URL. If your server requires OAuth or other authentication, complete the supported Inspector/client authentication flow first. Do not paste bearer tokens into shell history or upload authorization headers. This app does not connect to the server for you. CLI and UI details can vary by Inspector version; the current official docs are linked below.

CHECK THE JSON
Open the file in a text editor. The accepted shape is {"tools":[...]} or a complete JSON-RPC response containing {"result":{"tools":[...]}}. Save UTF-8 JSON, not Markdown code fences, terminal banners, line-delimited logs or SSE event:/data: text. If the response is wrapped differently, extract the actual complete tools/list result and preserve each tool object in full.

PAGINATED SERVERS
If the result contains nextCursor, request the next tools/list page using that cursor through your MCP client. Continue until nextCursor is absent. Collect every page's tools entries, in order, into one {"tools":[...]} object. Do this separately for the baseline and current release. Remove nextCursor only after all pages are collected. Do not upload a single page or silently omit tools. Duplicate names or a catalog that still contains nextCursor are rejected. Do not assume a client has automatically collected all pages: inspect its output.

DOWNLOADABLE EXAMPLE
examples/baseline.json advertises get_order.order_id as a string.
examples/current.json changes it to an integer.
Expected finding: get_order, /inputSchema/properties/order_id/type, changed. This is a contract review finding, not proof that every client will break.
These files are synthetic demonstrations. They are not evidence about your own server.

LIMITS AND PRIVACY
Up to 50 tools per catalog. Keep the two JSON files below 60 KB combined to leave space in the 64 KiB request limit for metadata. Remove credentials, personal information and confidential content you are not authorized to share. Tool descriptions and schema examples may themselves contain sensitive data. Keep the contract fields you want compared; redacting them can change the report. Raw catalogs are sent to the service for analysis, not to an AI model, and are not stored by the app.

OFFICIAL REFERENCES (reviewed 30 October 2026)
Inspector quickstart: https://github.com/modelcontextprotocol/modelcontextprotocol/blob/main/docs/docs/2026-07-28/tools/inspector.mdx
Inspector CLI: https://github.com/modelcontextprotocol/modelcontextprotocol/blob/main/docs/docs/2026-07-28/tools/inspector/cli.mdx
Tools discovery and pagination: https://modelcontextprotocol.io/specification/2025-06-18/server/tools