Agent Verifier

guru.packetPublished by packet.guruOfficial publisherv1.0.0Updated Oct 24, 2026

Test and debug your AI agent's Web Bot Auth (RFC 9421) signature: is it valid, and what to fix?

VerifiedStreamable HTTPWeb executableDeveloper ToolsSecurity & Monitoring

Overview

AI-generated overview

Remote MCP server that checks whether an AI agent's Web Bot Auth (RFC 9421) request signature verifies and explains what to fix.

What you can do
  • Check request signatures: report whether the Web Bot Auth (RFC 9421) signature on the incoming request verified.
  • Inspect key directories: show what the key directory named by the request publishes.
  • Diagnose faults: return the exact fault and the sentence describing what to change.
  • Report request origin: give plain facts about the address the request arrived from.
When to use it
Useful when building or debugging an agent that signs its HTTP requests with Web Bot Auth and you need to confirm the signature verifies and see a concrete fix when it does not.
Requirements
A remote streamable HTTP endpoint; no package, environment variable or header is declared. The calling agent must send a Web Bot Auth (RFC 9421) signed request for the check to be meaningful.
Before you install
The server inspects the request that carries the call, including its signature and originating address, and reports those facts back; consider whether that request metadata should leave your environment. No authentication is declared.

Installation

In SourceWeft

  1. Open Agent Verifier in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/guru.packet%2Fagent-verifier/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "agent-verifier": {
      "type": "http",
      "url": "https://fp.packet.guru/api/v1/mcp"
    }
  }
}

Tools

1

self_check_web_bot_auth

Check my own Web Bot Auth setup

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.

Takes no parameters.

Version history

1
  1. v1.0.0LatestOct 2, 2026

Score

83% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.

Other Packet integrations