Remote MCP · Endpoint

Agent Verifier MCP server

No. Agent Verifier answered an MCP handshake 43 minutes ago.

UpLast checked 43 minutes ago

Server URL

https://fp.packet.guru/api/v1/mcp

The last check completed an MCP handshake.

Registry name
guru.packet/agent-verifier
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
335 ms
Tools exposed
1 tool
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Test and debug your AI agent's Web Bot Auth (RFC 9421) signature: is it valid, and what to fix?
Listing
From the official MCP registry (active).
Recent checks of Agent Verifier
CheckedResultHandshake
43 minutes agoHandshake completed335 ms
3 days agoHandshake completed336 ms
12 days agoHandshake completed324 ms
13 days agoHandshake completed317 ms
14 days agoHandshake completed381 ms
15 days agoHandshake completed302 ms
16 days agoHandshake completed406 ms
17 days agoHandshake completed589 ms
18 days agoHandshake completed429 ms
19 days agoHandshake completed347 ms
22 days agoHandshake completed343 ms
25 days agoHandshake completed336 ms
27 days agoHandshake completed409 ms
29 days agoHandshake completed291 ms

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

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