xrpl-identity-mcp
Provides tools for managing identity on the XRP Ledger, including DID resolution and management, credential creation and verification, multisig signer lists, and safe transaction prepare/verify/submit workflows.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@xrpl-identity-mcp resolve DID for rN7n7ot6dSgW6sZJ9hVqJ7g5YbJ6cX8kL"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
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:
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.
Network is explicit.
XRPL_NETWORKismainnet,testnet, ordevnet. The default istestnet. Every tool result includesnetwork.Mainnet submit is opt-in.
tx_submit_signedon mainnet is blocked unlessALLOW_MAINNET_SUBMIT=trueis set.Prepare, verify, then submit. Write workflows return unsigned JSON with instructions to sign externally, call
tx_decode_verify, and only then calltx_submit_signed.
Related MCP server: Agent Identity MCP Server
Quickstart
Claude MCP:
claude mcp add xrpl-identity -- npx -y xrpl-identity-mcpGeneric MCP client config:
{
"mcpServers": {
"xrpl-identity": {
"command": "npx",
"args": ["-y", "xrpl-identity-mcp"],
"env": {
"XRPL_NETWORK": "testnet"
}
}
}
}Environment variables:
Variable | Values | Default | Purpose |
|
|
| Selects the XRPL network. |
| WebSocket URL | Network default | Overrides the rippled WebSocket endpoint. |
|
| unset | Required for |
Default endpoints:
Network | Endpoint |
|
|
|
|
|
|
Tools
Tool | What it does | Network writes? |
| Resolve an XLS-40 DID object and fetch an | No |
| Prepare an unsigned | No |
| Prepare an unsigned | No |
| Prepare an unsigned | No |
| Prepare an unsigned | No |
| Prepare an unsigned | No |
| Read a credential object and report existence, acceptance, and expiration. | No |
| List up to 400 credential objects visible to an account, with issuer/subject filtering. | No |
| Summarize auth posture, signer list, DID presence, and credential counts for an account. | No |
| Prepare an unsigned | No |
| Decode a signed blob, compute hash, and compare against expected intent. | No |
| Submit a pre-signed blob and poll for validation. Mainnet requires | Yes |
Example Agent Flows
Resolve a DID and read its document:
Call
did_resolvewithaddressset to a classic XRPL address ordid:xrpl:<address>.Inspect
decoded.URI,decoded.Data, anddecoded.DIDDocument.If the URI is
ipfs://orhttps://, inspectdocumentanddocumentSource. Only text and JSON documents are inlined; binary content (for example an image) is reported asdocumentSource,documentContentType, anddocumentByteLengthwithdocumentSkippedexplaining why the body was omitted.
Issue and accept a credential on testnet:
Set
XRPL_NETWORK=testnet.Call
credential_prepare_createwith issuer, subject, credential type, optional expiration, and optional URI.Sign the returned
unsignedTxexternally with the issuer account.Call
tx_decode_verifywith the signed blob and the expected intent.Call
tx_submit_signed.Call
credential_prepare_acceptfor the subject, sign externally, verify withtx_decode_verify, then submit.Call
credential_verifyto confirmaccepted: trueandexpired: false.
Verify a signed blob before submitting:
Call
tx_decode_verifywithsignedBloband anexpectedIntentpartial transaction JSON.Check
matchesand anymismatches.Submit only when the decoded transaction matches the user's intent.
Development
npm install
npm run typecheck
npm run build
SKIP_INTEGRATION=1 npm testIntegration 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
Available Tools
12 toolsaccount_identity_summaryAccount Identity SummaryA
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).
Inputs: address (required).
credential_listList Account CredentialsA
List up to 400 XLS-70 Credential objects visible in an account owner directory, optionally filtered by whether the account is issuer or subject.
Inputs: address (required), role.
credential_prepare_acceptPrepare CredentialAcceptA
Prepare an unsigned XLS-70 CredentialAccept transaction for a subject to accept an issued credential. Signing happens outside this server.
Inputs: issuer (required), account (required), credentialType (required).
credential_prepare_createPrepare CredentialCreateA
Prepare an unsigned XLS-70 CredentialCreate transaction. The issuer signs externally; this server only prepares JSON and never custodies keys.
Inputs: subject (required), issuerAccount (required), credentialType (required), uri, +1 more.
credential_prepare_deletePrepare CredentialDeleteA
Prepare an unsigned XLS-70 CredentialDelete transaction. The submitter signs externally; this server never signs or stores keys.
Inputs: account (required), credentialType (required), issuer, subject.
credential_verifyVerify CredentialA
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.
Inputs: issuer (required), subject (required), credentialType (required).
did_prepare_deletePrepare DIDDeleteA
Prepare an unsigned XLS-40 DIDDelete transaction for an account DID. This server never signs; sign externally and verify the blob before submitting.
Inputs: account (required).
did_prepare_setPrepare DIDSetA
Prepare an unsigned XLS-40 DIDSet transaction. This server does not sign or custody keys; sign externally and verify the signed blob before submission.
Inputs: account (required), uri, data, didDocument.
did_resolveResolve XRPL DIDA
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.
Inputs: address (required).
signer_list_prepare_setPrepare SignerListSetA
Prepare an unsigned SignerListSet transaction to create, replace, or delete an XRPL multisign signer list. This server never signs or stores keys.
Inputs: quorum (required), account (required), signers (required).
tx_decode_verifyDecode and Verify Signed TransactionA
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.
Inputs: signedBlob (required), expectedIntent.
tx_submit_signedSubmit Signed TransactionA
Submit a pre-signed XRPL transaction blob and poll for validation. On mainnet this is blocked unless ALLOW_MAINNET_SUBMIT=true is set.
Inputs: signedBlob (required), failHard.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 12 tools
Each tool targets a distinct operation: account summary, credential CRUD, DID management, signer list preparation, and transaction verification/submission. No two tools have overlapping purposes.
All tools use snake_case with a consistent verb_noun pattern (e.g., credential_prepare_create, did_resolve). The naming is uniform and predictable.
12 tools are well-scoped for the XRPL identity domain, covering credentials, DIDs, signer lists, and transaction safety without being excessive.
The tool set covers the main identity operations (credential lifecycle, DID, signer list) and includes transaction safety tools. Missing are account root flag modification and regular key management, but these are minor gaps for the focused purpose.
Related MCP Connectors
MCP server for mandates, delegation, policy-gated execution, credential grants, and audit.
A paid remote MCP for ZeroID, built to return verdicts, receipts, usage logs, and audit-ready JSON.
Tenzro Network MCP server: wallet, identity, payments, inference, staking, bridges, verification.
Discover MCP servers and A2A agents; verify, message, post, follow, react, and receive webhooks.
Related MCP Servers
- AlicenseAqualityDmaintenanceMCP server for AI agent identity — verify agents with Ed25519 signatures, check trust scores, sign and verify content, exchange encrypted messages. Built on the Agent Identity Protocol (AIP).81MIT
- AlicenseNot gradedqualityDmaintenanceMCP Server for AI agent identity and authorization. Create, verify, and manage agent identities with trust scores and scoped authorization tokens.31 PyPIMIT
- FlicenseAqualityBmaintenanceMock identity-management MCP server for decentralized identity that allows minting DIDs, issuing signed Verifiable Credentials, and verifying them.8-
- AlicenseNot gradedqualityCmaintenanceProvides a sovereign, MIT-licensed MCP server for professional-service workflows, running entirely on your infrastructure with Ed25519 cryptographic signing for every action.MIT