Agent Verifier
Server Details
Test and debug your AI agent's Web Bot Auth (RFC 9421) signature: is it valid, and what to fix?
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 1 tool
There is only one tool, so there is no possibility of confusing it with another. Its purpose (self-diagnosing how the current request looks from the outside, including Web Bot Auth signature verification) is unambiguous.
A single snake_case name, self_check_web_bot_auth, that clearly encodes subject (web bot auth) and action (self check). With one tool there is no convention to break.
One tool is thin against the 3-15 heuristic, but the server's scope is a single diagnostic operation, so a solo tool is genuinely well-matched rather than an oversight. It is not a trivial stub; it returns verification status, key directory facts, faults, and address data.
For its stated narrow purpose the tool covers the full diagnostic loop: it works signed or unsigned and reports verification result, directory contents, fault text, remediation sentence, and caller-address facts. No obvious dead ends, though there are no companion operations (e.g. re-checking after a config change or inspecting a different request).
Available Tools
1 toolself_check_web_bot_authCheck my own Web Bot Auth setupARead-onlyIdempotentInspect
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.
Inputs: no named parameters. Returns: id, ip, geo, meta, +4 more
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Generates deterministic webhook HMAC-SHA256 fixtures and optionally verifies a supplied signature...
Debug webhooks from your AI agent: inspect and replay captured webhooks on localhost.
Webhook, email, WebSocket and tunnel testing for AI agents: capture, wait, verify, replay.
Issue signed receipts for AI agent actions; verify any receipt offline - free, no account.
Related MCP Servers
- AlicenseAqualityDmaintenanceProvides timing-safe, replay-resistant webhook signature verification for Stripe, GitHub, Slack, Shopify, and Twilio, returning valid/invalid with precise failure reasons.1MIT
- AlicenseAqualityBmaintenanceLets AI coding agents list captured webhooks, explain why a signature failed, replay events to localhost and generate handler code. Works with Stripe, GitHub, Shopify, Slack and Twilio.1160 npmMIT
- FlicenseNot gradedqualityBmaintenanceEnables verifying event-driven webhook signatures and providing HMAC replay protection for AI agents and MCP clients.8-
- AlicenseAqualityCmaintenanceGive AI agents cryptographically signed proof of web observations: Ed25519-signed proof packets (HTTP status, page title, body SHA-256, DNS, TLS) for any public URL.1MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.