MCP.Market

Xrpl Identity MCP server

by jarod-vyent·io.github.jarod-vyent/xrpl-identity-mcp·v0.1.1·1 stars

MCP server for XRPL identity: DIDs, credentials, signer lists, and safe transaction workflows.

A88/100grade A
What users say
No reviews yet
Be the first
Safety scan
A88/100

full report

Adoption
New

1 stars38 downloads/wk

Reviews

Write one

Nobody has reviewed Xrpl Identity yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Xrpl Identity tools (12, 4 write)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • account_identity_summary

    Summarize an XRPL account identity posture: AccountRoot auth flags, RegularKey and Domain state, signer list, DID presence, and visible credential counts as issuer and subject (each with a *Truncated boolean flagging when the count hit the 400-object scan cap).

  • credential_list

    List up to 400 XLS-70 Credential objects visible in an account owner directory, optionally filtered by whether the account is issuer or subject.

  • credential_prepare_accept

    Prepare an unsigned XLS-70 CredentialAccept transaction for a subject to accept an issued credential. Signing happens outside this server.

  • credential_prepare_createwrite action

    Prepare an unsigned XLS-70 CredentialCreate transaction. The issuer signs externally; this server only prepares JSON and never custodies keys.

  • credential_prepare_deletewrite action

    Prepare an unsigned XLS-70 CredentialDelete transaction. The submitter signs externally; this server never signs or stores keys.

  • credential_verify

    Read an XLS-70 Credential ledger object and report whether it exists, has been accepted, and is expired relative to the validated ledger close time.

  • did_prepare_deletewrite action

    Prepare an unsigned XLS-40 DIDDelete transaction for an account DID. This server never signs; sign externally and verify the blob before submitting.

  • did_prepare_set

    Prepare an unsigned XLS-40 DIDSet transaction. This server does not sign or custody keys; sign externally and verify the signed blob before submission.

  • did_resolve

    Resolve an XLS-40 DID object for an XRPL account or did:xrpl identifier. Returns raw ledger data, UTF-8 decoded DID fields where valid, and fetched DID document content for ipfs:// or https:// URIs. Only text/JSON documents are inlined; binary content is reported as metadata (source, content type, byte length) with the body omitted.

  • signer_list_prepare_set

    Prepare an unsigned SignerListSet transaction to create, replace, or delete an XRPL multisign signer list. This server never signs or stores keys.

  • tx_decode_verify

    Decode a signed XRPL transaction blob, compute its hash, and optionally compare it against an expected partial intent before submission. This is the WYSIWYS safety gate.

  • tx_submit_signedwrite action

    Submit a pre-signed XRPL transaction blob and poll for validation. On mainnet this is blocked unless ALLOW_MAINNET_SUBMIT=true is set.

Public scan report

scanner v0.1.9 · 2026-09-26 · same rubric, same numbers if you re-run it

no findings
  • Code scan25 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitylocal package, no credentials required12/15
  • Maintenancelast push 80 days ago12/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Overall 88/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Xrpl Identity compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
88/100
higher than 75% of 48,255 servers
Tools
12
the typical server has 7
Tools that change things
33%
typical: 0%. Fewer write tools means less an agent can break
GitHub stars
1
more than 65% of 28,688 servers
Downloads a week
38
more than 29% of 12,191 servers with a package

What its tools let an agent do: 8 read · 4 change

Install Xrpl Identity in Claude Code, Cursor or VS Code

Runs npx -y xrpl-identity-mcp on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add xrpl-identity-mcp -- npx -y xrpl-identity-mcp
Add to Cursor

What the publisher says

From the Xrpl Identity repository's README, as published. We do not edit it. Read it on GitHub

xrpl-identity-mcp

xrpl-identity-mcp is the first identity-focused MCP server for the XRP Ledger: DIDs (XLS-40), credentials (XLS-70), multisig signer lists, and safe transaction prepare/verify/submit workflows. It prepares unsigned transactions, reads ledger state, verifies signed blobs against intent, and can submit pre-signed blobs without ever taking custody of keys.

Built by Jarod Vyent, from the team behind SciPHR.

Security Model

These invariants are core behavior:

  1. No key custody. The server has no seed, private key, mnemonic, wallet import, or signing path. Signing happens in the user's wallet or agent.
  2. Network is explicit. XRPL_NETWORK is mainnet, testnet, or devnet. The default is testnet. Every tool result includes network.
  3. Mainnet submit is opt-in. txsubmitsigned on mainnet is blocked unless ALLOWMAINNETSUBMIT=true is set.
  4. Prepare, verify, then submit. Write workflows return unsigned JSON with instructions to sign externally, call txdecodeverify, and only then call txsubmitsigned.

Quickstart

Claude MCP:

claude mcp add xrpl-identity -- npx -y xrpl-identity-mcp

Generic MCP client config:

{
  "mcpServers": {
    "xrpl-identity": {
      "command": "npx",
      "args": ["-y", "xrpl-identity-mcp"],
      "env": {
        "XRPL_NETWORK": "testnet"
      }
    }
  }
}

Environment variables:

Default endpoints:

Tools

Example Agent Flows

Resolve a DID and read its document:

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Xrpl Identity: common questions

Is Xrpl Identity MCP server safe?
Yes, by our scan: it is graded A (88/100). Read the Xrpl Identity safety report
How do I install Xrpl Identity?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Xrpl Identity need an API key?
No secret keys are declared. It reads 3 settings from the environment.
Is Xrpl Identity maintained?
The last commit was 119 days ago (2026-07-08). The latest release is v0.1.1.
How does Xrpl Identity compare with other MCP servers?
safety score 88/100 (higher than 75% of 48,255 servers); tools 12 (the typical server has 7); tools that change things 33% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.