Back to Browse

Xrpl Identity MCP Server

Developer ToolsModerate6.2MCP RegistryLocal
Free

Server data from the Official MCP Registry

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

About

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

Security Report

6.2
Moderate6.2Moderate Risk

This is a well-architected XRPL identity MCP server with strong security fundamentals. The server implements proper authentication gates (mainnet submit opt-in), has no key custody, enforces input validation, and includes robust SSRF protections for document fetching. Minor code quality issues around error handling and some input validation edge cases exist but do not materially impact security. Supply chain analysis found 1 known vulnerability in dependencies (1 critical, 0 high severity). Package verification found 1 issue.

7 files analyzed · 7 issues found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Permissions Required

This plugin requests these system permissions. Most are normal for its category.

HTTP Network Access

Connects to external APIs or services over the internet.

env_vars

Check that this permission is expected for this type of plugin.

What You'll Need

Set these up before or after installing:

XRPL network to target: mainnet, testnet, or devnet (default: testnet)Optional

Environment variable: XRPL_NETWORK

Custom XRPL websocket endpoint override (default: public endpoint for the selected network)Optional

Environment variable: XRPL_ENDPOINT

Must be set to 'true' to allow tx_submit_signed on mainnet (default: blocked)Optional

Environment variable: ALLOW_MAINNET_SUBMIT

How to Install

Add this to your MCP configuration file:

{
  "mcpServers": {
    "io-github-jarod-vyent-xrpl-identity-mcp": {
      "env": {
        "XRPL_NETWORK": "your-xrpl-network-here",
        "XRPL_ENDPOINT": "your-xrpl-endpoint-here",
        "ALLOW_MAINNET_SUBMIT": "your-allow-mainnet-submit-here"
      },
      "args": [
        "-y",
        "xrpl-identity-mcp"
      ],
      "command": "npx"
    }
  }
}

Documentation

View on GitHub

From the project's GitHub README.

xrpl-identity-mcp

CI npm License: MIT

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. tx_submit_signed on mainnet is blocked unless ALLOW_MAINNET_SUBMIT=true is set.
  4. Prepare, verify, then submit. Write workflows return unsigned JSON with instructions to sign externally, call tx_decode_verify, and only then call tx_submit_signed.

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:

VariableValuesDefaultPurpose
XRPL_NETWORKmainnet, testnet, devnettestnetSelects the XRPL network.
XRPL_ENDPOINTWebSocket URLNetwork defaultOverrides the rippled WebSocket endpoint.
ALLOW_MAINNET_SUBMITtrue or unsetunsetRequired for tx_submit_signed on mainnet.

Default endpoints:

NetworkEndpoint
mainnetwss://xrplcluster.com
testnetwss://s.altnet.rippletest.net:51233
devnetwss://s.devnet.rippletest.net:51233

Tools

ToolWhat it doesNetwork writes?
did_resolveResolve an XLS-40 DID object and fetch an ipfs:// or https:// DID document when present.No
did_prepare_setPrepare an unsigned DIDSet transaction.No
did_prepare_deletePrepare an unsigned DIDDelete transaction.No
credential_prepare_createPrepare an unsigned CredentialCreate transaction.No
credential_prepare_acceptPrepare an unsigned CredentialAccept transaction.No
credential_prepare_deletePrepare an unsigned CredentialDelete transaction.No
credential_verifyRead a credential object and report existence, acceptance, and expiration.No
credential_listList up to 400 credential objects visible to an account, with issuer/subject filtering.No
account_identity_summarySummarize auth posture, signer list, DID presence, and credential counts for an account.No
signer_list_prepare_setPrepare an unsigned SignerListSet transaction for multisig create, replace, or delete.No
tx_decode_verifyDecode a signed blob, compute hash, and compare against expected intent.No
tx_submit_signedSubmit a pre-signed blob and poll for validation. Mainnet requires ALLOW_MAINNET_SUBMIT=true.Yes

Example Agent Flows

Resolve a DID and read its document:

  1. Call did_resolve with address set to a classic XRPL address or did:xrpl:<address>.
  2. Inspect decoded.URI, decoded.Data, and decoded.DIDDocument.
  3. If the URI is ipfs:// or https://, inspect document and documentSource. Only text and JSON documents are inlined; binary content (for example an image) is reported as documentSource, documentContentType, and documentByteLength with documentSkipped explaining why the body was omitted.

Issue and accept a credential on testnet:

  1. Set XRPL_NETWORK=testnet.
  2. Call credential_prepare_create with issuer, subject, credential type, optional expiration, and optional URI.
  3. Sign the returned unsignedTx externally with the issuer account.
  4. Call tx_decode_verify with the signed blob and the expected intent.
  5. Call tx_submit_signed.
  6. Call credential_prepare_accept for the subject, sign externally, verify with tx_decode_verify, then submit.
  7. Call credential_verify to confirm accepted: true and expired: false.

Verify a signed blob before submitting:

  1. Call tx_decode_verify with signedBlob and an expectedIntent partial transaction JSON.
  2. Check matches and any mismatches.
  3. Submit only when the decoded transaction matches the user's intent.

Development

npm install
npm run typecheck
npm run build
SKIP_INTEGRATION=1 npm test

Integration tests target testnet and are skipped when SKIP_INTEGRATION=1. To run the account summary integration test, set XRPL_INTEGRATION_ACCOUNT to a funded testnet account address.

License

MIT

Reviews

No reviews yet

Be the first to review this server!

Xrpl Identity MCP Server - MCP server for XRPL identity: DIDs, credentials, signer | MCP Marketplace