Skip to content

Hive Identity

by srotzin · remote · no sign-in to list tools · v1.0.0 · published by GitHub user srotzin

W3C DID issuance and verification for autonomous AI agents

Changes · 1
CompareRegistry entry

4 tools: 1 change things and 3 only read.

Scanned Oct 21, 2026

No check matched anything in the tool definitions. No finding is not a safety guarantee. How the checks work.

claude mcp add --transport http hive-identity https://hive-mcp-identity.onrender.com/mcp

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

4 tools

Changes things 1Claude Code: ask
  • verify_attestationVerify whether a specific attestation (by hash) was issued to a DID and is currently valid.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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).
Only reads 3Claude Code: allow
  • get_trust_scoreRetrieve the Hive trust score (0-100) for a DID.No findings

    Why it is in this group

    • The name "get_trust_score" says "get": a word for reading.
    Description, as the server wrote it
    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).
  • list_attestationsList all attestations associated with a DID — issued, received, and expired.No findings

    Why it is in this group

    • The name "list_attestations" says "list": a word for reading.
    Description, as the server wrote it
    List all attestations associated with a DID — issued, received, and expired. Returns array of attestation metadata. Backend pending (Q3 2026).
  • resolve_didResolve a DID to its public profile: display name, verification methods, service endpoints, and Hive trust metadata.No findings

    Why it is in this group

    • The name "resolve_did" says "resolve": a word for reading.
    Description, as the server wrote it
    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).

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http hive-identity https://hive-mcp-identity.onrender.com/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__hive-identity__resolve_did",
      "mcp__hive-identity__get_trust_score",
      "mcp__hive-identity__list_attestations"
    ],
    "ask": [
      "mcp__hive-identity__verify_attestation"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as hive-identity. Review it before you use it.