Zero-Trust Physics

Ingested from the official MCP Registry

FastDrop pulled this entry from the official MCP Registry as com.zerotrustphysics/verifier and probed the endpoint. The maker did not submit it, so the outbound link is not endorsed and the description is not theirs.

If this is your server, claim the listing to edit it and take ownership. The registry index lists everything else still awaiting a probe.

Tools this endpoint exposes

Read directly from the endpoint on 13 Oct 2026. Not supplied by the maker.

• list_cards

  Every domain and card, each with one sentence, and count, how many there are.

• describe_card

  Inputs, units, bounds, step limits, reject names and meanings, advisory flags, frame slots, and worked examples for one pair.

• verify_step

  One anchored step. Same bytes as POST /verify_physics. On this open connection one address holds at most 1 physics permit at a time, and a solve, a dataset job and a run of more than 10000 steps are l

• run_trajectory

  One anchored run under a changing load. Same bytes as POST /run_trajectory. The size of the answer follows from the request: about 230 characters for each recorded state, plus the request as it was se

• verify_tape

  Check a run's seal. Short form, which needs only what is short: request is the run_trajectory request as it was sent (the answer's inputs), and run_seal is the seal its answer gave. The run is compute

• list_solvers

  Every field solver, each with one sentence, and count, how many there are.

• describe_solver

  Inputs and bounds, outputs, invariants and tolerances, refusal names and meanings, the published reference, and a worked example for one solver.

• solve

  One sealed solution. Same bytes as POST /solve. Send parameters, or example in their place: the name of a worked example describe_solver lists (example_solve, or a key beginning example_solve_), so a

Is this tool yours?

Claim this listing and we’ll verify ownership before handing it over.