Agent Identity Trust MCP Server

Agent Identity Trust MCP MCP server exists for a simple reason — assistants are far more useful when they can act on Agent Identity Trust MCP directly instead of describing what you should do. Agent Identity Trust tools for AI agents. Capabilities: register agent identity, issue credential, verify credential. Built by MEOK AI Labs.

What you get

Agent Identity MCP — DIDs, verifiable credentials, reputation scoring. Agent passports for the MCP ecosystem. MIT.

What the assistant can call

Once Agent Identity Trust MCP is connected, these are the calls the assistant has available:

• DID — based agent identity
• Cross — domain trust
• Pro — ** $99/mo — Full MCP suite + EU AI Act tracking
• Enterprise — ** $499/mo — Custom dev + SLA + Dedicated support
• Domain — Purpose
• Tier — Price

Setting it up

@smithery/cli on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.

Choosing this one

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Agent Identity Trust MCP's toolset — DID, Cross, Pro and 3 more — is a fair guide to whether it matches your workflow. It is maintained by csoai-org; worth a glance at recent repository activity before you build anything load-bearing on it.

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.

Before you rely on it

• 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.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the agent identity trust mcp mcp server does with a few real requests.