Skip to main content
Glama
DuNorth595

xrpl-did-mcp

by DuNorth595
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to xrpl-did-mcp

No user-submitted related servers found.

    Related Servers

    • vantic-mcp by vanticlabs

      vantic-mcpofficial

      vanticlabs
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables MCP hosts to verify agent spending mandates and receipts, providing stateless tools for authorization, chain verification, credential verification, and DID resolution.
      Apache 2.0

    • idm-mcp

      fcapub
      F
      license
      A
      quality
      B
      maintenance
      Mock identity-management MCP server for decentralized identity that allows minting DIDs, issuing signed Verifiable Credentials, and verifying them.
      8
      -
    • Proofable MCP by proofable

      Proofable MCPofficial

      proofable
      A
      license
      A
      quality
      B
      maintenance
      Enables AI agents to manage identity, permissions, secrets, and verifiable proofs through a hosted MCP server, letting clients sign in and check what an agent may do before it acts.
      15
      27 npm
      Apache 2.0
    • Callsign by callsign-im

      Callsignofficial

      callsign-im
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to discover each other by @handle, exchange consent-based message requests, and record auditable, tamper-evident ledger entries through MCP.
      7
      Apache 2.0

    • kredent-mcp

      goun7
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to generate and persist a self-sovereign did:key identity, sign claims about their actions as Ed25519 attestations, verify those attestations offline without any registry or network access, and compute an auditable reputation score from a ledger of events. All four operations are exposed as MCP tools so an agent can manage its own identity and prove its history during a session.
      Apache 2.0
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.1/5.0

    Scored across 12 tools

    Disambiguation5/5

    Each tool targets a distinct ledger action or read: derive/resolve/publish/revoke for DIDs, issue/accept/revoke/get/list for credentials, plus account and transaction reads. Descriptions explicitly disambiguate the closest pairs (derive_did vs resolve_did, get_credential vs list_credentials, lookup_account vs lookup_transaction) with explicit 'use X instead' pointers.

    Naming Consistency4/5

    Nearly all names follow verb_noun (derive_did, issue_credential, revoke_credential, lookup_account). The exceptions are publish_did_set, which is named after the ledger transaction type rather than a verb_noun, and the split between get_/list_/lookup_/resolve_ for read operations, which is readable but not perfectly uniform.

    Tool Count5/5

    Twelve tools is well within a comfortable range and each one maps to a concrete step in the DID or credential lifecycle. Nothing appears redundant or padded; the read-only/write split also justifies separate tools.

    Completeness4/5

    Coverage is strong: DIDs have derive, publish (also usable to update the document), resolve, and revoke; credentials have issue, accept, read, list, and revoke; policy evaluation and account/transaction reads round it out. The main gap is transaction discovery — lookup_transaction requires a known hash and there is no way to list an account's transactions, so agents must obtain hashes elsewhere.

    Maintenance

    ActivityMaintained
    ResponsivenessResponsive

    Resources