About this integration
AI agent real-name identity: SM2 keypair, QR real-name link, SD-JWT VP generate/verify.
- Transport
- stdio
- Authentication
- unknown
- Initial setup
- user-authorization
- Runtime
- unattended
- Evidence
- documented
- Version
- 0.3.2
- Package
- realagent-mcp
- Last compatibility test
- Not independently tested
Connect your agent
realagent-mcpPublisher README and executable manifest were reviewed from pinned captures. The custom agent-ID and QR-scan identity flow is documented but was not executed; the package, postinstall behavior, remote identity service, and cryptographic claims were not independently tested or security-audited.
Capabilities: Create and use local SM2 key pairs, Link an agent identity and manage verifiable credentials, Generate and verify selective-disclosure proofs
Connected profiles
Additional details
io.github.RedDateTech/realagent-mcp
Source ↗ · Checked 2026-09-170.3.2
Source ↗ · Checked 2026-09-17CC0-1.0; package licenses are separate
Source ↗ · Checked 2026-09-17npm
Source ↗ · Checked 2026-09-17realagent-mcp
Source ↗ · Checked 2026-09-190.3.2
Source ↗ · Checked 2026-09-19The MCP client launches the package as a persistent stdio subprocess; after client restart the publisher says the server exposes 14 tools. No runtime execution was performed.
Source ↗ · Checked 2026-09-19The publisher documents a custom SM2/VC identity flow in which real-name linking creates a QR code, requires a user scan, and then claims a credential; startup also requires a unique non-secret agent ID. This mechanism is outside the native authentication taxonomy.
Source ↗ · Checked 2026-09-19Run npx with realagent-mcp, the stdio subcommand, and a unique --agent-id argument as the local MCP client command.
Source ↗ · Checked 2026-09-19Publisher documentation reviewed; package and integration endpoint not executed or independently security-audited.
Source ↗ · Checked 2026-09-19