Browser-based tools for anyone building or evaluating an MCP server. No install, no signup, no rate-limited API key.
Paste an MCP server URL and see every tool, resource and prompt it exposes, with full schemas and the raw request log. Nothing to install.
Check that your MCP server actually works. Paste the URL and get a pass/fail report on the connection, the handshake, the transport and the tools it advertises.
Before you point an agent at an MCP server, see what it is asking for. Graded A–F on transport, authentication, tool-poisoning markers and dangerous parameters.
Tool definitions are sent on every request, not once. Paste your MCP server URL to see how many tokens that is, which tools are the heaviest, and what it costs.
Paste an OpenAPI document and get MCP tool definitions and a working Python server scaffold. Everything runs in your browser — your spec is never uploaded.
When an agent calls the wrong tool, the descriptions are usually why. Paste your MCP server URL for a review of every tool description and input schema, with suggested rewrites.
See what your MCP server looks like as a demo your customers could actually use. Paste the URL and we generate the whole page — overview, example conversations and tools — in about a minute.
Pick your client and get an MCP config it will actually read — correct file, correct root key, correct transport. Ten clients, ten different answers.
Most broken MCP configs are valid JSON, which is exactly why nothing tells you they are wrong. Pick your client and find out what it will actually do with your file.
Paste a config from any MCP client and get it back in the format another one reads — including the format changes nobody documents.
Eight languages, eight SDKs at very different levels of maturity, and one working example each. Pick yours.
Check whether your MCP server actually answers on the HTTP+SSE transport — and whether that is still enough for the clients you care about.
Check whether your MCP server answers on streamable HTTP, the transport current clients try first and some no longer fall back from.
Find out what an unauthenticated client sees when it connects — whether your server requires OAuth, and whether it says so in a way clients can act on.
Connect to your MCP server with no credentials at all and see exactly what it hands over. It is rarely what people assume.
Which revision of the Model Context Protocol does your server actually negotiate? Pick the one you care about.
Inspecting proves your server works. A live playground shows prospects what it does.