Agent Verifier
guru.packet/agent-verifierVersion 1.0.0Test and debug your AI agent's Web Bot Auth (RFC 9421) signature: is it valid, and what to fix?
Status
Responds590 msAnswered our handshake without sign-in.- Last checked
- Nov 14, 2026, 14:32 UTC
- Latency
- 590 ms
- Remotes responding
- 1 of 1
- Sign-in
- No sign-in
- Hosting
- EU hosting detected (detected, not a legal statement)
- Registry data as of
- Nov 14, 2026, 22:14 UTC
Data from the official MCP Registry, checked by run.zero. How we check
Connect
Streamable HTTP
https://fp.packet.guru/api/v1/mcpResponds590 msNo sign-in
Claude Code
claude mcp add --transport http agent-verifier https://fp.packet.guru/api/v1/mcpClaude Desktop and claude.ai
Settings > Connectors > Add custom connector
Name: agent-verifier
Remote MCP server URL: https://fp.packet.guru/api/v1/mcpCursor
{
"mcpServers": {
"agent-verifier": {
"url": "https://fp.packet.guru/api/v1/mcp"
}
}
}VS Code
code --add-mcp '{"name":"agent-verifier","type":"http","url":"https://fp.packet.guru/api/v1/mcp"}'Built your own server? run.zero hosts MCP servers on European infrastructure.
Tools
1 tools
Read-only | Idempotent | Open world | ||
|---|---|---|---|---|
self_check_web_bot_authReports 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. | No | Yes | Yes | No |
Details
- Registry status
- Active
- Published
- Oct 1, 2026
- Updated
- Oct 1, 2026
- Repository
- Not given
- Categories (suggested)
- Developer toolsSuggested categories are assigned automatically from the registry text and may be wrong. Verified operators can correct them.
- GDPR
- Not declared