Certified MCP registry
Every MCP server on this list was driven, over its own stdio, through the fixed NativeCAD conformance suite — primitives, boolean volume identity, a blend, a STEP round trip that has to come back watertight, a refusal vocabulary, and a tool-schema lint — and passed every required case. Each entry quotes the hash of a conformance manifest counter-signed with the kernel release key, which anyone can verify offline.
| Server | Version | Kernel | SDK | Certified | Manifest |
|---|
Verifying an entry yourself
The runner and the public keys are in the repository; the private signing key is not. Anyone can re-run the suite against any server, and anyone can check that a manifest we published is intact and was signed by us:
node tools/conformance/run.js run --name my-mcp -- node path/to/server.js node tools/conformance/run.js verify conformance.json
The rules
- Certification is per name and version. A minor bump means a re-run.
- An entry names the kernel version it was certified against. A server certified against an older kernel stays listed and stays honest — it says which one.
- A listing can be withdrawn. See
docs/CERTIFICATION.mdfor what triggers that.