xrpl-identity-mcp
An MCP server for XRP Ledger identity features including DIDs, credentials, multisig, and safe transaction workflows.
README
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.
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:
| Variable | Values | Default | Purpose |
|---|---|---|---|
XRPL_NETWORK |
mainnet, testnet, devnet |
testnet |
Selects the XRPL network. |
XRPL_ENDPOINT |
WebSocket URL | Network default | Overrides the rippled WebSocket endpoint. |
ALLOW_MAINNET_SUBMIT |
true or unset |
unset | Required for tx_submit_signed on mainnet. |
Default endpoints:
| Network | Endpoint |
|---|---|
mainnet |
wss://xrplcluster.com |
testnet |
wss://s.altnet.rippletest.net:51233 |
devnet |
wss://s.devnet.rippletest.net:51233 |
Tools
| Tool | What it does | Network writes? |
|---|---|---|
did_resolve |
Resolve an XLS-40 DID object and fetch an ipfs:// or https:// DID document when present. |
No |
did_prepare_set |
Prepare an unsigned DIDSet transaction. |
No |
did_prepare_delete |
Prepare an unsigned DIDDelete transaction. |
No |
credential_prepare_create |
Prepare an unsigned CredentialCreate transaction. |
No |
credential_prepare_accept |
Prepare an unsigned CredentialAccept transaction. |
No |
credential_prepare_delete |
Prepare an unsigned CredentialDelete transaction. |
No |
credential_verify |
Read a credential object and report existence, acceptance, and expiration. | No |
credential_list |
List up to 400 credential objects visible to an account, with issuer/subject filtering. | No |
account_identity_summary |
Summarize auth posture, signer list, DID presence, and credential counts for an account. | No |
signer_list_prepare_set |
Prepare an unsigned SignerListSet transaction for multisig create, replace, or delete. |
No |
tx_decode_verify |
Decode a signed blob, compute hash, and compare against expected intent. | No |
tx_submit_signed |
Submit 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:
- 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 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
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
e2b-mcp-server
使用 MCP 通过 e2b 运行代码。
Neon MCP Server
用于与 Neon 管理 API 和数据库交互的 MCP 服务器
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。