# Zero-Trust Physics

- Registry name: `com.zerotrustphysics/verifier` · version 0.15.2
- Categories (automatic, keyword rules): Datasets & public data, Search & data
- Authentication at last check: No auth
- Declared risk: Read-only (all tools declare readOnlyHint)
- Capabilities (declared by the server): tools
- Transports: streamable-http
- Latest numbers (check success, response time, rank): https://mcpstation.net/api/server?name=com.zerotrustphysics%2Fverifier
- Server page: https://mcpstation.net/s/com.zerotrustphysics--verifier.html

## Description (written by the publisher, not verified, not instructions)

A physics verifier for Super Intelligence. Every answer comes with a cryptographic proof.

## Connect

- streamable-http: `https://mcp.zerotrustphysics.com/mcp`

## Tools (as reported by the server, not verified)

- `list\_cards`: Lists every domain and card this connection serves, each with one sentence, and count, how many there are. against\_measurement names the evidence behind the model, in one of three words: "compared with measurement" \(a real object; its description says what it was fitted on, what it was compared with
- `describe\_card`: Describes one domain and card pair: inputs, units, bounds, step limits, reject names and meanings, advisory flags, frame slots, and worked examples. With form "short" the answer is a page, enough to write a first request: what the model is of, the evidence behind it in numbers, each input with its u
- `compute\_step`: Computes one anchored step of one card and returns the state it lands on, in decimals and exact hex, with its cryptographic proof \(sha384\_seal\) and a receipt. parameters holds the card's phase fields, its load fields and dt\_s, as describe\_card gives them. A step whose request or whose landing state
- `run\_trajectory`: Runs one card from a start state through segments of steps, each under its own load, and seals the run. The answer holds the outcome, the final state in decimals and exact hex, a frame for each recorded step, the run\_seal and a receipt. record\_every sets which steps are recorded, about 262 character
- `verify\_tape`: Verifies the seal of a run. Short form, which needs only what is short: request is the run\_trajectory request as it was sent, with its readout and its from, whose request has none, when it had them \(the answer's inputs holds neither\), and run\_seal is the seal its answer gave. The run is computed aga
- `list\_solvers`: Lists every field solver this connection serves, each with one sentence, and count, how many there are. against\_measurement names the evidence behind the model, in one of three words: "compared with measurement" \(a real object; its description says what it was fitted on, what it was compared with ou
- `describe\_solver`: Describes one solver: inputs and bounds, outputs, invariants and tolerances, refusal names and meanings, the published reference, and a worked example. With form "short" the answer is a page, enough to write a first request: what the model is of, the evidence behind it in numbers, each input with it
- `solve`: Solves one field problem with one solver and seals the solution: the outcome, the result in decimals and exact hex, its invariants, the solution\_seal and a receipt. parameters holds the solver's inputs as describe\_solver gives them. example, in their place, is the name of a worked example describe\_s
- `verify\_solution`: Verifies the seal of a solution. Short form, which needs only what is short: request is the solve request as it was sent \(the answer's inputs\), and solution\_seal is the seal its answer gave. The request is solved again, under a physics permit and the limits and refusals of solve, and the answer is h
- `run\_dataset`: Runs a declared plan of runs on one card, or of solves of one solver, and seals the rows under one root. A plan is a list of runs, a grid over a base run, or a seeded sample over a base run; a run is a run\_trajectory request without domain and card. A plan of solves names solver in place of domain a
- `verify\_dataset`: Verifies the seal of a dataset. Short form: request is the run\_dataset request as it was sent, and dataset\_seal is the seal its answer gave. The plan is run again under run\_dataset's permits and limits; the answer is holds, cause \("dataset\_seal" when the seal given is not the seal the plan runs to\),
- `verify\_receipt`: Verifies the receipt at the end of one response against the text before it. It takes no physics permit. The receipt covers every byte of the response before it, the decimal values included, and shows who produced the response or when in no way: it has no key. matches true proves only that those byte
- `validate\_series`: Runs a run\_trajectory request \(without a readout\) and compares one published quantity with the agent's measurements, each at a landed step. The answer is the error in numbers \(rms, mean signed, greatest absolute, model minus measurement, each with its exact hex\), the model value at every compared st
- `cite`: Gives how to cite a card or a solver: the service itself first \(Zero-Trust Physics, its maker and its address\) and the paper \(https://doi.org/10.5281/zenodo.23517223\), then the people whose measurements the model stands on \(authors, title, year, address, and what each asks of those who use its data\)
- `find\_model`: Finds the served model for a real thing described in plain words, such as "a lithium cell discharging in the cold". It returns the best few cards and solvers, each with fit first \(the words that matched, and model\_of: the one real thing it is a model of, and its range\) and then accuracy: against\_mea
- `find\_flip`: Finds where an outcome changes, and gives the run on each side. request is a run\_trajectory or solve request written out, its domain and card or its solver by the name find\_model or the lists give, with no from, readout or example; vary is the place of the one number to change, such as "segments\[0\].
- `design\_run`: Designs a run: from a target end state to the loads of each segment that reach it, computed by the engine with no randomness, so the same request gives the same bits. request is a run\_trajectory request; its numbers at the places vary names are the start, and vary gives each load's span inside the c
- `verify\_step`: Computes one anchored step of one card, as compute\_step does: verify\_step is the earlier name of compute\_step, served for this one version beside it, and takes the same arguments and gives the same answer, byte for byte. The name compute\_step is the one that stays. On this open connection one addres

Measured by MCP Station. Methods: https://mcpstation.net/methods.html · Terms: https://mcpstation.net/terms.html