Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@provespec-mcp find the TodoMVC spec and grade my implementation"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
MCP server over the public ProveSpec catalog — pull a specification, build against it, then grade what you built.
No account, no database, no desktop app. Specs are fetched over HTTPS and grading is computed locally, so this process holds nothing and stores nothing.
claude mcp add provespec -- npx -y provespec-mcpAny MCP client works. The raw command is npx -y provespec-mcp over stdio; Node 18+.
Related MCP server: swag
Tool | What it does |
| Every published spec, optionally filtered by category |
| Keyword search; |
| One spec as a readable outline, optionally scoped to a top-level group |
| The same spec as a flat, gradeable list of capability paths |
| Score an implementation: parity %, missing, partial, ungraded, beyond-spec |
| Compare two specs: what one asks that the other does not |
| Novelty check — does the catalog already cover the spec you are about to write |
| How to extract a specification from a codebase: granularity, stable keys, provenance |
| Check a draft spec before writing it — blocking errors and judgement warnings |
| How to author a comparison between two independently written specs |
| Check a draft comparison: keys resolve, verdicts legal, nothing silently skipped |
"Build me a URL shortener to the ProveSpec spec."
The agent calls spec_search → spec_get, builds against a real capability list instead
of a vague prompt, then calls spec_checklist → spec_grade to check its own work. The
gap list is the remaining work queue.
"Grade this repo against TodoMVC."
spec_checklist gives the agent the questions to answer; it reads the code and returns a
verdict per capability with a file reference as evidence. The report says what is missing,
what is half-built, and what exists beyond the spec.
Software specs put engine capabilities under AI and interface capabilities under UI, so parity can be asked per layer:
spec_get(slug: "todomvc", scope: "AI") → engine only
spec_grade(slug: "todomvc", scope: "UI", grades: [...])Asking "does the interface expose what the engine can do?" is the same relation pointed at two layers of one product.
Parity is fully-has / specified, matching the ProveSpec desktop app exactly.
Statuses: yes · partial · no · na.
Anything you leave ungraded counts as missing — silence is not credit.
na on either side (spec or grade) drops the capability from the denominator.
Grades that match no capability in the spec are reported as beyond the spec, not as defects — a build may legitimately do more than the spec asks.
Paths accept ["A","B"], "A > B" or "A/B", and match case- and space-insensitively.
Variable | Default | Purpose |
|
| Point at a mirror or a local site |
Responses are cached in memory for 10 minutes.
npm install
node test.mjs # pure logic, no network
node smoke.mjs # end-to-end against the live catalogMIT for this server. The specifications it fetches are CC BY 4.0 — see https://provespec.com.
This server cannot be deployed
Discover, search, invoke, and rate A2A (Agent-to-Agent) protocol agents.
Public read-only discovery of agent, model, training, task, and verification opportunities.
Find governed AI capabilities and verify signed receipts. Read-only, no account.
Free agent-service discovery, OpenAPI document checks, and receipt verification. No API key needed.
