MCP tools

Generated from src/mcp/server.ts by npm run parity. The server is the only source; this page is never edited by hand, because a hand-written copy of a tool list drifts and nothing notices.

This package ships an MCP server as the bin zeropoint-mcp, exposing 15 tools. It is the surface an agent reaches first, and until this page existed it was documented nowhere on the site.

npx zeropoint-mcp

tool	what it answers
zeropoint.fold	Fold two seeds into a content-addressed pair (toUuid/merge).
zeropoint.vortex	Vortex fold validity + stroke gateways.
zeropoint.contentUuid	JCS→SHA-256→uuidv8 content address for an object.
zeropoint.verify	Verify stored uuid matches recomputed content-uuid.
zeropoint.digitalRoot	Kernel digital root (0→9).
zeropoint.developmentVortex	Double-torus development vortex for a wave phase.
zeropoint.importGraph	Computed a432.* import/export self-ref census (content-uuid + merkleFold). Tip only — not a hand inventory.
zeropoint.criteria	The six predicates that gate a release, plus the one only reported: how many conditions each meets, and what would refute each. The real-time one MEASURES, so its verdict is a property of this machine.
zeropoint.seals	Every theorem this repository states that carries a predicate which RUNS, and whether it holds right now. A seal is recomputed on each call; nothing here is remembered.
zeropoint.claims	The claim ledger: every effect claim the corpus makes and the theorem or declared axiom it is bound to, with what that binding establishes and what it does NOT. Answers "what does this package claim, and what backs it".
zeropoint.selfNext	Next self-develop tip from planTrinity/audit. If development stops, gaps in self-development exist.
zeropoint.quantumRun	Run a Clifford circuit (h, s, x, z, cnot) on a stabilizer tableau and measure qubits. Polynomial in the qubit count rather than exponential, so hundreds of qubits are reachable — the same circuits a state vector cannot hold past about 30. Each measurement reports whether the outcome was DETERMINED by the state or genuinely undetermined; supply coins for the latter. No T gate: this is the Clifford fragment, which is exactly the fragment that is classically cheap.
zeropoint.quantumExact	Run a Clifford+T circuit (h, s, t, tdg, x, z, cnot, cz) with NO FLOATING POINT and return exact probabilities. Amplitudes live in the ring generated by the eighth root of unity, so T is exact rather than absent or approximated. Each probability comes back as (p + q*sqrt2)/2^scale with integer p and q: Clifford-only circuits give q=0 and a rational, and any T makes it irrational — H T H on |0> is exactly (2 + sqrt2)/4. Arbitrary-angle rotations are absent, not approximated.
zeropoint.quantumCapacity	What this quantum computer costs and where it stops, measured rather than claimed: the axes that were measured, the ones that were NOT, which algorithms are identified by their method rather than their answer, and the oracle-call counts. No quantum advantage is claimed anywhere — simulating one quantum query costs 2^n classical evaluations, and every measurement says so.
zeropoint.quantumAgrees	What qpu.uuidna.com serves about its quantum processing unit, recomputed by instruments that never read its source: the exact simulator for the Bell, GHZ and product states, the Shor of this package for the factorisation of 91, and the Lean kernel on the recording machine for the served proof, plus the exhaustive Shor sweep of this package sent pair by pair to that QPU and compared arm by arm. Per-claim agreement as recorded in src/verification/qpu-agrees.json and qpu-shor-agrees.json; nothing is fetched at call time.

The same work through the library

The 23 importable entry points cover far more than the 15 tools do — the tools are a deliberate selection of what an agent should reach for, not the whole surface. Nothing here claims the two are equivalent.

• zeropoint-node
• zeropoint-node/kernel
• zeropoint-node/kernel/import-graph
• zeropoint-node/0
• zeropoint-node/security
• zeropoint-node/security/threat-analysis
• zeropoint-node/security/tomography
• zeropoint-node/security/post-quantum
• zeropoint-node/integrity
• zeropoint-node/verification
• zeropoint-node/mcp
• zeropoint-node/quantum
• zeropoint-node/simple
• zeropoint-node/navigation
• zeropoint-node/cmyk
• zeropoint-node/kabbalah
• zeropoint-node/sacred-geometry
• zeropoint-node/electric-flow
• zeropoint-node/math-constants
• zeropoint-node/a432-math
• zeropoint-node/wave-energy
• zeropoint-node/mobius-circuit
• zeropoint-node/a432-i

Claims and how to disagree with them

Every claim this package makes carries the command that computes against it:

npm run refute