xrpl-identity-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| XRPL_NETWORK | No | Selects the XRPL network: mainnet, testnet, or devnet. | testnet |
| XRPL_ENDPOINT | No | Overrides the rippled WebSocket endpoint. | |
| ALLOW_MAINNET_SUBMIT | No | Set to 'true' to allow tx_submit_signed on mainnet. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| did_resolveA | 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. |
| did_prepare_setA | 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_prepare_deleteA | Prepare an unsigned XLS-40 DIDDelete transaction for an account DID. This server never signs; sign externally and verify the blob before submitting. |
| credential_prepare_createA | Prepare an unsigned XLS-70 CredentialCreate transaction. The issuer signs externally; this server only prepares JSON and never custodies keys. |
| credential_prepare_acceptA | Prepare an unsigned XLS-70 CredentialAccept transaction for a subject to accept an issued credential. Signing happens outside this server. |
| credential_prepare_deleteA | Prepare an unsigned XLS-70 CredentialDelete transaction. The submitter signs externally; this server never signs or stores keys. |
| credential_verifyA | 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. |
| credential_listA | List up to 400 XLS-70 Credential objects visible in an account owner directory, optionally filtered by whether the account is issuer or subject. |
| account_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). |
| signer_list_prepare_setA | Prepare an unsigned SignerListSet transaction to create, replace, or delete an XRPL multisign signer list. This server never signs or stores keys. |
| tx_decode_verifyA | 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_signedA | Submit a pre-signed XRPL transaction blob and poll for validation. On mainnet this is blocked unless ALLOW_MAINNET_SUBMIT=true is set. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.