W3C DID issuance and verification for autonomous AI agents
The io.github.srotzin/hive-mcp-identity MCP server provides W3C DID issuance and verification for autonomous AI agents. It focuses on resolving identities and enabling agent KYC for autonomous agent counterparties, using Model Context Protocol server tooling (4 tools) under the “hive-civilization” ecosystem.
🛠️ Key Features
W3C DID issuance and verification
W3C DID resolution
Agent KYC for autonomous agent counterparties
4 MCP tools
🚀 Use Cases
Verifying agent identities via W3C DIDs
Issuing and resolving DIDs for autonomous AI agents
Performing KYC for agent-to-agent counterparties
⚡ Developer Benefits
Integrates identity and KYC workflows into an MCP server
Limited public detail provided beyond W3C DID issuance/verification, DID resolution, and agent KYC; additional tool behavior is not described in the provided excerpt.
Resolve a DID to its public profile: display name, verification methods, service endpoints, and Hive trust metadata. Conforms to W3C DID spec. Backend pending (Q3 2026).
Parameters1
did
string
required
Decentralized Identifier (DID) to resolve (e.g. did:hive:0x...)
Retrieve the Hive trust score (0-100) for a DID. Factors include on-chain activity, attestation count, repayment history, and peer endorsements. Backend pending (Q3 2026).
Verify whether a specific attestation (by hash) was issued to a DID and is currently valid. Returns boolean. Used in KYC-lite flows and smart-contract gating. Backend pending (Q3 2026).
Parameters2
did
string
required
DID to verify attestation for
attestation_hash
string
required
SHA-256 hash of the attestation to verify
Raw schema
{
"type": "object",
"properties": {
"did": {
"type": "string",
"description": "DID to verify attestation for"
},
"attestation_hash": {
"type": "string",
"description": "SHA-256 hash of the attestation to verify"
}
},
"required": [
"did",
"attestation_hash"
]
}
list_attestations
List all attestations associated with a DID — issued, received, and expired. Returns array of attestation metadata. Backend pending (Q3 2026).
W3C DID resolution and agent KYC for autonomous agent counterparties.
MCP server for HiveIdentity — W3C DID resolution and agent KYC. Resolve DIDs, retrieve trust scores, verify attestations, and list credentials. OFAC/FATF screening per agent. USDC settlement on Base L2. Scaffold shim — backend pending Q3 2026.
What this is
hive-mcp-identity is a Model Context Protocol (MCP) server that exposes the HiveIdentity platform on the Hive Civilization to any MCP-compatible client (Claude Desktop, Cursor, Manus, etc.). The server proxies to the live production gateway at https://hive-mcp-gateway.onrender.com.
Protocol: MCP 2024-11-05 over Streamable-HTTP / JSON-RPC 2.0
x402 micropayments: every paid call produces a real on-chain settlement
Rails: USDC on Base L2 — real rails, no mocks
Author: Steve Rotzin · Hive Civilization · brand gold #C08D23
Endpoints
Path
Purpose
POST /mcp
JSON-RPC 2.0 / MCP 2024-11-05
GET /
HTML landing with comprehensive meta tags + JSON-LD
