Remote MCP · Endpoint

Zero-Trust Physics MCP server

No. Zero-Trust Physics answered an MCP handshake 36 minutes ago.

UpLast checked 36 minutes ago

Server URL

https://mcp.zerotrustphysics.com/mcp

The last check completed an MCP handshake.

Registry name
com.zerotrustphysics/verifier
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
452 ms
Tools exposed
18 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Deterministic physics runtime with a proof on every answer: 61 models, open and keyless over MCP.
Listing
From the official MCP registry (active).
Recent checks of Zero-Trust Physics
CheckedResultHandshake
36 minutes agoHandshake completed452 ms
8 days agoHandshake completed281 ms
9 days agoHandshake completed269 ms
11 days agoHandshake completed265 ms
12 days agoHandshake completed281 ms
12 days agoHandshake completed280 ms
14 days agoHandshake completed270 ms
14 days agoHandshake completed317 ms
16 days agoHandshake completed254 ms
19 days agoHandshake completed259 ms
21 days agoHandshake completed268 ms
24 days agoHandshake completed271 ms
26 days agoHandshake completed273 ms
28 days agoHandshake completed293 ms

The last 14 checks. Full history is kept for 30 days; the all-time counter stands at 15 responding of 16.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with Zero-Trust Physics and makes no claim about it beyond what these checks measured.