resolve_did

4 registry entries were observed exposing a tool named resolve_did — none of them flagged as a privileged capability.

Every row is point-in-time scan output, dated below. Forge has an observed tool surface for 12,346 of 40,589 scannable entries (30%) — an entry that has not been scanned cannot appear here, so absence from this list is not evidence that an entry does not expose this tool.

  1. @merk.a2a/mcp-serverMCP@globallayertrust 80/100 · A
    v1.0.10

    Merka2a MCP server - AI agents search, negotiate and order GPU compute

    ClaudeCursorCopilotGemini
    io.github.globallayerUnknown2mo agonpmGitHubobserved · static extraction
    mcp
  2. @codespar/mcp-ap2MCPcommunitytrust 60/100 · B
    v0.2.0-alpha.4
    ↓ 20/wk
    ★ 271

    DEPRECATED: no live endpoint (AP2 is a spec; ap2.googleapis.com serves no API)

    ClaudeCursorCopilotGemini
    io.github.codesparMIT15d agonpmGitHubobserved · static extraction
    mcp
  3. io.github.hungnguyenhtbvn-max/autron-coreMCPcommunitytrust 60/100 · B
    v0.3.1

    Open Identity Standard for AI Agents — DID, Agent Cards, delegation, reputation, payment & escrow

    ClaudeCursorCopilotGemini
    io.github.hungnguyenhtbvn-maxUnknown7mo agonpmGitHubobserved · static extraction
    mcp
  4. io.github.srotzin/hive-mcp-identityMCPcommunitylivetrust 60/100 · B
    v1.0.0

    W3C DID issuance and verification for autonomous AI agents

    ClaudeCursorCopilotChatGPTGemini
    io.github.srotzinUnknown5mo agoGitHubobserved · static extraction
    mcp

All indexed toolsSearch the registry for resolve_did