All servers · Government & law · Utilities

APIR Agent Verification

ai.apir/verify · v1.0.0

Measured by MCP Station

Last check	Reachable
Checked at	—
Check success 7 / 30 days	—
First-try success 30 days	—
Median response	—
Lookups 30 days	—
Authentication	No auth
MCP version	2025-06-18
Rank score	—
Declared risk	Not declared (tools carry no read/destructive hints)
Capabilities declared	tools
Tool definitions	3 tools · with description 100% · input schema is an object 100% · read/destructive hints 0%

Check an AI agent you did not build: is it who it claims, inside its mandate, and what's its record

streamable-http · https://apir.ai/api/mcp

claude mcp add --transport http verify https://apir.ai/api/mcp

{
  "mcpServers": {
    "verify": {
      "url": "https://apir.ai/api/mcp"
    }
  }
}

verify_agent
Check whether an AI agent carries a real, cryptographically signed credential. Accepts an agent name, a credential id (TP-...), an agent UUID, a domain or a DID. Returns one of seven verdicts: VERIFIED, EXPIRED, REVOKED, SUPERSEDED, UNSIGNED, UNCHECKED or NO_RECORD. IMPORTANT for interpreting the an
check_authority
Resolve the human mandate behind an AI agent: which actions a named person actually permitted, any value cap, the expiry, and whether the grant itself is signed. Where authority was delegated agent to agent, the full chain is walked back to the human at the root, and one law is enforced at every hop
get_verification_keys
Return the Ed25519 public keys APIR publishes, so a signature can be recomputed offline without trusting any APIR response, including this one. Keys are published as a JWKS at apir.ai/.well-known/jwks.json and as did:web:apir.ai. Retired keys stay published so older credentials still verify.

Website · JSON · Text for agents · Registry updated 2026-10-13