AIP Identity MCP Server

Cryptographic identity for MCP clients — Ed25519 keypairs, DID-based verification, trust scoring, encrypted messaging, and artifact signing. Exposed over MCP by the aip identity mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.

What it actually does

Watch AIP create two agent identities, sign and verify a message, send an end-to-end encrypted message, and create a cryptographic trust vouch — all running locally, no server needed.

Adding it to your client

The server ships on PyPI as aip-identity, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.

Its toolset

Everything the assistant can do here goes through one of these:

• init — One-command setup: register + set profile
• register — Register a new agent DID
• verify — Verify a signed artifact
• vouch — Vouch for another agent
• revoke — Revoke a vouch you previously issued
• sign — Sign a skill directory or file
• message — Send an encrypted message to another agent
• messages — Retrieve your messages
• reply — Reply to a received message by ID
• rotate-key — Rotate your signing key
• badge — Show trust badge for a DID
• list — List registered agents

Configuration

You will need 2 environment variables: AIP_PRIVATE_KEY, AIP_CREDENTIALS_PATH. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Caveats

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch AIP Identity.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the aip identity mcp server does with a few real requests.

When to reach for it

This sits in the team communication group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. AIP Identity's toolset — init, register, verify and 11 more — is a fair guide to whether it matches your workflow.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.