Home / MCP registry index / com.zerotrustphysics/verifier

Zero-Trust Physics

com.zerotrustphysics/verifier in the official MCP registry. Endpoint https://mcp.zerotrustphysics.com/mcp.

The registry describes it as: A physics verifier for Super Intelligence. Every answer comes with a cryptographic proof.

We read its 18 tools on 2026-10-27. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.

A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.

Tools it advertises

list_cards describe_card compute_step run_trajectory verify_tape list_solvers describe_solver solve verify_solution run_dataset verify_dataset verify_receipt validate_series cite find_model find_flip design_run verify_step

Run this server? Show the check in your README

The badge reflects the latest weekly read: MCP tool check badge

Markdown
[![MCP tool check](https://lazaretto.dev/mcp-registry/com-zerotrustphysics-verifier/badge.svg)](https://lazaretto.dev/mcp-registry/com-zerotrustphysics-verifier)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.