Check an AI agent you did not build: is it who it claims, inside its mandate, and what's its record
Connect Remote server
claude mcp add --transport http verify https://apir.ai/api/mcp
{
"mcpServers": {
"verify": {
"url": "https://apir.ai/api/mcp"
}
}
}
{
"servers": {
"verify": {
"type": "http",
"url": "https://apir.ai/api/mcp"
}
}
}
Settings > Connectors > Add custom connector
URL: https://apir.ai/api/mcp
Tools 3 found in our last check
verify_agentCheck 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 fo…
check_authorityResolve 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…
get_verification_keysReturn 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…
Details
| Endpoint | https://apir.ai/api/mcp (Streamable HTTP) |
| First published | 13 Oct 2026 |
| Last updated | 13 Oct 2026 |
| Registry name | ai.apir/verify |
More ai and media servers See all
Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.
