Skip to main content
The ProofAge MCP server lets an AI assistant work with your ProofAge account the way your team does in the console: integrate ProofAge into an app, look into a verification, send a verification link, block a face, replay a webhook, or erase a person’s data on request.

​
What it can do

Integrate

Create a test workspace, read its keys and URLs, create verifications, set test outcomes and replay webhooks against a local handler. Then create the live workspace.

Investigate

Look up verifications, their decision and reason, images, webhook deliveries and statistics, with the same data as the console.

Support

Send a verification link, block or unblock a face, erase a person’s data on request.

Read the docs

The developer documentation and the OpenAPI spec are served as MCP resources, so the assistant writes code against the real API.
The full list is on MCP tools reference.

​
Connect

The server uses OAuth: your MCP client opens a browser window where you sign in with your ProofAge console account and approve access. There are no API keys to paste.
Then run /mcp in Claude Code and choose proofage to sign in.

​
Who you are on the server

The assistant acts as you, in the account you are working in in the console, and sees the tools your role allows: Every action is recorded under your name, as it is in the console.

​
Safety

  • Destructive actions take two steps. Blocking or unblocking a face and erasing personal data first return a preview and a short-lived token; the assistant must then confirm with an exact phrase and a reason.
  • Live workspaces are protected. Changing a live workspace or its keys only returns a preview; nothing is applied until you confirm. Live secret keys are never returned: you copy them from the console.
  • Creation is rate-limited per user: verifications, workspaces, test outcomes and erasures.
To remove access, disconnect the server in your MCP client.