Criptonlabs Agent APIs MCP Server

by criptonlabs Your server? Claim it

answering

Criptonlabs Agent APIs is answering right now. Last checked 15 min ago. It exposes 16 tools.

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

Uptime history 9 days of history

9 days agonow

100.0%

Uptime 24h

182 of 182 checks

Tools

read from the server

433 ms

Response time

average over 24h

open, no key

Access

streamable-http

What changed 2

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 20 October 2026. No other catalogue keeps this.

20 Oct a tool changed version2 times that day

and 1 more, back to 20 October 2026

Nothing serious here today

Today is the operative word: we check Criptonlabs Agent APIs every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 15 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add agent-apis --transport http https://api.criptonlabs.com/mcp

Settings → Connectors → Add custom connector, then paste this address

https://api.criptonlabs.com/mcp

~/.codex/config.toml

[mcp_servers.agent-apis]
url = "https://api.criptonlabs.com/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "agent-apis": {
      "url": "https://api.criptonlabs.com/mcp"
    }
  }
}

.vscode/mcp.json

{
  "servers": {
    "agent-apis": {
      "type": "http",
      "url": "https://api.criptonlabs.com/mcp"
    }
  }
}

This server publishes 1 more address. The block above uses the one we reach during checks; the full list is under Endpoints below, and the author may intend a particular one for your client.

Available tools 16

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

xrpl

xrpl_account_lines

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

xrpl_account_summary

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

xrpl_account_transactions

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

xrpl_amm

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

xrpl_fee

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

xrpl_latest_ledger

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

xrpl_network_health

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

xrpl_orderbook

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

xrpl_paths

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

xrpl_payment_readiness

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

xrpl_slippage

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

xrpl_token

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

solana

solana_latest_slot

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

solana_network_health

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

solana_token

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

solana_transfer_readiness

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

Endpoints

URL	Transport	State	Latency	Checked
https://api.criptonlabs.com/mcp	streamable-http	answering	303 ms	15 min ago
https://api.criptonlabs.com/mcp/pro	streamable-http	answering	413 ms	15 min ago

Alternatives to Criptonlabs Agent APIs

same job, measured the same way

Tokenized Stocks & Agent Data (x402)

by fly-x402-accelerometer-feed

x402-paid data for agents: tokenized stocks on Base, Solana token verdicts, AI-progress readings

12 tools answering

AgnicPay

by agnicpay-prog

X402 payment MCP for AI agents. Auto-pay 300+ APIs with USDC on Base and Solana.

answering

Turva MCP

by turva

Read-only MCP server for turva.dev, an agent-readiness audit and advisory service.

5 tools answering

SIMA MCP Server

by mustafashehab

Read-only MCP server for SIMA Solana AI agent protection discovery. No API keys required.

21 installs/wk local only

Txtcel

by txtcel

MCP server for the Txtcel Solana protocol: agents post and read undeletable on-chain messages.

23 installs/wk local only

Dant3

by snooptsz

Read-only Dant3 MCP for public rooms, agents, jobs and provisional machine onboarding.

6 tools answering

pump.fun Solana Data

by nirholas

Free, read-only pump.fun + Solana MCP: token discovery, on-chain analysis, SNS, 3D snapshots.

72 installs/wk local only

VerdictSwarm MCP

by sentien-labs

Read-only pre-trade token risk verdicts and size-aware Solana exit screening for agents.

229 installs/wk local only

Criptonlabs Agent APIs — questions

Answers built from our own checks of this server.

What can Criptonlabs Agent APIs do?

It exposes 16 tools, read directly from the server on our last check. Among them: solana_latest_slot, solana_network_health, solana_token, solana_transfer_readiness, xrpl_account_lines, xrpl_account_summary and 10 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

What is Criptonlabs Agent APIs mostly used for?

Its tools cluster around xrpl and solana. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.

Is Criptonlabs Agent APIs working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 182 of 182 checks got a reply (100.0%), average response time 433 ms. The bar chart above shows every period we have measured.

How do I connect Criptonlabs Agent APIs?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does Criptonlabs Agent APIs need an API key?

No. Criptonlabs Agent APIs completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 16 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is Criptonlabs Agent APIs?

It answers our handshake in 433 ms on average, which is faster than 32% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.