Skip to content
MCP server

Agent Verifier

Checks whether an AI agent's Web Bot Auth (RFC 9421) signature verifies and what to fix

Answered our latest tool-list check 3 hours ago with 1 tools. It will be marked verified after 3 successful checks in 7 days.

Install
Pricing
Free
Platforms
Web, API
Runs
Remotely
Version
1.0.0
Listing updated
today

Similar MCP servers

About Agent Verifier

Agent Verifier is a free MCP server for security. It runs as a hosted remote server, so there is nothing to install locally.

The README-style MCP entry describes it as a way to test and debug an agent's Web Bot Auth signature. The site itself offers a free web form where you paste a signed or unsigned HTTP request and receive a verdict on the signature, the key directory it points to, and the single change that would make it verify.

The check reads the signature from the request, fetches the key directory named in the Signature-Agent header, and looks for the signing key there. It also reports the network the calling address belongs to, whether that address sits in a crawler range its operator publishes, and whether it appears on public abuse lists. Unsigned callers still receive the address part of the answer.

It suits developers building crawlers or agents that sign their requests with Web Bot Auth, and who need to find out why a site refuses them. The page notes that a form-pasted request cannot reveal the originating address, so full results require the agent to call the API or MCP server directly.

Install

Run in a terminal

claude mcp add --transport http agent-verifier https://fp.packet.guru/api/v1/mcp

Add to Settings → Connectors → Add custom connector

https://fp.packet.guru/api/v1/mcp
Install in CursorOpens Cursor, which asks you to confirm. Or add it by hand:

Add to ~/.cursor/mcp.json

{
  "mcpServers": {
    "agent-verifier": {
      "url": "https://fp.packet.guru/api/v1/mcp"
    }
  }
}
Install in VS CodeOpens VS Code, which asks you to confirm. Or add it by hand:

Add to .vscode/mcp.json

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

Add to ~/.codeium/windsurf/mcp_config.json

{
  "mcpServers": {
    "agent-verifier": {
      "serverUrl": "https://fp.packet.guru/api/v1/mcp"
    }
  }
}

Add to Grok Bot desktop app → Connect apps → Add a custom connector

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

Enter a Name (for example "Agent Verifier"), choose Type: Remote HTTPS, paste this as the Server URL and choose Add plugin.

Add to your client's MCP settings (most use this shape)

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

Using several servers? Build one config file with the MCP config generator.

Tools this server provides (1)

Read directly from the server.

All 1 tool say they're read-only.

From the server's own tool annotations; not verified by us.

self_check_web_bot_authSays read-only
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 un

What it does

Signature verification report
Shows whether an RFC 9421 Web Bot Auth signature verifies against the key directory it names.
Key directory lookup
Fetches the Signature-Agent directory and reports which keys it publishes.
Specific fault and fix
Names the failure reason, such as a key missing from the directory, and the change needed.
Caller network check
Reports the network type and operator of the connecting address and any crawler range membership.
Agent card comparison
Reads a declared agent card and compares its promised User-Agent with the one received.

Good for

  • Debugging a crawler whose signed requests are refused by a website
  • Confirming that a signing key is published correctly in a key directory
  • Checking whether an agent's connecting IP belongs to a published crawler range
  • Testing an agent's Web Bot Auth setup from an MCP client before deployment

Pricing

Free

Free check; no account required.

Prices change. Check packet.guru before you buy.

Agent Verifier FAQ

Does the check require an account or a key?

No. The page states the check is free and needs no account or key, and the API takes no parameters.

Can I check a request by pasting it into the form?

Yes, but the form answer covers the signature only. It cannot see the originating address, so the full answer requires calling the API or MCP server directly.

Does it work with unsigned requests?

Yes. The page says unsigned callers still receive an answer about the address they called from.

Is Agent Verifier free?

Yes. Agent Verifier is free to use.

How do I add Agent Verifier to Claude Code?

Run this command in your terminal: claude mcp add --transport http agent-verifier https://fp.packet.guru/api/v1/mcp

What are the best alternatives to Agent Verifier?

The closest alternatives to Agent Verifier are Agent Verify, APIR Agent Verification, AgentArchitect Network, Agency Check and Metal Mantra.

Where this comes from

  • Description: written from the project's website and its MCP Registry entry.
  • Status and tools: checked automatically by AIPoweredBot on 19 November 2026.
  • Install steps: from the official MCP Registry entry.

How AIPoweredBot checks servers