MCP.so
Sign In
A

APIR Agent Verification MCP Server

@APIR Agent Verification

Basic information

Transport

streamable-http

Authentication

None

Category

Other

Author

APIR Agent Verification

About APIR Agent Verification MCP Server

APIR is the evidence record for AI agents. Its MCP server answers two questions about an agent you did not build: is it who it claims to be, and is it acting inside a human mandate. Credentials are signed with Ed25519 and the public keys are published, so any answer can be rechecked offline without trusting APIR.

Connection details

https://apir.ai/api/mcp

Setup

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

APIR Agent Verification MCP Server tools

3

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 answer: VERIFIED means the Ed25519 signature recomputes against the key published at apir.ai and the credential is unexpired and unrevoked. It confirms WHO issued the credential and that its contents are unaltered. It is NOT a guarantee that the agent behaves well. NO_RECORD is an honest, first-class answer: it means nothing is on file, which is not evidence of wrongdoing and not a warning. It means any claim the agent makes about itself is unverified. Free, unauthenticated, and no account is required.

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: authority may only ever narrow. No hop can hold an action, a target or a spending cap wider than the hop above it, and the root must be a human. Use this before letting an agent transact, sign, spend or commit on someone else's behalf. An agent holding a valid credential may still be acting outside its mandate, and those are different questions. The answer is the mandate on file as of checked_at. It is not proof the permission still holds at the moment the action runs: check again at the point of action, and treat a record as proof of what was recorded and when.

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.

Overview

What it is

APIR is the evidence record for AI agents. Its MCP server answers two questions about an agent you did not build: is it who it claims to be, and is it acting inside a human mandate. Credentials are signed with Ed25519 and the public keys are published, so any answer can be rechecked offline without trusting APIR.

This listing was submitted by the publisher.

Connect

  • Endpoint: https://apir.ai/api/mcp (Streamable HTTP)
  • Authentication: no authentication

Claude Code:

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

Other clients (mcpServers config):

{ "mcpServers": { "apir-agent-verification": { "type": "http", "url": "https://apir.ai/api/mcp" } } }

Tools

Read from the server's tools/list on 2026-11-08:

  • verify_agent — Check whether an AI agent carries a real, cryptographically signed credential
  • 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
  • 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

Notes

  • Description above is the publisher's own summary from their submission; check the website for plans, pricing and limits.
  • The endpoint answered a standard MCP initialize request when checked on 2026-11-08.

Sources: Submission.

Frequently asked questions

1

What is the APIR Agent Verification remote MCP server?

The APIR Agent Verification remote MCP server is a hosted Model Context Protocol endpoint at https://apir.ai/api/mcp, so AI assistants can connect to it without installing or running anything locally.

2

How do I connect to the APIR Agent Verification MCP server?

Add the endpoint https://apir.ai/api/mcp to any MCP-compatible client such as Claude Code, Cursor, or VS Code. The setup snippets on this page configure each client in one step.

3

Does the APIR Agent Verification MCP server require authentication?

No. APIR Agent Verification's MCP server does not require authentication — you can connect directly with the endpoint URL.

4

Which transport does the APIR Agent Verification MCP server use?

APIR Agent Verification exposes a streamable-http endpoint, the transport used by remote MCP servers and supported by all major MCP clients.

Comments