Criptonlabs Agent APIs MCP server
com.criptonlabs/agent-apiscriptonlabs.comstreamable-httpv0.26.0Scanned
Read-only XRPL and Solana data for agents: fees, slippage, readiness. Free /mcp; x402 /mcp/pro.
35 tools: 4 do something that can't be undone and 31 change things.
- Reads private data · 0
- Reads text others write · 35
- Can send data out · 1
- 18 findings
Sign-in required, no OAuth metadata. Remote posture
With Anlyon
4 tools here do something that can't be undone. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the Criptonlabs Agent APIs MCP server can do
The Criptonlabs Agent APIs MCP server is published by criptonlabs.com, a domain the MCP Registry verified. It has 35 tools. It can do things that cannot be undone, such as sending, paying or publishing (xrpl_payment_readiness, xrpl_payment_verify, solana_transfer_readiness and solana_payment_verify) and create or change data (31 tools: xrpl_fee, xrpl_network_health, xrpl_orderbook, xrpl_slippage and 27 more), but cannot delete data. None of its tools only reads.
35 tools bring in text other people can write (xrpl_fee, xrpl_network_health, xrpl_orderbook and 32 more); 1 tool can send data out of your system (solana_payment_verify).
The fixed checks matched 18 findings (credentials-mention, annotation-conflict and base64-blob). Each one comes with the text it matched.
Its tools changed once since Anlyon Radar first saw them.
Last scanned Nov 21, 2026, version 0.26.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
35 tools
Can't be undone 4Claude Code: ask
solana_payment_verifyDid this settled Solana payment deliver the expected amount to the expected recipient?Reads text others writeCan send data out3 findings
Why it is in this group
- The name "solana_payment_verify" says "payment": a word that usually means money moves, which cannot be taken back.
- The input addresses people (input.recipient): what it sends cannot be taken back.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
- outboundThe input takes a destination (input.recipient): what the tool writes goes there.
Findings
- Warn
The description contains a 87-character base64 string.
What this check looks forMatched text
description: "...erify {"signature":"B7yABUkY4RudiDfoax94mfqVv2YuNJ4AVsg7LjdFT9Qm8bScsw3PoB2LxpuUqzCkiniK..."
- Warn
The description contains a 44-character base64 string.
What this check looks forMatched text
description: "...WYFaF","recipient":"GEJySUi6LjHwQWKD2BDg3TiGKwhKmBU7JJTjZfk1RD54","mint":"SOL","amou..."
- Warn
The server marks "solana_payment_verify" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The name "solana_payment_verify" says "payment": a word that usually means money moves, which cannot be taken back.
Description, as the server wrote it Did this settled Solana payment deliver the expected amount to the expected recipient? When to use: After a payment has been submitted: to confirm from the chain that the recipient received the mint and amount you expected, including the Token-2022 fee case. Prefer another tool: Before sending a transfer (use `/v1/solana/transfer-readiness`), or to list a wallet's transfers or balances (none are returned). Example: solana_payment_verify {"signature":"B7yABUkY4RudiDfoax94mfqVv2YuNJ4AVsg7LjdFT9Qm8bScsw3PoB2LxpuUqzCkiniKQJ9AKXfSfWaw1kWYFaF","recipient":"GEJySUi6LjHwQWKD2BDg3TiGKwhKmBU7JJTjZfk1RD54","mint":"SOL","amount":"0.02"}
Annotations the server declares
- readOnlyHint: true
- idempotentHint: true
- destructiveHint: false
- openWorldHint: true
solana_transfer_readinessWill this Solana transfer succeed?Reads text others write3 findings
Why it is in this group
- The name "solana_transfer_readiness" says "transfer": a word for a change that another call does not undo.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Findings
- Warn
The description contains a 44-character base64 string.
What this check looks forMatched text
description: "...eadiness {"source":"83astBRguLMdt2h5U1Tpdq5tjFoJ6noeGwaY3mDLVcri","destination":"A1T..."
- Warn
The description contains a 44-character base64 string.
What this check looks forMatched text
description: "...cri","destination":"A1TMhSGzQxMr1TboBKtgixKz1sS6REASMxPo1qsyTSJd","mint":"SOL","amou..."
- Warn
The server marks "solana_transfer_readiness" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The name "solana_transfer_readiness" says "transfer": a word for a change that another call does not undo.
Description, as the server wrote it Will this Solana transfer succeed? A verdict for SOL or an SPL or Token-2022 token. When to use: Before building or signing a Solana transfer, to learn whether it will fail and what it will cost in rent and fees. Prefer another tool: Not a simulation of the exact transaction (no priority fee, no program logic), not a token price or holder lookup, and not a way to read raw accounts. Example: solana_transfer_readiness {"source":"83astBRguLMdt2h5U1Tpdq5tjFoJ6noeGwaY3mDLVcri","destination":"A1TMhSGzQxMr1TboBKtgixKz1sS6REASMxPo1qsyTSJd","mint":"SOL","amount":"0.5"}
Annotations the server declares
- readOnlyHint: true
- idempotentHint: true
- destructiveHint: false
- openWorldHint: true
xrpl_payment_readinessPre-payment check: can this payment from source to destination succeed now?Reads text others write2 findings
Why it is in this group
- The name "xrpl_payment_readiness" says "payment": a word that usually means money moves, which cannot be taken back.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Findings
- Info
The input schema at properties.credentials.description mentions "Credential".
What this check looks forMatched text
inputSchema.properties.credentials.description: "Comma-separated Credential entry IDs (1 to 8, 64 hex); checked wit..."
- Warn
The server marks "xrpl_payment_readiness" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The name "xrpl_payment_readiness" says "payment": a word that usually means money moves, which cannot be taken back.
Description, as the server wrote it Pre-payment check: can this payment from source to destination succeed now? When to use: Right before sending a payment: to catch a missing or unfunded destination, a required destination tag, deposit authorization, missing or frozen trust lines, MPT authorization and locks, insufficient balance and issuer freezes, in one call. Prefer another tool: To find a multi-hop route or the source amount needed for a cross-currency payment (use the paths endpoint), or to list balances (use `/v1/xrpl/account/{address}/summary`). Example: xrpl_payment_readiness {"source":"rvYAfWj5gh67oV6fW32ZzP3Aw4Eubs59B","destination":"rhub8VRN55s94qWKDv6jmDy1pUykJzF3wq"}
Annotations the server declares
- readOnlyHint: true
- idempotentHint: true
- destructiveHint: false
- openWorldHint: true
xrpl_payment_verifyDid this settled payment deliver the expected asset and amount to the expected account?Reads text others write1 finding
Why it is in this group
- The name "xrpl_payment_verify" says "payment": a word that usually means money moves, which cannot be taken back.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Findings
- Warn
The server marks "xrpl_payment_verify" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The name "xrpl_payment_verify" says "payment": a word that usually means money moves, which cannot be taken back.
Description, as the server wrote it Did this settled payment deliver the expected asset and amount to the expected account? When to use: After a payment has been submitted: to confirm from the ledger that it delivered the asset and amount you expected to the account you expected, including the partial-payment case. Prefer another tool: Before sending a payment (use `/v1/xrpl/payment-readiness`), or to list an account's recent payments (use `/v1/xrpl/account/{address}/transactions`). Example: xrpl_payment_verify {"hash":"002C12C53476173ABC1001505C40A24CCC90F642480C924C1B748E339FA1B069","destination":"rfaecmugiPaAkFpBT9Bmq8f3n42oXe6m1C","asset":"XRP","amount":"0.00001"}
Annotations the server declares
- readOnlyHint: true
- idempotentHint: true
- destructiveHint: false
- openWorldHint: true
Changes things 31Claude Code: ask
solana_address_kindWhat kind of Solana account is this address, and should a payment go to it?Reads text others write1 finding
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Findings
- Warn
The description contains a 44-character base64 string.
What this check looks forMatched text
description: "...ss_kind {"address":"Ffeie177PRngys3SwNH44AYdT9yExm63GAmTXHdmL1k1"}"
Description, as the server wrote it What kind of Solana account is this address, and should a payment go to it? When to use: Before sending SOL or tokens to an address: to learn whether it is a wallet, a token account (and whose), a mint, a program or another program-owned account. Prefer another tool: To check one transfer end to end with amounts and fees (use `/v1/solana/transfer-readiness`), or to read balances (none are returned). Example: solana_address_kind {"address":"Ffeie177PRngys3SwNH44AYdT9yExm63GAmTXHdmL1k1"}
Annotations the server declares
- readOnlyHint: true
- idempotentHint: true
- destructiveHint: false
- openWorldHint: true
solana_fee_readinessCan this Solana account pay the fees of N transactions now?Reads text others write1 finding
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Findings
- Warn
The description contains a 44-character base64 string.
What this check looks forMatched text
description: "...adiness {"address":"83astBRguLMdt2h5U1Tpdq5tjFoJ6noeGwaY3mDLVcri"}"
Description, as the server wrote it Can this Solana account pay the fees of N transactions now? When to use: Before sending one or more transactions from a wallet: to learn whether it can pay their base fees without dropping below its rent-exempt minimum. Prefer another tool: To check one SOL or token transfer end to end (use `/v1/solana/transfer-readiness`), or to read a balance (none is returned). Example: solana_fee_readiness {"address":"83astBRguLMdt2h5U1Tpdq5tjFoJ6noeGwaY3mDLVcri"}
Annotations the server declares
- readOnlyHint: true
- idempotentHint: true
- destructiveHint: false
- openWorldHint: true
solana_latest_slotLatest finalized Solana slot and its block time.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Latest finalized Solana slot and its block time. When to use: To check how fresh the finalized view of Solana is, or to anchor a read to a slot. Prefer another tool: Not a tip-of-chain feed: it is finalized, not processed or confirmed, and it is cached for 2 seconds. Example: solana_latest_slot {}
Annotations the server declares
- readOnlyHint: true
- idempotentHint: true
- destructiveHint: false
- openWorldHint: true
solana_network_healthWhether Solana data is currently being served: latest probe status and finalized slot.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Whether Solana data is currently being served: latest probe status and finalized slot. When to use: Before relying on the Solana verdict endpoints, or to explain a 503 from them. Prefer another tool: Not a measure of the Solana network itself, only of this service's access to it; use the latest-slot endpoint to see chain progress. Example: solana_network_health {}
Annotations the server declares
- readOnlyHint: true
- idempotentHint: true
- destructiveHint: false
- openWorldHint: true
solana_stablecoinIs this Solana mint the canonical stablecoin it claims to be?Reads text others write1 finding
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Findings
- Warn
The description contains a 44-character base64 string.
What this check looks forMatched text
description: "...stablecoin {"mint":"2b1kV6DkPAnxd5ixfnxCpjxmKwqjjaYmCZfHsFu24GXo"}"
Description, as the server wrote it Is this Solana mint the canonical stablecoin it claims to be? When to use: Before accepting or quoting a stablecoin: to check the mint is the canonical one and that its mint facts have not changed since the snapshot. Prefer another tool: To read supply or balances (use `/v1/solana/token/{mint}`), or as a regulatory or licensing check: none is served. Example: solana_stablecoin {"mint":"2b1kV6DkPAnxd5ixfnxCpjxmKwqjjaYmCZfHsFu24GXo"}
Annotations the server declares
- readOnlyHint: true
- idempotentHint: true
- destructiveHint: false
- openWorldHint: true
solana_tokenIs this Solana token safe to hold or receive?Reads text others write1 finding
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Findings
- Warn
The description contains a 44-character base64 string.
What this check looks forMatched text
description: "...lana_token {"mint":"EPjFWdd5AufqSSqeM2qN1xzybapC8G4wEGGkZwyTDt1v"}"
Description, as the server wrote it Is this Solana token safe to hold or receive? A SAFE, WARN or DANGER verdict. When to use: Before accepting or swapping into an unfamiliar token, to see whether its mint can freeze, mint more, move or tax balances. Prefer another tool: Not a price, liquidity or holder lookup and not an audit of the token's project; it reads only the mint account. Example: solana_token {"mint":"EPjFWdd5AufqSSqeM2qN1xzybapC8G4wEGGkZwyTDt1v"}
Annotations the server declares
- readOnlyHint: true
- idempotentHint: true
- destructiveHint: false
- openWorldHint: true
solana_token_hygieneWhich of this wallet's Solana token accounts can be closed for rent, or are delegated or frozen?Reads text others write1 finding
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Findings
- Warn
The description contains a 44-character base64 string.
What this check looks forMatched text
description: "...hygiene {"address":"83astBRguLMdt2h5U1Tpdq5tjFoJ6noeGwaY3mDLVcri"}"
Description, as the server wrote it Which of this wallet's Solana token accounts can be closed for rent, or are delegated or frozen? When to use: Before cleaning up a wallet: to learn how much rent closing its empty token accounts returns, and whether any token account has an active delegate or is frozen. Prefer another tool: To list token accounts, mints or balances (none are returned), or to check one transfer end to end (use `/v1/solana/transfer-readiness`). Example: solana_token_hygiene {"address":"83astBRguLMdt2h5U1Tpdq5tjFoJ6noeGwaY3mDLVcri"}
Annotations the server declares
- readOnlyHint: true
- idempotentHint: true
- destructiveHint: false
- openWorldHint: true
solana_x402_preflightCan this payer settle this x402 payment requirement right now?Reads text others write3 findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Findings
- Warn
The description contains a 44-character base64 string.
What this check looks forMatched text
description: "...preflight {"asset":"2b1kV6DkPAnxd5ixfnxCpjxmKwqjjaYmCZfHsFu24GXo","amount":"1000000"..."
- Warn
The description contains a 44-character base64 string.
What this check looks forMatched text
description: "..."1000000","pay_to":"29d2S7vB453rNYFdR5Ycwt7y9haRT5fwVwL9zTmBhfV2","payer":"6vk7icY2F..."
- Warn
The description contains a 44-character base64 string.
What this check looks forMatched text
description: "...9zTmBhfV2","payer":"6vk7icY2FzdMTzMGE4aNRSzovanAmS7xsv9uHwj4YuzY"}"
Description, as the server wrote it Can this payer settle this x402 payment requirement right now? When to use: After an x402 server answered 402 with a Solana `exact` requirement: to check, before signing, that this payer can settle that exact requirement to that recipient now. Prefer another tool: For a transfer that is not an x402 requirement (use `/v1/solana/transfer-readiness`), or once the payment has settled (use `/v1/solana/payment/verify`). Example: solana_x402_preflight {"asset":"2b1kV6DkPAnxd5ixfnxCpjxmKwqjjaYmCZfHsFu24GXo","amount":"1000000","pay_to":"29d2S7vB453rNYFdR5Ycwt7y9haRT5fwVwL9zTmBhfV2","payer":"6vk7icY2FzdMTzMGE4aNRSzovanAmS7xsv9uHwj4YuzY"}
Annotations the server declares
- readOnlyHint: true
- idempotentHint: true
- destructiveHint: false
- openWorldHint: true
xrpl_account_commitmentsAn account's escrows, payment channels and checks by direction, its deposit preauthorizations, tickets and owner reserve, and what blocks deleting it.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it An account's escrows, payment channels and checks by direction, its deposit preauthorizations, tickets and owner reserve, and what blocks deleting it. When to use: Before deleting or winding down an account: to see which escrows can be finished or cancelled now, how much XRP is left in its payment channels, which checks expire soon, how much XRP its owned objects lock in reserve, and which owned entries block AccountDelete. Prefer another tool: To list the open DEX offers and how funded each one is (use `/v1/xrpl/account/{address}/offers`) or the trust lines (use `/v1/xrpl/account/{address}/lines`); for the balance and owner count, use `/v1/xrpl/account/{address}/summary`. Example: xrpl_account_commitments {"address":"rGAs3npYy1VwLPE92kvKvA2QYLR6FSA9n6"}
Annotations the server declares
- readOnlyHint: true
- idempotentHint: true
- destructiveHint: false
- openWorldHint: true
xrpl_account_linesOne page of an account's trust lines, with an opaque cursor for the next page.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it One page of an account's trust lines, with an opaque cursor for the next page. When to use: To list every trust line of an account (balances, limits, freeze and authorization flags), page by page. Prefer another tool: For a quick capped overview with the XRP balance, use `/v1/xrpl/account/{address}/summary`; for issued totals of a token, use the token endpoint. Example: xrpl_account_lines {"address":"rvYAfWj5gh67oV6fW32ZzP3Aw4Eubs59B"}
Annotations the server declares
- readOnlyHint: true
- idempotentHint: true
- destructiveHint: false
- openWorldHint: true
xrpl_account_offersOne page of an account's open DEX offers, with how funded each one is.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it One page of an account's open DEX offers, with how funded each one is. When to use: To see which DEX offers an account has open and whether each can still execute: before cancelling or replacing offers, or to check how much of an account's open offers its balances back. Prefer another tool: To read the order book of a pair (use `/v1/xrpl/orderbook`) or estimate the cost of a trade (use `/v1/xrpl/slippage`); for the account's balances and trust lines, use `/v1/xrpl/account/{address}/summary` or `/v1/xrpl/account/{address}/lines`. Example: xrpl_account_offers {"address":"rGAs3npYy1VwLPE92kvKvA2QYLR6FSA9n6"}
Annotations the server declares
- readOnlyHint: true
- idempotentHint: true
- destructiveHint: false
- openWorldHint: true
xrpl_account_summaryXRP balance, sequence, owner count, transfer rate and trust lines (capped) for an account.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it XRP balance, sequence, owner count, transfer rate and trust lines (capped) for an account. When to use: To inspect an account before building a transaction for it. Prefer another tool: Not for transaction history or reserves; it is a summary, not a full account dump. Example: xrpl_account_summary {"address":"rvYAfWj5gh67oV6fW32ZzP3Aw4Eubs59B"}
Annotations the server declares
- readOnlyHint: true
- idempotentHint: true
- destructiveHint: false
- openWorldHint: true
xrpl_account_transactionsOne page of an account's most recent validated transactions, newest first.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it One page of an account's most recent validated transactions, newest first. When to use: To check what an account did recently (payments sent or received, offers, trust line changes) and whether each transaction succeeded. Prefer another tool: For balances and trust lines, use `/v1/xrpl/account/{address}/summary` or `/v1/xrpl/account/{address}/lines`; for full archival history, use a full-history node or indexer: history depth depends on the serving node and older pages may be slower. Example: xrpl_account_transactions {"address":"rvYAfWj5gh67oV6fW32ZzP3Aw4Eubs59B"}
Annotations the server declares
- readOnlyHint: true
- idempotentHint: true
- destructiveHint: false
- openWorldHint: true
xrpl_address_kindWhat kind of XRPL address is this, and what does a payment to it need?Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it What kind of XRPL address is this, and what does a payment to it need? When to use: Before paying or listing an XRPL address: to learn whether it exists, whether it is a pseudo-account that rejects payments, and whether a payment needs a destination tag or deposit preauthorization. Prefer another tool: To check one payment end to end with amounts, trust lines and reserves (use `/v1/xrpl/payment-readiness`), or to read balances (use `/v1/xrpl/account/{address}/summary`). Example: xrpl_address_kind {"address":"rhWTXC2m2gGGA9WozUaoMm6kLAVPb1tcS3"}
Annotations the server declares
- readOnlyHint: true
- idempotentHint: true
- destructiveHint: false
- openWorldHint: true
xrpl_ammAMM pool reserves and trading fee for an asset pair.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it AMM pool reserves and trading fee for an asset pair. When to use: To read AMM pool depth and fee for a pair. Prefer another tool: It does not estimate slippage or compare venues (use the slippage page for the CLOB vs AMM comparison); a pair without a pool returns 404. Example: xrpl_amm {"a":"XRP","b":"5553444300000000000000000000000000000000.rGm7WCVp9gb4jZHWTEtGUr4dd74z2XuWhE"}
Annotations the server declares
- readOnlyHint: true
- idempotentHint: true
- destructiveHint: false
- openWorldHint: true
xrpl_domain_eligibilityIs this account a member of this XRPL permissioned domain, as its owner or through an accepted, unexpired credential?Reads text others write1 finding
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Findings
- Info
The description mentions "credential".
What this check looks forMatched text
description: "...owner or through an accepted, unexpired credential? When to use: Before trading in a permi..."
Description, as the server wrote it Is this account a member of this XRPL permissioned domain, as its owner or through an accepted, unexpired credential? When to use: Before trading in a permissioned order book (`/v1/xrpl/orderbook` or `/v1/xrpl/slippage` with `domain`): to check whether an account is a member of the domain, as its owner or through an accepted, unexpired credential, and which credential qualifies it. Prefer another tool: To check whether one payment can succeed now (use `/v1/xrpl/payment-readiness`, whose `credentials` takes the `credential_id` values of this answer), or to read the permissioned order book itself (use `/v1/xrpl/orderbook` with `domain`). Example: xrpl_domain_eligibility {"domain_id":"DBABFD44A80DB623522628550B270FA5E2A845341E137530728E2E3699181A4E","account":"rcKV6taNcBAi8GxudZnMdFUPcH3Ls5TAv"}
Annotations the server declares
- readOnlyHint: true
- idempotentHint: true
- destructiveHint: false
- openWorldHint: true
xrpl_feeCurrent XRPL fee tiers in drops with a congestion score.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Current XRPL fee tiers in drops with a congestion score. When to use: Before submitting a transaction, to choose a `Fee` and to decide whether the network is congested. Prefer another tool: Not a price feed and not a historical series; it describes the current open ledger only. Example: xrpl_fee {}
Annotations the server declares
- readOnlyHint: true
- idempotentHint: true
- destructiveHint: false
- openWorldHint: true
xrpl_latest_ledgerLatest validated ledger index, hash and close time.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Latest validated ledger index, hash and close time. When to use: To anchor other readings to a ledger or to check how current the network view is. Prefer another tool: Not for transaction data or account state; use the account endpoint for those. Example: xrpl_latest_ledger {}
Annotations the server declares
- readOnlyHint: true
- idempotentHint: true
- destructiveHint: false
- openWorldHint: true
xrpl_metrics_arbitrageWhether a pair's AMM pool and its order book are apart after the AMM fee: per direction the gap, the executable size and the profit after transfer fees.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Whether a pair's AMM pool and its order book are apart after the AMM fee: per direction the gap, the executable size and the profit after transfer fees. When to use: To find whether a pair's AMM pool and its funded order book are apart after the AMM fee, in which direction, how much base the gap allows and the profit after transfer fees, optionally with the cycles of the USD registry stablecoins via XRP. Prefer another tool: To estimate the cost of a trade of a given size, CLOB against AMM (use `/v1/xrpl/slippage`), or to read the order book levels (use `/v1/xrpl/orderbook`) or an AMM pool (use `/v1/xrpl/amm/{a}/{b}`); the answer measures the ledger and is not an executable quote. Example: xrpl_metrics_arbitrage {"base":"XRP","quote":"524C555344000000000000000000000000000000.rMxCKbEDwqr76QuheSUMdEGf4B9xJ8m5De"}
Annotations the server declares
- readOnlyHint: true
- idempotentHint: true
- destructiveHint: false
- openWorldHint: true
xrpl_metrics_fx_basisThe EUR/USD rate the XRP Ledger DEX implies through the EUR registry stablecoin against each USD registry stablecoin, and its basis to the ECB reference rate.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it The EUR/USD rate the XRP Ledger DEX implies through the EUR registry stablecoin against each USD registry stablecoin, and its basis to the ECB reference rate. When to use: To measure, from the XRP Ledger's own order books and AMM pools, the EUR/USD rate the DEX implies through the EUR registry stablecoin against each USD registry stablecoin, and how far it sits from the ECB reference rate. Prefer another tool: To measure how far one registry stablecoin trades from its peg against another registry coin (use `/v1/xrpl/metrics/peg`), or to read an order book or an AMM pool (use `/v1/xrpl/orderbook` or `/v1/xrpl/amm/{a}/{b}`). Example: xrpl_metrics_fx_basis {}
Annotations the server declares
- readOnlyHint: true
- idempotentHint: true
- destructiveHint: false
- openWorldHint: true
xrpl_metrics_liquidity_stressHow stressed a registry stablecoin's liquidity is against its peg default: a score from 0 to 100, its band and the four weighted components behind it.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it How stressed a registry stablecoin's liquidity is against its peg default: a score from 0 to 100, its band and the four weighted components behind it. When to use: To score, from the XRP Ledger's own order books, AMM pool and issuer account, how stressed a registry stablecoin's liquidity is against its peg default, as one score with its band and the components behind it. Prefer another tool: To read the peg deviation of each price route (use `/v1/xrpl/metrics/peg`), or to check that an issued currency is the canonical registry coin and read its issuer posture (use `/v1/xrpl/stablecoin/{asset}`); for an asset outside the registry, which this route refuses, read its order book (`/v1/xrpl/orderbook`) or its AMM pool (`/v1/xrpl/amm/{a}/{b}`). Example: xrpl_metrics_liquidity_stress {"asset":"524C555344000000000000000000000000000000.rMxCKbEDwqr76QuheSUMdEGf4B9xJ8m5De"}
Annotations the server declares
- readOnlyHint: true
- idempotentHint: true
- destructiveHint: false
- openWorldHint: true
xrpl_metrics_pegHow far a registry stablecoin trades from its peg on the XRP Ledger DEX: the deviation of each price route, their median and a status.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it How far a registry stablecoin trades from its peg on the XRP Ledger DEX: the deviation of each price route, their median and a status. When to use: To check, from the XRP Ledger's own order books and AMM pools, how far a registry stablecoin trades from its peg against another registry coin, and how much funded depth sits near the peg. Prefer another tool: To check that an issued currency is the canonical registry coin, or to read its issuer posture (use `/v1/xrpl/stablecoin/{asset}`); for an asset outside the registry, which this route refuses, read its order book (`/v1/xrpl/orderbook`) or its AMM pool (`/v1/xrpl/amm/{a}/{b}`). Example: xrpl_metrics_peg {"asset":"524C555344000000000000000000000000000000.rMxCKbEDwqr76QuheSUMdEGf4B9xJ8m5De"}
Annotations the server declares
- readOnlyHint: true
- idempotentHint: true
- destructiveHint: false
- openWorldHint: true
xrpl_metrics_pressureBuy or sell pressure of a pair's funded order book: a score from 0 to 100 and its band, from the depth near mid.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Buy or sell pressure of a pair's funded order book: a score from 0 to 100 and its band, from the depth near mid. When to use: To measure how the funded depth near mid of a pair's order book is split between bids and asks, as one score with its band. Prefer another tool: To read the order book levels (use `/v1/xrpl/orderbook`), the cost of a trade of a given size, CLOB against AMM (use `/v1/xrpl/slippage`), or an AMM pool (use `/v1/xrpl/amm/{a}/{b}`). Example: xrpl_metrics_pressure {"base":"XRP","quote":"5553444300000000000000000000000000000000.rGm7WCVp9gb4jZHWTEtGUr4dd74z2XuWhE"}
Annotations the server declares
- readOnlyHint: true
- idempotentHint: true
- destructiveHint: false
- openWorldHint: true
xrpl_mptMPT issuance: issuer, supply, scale, transfer fee and flags.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it MPT issuance: issuer, supply, scale, transfer fee and flags. When to use: Before accepting or sending an MPT: to check its issuer, decimal scale, supply against its maximum, transfer fee, and whether it can be transferred, locked, escrowed or clawed back. Prefer another tool: To check whether one MPT payment between two accounts can succeed now (use `/v1/xrpl/payment-readiness` with the issuance id as `asset`), or for a trust-line token written `CODE.issuer` (use `/v1/xrpl/token/{asset}`). Example: xrpl_mpt {"mpt_issuance_id":"05FA6AB8561E39FA605779B829BB5974E82B40AF173D6AF3"}
Annotations the server declares
- readOnlyHint: true
- idempotentHint: true
- destructiveHint: false
- openWorldHint: true
xrpl_network_healthOverall and per-node health of the upstream XRPL nodes.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Overall and per-node health of the upstream XRPL nodes. When to use: To decide whether to trust or retry data, or to explain a 503 from another endpoint. Prefer another tool: Not a probe of your own connectivity; it reports the service's upstream nodes. Example: xrpl_network_health {}
Annotations the server declares
- readOnlyHint: true
- idempotentHint: true
- destructiveHint: false
- openWorldHint: true
xrpl_orderbookCLOB order book for a currency pair with unfunded offers removed.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it CLOB order book for a currency pair with unfunded offers removed. When to use: To read executable liquidity for a pair on the XRPL central limit order book (CLOB). Prefer another tool: Not for AMM liquidity (use the amm page) and not for a cost estimate (use the slippage page). Example: xrpl_orderbook {"base":"XRP","quote":"USD.rvYAfWj5gh67oV6fW32ZzP3Aw4Eubs59B"}
Annotations the server declares
- readOnlyHint: true
- idempotentHint: true
- destructiveHint: false
- openWorldHint: true
xrpl_pathsMulti-hop payment paths and their source cost.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Multi-hop payment paths and their source cost. When to use: Before a cross-currency or multi-hop payment: to see whether a route exists and how much the source would spend to deliver the amount. A call can take up to about 20 seconds and paths may be non-optimal. Prefer another tool: To check whether a direct payment can succeed (use `/v1/xrpl/payment-readiness`), or for the single-hop cost of a trade on one pair (use `/v1/xrpl/slippage`, which compares the order book and the AMM). Example: xrpl_paths {"source":"rvYAfWj5gh67oV6fW32ZzP3Aw4Eubs59B","destination":"rhub8VRN55s94qWKDv6jmDy1pUykJzF3wq","asset":"XRP","amount":"1"}
Annotations the server declares
- readOnlyHint: true
- idempotentHint: true
- destructiveHint: false
- openWorldHint: true
xrpl_slippageSlippage and average price for buying or selling an amount of base currency.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Slippage and average price for buying or selling an amount of base currency. When to use: Before placing a market-style trade, to size it against available depth and to see whether the CLOB or the AMM pool gives the better average price for the side. Prefer another tool: It is an estimate, not a quote, and it does not split an amount across venues or route through other pairs. To read pool reserves, use the amm page. Example: xrpl_slippage {"base":"XRP","quote":"USD.rvYAfWj5gh67oV6fW32ZzP3Aw4Eubs59B","amount":"1000"}
Annotations the server declares
- readOnlyHint: true
- idempotentHint: true
- destructiveHint: false
- openWorldHint: true
xrpl_stablecoinIs this XRPL issued currency the canonical stablecoin it claims to be?Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Is this XRPL issued currency the canonical stablecoin it claims to be? When to use: Before accepting or quoting a stablecoin: to check the asset is the canonical one and that its issuer facts have not changed since the snapshot. Prefer another tool: To read supply or balances (use `/v1/xrpl/token/{asset}` or `/v1/xrpl/account/{address}/lines`), or as a regulatory or licensing check: none is served. Example: xrpl_stablecoin {"asset":"4555524F50000000000000000000000000000000.rMkEuRii9w9uBMQDnWV5AA43gvYZR9JxVK"}
Annotations the server declares
- readOnlyHint: true
- idempotentHint: true
- destructiveHint: false
- openWorldHint: true
xrpl_tokenIssuer data for an issued asset: flags, domain, transfer fee and total issued.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Issuer data for an issued asset: flags, domain, transfer fee and total issued. When to use: Before accepting or sending an issued token: check that the issuer exists, is not frozen, whether holders need authorization, and the transfer fee charged on every transfer between non-issuer accounts. Prefer another tool: For XRP (not an issued asset; 400), for one account's own balances use `/v1/xrpl/account/{address}/lines`, and for prices use `/v1/xrpl/orderbook` or `/v1/xrpl/amm/{a}/{b}`. Example: xrpl_token {"asset":"USD.rvYAfWj5gh67oV6fW32ZzP3Aw4Eubs59B"}
Annotations the server declares
- readOnlyHint: true
- idempotentHint: true
- destructiveHint: false
- openWorldHint: true
xrpl_x402_preflightCan this payer settle this x402 payment requirement right now?Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Can this payer settle this x402 payment requirement right now? When to use: After an x402 server answered 402 with an XRPL `exact` requirement: to check, before signing, that this payer can settle that exact requirement to that recipient now. Prefer another tool: For a payment that is not an x402 requirement (use `/v1/xrpl/payment-readiness`), or once the payment has settled (use `/v1/xrpl/payment/verify`). Example: xrpl_x402_preflight {"asset":"XRP","amount":"10000000","pay_to":"rhub8VRN55s94qWKDv6jmDy1pUykJzF3wq","payer":"rvYAfWj5gh67oV6fW32ZzP3Aw4Eubs59B"}
Annotations the server declares
- readOnlyHint: true
- idempotentHint: true
- destructiveHint: false
- openWorldHint: true
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write35
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out1
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:36 UTC, unchanged since Nov 13, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 429
- tools/list served without credentials
- no
- Tools that change things, listed without credentials
- 0
- Protocol version
- not observed
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
The probe stopped: initialize answered HTTP 429.
Posture changes
- Nov 13, 2026
- HTTP status of an anonymous initialize: 200 to 429
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 16 to 0
- Protocol version: 2025-06-18 to none
Findings
Matches of fixed checks, with the text they matched.
The server marks "xrpl_payment_readiness" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The name "xrpl_payment_readiness" says "payment": a word that usually means money moves, which cannot be taken back.
The server marks "xrpl_payment_verify" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The name "xrpl_payment_verify" says "payment": a word that usually means money moves, which cannot be taken back.
The description contains a 44-character base64 string.
What this check looks forMatched text
description: "...eadiness {"source":"83astBRguLMdt2h5U1Tpdq5tjFoJ6noeGwaY3mDLVcri","destination":"A1T..."
The description contains a 44-character base64 string.
What this check looks forMatched text
description: "...cri","destination":"A1TMhSGzQxMr1TboBKtgixKz1sS6REASMxPo1qsyTSJd","mint":"SOL","amou..."
The server marks "solana_transfer_readiness" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The name "solana_transfer_readiness" says "transfer": a word for a change that another call does not undo.
- Warnsolana_token
The description contains a 44-character base64 string.
What this check looks forMatched text
description: "...lana_token {"mint":"EPjFWdd5AufqSSqeM2qN1xzybapC8G4wEGGkZwyTDt1v"}"
Show 12 more findingsShow fewer
The description contains a 44-character base64 string.
What this check looks forMatched text
description: "...adiness {"address":"83astBRguLMdt2h5U1Tpdq5tjFoJ6noeGwaY3mDLVcri"}"
The description contains a 44-character base64 string.
What this check looks forMatched text
description: "...hygiene {"address":"83astBRguLMdt2h5U1Tpdq5tjFoJ6noeGwaY3mDLVcri"}"
The description contains a 44-character base64 string.
What this check looks forMatched text
description: "...ss_kind {"address":"Ffeie177PRngys3SwNH44AYdT9yExm63GAmTXHdmL1k1"}"
The description contains a 44-character base64 string.
What this check looks forMatched text
description: "...stablecoin {"mint":"2b1kV6DkPAnxd5ixfnxCpjxmKwqjjaYmCZfHsFu24GXo"}"
The description contains a 87-character base64 string.
What this check looks forMatched text
description: "...erify {"signature":"B7yABUkY4RudiDfoax94mfqVv2YuNJ4AVsg7LjdFT9Qm8bScsw3PoB2LxpuUqzCkiniK..."
The description contains a 44-character base64 string.
What this check looks forMatched text
description: "...WYFaF","recipient":"GEJySUi6LjHwQWKD2BDg3TiGKwhKmBU7JJTjZfk1RD54","mint":"SOL","amou..."
The server marks "solana_payment_verify" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The name "solana_payment_verify" says "payment": a word that usually means money moves, which cannot be taken back.
The description contains a 44-character base64 string.
What this check looks forMatched text
description: "...preflight {"asset":"2b1kV6DkPAnxd5ixfnxCpjxmKwqjjaYmCZfHsFu24GXo","amount":"1000000"..."
The description contains a 44-character base64 string.
What this check looks forMatched text
description: "..."1000000","pay_to":"29d2S7vB453rNYFdR5Ycwt7y9haRT5fwVwL9zTmBhfV2","payer":"6vk7icY2F..."
The description contains a 44-character base64 string.
What this check looks forMatched text
description: "...9zTmBhfV2","payer":"6vk7icY2FzdMTzMGE4aNRSzovanAmS7xsv9uHwj4YuzY"}"
The input schema at properties.credentials.description mentions "Credential".
What this check looks forMatched text
inputSchema.properties.credentials.description: "Comma-separated Credential entry IDs (1 to 8, 64 hex); checked wit..."
The description mentions "credential".
What this check looks forMatched text
description: "...owner or through an accepted, unexpired credential? When to use: Before trading in a permi..."
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools19 added, 11 changed.+19 added~11 changedView diff
- Added:solana_address_kindChanges things
- Added:solana_fee_readinessChanges things
- Added:solana_payment_verifyCan't be undone
- Added:solana_stablecoinChanges things
- Added:solana_token_hygieneChanges things
- Added:solana_x402_preflightChanges things
- Added:xrpl_account_commitmentsChanges things
- Added:xrpl_account_offersChanges things
- Added:xrpl_address_kindChanges things
- Added:xrpl_domain_eligibilityChanges things
- Added:xrpl_metrics_arbitrageChanges things
- Added:xrpl_metrics_fx_basisChanges things
- Added:xrpl_metrics_liquidity_stressChanges things
- Added:xrpl_metrics_pegChanges things
- Added:xrpl_metrics_pressureChanges things
- Added:xrpl_mptChanges things
- Added:xrpl_payment_verifyCan't be undone
- Added:xrpl_stablecoinChanges things
- Added:xrpl_x402_preflightChanges things
- Changed:solana_transfer_readinessCan't be undoneinputSchema
- Changed:xrpl_account_linesChanges thingsdescription
- Changed:xrpl_account_summaryChanges thingsdescription
- Changed:xrpl_account_transactionsChanges thingsdescription
- Changed:xrpl_ammChanges thingsdescriptioninputSchema
- Changed:xrpl_feeChanges thingsdescription
- Changed:xrpl_orderbookChanges thingsdescriptioninputSchema
- Changed:xrpl_pathsChanges thingsdescriptioninputSchema
- Changed:xrpl_payment_readinessCan't be undonedescriptioninputSchema
- Changed:xrpl_slippageChanges thingsdescriptioninputSchema
- Changed:xrpl_tokenChanges thingsdescriptioninputSchema
PostureRemote posture changed. HTTP status of an anonymous initialize: 200 -> 429; tools/list served without credentials: yes -> no; Tools that change things, listed without credentials: 16 -> 0 (and 1 more).View diff
- HTTP status of an anonymous initialize: 200 to 429
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 16 to 0
- Protocol version: 2025-06-18 to none
Install
Pinned to version 0.26.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http agent-apis https://api.criptonlabs.com/mcpclaude mcp add --transport http agent-apis https://api.criptonlabs.com/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [],
"ask": [
"mcp__agent-apis__xrpl_fee",
"mcp__agent-apis__xrpl_network_health",
"mcp__agent-apis__xrpl_orderbook",
"mcp__agent-apis__xrpl_slippage",
"mcp__agent-apis__xrpl_amm",
"mcp__agent-apis__xrpl_account_summary",
"mcp__agent-apis__xrpl_account_lines",
"mcp__agent-apis__xrpl_account_transactions",
"mcp__agent-apis__xrpl_token",
"mcp__agent-apis__xrpl_payment_readiness",
"mcp__agent-apis__xrpl_paths",
"mcp__agent-apis__xrpl_latest_ledger",
"mcp__agent-apis__xrpl_mpt",
"mcp__agent-apis__xrpl_address_kind",
"mcp__agent-apis__xrpl_stablecoin",
"mcp__agent-apis__xrpl_payment_verify",
"mcp__agent-apis__xrpl_x402_preflight",
"mcp__agent-apis__xrpl_domain_eligibility",
"mcp__agent-apis__xrpl_account_offers",
"mcp__agent-apis__xrpl_account_commitments",
"mcp__agent-apis__xrpl_metrics_pressure",
"mcp__agent-apis__xrpl_metrics_peg",
"mcp__agent-apis__xrpl_metrics_fx_basis",
"mcp__agent-apis__xrpl_metrics_arbitrage",
"mcp__agent-apis__xrpl_metrics_liquidity_stress",
"mcp__agent-apis__solana_transfer_readiness",
"mcp__agent-apis__solana_token",
"mcp__agent-apis__solana_latest_slot",
"mcp__agent-apis__solana_network_health",
"mcp__agent-apis__solana_fee_readiness",
"mcp__agent-apis__solana_token_hygiene",
"mcp__agent-apis__solana_address_kind",
"mcp__agent-apis__solana_stablecoin",
"mcp__agent-apis__solana_payment_verify",
"mcp__agent-apis__solana_x402_preflight"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as agent-apis. Review it before you use it.
Capability tags behind 35 rules
- mcp__agent-apis__xrpl_fee untrusted-input
- mcp__agent-apis__xrpl_network_health untrusted-input
- mcp__agent-apis__xrpl_orderbook untrusted-input
- mcp__agent-apis__xrpl_slippage untrusted-input
- mcp__agent-apis__xrpl_amm untrusted-input
- mcp__agent-apis__xrpl_account_summary untrusted-input
- mcp__agent-apis__xrpl_account_lines untrusted-input
- mcp__agent-apis__xrpl_account_transactions untrusted-input
- mcp__agent-apis__xrpl_token untrusted-input
- mcp__agent-apis__xrpl_payment_readiness untrusted-input
- mcp__agent-apis__xrpl_paths untrusted-input
- mcp__agent-apis__xrpl_latest_ledger untrusted-input
- mcp__agent-apis__xrpl_mpt untrusted-input
- mcp__agent-apis__xrpl_address_kind untrusted-input
- mcp__agent-apis__xrpl_stablecoin untrusted-input
- mcp__agent-apis__xrpl_payment_verify untrusted-input
- mcp__agent-apis__xrpl_x402_preflight untrusted-input
- mcp__agent-apis__xrpl_domain_eligibility untrusted-input
- mcp__agent-apis__xrpl_account_offers untrusted-input
- mcp__agent-apis__xrpl_account_commitments untrusted-input
- mcp__agent-apis__xrpl_metrics_pressure untrusted-input
- mcp__agent-apis__xrpl_metrics_peg untrusted-input
- mcp__agent-apis__xrpl_metrics_fx_basis untrusted-input
- mcp__agent-apis__xrpl_metrics_arbitrage untrusted-input
- mcp__agent-apis__xrpl_metrics_liquidity_stress untrusted-input
- mcp__agent-apis__solana_transfer_readiness untrusted-input
- mcp__agent-apis__solana_token untrusted-input
- mcp__agent-apis__solana_latest_slot untrusted-input
- mcp__agent-apis__solana_network_health untrusted-input
- mcp__agent-apis__solana_fee_readiness untrusted-input
- mcp__agent-apis__solana_token_hygiene untrusted-input
- mcp__agent-apis__solana_address_kind untrusted-input
- mcp__agent-apis__solana_stablecoin untrusted-input
- mcp__agent-apis__solana_payment_verify untrusted-input, outbound
- mcp__agent-apis__solana_x402_preflight untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/com.criptonlabs/agent-apis/verify?hash=c9cb8e949491ca1cd97bc9c9f21f4bd9aff56a25d069fb6af4d071f82677db3b" | jq -e '.changed == false'Pinned hash c9cb8e949491, from Nov 21, 2026, 00:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.criptonlabs/agent-apis/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.criptonlabs/agent-apis)Source: MCP Registry. Synced Nov 21, 2026, 00:17 UTC.
Criptonlabs Agent APIs MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Criptonlabs Agent APIs MCP server safe?
- No scan can promise that. What its definitions show: 35 tools, 35 of which can change, send or delete something, and 18 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Criptonlabs Agent APIs MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Criptonlabs Agent APIs MCP server do things that cannot be undone?
- Yes. 4 tools can send, pay, publish or merge: xrpl_payment_readiness, xrpl_payment_verify, solana_transfer_readiness and solana_payment_verify.
What tools does the Criptonlabs Agent APIs MCP server have?
- 35 tools: 4 irreversible, 31 write. xrpl_payment_readiness, xrpl_payment_verify, solana_transfer_readiness, solana_payment_verify, xrpl_fee, xrpl_network_health, xrpl_orderbook, xrpl_slippage and 27 more.
Does the Criptonlabs Agent APIs MCP server need sign-in or OAuth?
- Its remote endpoint did not answer the last anonymous look.
Does the Criptonlabs Agent APIs MCP server send data to outside services?
- 1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): solana_payment_verify.
Has the Criptonlabs Agent APIs MCP server changed its tools?
- Yes, once since Anlyon Radar started tracking it, most recently on Nov 18, 2026. Every change is on this page and in its Atom feed.