Remote MCP · Endpoint

Agent Output Verifier by SarnAI MCP server

No. Agent Output Verifier by SarnAI answered an MCP handshake 5 hours ago.

UpLast checked 5 hours ago

Server URL

https://verify.sarnai.dev/mcp

The last check completed an MCP handshake.

Registry name
dev.sarnai/agent-output-verifier
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
78 ms
Tools exposed
2 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Independent schema and rule check of AI agent output before you pay. Signed attestation and receipt.
Listing
From the official MCP registry (active).
Recent checks of Agent Output Verifier by SarnAI
CheckedResultHandshake
5 hours agoHandshake completed78 ms
10 hours agoHandshake completed68 ms
2 days agoHandshake completed87 ms
4 days agoHandshake completed77 ms
7 days agoHandshake completed96 ms
9 days agoHandshake completed117 ms
11 days agoHandshake completed98 ms
13 days agoHandshake completed115 ms
15 days agoHandshake completed137 ms
18 days agoHandshake completed90 ms
20 days agoHandshake completed129 ms
21 days agoHandshake completed90 ms
23 days agoHandshake completed90 ms

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

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 Agent Output Verifier by SarnAI and makes no claim about it beyond what these checks measured.