See what an MCP server can actually do.
MCP is written for machines to read. Paste a server URL and get the human version: every tool, resource and prompt laid out as readable documentation — with a form to call each one and see the real response.
Read-only exploration of public servers. Nothing is stored, and authenticated servers aren't supported yet.
Try one of these
These are third-party servers listed for convenience. Availability and behaviour are outside our control.
How it works
-
1
Handshake
Your browser runs the MCP
initializeexchange and asks the server to list its tools, resources and prompts. -
2
Render
Each tool's JSON Schema becomes a documented parameter list — types, defaults, constraints and descriptions — instead of a wall of JSON.
-
3
Call it
Fill in the form, hit Execute, and read the response rendered as text, images or structured data. The raw JSON-RPC is always one click away.
A small Cloudflare Worker relays the requests, because MCP servers don't send CORS headers a browser will accept. It passes bytes through and keeps no state.