Agent Verification API MCP Server

by nexus-mcp-infra Your server? Claim it

not responding

Agent Verification API is listed as active in the registry but did not answer our last check. It exposes 1 tools. Last commit 22 Aug 2026.

Confirms an AI agent/service is who it claims to be (domain + agent-card + MCP handshake).

Uptime history 72 days of history · worst day 0%

72 days agonow

0.0%

Uptime 24h

0 of 91 checks

Tools

read from the server

183 ms

Response time

average over 24h

Stars

last commit 22 Aug 2026

Agent Verification API does not always answer

Over the last week it answered 0.0% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 12 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add agent-verification-api --transport http https://agent-verification-api-325572559480.us-central1.run.app/mcp

Settings → Connectors → Add custom connector, then paste this address

https://agent-verification-api-325572559480.us-central1.run.app/mcp

~/.codex/config.toml

[mcp_servers.agent-verification-api]
url = "https://agent-verification-api-325572559480.us-central1.run.app/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "agent-verification-api": {
      "url": "https://agent-verification-api-325572559480.us-central1.run.app/mcp"
    }
  }
}

.vscode/mcp.json

{
  "servers": {
    "agent-verification-api": {
      "type": "http",
      "url": "https://agent-verification-api-325572559480.us-central1.run.app/mcp"
    }
  }
}

Available tools 1

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

verify

verify_agent_identity

Confirms an AI agent/service is who it claims to be. Fuses cross-signal domain verification (WHOIS/CT/Wayback/DNS) with a real .well-known/agent-card.json fetch and a real MCP `initialize` handshake against agent_endpoint_url (if given), and checks that the agent card's own declared url is bound to `domain`. Returns VERIFIED_LIVE_AGENT, AGENT_DOMAIN_MISMATCH, LIKELY_HALLUCINATED_AGENT, DOMAIN_VERIFIED_AGENT_UNREACHABLE, VERIFIED_LIVE_DOMAIN_ONLY (no agent_endpoint_url given), or UNVERIFIED_AGENT.

Endpoints

URL	Transport	State	Latency	Checked
https://agent-verification-api-325572559480.us-central1.run.app/mcp	streamable-http	answering	183 ms	12 min ago

Alternatives to Agent Verification API

same job, measured the same way

Bloomfilter

by eronmmer

Service that lets AI Agents search, register, and configure domains

107 installs/wk local only

NEUS MCP

by neus

The trust harness for AI agents. Set what an agent can do before it acts.

4 tools answering

MCP Confirm

by les-k

An MCP server whose confirmation cannot be replayed against a different call.

82 installs/wk local only

Isitdisposable MCP

by richelo

An MCP server that lets AI agents check whether an email address or domain is disposable.

29 installs/wk local only

yutu

by eat-pray-ai

CLI, MCP server, and AI agent to automate YouTube workflows

179 installs/wk local only

Dibs

by agenxy

Tells an AI agent when another is already doing its work. Board, typed mail, directory claims.

local only

Teztun

by asadullokhn

Manage TezTun tunnels, subdomains, and service tokens from any MCP-compatible AI client.

35 installs/wk local only

KanbanMCP

by kanbanmcp

Hosted kanban board where AI agents claim cards, check in, and hand off with notes.

31 tools answering

Agent Verification API — questions

Answers built from our own checks of this server.

What can Agent Verification API do?

It exposes 1 tools, read directly from the server on our last check. Among them: verify_agent_identity. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is Agent Verification API working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 0 of 91 checks got a reply (0.0%), average response time 183 ms. The bar chart above shows every period we have measured.

The registry lists Agent Verification API as active — why does it not respond?

The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.

How do I connect Agent Verification API?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does Agent Verification API need an API key?

No. Agent Verification API completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 1 of them are readable on this page. This is what we observed, not what the docs claim.

Is Agent Verification API open source?

We cannot say either way: written in Python and 0 stars on GitHub, but we could not determine the licence, and without one the code is not open source by default.