mcp-agent-identity

The Agent Identity Protocol (AIP) MCP server provides a local, persistent identity wallet for AI agents. It generates a cryptographic keypair for an agent, signs payloads, and exposes a verification flow that other services can rely on to prove authorship and integrity of actions. The server is designed to be used locally within an agent environment or enterprise setup, storing identity data in a local identity.json by default, with options to point to a permanent path via the AGENT_IDENTITY_PATH environment variable. To interact with the server, install it and run the Node.js entry point, which makes available tooling within the agent to create, inspect, sign, and verify identities. For external verification in downstream systems, you can use the provided NPM SDK at @agent-identity/verify to validate signatures against a public key.

Prerequisites:

• Node.js and npm installed on your host
• Access to the MCP server repository (cloned or via package manager)

Option A: Quick install (Smithery) for testing

npx -y @smithery/cli@latest install @faalantir/mcp-agent-identity --client claude

Option B: Developer install (source) for production use

# Clone the repository 
git clone https://github.com/faalantir/mcp-agent-identity.git

# Install dependencies and build
cd mcp-agent-identity 
npm install && npm run build

Then configure the MCP server in Claude/desktop config (example):

{
  "mcpServers": {
    "agent-identity": {
      "command": "node",
      "args": ["/ABSOLUTE/PATH/TO/mcp-agent-identity/dist/index.js"]
    }
  }
}

Tips and common considerations:

• Identity data defaults to identity.json in the host project folder. If write access is restricted (e.g., within containers), it may fall back to the system temp directory. To force a permanent storage location, set AGENT_IDENTITY_PATH in the server config.
• Use AGENT_IDENTITY_PATH to point to a stable, persistent JSON file that stores the private key material securely. Ensure proper file permissions.
• For production, consider integrating with enterprise-backed storage or KMS instead of local file storage as you scale.
• The server exposes one main MCP endpoint per configured server name (here, agent-identity). You can create identities, view identity details, sign messages, and verify signatures using the included SDKs.
• If you use Smithery for testing, remember that identities created there are sandboxed and may not persist across restarts unless you configure a persistent path.
• The npm package for verification in the backend is @agent-identity/verify; you can install it and use verifyAgentIdentity to validate signatures with a public key.