π¬ 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.
Not connected.
β
Pick a tool on the left to inspect its schema and run it β or click a resource/prompt to read it.
No traffic yet.
How to test a Streamable HTTP MCP endpoint
- Paste the endpoint URL (e.g.
https://mcp.deepwiki.com/mcp) and hit β‘ Connect & Initialize. - The inspector sends an
initializeJSON-RPC request withAccept: application/json, text/event-streamand stores the returnedMcp-Session-Id. - It then calls
tools/list(andresources/list/prompts/listwhen 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 | |
|---|---|---|
| Endpoints | One URL for POST (+ optional GET stream) | GET /sse + POST message URL |
| Responses | JSON or SSE per-request | Always via SSE stream |
| Status | Current spec β use this | Deprecated, still used by some servers |
JSON-RPC error codes
| Code | Meaning | Typical fix |
|---|---|---|
-32700 | Parse error | Body isn't valid JSON |
-32600 | Invalid request | Missing jsonrpc/id/method |
-32601 | Method not found | Wrong method name or capability missing |
-32602 | Invalid params | Tool arguments don't match inputSchema |
-32603 | Internal error | Server-side failure |
-32000β¦-32099 | Server-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 inspector | npx @modelcontextprotocol/inspector | |
|---|---|---|
| Best for | Remote HTTPS /mcp & /sse endpoints on the public internet | localhost endpoints and local stdio server processes |
| Setup | None β paste a URL and connect | Requires Node.js; spawns the inspector UI locally |
| Auth testing | Browser OAuth 2.1 (DCR / CIMD + PKCE S256), Bearer token & custom headers | Full OAuth flow against localhost |
| Sharing | Share a link like /inspector?url=β¦&tool=β¦ that restores the whole session | Session lives only on your machine |
| Transports | Streamable HTTP (2025-03-26) and legacy HTTP+SSE | stdio, 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
| Status | Meaning | Fix |
|---|---|---|
401 | OAuth required | Complete the OAuth flow; see OAuth Debugger |
404 | Wrong path | Try /mcp vs /sse vs /v1/mcp |
405 | Method not allowed | Endpoint may be SSE-only or disabled |
406 | Bad Accept header | Send Accept: application/json, text/event-stream |
410 | Endpoint removed | Legacy transport retired β switch to /mcp |
429 | Rate limited | Back off / add auth |
5xx | Server error | Retry; check provider status |