MCP Server Inspector
Connect to a remote MCP server and discover its capabilities — tools, resources, and prompts. No install required.
Last updated Mar 2026
Enter the URL of a remote MCP server (Streamable HTTP or SSE transport). The server must be publicly accessible.
How the Inspector Works
The inspector sends standard MCP JSON-RPC requests to your server through a secure CORS proxy. It performs the MCP handshake (initialize → notifications/initialized), then queries all three capability types: tools/list, resources/list, and prompts/list. The raw JSON-RPC responses are available in the "Raw JSON" tab for debugging.
Requirements
- • Your MCP server must use Streamable HTTP or SSE transport (stdio servers run locally and cannot be tested remotely).
- • The server must be publicly accessible — the inspector connects from the cloud, not from your browser directly.
- • If your server requires authentication, the inspector will show the auth error in the response.
What You Can Learn
Use the inspector to verify your MCP server is working correctly before connecting it to Claude, Cursor, or other AI clients. Check that all your tools are properly listed with correct descriptions and input schemas. Compare what the server reports versus what you expect. Debug "tool not found" errors by confirming the tool name exactly matches what the server exposes.
Privacy
Requests are proxied through a Cloudflare Worker for CORS compatibility. The proxy does not store any data — it forwards your request to the MCP server and returns the response. No request bodies, server URLs, or responses are logged.