Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Kriptonianlabs Agent APIs

REMOTE · API.KRIPTONIANLABS.COM · 2 COMPONENTS

Read-only XRPL and Solana data for agents: fees, slippage, readiness. Free /mcp; x402 /mcp/pro.

66 Trust /100

Last scanned (1 hour ago)

Scores higher than 56% of remote servers

Reachable. Last reached 17 Oct 2026.

Category Crypto and Web3

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security74
Transport & Reachability100
Schema Quality & AI Usability52
  • 2% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Partial
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 3323 tokens (~54/item across 61 items; 16 tools + 45 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management3
  • Stability observed for 1 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
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "solana_transfer_readiness" implies "transfer" and declares readOnlyHint instead, contradicting what its own name says it does. See how to fix → Fail
  • An AI judge read all 17 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
Changelog

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.

  • 17 Oct 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 16 Oct 26 65

    First indexed and scored.

Diagnostics

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 17 Oct 2026 · Probed https://api.kriptonianlabs.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=kriptonianlabs.com CN=WE1,O=Google Trust Services,C=US 5 Oct 2026 3 Jan 2027 ECDSA 256 ECDSA-SHA256 5d74b6ac810d2b9d13e36aa9a2212f24
SANs: kriptonianlabs.com, api.kriptonianlabs.com, *.api.kriptonianlabs.com
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of api.kriptonianlabs.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
kriptonianlabs.com. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://api.kriptonianlabs.com/mcp Verified 200
http (plaintext) http://api.kriptonianlabs.com/mcp HTTPS enforced 301 https://api.kriptonianlabs.com/mcp
MCP tools · 16 exposed · ~2,994 tokens

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 →

Tool Tokens
solana_latest_slot ~81

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 {}

Input schema present but exposes no named parameters.

NameTypeReqDescription
block_time–yesBlock time of that slot; null when unavailable
meta–yes–
slotintegeryesLatest finalized slot

No examples provided.

solana_network_health ~88

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 {}

Input schema present but exposes no named parameters.

NameTypeReqDescription
last_probe_at–yes–
latency_msnumber|nullyes–
meta–yes–
slot–yesFinalized slot of the latest successful probe
statusstringyesLatest probe result; `unavailable` while Solana data is not configured

No examples provided.

solana_token ~154

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"}

NameTypeReqDescription
mintstringyesMint address of an SPL Token or Token-2022 token (base58, 32 bytes)
NameTypeReqDescription
decimalsintegeryes–
extensionsarrayyesToken-2022 mint extensions by name; empty for SPL Token
freeze_authoritystring|nullyesNull when the freeze authority is renounced
meta–yes–
mintstringyes–
mint_authoritystring|nullyesNull when the mint authority is renounced
reasonsarrayyesEvery matched code of every level; empty for SAFE
supplystringyesTotal supply in raw units, exact
token_programstringyesSPL Token or Token-2022 program address
transfer_fee–yesTransfer fee active at the current epoch; null without a fee config
verdictstringyesHighest level matched: DANGER > WARN > SAFE

No examples provided.

solana_transfer_readiness ~293

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"}

NameTypeReqDescription
amountstringyesPositive decimal amount in UI units (SOL or tokens, not lamports or raw units)
destinationstringyesReceiving wallet (not its token account): Solana wallet address: a base58 string that decodes to exactly 32 bytes
mintstringyes`SOL` for native SOL, or the mint address of an SPL Token or Token-2022 token
sourcestringyesSending wallet: Solana wallet address: a base58 string that decodes to exactly 32 bytes
NameTypeReqDescription
amountstringyesAmount checked, in the asset's UI units (as sent)
amount_rawstringyesAmount in raw units (lamports for SOL)
ata_creation_lamports–yesRent-exempt lamports to create the destination token account; null when not needed
blockersarrayyesEvery blocking code that matched
decimalsintegeryesDecimals of the asset (9 for SOL)
destinationstringyesReceiving wallet address
meta–yes–
mintstringyes`SOL` or the mint address
net_amountstringyesRaw units the destination receives after any transfer fee
readybooleanyesTrue when no blocker applies
requires_ata_creationbooleanyesTrue when the destination has no associated token account yet
sourcestringyesSending wallet address
token_programstring|nullyesToken program that owns the mint; null for SOL
transfer_fee–yesToken-2022 transfer fee in raw units; null without a fee config
warningsarrayyesEvery non-blocking warning that matched

No examples provided.

xrpl_account_lines ~205

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":"rHb9CJAWyB4rj91VRWn96DkukG4bwdtyTh"}

NameTypeReqDescription
addressstringyesValid classic XRPL account address (r..., checksum verified)
limitstring–Lines per page: an integer from 10 to 400 (default 100)
markerstring–Opaque cursor from the previous page's `marker`, for the same address
peerstring–Only lines with this counterparty (classic address)
NameTypeReqDescription
addressstringyes–
limitintegeryes–
linesarrayyes–
markerstring|nullyesOpaque cursor for the next page (send as `marker`); null on the last page
meta–yes–
peerstring|nullyes–

No examples provided.

xrpl_account_summary ~122

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, reserves or account flags; it is a summary, not a full account dump. Example: xrpl_account_summary {"address":"rHb9CJAWyB4rj91VRWn96DkukG4bwdtyTh"}

NameTypeReqDescription
addressstringyesValid classic XRPL account address (r..., checksum verified)
NameTypeReqDescription
addressstringyes–
balance_xrpstringyesDecimal string
lines_truncatedbooleanyes–
meta–yes–
owner_countintegeryes–
sequenceintegeryes–
transfer_rateintegeryesIssuer TransferRate, 1000000000 = no fee
trust_linesarrayyes–

No examples provided.

xrpl_account_transactions ~213

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":"rHb9CJAWyB4rj91VRWn96DkukG4bwdtyTh"}

NameTypeReqDescription
addressstringyesValid classic XRPL account address (r..., checksum verified)
limitstring–Transactions per page: an integer from 1 to 50 (default 20)
markerstring–Opaque cursor from the previous page's `marker`, for the same address
NameTypeReqDescription
addressstringyes–
limitintegeryes–
markerstring|nullyesOpaque cursor for the next (older) page (send as `marker`); null on the last page
meta–yes–
transactionsarrayyesValidated transactions, newest first

No examples provided.

xrpl_amm ~232

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":"USD.rHb9CJAWyB4rj91VRWn96DkukG4bwdtyTh"}

NameTypeReqDescription
astringyesFirst asset: `XRP` (no issuer) or `CODE.issuer` with a valid classic-address issuer (e.g. `USD.rHb9CJAWyB4rj91VRWn96DkukG4bwdtyTh`)
bstringyesSecond asset: `XRP` (no issuer) or `CODE.issuer` with a valid classic-address issuer (e.g. `USD.rHb9CJAWyB4rj91VRWn96DkukG4bwdtyTh`)
NameTypeReqDescription
asset_astringyes–
asset_bstringyes–
meta–yes–
reserve_astringyesDecimal string
reserve_bstringyesDecimal string
trading_feestringyesDecimal string

No examples provided.

xrpl_fee ~74

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 latest validated ledger only. Example: xrpl_fee {}

Input schema present but exposes no named parameters.

NameTypeReqDescription
base_feestringyesDecimal string
congestionobjectyes–
current_queue_sizestringyesDecimal string
feeobjectyes–
max_queue_sizestringyesDecimal string
median_feestringyesDecimal string
meta–yes–
minimum_feestringyesDecimal string
open_ledger_feestringyesDecimal string

No examples provided.

xrpl_latest_ledger ~69

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 {}

Input schema present but exposes no named parameters.

NameTypeReqDescription
close_time–yes–
ledger_hashstring|nullyes–
ledger_indexintegeryes–
meta–yes–

No examples provided.

xrpl_network_health ~72

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 {}

Input schema present but exposes no named parameters.

NameTypeReqDescription
last_probe_at–yes–
ledger_indexintegeryes–
meta–yes–
nodesarrayyes–
statusstringyes–

No examples provided.

xrpl_orderbook ~265

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.rHb9CJAWyB4rj91VRWn96DkukG4bwdtyTh"}

NameTypeReqDescription
basestringyesBase currency: `XRP` (no issuer) or `CODE.issuer` with a valid classic-address issuer (e.g. `USD.rHb9CJAWyB4rj91VRWn96DkukG4bwdtyTh`)
depthstring–Levels per side: a positive integer, rounded up to 10, 50, 100 or 200 (max 200)
quotestringyesQuote currency: `XRP` (no issuer) or `CODE.issuer` with a valid classic-address issuer (e.g. `USD.rHb9CJAWyB4rj91VRWn96DkukG4bwdtyTh`)
NameTypeReqDescription
asksarrayyesBest (lowest) price first
basestringyes–
bidsarrayyesBest (highest) price first, from the base-asset side
depthintegeryes–
meta–yes–
quotestringyes–

No examples provided.

xrpl_paths ~345

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":"rHb9CJAWyB4rj91VRWn96DkukG4bwdtyTh","destination":"rvYAfWj5gh67oV6fW32ZzP3Aw4Eubs59B","asset":"XRP","amount":"1"}

NameTypeReqDescription
amountstringyesPositive decimal amount of asset the destination receives
assetstringyesAsset delivered: XRP or CODE.issuer (3-character or 40-hex code, classic issuer)
destinationstringyesReceiving account: valid classic XRPL address
send_maxstring–Most the source may spend, in send_max_asset; not with source_assets
send_max_assetstring–Asset of send_max: XRP or CODE.issuer; give it with send_max
sourcestringyesSending account: valid classic XRPL address (r..., checksum verified)
source_assetsstring–Comma-separated assets the source may spend (1 to 4); not with send_max
NameTypeReqDescription
alternativesarrayyesPath alternatives; empty when none was found
meta–yes–
paths_may_be_non_optimalbooleanyesPath finding is best effort: a cheaper path may exist
warningsarrayyesNon-blocking warnings

No examples provided.

xrpl_payment_readiness ~284

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, 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":"rHb9CJAWyB4rj91VRWn96DkukG4bwdtyTh","destination":"rvYAfWj5gh67oV6fW32ZzP3Aw4Eubs59B"}

NameTypeReqDescription
amountstring–Positive decimal amount of asset; omit to skip amount-dependent checks
assetstring–XRP (default) or CODE.issuer (3-character or 40-hex code, classic issuer)
destinationstringyesReceiving account: valid classic XRPL address, different from source
destination_tagstring–Destination tag you will send: an integer from 0 to 4294967295
sourcestringyesSending account: valid classic XRPL address (r..., checksum verified)
NameTypeReqDescription
amount–yesAmount checked; null when omitted (amount checks skipped)
assetstringyes`XRP` or `CODE.issuer`
checks_failedarrayyesSub-checks that could not run
destinationstringyes–
destination_tag–yes–
meta–yes–
reasonsarrayyesBlocking reason codes
sourcestringyes–
spendable_xrp–yesSource XRP above its live reserve and the standard fee; null when not computable
transfer_fee_pct–yesIssuer transfer fee in percent, when it applies
verdictstringyes`not_ready` on any blocking reason; else `unknown` on any failed sub-check
warningsarrayyesNon-blocking warnings

No examples provided.

xrpl_slippage ~304

Slippage and average price for buying 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 is the cheaper venue. 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.rHb9CJAWyB4rj91VRWn96DkukG4bwdtyTh","amount":"1000"}

NameTypeReqDescription
amountstringyesPositive decimal amount of base to buy
basestringyesBase currency: `XRP` (no issuer) or `CODE.issuer` with a valid classic-address issuer (e.g. `USD.rHb9CJAWyB4rj91VRWn96DkukG4bwdtyTh`)
depthstring–Levels per side: a positive integer, rounded up to 10, 50, 100 or 200 (max 200)
quotestringyesQuote currency: `XRP` (no issuer) or `CODE.issuer` with a valid classic-address issuer (e.g. `USD.rHb9CJAWyB4rj91VRWn96DkukG4bwdtyTh`)
NameTypeReqDescription
amountstringyesDecimal string
avg_price–yes–
avg_price_after_fees–yes–
basestringyes–
best_price–yes–
depthintegeryes–
filledstringyesDecimal string
insufficient_liquiditybooleanyes–
meta–yes–
partialbooleanyes–
quotestringyes–
sidestringyes–
slippage_pct–yesPercent, null when liquidity is insufficient
transfer_fee–yes–
transfer_fee_appliedbooleanyes–
venuesobjectyesCLOB vs AMM comparison for the same amount; no routing split

No examples provided.

xrpl_token ~193

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.rHb9CJAWyB4rj91VRWn96DkukG4bwdtyTh"}

NameTypeReqDescription
assetstringyesIssued asset as CODE.issuer (3-character or 40-hex code, classic issuer address); not XRP
NameTypeReqDescription
currencystringyesCanonical currency code (3 characters or 40 hex)
currency_asciistring|null–Readable text of a 40-hex currency code; null when not printable ASCII; absent for XRP and 3-character codes
default_ripplebooleanyes–
domainstring|nullyesIssuer domain decoded to text, when set
global_freezebooleanyes–
issuerstringyesIssuer address
meta–yes–
no_freezebooleanyes–
obligations–yesTotal issued of this currency; null when `obligations_status` is `unavailable`
obligations_statusstringyes–
require_authbooleanyes–
transfer_fee_pctstringyesTransfer fee in percent
transfer_rateintegeryesIssuer TransferRate, 1000000000 = no fee

No examples provided.

Install

How do I install the Kriptonianlabs Agent APIs MCP server?

Kriptonianlabs Agent APIs is a hosted endpoint at https://api.kriptonianlabs.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · api.kriptonianlabs.com

# add to Claude Code
claude mcp add --transport http com-kriptonianlabs-agent-apis 'https://api.kriptonianlabs.com/mcp'
Common questions

What is the Kriptonianlabs Agent APIs MCP server?

Kriptonianlabs Agent APIs is an MCP server listed in the public MCP registry as com.kriptonianlabs/agent-apis. Read-only XRPL and Solana data for agents: fees, slippage, readiness. Free /mcp; x402 /mcp/pro. This page covers its hosted endpoint (https://api.kriptonianlabs.com/mcp).

Is the Kriptonianlabs Agent APIs MCP server safe to use?

Kriptonianlabs Agent APIs scores 66 out of 100 on VerifyMCP. 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 Kriptonianlabs Agent APIs MCP server expose?

Kriptonianlabs Agent APIs exposes 16 tools: xrpl_fee, xrpl_network_health, xrpl_orderbook, xrpl_slippage, xrpl_amm, and 11 more. Their descriptions and schemas cost roughly 2,994 tokens of context every time the server is loaded.

Does the Kriptonianlabs Agent APIs MCP server require authentication?

No. We connected to Kriptonianlabs Agent APIs without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Kriptonianlabs Agent APIs MCP server still maintained?

Kriptonianlabs Agent APIs is still listed as active in the MCP registry. We last reached this channel on 17 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.