The idea is sound — the specification fits in a context window, so fetching it exactly beats searching for it, and the version-aware templates matter when you are targeting a specific revision. But the repository carries a warning from its own author: it depends on the official llms.txt file, whose format no longer matches what this server expects, and it has not been updated for the latest specification. The author's recommendation is to use the official docs server and point at the schemas in the MCP repository instead.
A TypeScript server that serves the MCP specification and its documentation as resources and prompts, so a model works from the spec text rather than from what it remembers about MCP.
- The complete specification as one resource, plus separate ones for the JSON schema, architecture, base protocol, utilities, server features and client features
- Any supported version through resource templates — draft, 2024-11-05, 2025-03-26 and 2025-06-18, which is the default
- Explain — a prompt that answers a question about an MCP topic with the relevant documentation already loaded
- evaluate_server_compliance — a prompt that reviews a server repository against a chosen specification version
- Documentation beyond the spec: quickstarts, SDK docs, tutorials, debugging tools and community guidelines
- Content cached locally with a one hour lifetime, falling back to expired cache if a fetch fails
Nothing to authorize — no account, no key. Published to npm as mcp-advisor and run with npx; DEFAULT_SPEC_VERSION changes which version the plain resources return.
One command — npm install -g mcp-advisor