io.github.jarod-vyent/xrpl-identity-mcp
NPM · XRPL-IDENTITY-MCP · SCANNED SEP 21
MCP server for XRPL identity: DIDs, credentials, signer lists, and safe transaction workflows.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 32 of 113 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 75 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability81
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 1123 tokens (~93/item across 12 items; 12 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management93
- Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "did_prepare_delete" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the io.github.jarod-vyent/xrpl-identity-mcp server?
io.github.jarod-vyent/xrpl-identity-mcp runs locally as an npm package, launched with npx -y xrpl-identity-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · xrpl-identity-mcp
claude mcp add jarod-vyent-xrpl-identity-mcp -- npx -y xrpl-identity-mcp
{
"mcpServers": {
"jarod-vyent-xrpl-identity-mcp": {
"command": "npx",
"args": [
"-y",
"xrpl-identity-mcp"
]
}
}
} {
"servers": {
"jarod-vyent-xrpl-identity-mcp": {
"command": "npx",
"args": [
"-y",
"xrpl-identity-mcp"
]
}
}
} codex mcp add jarod-vyent-xrpl-identity-mcp -- npx -y xrpl-identity-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"jarod-vyent-xrpl-identity-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"xrpl-identity-mcp"
],
"enabled": true
}
}
} openclaw mcp add jarod-vyent-xrpl-identity-mcp --command npx --arg -y --arg xrpl-identity-mcp
mcp_servers:
jarod-vyent-xrpl-identity-mcp:
command: "npx"
args: ["-y", "xrpl-identity-mcp"] {
"McpServers": {
"jarod-vyent-xrpl-identity-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"xrpl-identity-mcp"
]
}
}
} assistant mcp add jarod-vyent-xrpl-identity-mcp -t stdio -c npx -a -y xrpl-identity-mcp
{
"mcpServers": {
"jarod-vyent-xrpl-identity-mcp": {
"command": "npx",
"args": [
"-y",
"xrpl-identity-mcp"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 21 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Sept 26 +1
- Security disclosure: unverified → fail ▼ functional
- 17 Sept 26 −2
- Security disclosure: fail → unverified ▼ functional
- Stability: pass → 0.80 functional
- 16 Sept 26 0
- Stability: 0.97 → pass security
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 −2
- Stability: pass → 0.80 functional
- 9 Sept 26 0
- Stability: 0.97 → pass security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Sept 2026 · Analysed npm/xrpl-identity-mcp@0.1.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 113 packages
| Packages resolved | 113 |
|---|---|
| Stale | 32 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
account_identity_summary Account Identity Summary ~79
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).
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Classic XRPL account address to summarize. |
No output schema declared.
No examples provided.
credential_list List Account Credentials ~67
List up to 400 XLS-70 Credential objects visible in an account owner directory, optionally filtered by whether the account is issuer or subject.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Classic XRPL account address. |
| role | string | – | Optional role filter comparing the account to Issuer or Subject fields. |
No output schema declared.
No examples provided.
credential_prepare_accept Prepare CredentialAccept ~89
Prepare an unsigned XLS-70 CredentialAccept transaction for a subject to accept an issued credential. Signing happens outside this server.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | yes | Classic XRPL subject account accepting the credential. |
| credentialType | string | yes | Credential type as UTF-8 text. Encoded to XRPL hex and capped at 64 bytes. |
| issuer | string | yes | Classic XRPL issuer account address. |
No output schema declared.
No examples provided.
credential_prepare_create Prepare CredentialCreate ~125
Prepare an unsigned XLS-70 CredentialCreate transaction. The issuer signs externally; this server only prepares JSON and never custodies keys.
| Name | Type | Req | Description |
|---|---|---|---|
| credentialType | string | yes | Credential type as UTF-8 text. Encoded to XRPL hex and capped at 64 bytes. |
| expiration | string | – | Optional ISO-8601 expiration time converted to Ripple epoch seconds. |
| issuerAccount | string | yes | Classic XRPL issuer account address. |
| subject | string | yes | Classic XRPL subject account address. |
| uri | string | – | Optional credential URI encoded as XRPL hex URI. |
No output schema declared.
No examples provided.
credential_prepare_delete Prepare CredentialDelete ~120
Prepare an unsigned XLS-70 CredentialDelete transaction. The submitter signs externally; this server never signs or stores keys.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | yes | Classic XRPL account submitting the delete transaction. |
| credentialType | string | yes | Credential type as UTF-8 text. Encoded to XRPL hex and capped at 64 bytes. |
| issuer | string | – | Optional issuer account; if omitted, Account may be treated as issuer by XRPL. |
| subject | – | – | Optional subject account; if omitted, Account may be treated as subject by XRPL. |
No output schema declared.
No examples provided.
credential_verify Verify Credential ~91
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.
| Name | Type | Req | Description |
|---|---|---|---|
| credentialType | string | yes | Credential type as UTF-8 text. Encoded to XRPL hex and capped at 64 bytes. |
| issuer | string | yes | Classic XRPL issuer account address. |
| subject | string | yes | Classic XRPL subject account address. |
No output schema declared.
No examples provided.
did_prepare_delete Prepare DIDDelete ~52
Prepare an unsigned XLS-40 DIDDelete transaction for an account DID. This server never signs; sign externally and verify the blob before submitting.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | yes | Classic XRPL account address deleting its DID. |
No output schema declared.
No examples provided.
did_prepare_set Prepare DIDSet ~119
Prepare an unsigned XLS-40 DIDSet transaction. This server does not sign or custody keys; sign externally and verify the signed blob before submission.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | yes | Classic XRPL account address setting the DID. |
| data | string | – | Optional DID data. UTF-8 encoded to XRPL hex Data. |
| didDocument | string | – | Optional DID document JSON/string payload. UTF-8 encoded to XRPL hex DIDDocument. |
| uri | string | – | Optional DID document URI. UTF-8 encoded to XRPL hex URI. |
No output schema declared.
No examples provided.
did_resolve Resolve XRPL DID ~114
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.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Classic XRPL address, did:xrpl:<address>, or did:xrpl:1:<address>. |
No output schema declared.
No examples provided.
signer_list_prepare_set Prepare SignerListSet ~107
Prepare an unsigned SignerListSet transaction to create, replace, or delete an XRPL multisign signer list. This server never signs or stores keys.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | yes | Classic XRPL account whose signer list is being changed. |
| quorum | integer | yes | Required signer weight sum. Use 0 with no signers to delete the list. |
| signers | array | yes | Signer entries. Use an empty array only when quorum is 0 to delete the list. |
No output schema declared.
No examples provided.
tx_decode_verify Decode and Verify Signed Transaction ~82
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.
| Name | Type | Req | Description |
|---|---|---|---|
| expectedIntent | object | – | Optional partial transaction JSON. Every provided field is compared against the decoded transaction. |
| signedBlob | string | yes | Signed XRPL transaction blob as a hexadecimal string. |
No output schema declared.
No examples provided.
tx_submit_signed Submit Signed Transaction ~78
Submit a pre-signed XRPL transaction blob and poll for validation. On mainnet this is blocked unless ALLOW_MAINNET_SUBMIT=true is set.
| Name | Type | Req | Description |
|---|---|---|---|
| failHard | boolean | – | Forward fail_hard behavior to rippled submit; defaults to false. |
| signedBlob | string | yes | Signed XRPL transaction blob as a hexadecimal string. |
No output schema declared.
No examples provided.
What is the io.github.jarod-vyent/xrpl-identity-mcp server?
io.github.jarod-vyent/xrpl-identity-mcp is listed in the public MCP registry as io.github.jarod-vyent/xrpl-identity-mcp. MCP server for XRPL identity: DIDs, credentials, signer lists, and safe transaction workflows. This page covers its npm package (xrpl-identity-mcp).
Is the io.github.jarod-vyent/xrpl-identity-mcp server safe to use?
io.github.jarod-vyent/xrpl-identity-mcp scores 83 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.jarod-vyent/xrpl-identity-mcp server expose?
io.github.jarod-vyent/xrpl-identity-mcp exposes 12 tools: did_resolve, did_prepare_set, did_prepare_delete, credential_prepare_create, credential_prepare_accept, and 7 more. Their descriptions and schemas cost roughly 1,123 tokens of context every time the server is loaded.
Is the io.github.jarod-vyent/xrpl-identity-mcp server still maintained?
io.github.jarod-vyent/xrpl-identity-mcp is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.jarod-vyent/xrpl-identity-mcp server under?
io.github.jarod-vyent/xrpl-identity-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.