πŸ”¬ Online MCP Inspector & Remote MCP Tester

Connect to any remote MCP endpoint and inspect the live JSON-RPC exchange β€” Streamable HTTP and legacy SSE supported.

Connection

Not connected.

β€”

Select a tool

Pick a tool on the left to inspect its schema and run it β€” or click a resource/prompt to read it.

Protocol Log

No traffic yet.

How to test a Streamable HTTP MCP endpoint

  1. Paste the endpoint URL (e.g. https://mcp.deepwiki.com/mcp) and hit ⚑ Connect & Initialize.
  2. The inspector sends an initialize JSON-RPC request with Accept: application/json, text/event-stream and stores the returned Mcp-Session-Id.
  3. It then calls tools/list (and resources/list/prompts/list when advertised) β€” pick a tool, fill the form, and run it.

Equivalent curl:

curl -X POST https://mcp.deepwiki.com/mcp \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json, text/event-stream' \
  -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-03-26","capabilities":{},"clientInfo":{"name":"inspector","version":"1.0"}}}'

Streamable HTTP vs SSE

Streamable HTTP (2025-03-26)Legacy HTTP + SSE
EndpointsOne URL for POST (+ optional GET stream)GET /sse + POST message URL
ResponsesJSON or SSE per-requestAlways via SSE stream
StatusCurrent spec β€” use thisDeprecated, still used by some servers

JSON-RPC error codes

CodeMeaningTypical fix
-32700Parse errorBody isn't valid JSON
-32600Invalid requestMissing jsonrpc/id/method
-32601Method not foundWrong method name or capability missing
-32602Invalid paramsTool arguments don't match inputSchema
-32603Internal errorServer-side failure
-32000…-32099Server-defined errors-32001 = unauthorized in many impls

Browser-based alternative to npx @modelcontextprotocol/inspector

The official @modelcontextprotocol/inspector CLI is excellent for local development, but this online MCP tester covers a different set of jobs β€” with zero install.

This online inspectornpx @modelcontextprotocol/inspector
Best forRemote HTTPS /mcp & /sse endpoints on the public internetlocalhost endpoints and local stdio server processes
SetupNone β€” paste a URL and connectRequires Node.js; spawns the inspector UI locally
Auth testingBrowser OAuth 2.1 (DCR / CIMD + PKCE S256), Bearer token & custom headersFull OAuth flow against localhost
SharingShare a link like /inspector?url=…&tool=… that restores the whole sessionSession lives only on your machine
TransportsStreamable HTTP (2025-03-26) and legacy HTTP+SSEstdio, Streamable HTTP and SSE

Rule of thumb: use this page to test a remote MCP endpoint or verify a Bearer-token header before wiring it into a client; use the CLI inspector when the server is a stdio process or only reachable on your own machine.

Common Streamable HTTP & SSE protocol errors

The two most-searched protocol errors and how to fix them:

client must accept both application/json and text/event-stream

HTTP 406. The Streamable HTTP spec requires every POST to carryAccept: application/json, text/event-stream β€” the server may answer either with plain JSON or an SSE stream. Add both MIME types to your client's Accept header:

curl -X POST https://<host>/mcp \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json, text/event-stream' \
  -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{...}}'

{"error": "server does not offer an sse stream at this endpoint"}

HTTP 400/404/405. Your client is using the legacyGET /sse handshake against a modern single-endpoint /mcp server. Switch the client's transport type to http / streamable_http(in Claude Code: re-add with claude mcp add --transport http <name> <url>), or use the server's dedicated legacy SSE URL if it still publishes one.

HTTP status cheat sheet

StatusMeaningFix
401OAuth requiredComplete the OAuth flow; see OAuth Debugger
404Wrong pathTry /mcp vs /sse vs /v1/mcp
405Method not allowedEndpoint may be SSE-only or disabled
406Bad Accept headerSend Accept: application/json, text/event-stream
410Endpoint removedLegacy transport retired β€” switch to /mcp
429Rate limitedBack off / add auth
5xxServer errorRetry; check provider status