Redocly has shipped the first tool I have seen that writes an MCP server down where humans can read it. In Document your MCP server with introspect-mcp, the company introduces an experimental command in the Redocly CLI that connects to a running Model Context Protocol server, asks it what it exposes, and records the answer as an x-mcp extension inside an ordinary OpenAPI description. The framing is the right one: “AI agents discover all of it at runtime, but the humans evaluating your API usually can’t, because that surface lives only in the server code.” Against the reference server the command finds 13 tools, 4 prompts, and 7 resources under protocol version 2025-06-18, connecting over Streamable HTTP and falling back to HTTP plus SSE for older servers.
There are no vendor numbers to discount, and the design decisions are what make it worth reporting. The command updates the description in place, leaving info, paths, servers, and components untouched and rewriting only the x-mcp block, so the tags, security schemes, and examples a human added survive a refresh. “Once x-mcp is in the description, it’s regular OpenAPI: lint it, bundle it, version it in Git.” And the –check flag turns the whole thing into a drift test: it compares the file with what a fresh introspection would produce, writes nothing, and exits with code 1 when they differ, which is exactly the shape a CI gate should have. Redocly is honest that this is experimental and asks for feedback. The idea underneath is not experimental at all. An MCP server is an API surface, and API surfaces belong in a contract a human can review and a catalog can read.
That last clause is the one the catalog has a stake in. The Redocly provider page lists 16 API pages, and the post touches two of them directly: the Redocly CLI, where introspect-mcp lives alongside the linting, bundling, and Arazzo tooling, and Redocly Realm, which renders the resulting x-mcp block as reference documentation. The MCP server dimension is lit on Redocly’s Agent Readiness score, and so are agent skills and the well-known catalog, which puts Redocly in the 2.7% of providers that publish a discoverable catalog at a well-known location. An x-mcp block in an OpenAPI file is something apis.io should be reading as a pointer type, and this post is the prompt to add it.
The Kin Score is 75.5, exemplar band, carried by access clarity at 100.0 and operational transparency at 92.1, with contract quality at 69.0 and contract governance at 43.2. The Agent Readiness score is 33.1, agent-ready, and the gap is the one the post is about from the other side. Agentic access is unlit. Redocly has just shipped the tool that makes an MCP server’s surface legible to a human reviewer, and the catalog has no profile of what an agent can do across Redocly’s own 16 APIs, which operations act and which only read. Protected resource metadata, dynamic client registration, and delegated identity are unlit as well, so an agent that found Redocly’s MCP server could not register itself to use it. The company has written the introspection. The record is still waiting for the introspection to be run on the company.