Zero-Trust Physics

Name: Zero-Trust Physics
Author: com.zerotrustphysics

MCP serverMCP

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

by com.zerotrustphysicshomepage ↗v0.15.2

Is this yours?

This record is unclaimed

Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.

Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"zero-trust-physics","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.

Claim this record

Observed by Wellknown

Evidence

Everything here was measured by our prober or read from a registry. Nothing is self-reported.

30-day availability51/51 checks ok

when	check	result	http	latency	detail
8 h ago	mcp initialize	ok	200	531 ms	server Zero-Trust Physics 0.15.2 · protocol 2025-06-18 · 18 tools
16 h ago	mcp initialize	ok	200	555 ms	server Zero-Trust Physics 0.15.2 · protocol 2025-06-18 · 18 tools
23 h ago	mcp initialize	ok	200	459 ms	server Zero-Trust Physics 0.15.2 · protocol 2025-06-18 · 18 tools
32 h ago	mcp initialize	ok	200	502 ms	server Zero-Trust Physics 0.15.2 · protocol 2025-06-18 · 18 tools
2 d ago	mcp initialize	ok	200	508 ms	server Zero-Trust Physics 0.15.2 · protocol 2025-06-18
2 d ago	mcp initialize	ok	200	460 ms	server Zero-Trust Physics 0.15.2 · protocol 2025-06-18 · 18 tools
2 d ago	mcp initialize	ok	200	505 ms	server Zero-Trust Physics 0.15.2 · protocol 2025-06-18 · 18 tools
3 d ago	mcp initialize	ok	200	497 ms	server Zero-Trust Physics 0.15.2 · protocol 2025-06-18 · 18 tools
3 d ago	mcp initialize	ok	200	589 ms	server Zero-Trust Physics 0.15.2 · protocol 2025-06-18 · 18 tools
3 d ago	mcp initialize	ok	200	460 ms	server Zero-Trust Physics 0.15.2 · protocol 2025-06-18 · 18 tools

Tools observed via MCP handshake

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 mod
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 "
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. p
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 decimal
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, who
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,
describe_solver — Describes one solver: inputs and bounds, outputs, invariants and tolerances, refusal names and meanings, the published reference, and a worked example. With for
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 rece
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_sea
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
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 aga
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,
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 er
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.235
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, e
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 t
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
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

Provenance

Where this record came from

Every source is kept verbatim. Field changes are logged as events.

Official MCP Registrycom.zerotrustphysics/verifier

first seen 15 d ago · fetched 29 h agoopen ↗

Field history (9 recent events)

5 d ago · declared · version → "0.15.2"
8 d ago · declared · version → "0.15.0"
12 d ago · declared · version → "0.14.1"
15 d ago · declared · homepageUrl → "https://zerotrustphysics.com"
15 d ago · declared · summary → "A physics verifier for Super Intelligence. Every answer comes with a cryptographic proof."
15 d ago · declared · protocols → ["mcp"]
15 d ago · declared · version → "0.10.0"
15 d ago · declared · description → "A physics verifier for Super Intelligence. Every answer comes with a cryptographic proof."
15 d ago · declared · publisherName → "com.zerotrustphysics"

Zero-Trust Physics

This record is unclaimed

Evidence

What the publisher says

Capabilities

Where this record came from