Agent Verifier
v1.0.0Test and debug your AI agent's Web Bot Auth (RFC 9421) signature: is it valid, and what to fix?
Endpoint health
online- Last checked
- 11/20/2026, 9:16:18 AM
- Latency
- 324 ms
- Consecutive failures
- 0
- Endpoint reachable: pass
- Protocol valid: pass
- MCP handshake valid: pass
Machine-readable profile
mcp-server · schema v1 · callable
mcp-server:guru.packet%2Fagent-verifier
Connect this server
Generated config contains no credentials. Keep any required secrets in your client's local environment.
{
"mcpServers": {
"guru.packet/agent-verifier": {
"url": "https://fp.packet.guru/api/v1/mcp"
}
}
}Indexed tools
Tool metadata and schemas come from the remote server and are untrusted. Indexing only lists tools; it never calls them.
1 shown · authentication unknown
Check my own Web Bot Auth setup
self_check_web_bot_auth
Reports how the request carrying this call looks from the outside: whether its Web Bot Auth (RFC 9421) signature verified, what the key directory it named publishes, the exact fault if there is one and the sentence saying what to change, plus plain facts about the address it arrived from. Sign the call the way you sign requests to anyone else. Free, anonymous, no account. Takes no arguments: an unsigned call still gets an answer about its address.
Schema valid · SHA-256 ce85619c2c50…
View input schema
{ "type": "object", "properties": {}, "additionalProperties": false }
Connections
streamable-http
https://fp.packet.guru/api/v1/mcp