MCP Inspector
Paste the URL of any Streamable HTTP MCP server and see the tools, schemas, and metadata it declares — right in your browser.
Inspect an MCP server
Enter the URL of a running Streamable HTTP MCP server. The request is proxied through Draftbase's server so it isn't blocked by browser CORS restrictions — the URL isn't logged or stored beyond handling this request.
OAuth sign-in redirects to the server's own login page. The resulting token is held only in this browser tab's session storage — never written to a database or log on Draftbase's side, and cleared once this page is closed.
How it works
This tool sends a standard MCP initialize request to the URL you provide, followed by a tools/list request, using the JSON-RPC 2.0 format the protocol defines. Both requests are proxied through Draftbase's server rather than sent directly from your browser.
That proxy step exists specifically to route around browser CORS restrictions: a server has to explicitly opt in to cross-origin browser requests, and most MCP servers today are built for CLI or desktop clients that never hit that restriction, so they never add it. Proxying server-to-server has no such requirement — it works against any server reachable over the public internet, whether or not that server was built with a browser client in mind.
Running MCP Inspector with npx
The official inspector runs locally: npx @modelcontextprotocol/inspector launches a local proxy plus a UI in your browser, and it’s the right choice for a stdio server since only a local process can spawn another local process. This page is the faster alternative when the server is already reachable over HTTP — paste the URL, skip the install and the terminal.
Browser-based vs. local inspection
A local inspector talks to a server directly, so it can reach anything on your machine or network, including a stdio server with no network listener at all. This tool trades that reach for zero setup: nothing to install, works from any device, but it can only reach a server exposed over public Streamable HTTP — a server sitting behind a firewall or on localhost is invisible to it.
Testing an MCP server before wiring it into an agent
Before pointing a real agent at a new server, confirm three things: it responds to initialize without an auth error, tools/list returns the tools you expect, and each tool’s input schema matches what you planned to send. Catching a broken schema here is a ten-second check — catching it after an agent has already tried and failed to call it is a debugging session. Both this and llms.txt are surfaces built for an AI reader rather than a person — one describing your tools, the other your pages.
Skip building your own MCP server
Draftbase ships a working MCP server out of the box, scoped to your content schema, so an AI agent can read and edit real entries instead of a test fixture.
Hobby is free, no card. Startup is $49/mo when you outgrow it. The price is on the pricing page, where prices go.
No migration quarter, no kickoff workshop. Define a template and ship something today.
Frequently asked questions
What is an MCP Inspector?
An MCP Inspector is a tool that connects to a Model Context Protocol server and shows what it exposes — its declared tools, each tool’s input schema, and basic server metadata — so you can verify a server works before wiring an AI agent to it.
Why did my inspection fail?
Most often the server requires auth — a 401 response means it needs a token. Click “Sign in with OAuth” to authenticate directly with the server (if it supports dynamic client registration), or paste a token you already have. Other causes: the URL isn’t a Streamable HTTP MCP endpoint, or the server isn’t reachable from the public internet (a local-only or stdio-only server won’t be).
How does “Sign in with OAuth” work, and is my token stored?
It runs the standard OAuth 2.1 + PKCE flow the MCP spec defines: Draftbase’s server discovers the target’s auth endpoints, registers a throwaway client, and redirects you to the server’s own login page. After you approve access there, the resulting access token is held only in this browser tab’s session storage — it is never written to a database or log on Draftbase’s side, and it’s cleared once you close the tab. The code exchange happens server-to-server (so it isn’t blocked by CORS either), but the token itself is relayed straight back to your browser, not kept.
Is my data sent to Draftbase?
The inspection request is proxied through Draftbase’s server — that’s what lets this tool reach servers that don’t send CORS headers for browser requests, which is most of them. The target URL and the server’s response pass through our infrastructure to render the result, but aren’t logged or stored beyond handling that one request. See the OAuth question above for how sign-in tokens specifically are handled.
Does this replace the official MCP Inspector CLI?
No — the official @modelcontextprotocol/inspector runs a local proxy and supports stdio servers, which this tool can’t reach since it only proxies public HTTP URLs. This tool is a fast, no-install check for any server reachable over HTTP.
More free tools on the tools page, or read the mcp guide on /mcp.