trackmcp

MCP inspector

Inspect your MCP server without executing a tool

See the server identity, negotiated protocol, capabilities, and read-only catalogs returned by an HTTPS Streamable HTTP endpoint.

Browser-direct probe

Enter an MCP endpoint

Only HTTPS endpoints are accepted. Local, private IP, link-local, metadata, credential-bearing, and non-HTTP targets are rejected.

Privacy warning for custom headers

Use a short-lived test credential only. Headers stay in memory for this run, are sent directly by your browser, then cleared. They are never persisted or included in the report.

No tools are executed. Resources and prompts are catalogued only. The tester never calls resources/read or prompts/get.

Live progress

Read-only inspection timeline

Ready. Run a bounded browser-direct probe to see each phase outcome.
  1. 1
    Validate endpoint
  2. 2
    Validate request headers
  3. 3
    Negotiate MCP protocol
  4. 4
    Confirm initialized session
  5. 5
    Discover tools catalog
  6. 6
    Discover resources catalog when advertised
  7. 7
    Discover prompts catalog when advertised
  8. 8
    Check catalog quality
  9. 9
    Assemble bounded health report
Safety boundary: browser-direct HTTPS only, with bounded response bodies, JSON, timeline events, pagination, and total duration.