# RealAgent MCP [Health: Active]

**Category:** 💻 Developer Tools  
**Repository:** https://github.com/RedDateTech/RealAgentMCP  
**GitHub Stars:** 1  
**npm Downloads (last month):** 480  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/realagent-mcp

## Description
AI agent real-name identity: SM2 keypair, QR real-name link, SD-JWT VP generate/verify.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "realagent-mcp": {
    "command": "npx",
    "args": ["-y","realagent-mcp"]
  }
}
```

## Documentation

## What RealAgent MCP MCP server does

RealAgent MCP MCP server exposes identity and cryptography functions to an MCP client through a local executable. It can create an SM2 key pair, begin a QR-based real-name association, and obtain a verifiable credential after the user completes authentication. Agents can inspect or revoke that association and query credential or key metadata.

The server also supports SD-JWT verifiable presentations. An agent can create a presentation with selected disclosures, verify its signature and disclosed content, or parse the presentation to extract disclosed claims. These capabilities suit workflows where an agent must present or validate identity attributes without exposing every available field.

## How it works

The server is started in stdio mode with an `--agent-id` argument. Each agent ID maps to one identity and one SM2 key pair, so IDs must be unique and should not be reused between agents. The first identity workflow generally starts with `identity_status`, followed by `identity_link` when no association exists.

RealAgent MCP MCP server stores local private keys and credentials below `.realagent/agents/` by default. Private keys and verifiable credentials are protected locally with SM4-CTR encryption and an SM3-HMAC. The available operations are exposed dynamically as 14 MCP tools covering identity, VP, credential and key lookup, SM2 cryptography, and version checks.

## Setup and configuration

Install Node.js 18.13 or newer before installing the package. Then install the server globally:

```bash
npm i -g realagent-mcp
```

Configure the MCP client to launch `npx` with the `realagent-mcp stdio` command and a confirmed, unique agent ID:

```json
{
  "mcpServers": {
    "realagent-mcp": {
      "command": "npx",
      "args": ["-y", "realagent-mcp", "stdio", "--agent-id", "my-agent"]
    }
  }
}
```

Global installation is required by the documented setup so the command resolves to the installed package rather than repeatedly using an npx cache copy. Add `--data-dir` to choose another storage location. Restart the MCP client after installation or upgrades. Upgrade with `npm update -g realagent-mcp` or install the latest package explicitly.

## Tools and capabilities

Identity tools include `identity_link`, `identity_status`, and `identity_revoke`. VP tools are `identity_vp`, `identity_verify_vp`, and `vp_parse`. `vc_info`, `vc_raw`, and `key_info` expose local credential and key information.

SM2 operations are available through `crypto_sign`, `crypto_verify`, `crypto_encrypt`, and `crypto_decrypt`. `system_update` checks for a newer server version; the documented agent instructions recommend calling it at the beginning of a conversation or at least daily.

## Limitations and notes

RealAgent MCP MCP server requires a user to scan the generated QR code and complete authentication before the real-name credential can be collected. The README does not describe remote deployment, HTTP transport, or configurable identity providers; the documented launch mode is local stdio.

Keep each agent ID unique. Reusing one can create identity conflicts because the platform treats each key pair as a separate identity. The server also depends on the local data directory remaining available, and changing that location can affect access to stored keys and credentials.

_Full upstream README: https://allmcps.com/mcp/realagent-mcp/readme_