_ registry / mcp + a2a http-sse · checked 3h ago

com.criptonlabs/agent-apis

https://api.criptonlabs.com

Registry code: d7fc169cb4398fd3

api record

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

from a public catalogue that lists it, not from the operator

endpoint
https://api.criptonlabs.com/mcp
door code
3215d94591a08a09
protocol
http-sse ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is com.criptonlabs/agent-apis live?
Yes — it answered the hub's last check (checked 3h ago). It answered 100% of checks over the last 30 days.
Is com.criptonlabs/agent-apis free to use?
Yes — the hub reached it with no key and no payment.
What tools does com.criptonlabs/agent-apis have?
16 tools: xrpl_account_summary, xrpl_network_health, xrpl_amm, xrpl_orderbook, xrpl_slippage, xrpl_account_lines, xrpl_account_transactions, xrpl_token, ….
Is com.criptonlabs/agent-apis safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
449ms

last good check

priced tools
0

of 16 tools

_ answered our checks, 90 days 2 checks · signed record
  • unknown → live
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 16 tools
3 open 13 never probed 3 of 16 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • solana_latest_slot open 3h ago

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

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "properties": {}
}
    arguments 5 lines
  • solana_network_health open 3h ago

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

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "properties": {}
}
    arguments 5 lines
  • xrpl_fee open 3h ago

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

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "properties": {}
}
    arguments 5 lines
  • xrpl_account_summary unknown never probed

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

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "address"
  ],
  "properties": {
    "address": {
      "type": "string",
      "description": "Valid classic XRPL account address (r..., checksum verified)"
    }
  }
}
    arguments 13 lines
  • xrpl_network_health unknown never probed

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

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "properties": {}
}
    arguments 5 lines
  • xrpl_amm unknown never probed

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

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "a",
    "b"
  ],
  "properties": {
    "a": {
      "type": "string",
      "description": "First asset: `XRP` (no issuer) or `CODE.issuer` with a valid classic-address issuer (e.g. `USD.rHb9CJAWyB4rj91VRWn96DkukG4bwdtyTh`)"
    },
    "b": {
      "type": "string",
      "description": "Second asset: `XRP` (no issuer) or `CODE.issuer` with a valid classic-address issuer (e.g. `USD.rHb9CJAWyB4rj91VRWn96DkukG4bwdtyTh`)"
    }
  }
}
    arguments 18 lines
  • xrpl_orderbook unknown never probed

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

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "base",
    "quote"
  ],
  "properties": {
    "base": {
      "type": "string",
      "description": "Base currency: `XRP` (no issuer) or `CODE.issuer` with a valid classic-address issuer (e.g. `USD.rHb9CJAWyB4rj91VRWn96DkukG4bwdtyTh`)"
    },
    "depth": {
      "type": "string",
      "description": "Levels per side: a positive integer, rounded up to 10, 50, 100 or 200 (max 200)"
    },
    "quote": {
      "type": "string",
      "description": "Quote currency: `XRP` (no issuer) or `CODE.issuer` with a valid classic-address issuer (e.g. `USD.rHb9CJAWyB4rj91VRWn96DkukG4bwdtyTh`)"
    }
  }
}
    arguments 22 lines
  • xrpl_slippage unknown never probed

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

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "base",
    "quote",
    "amount"
  ],
  "properties": {
    "base": {
      "type": "string",
      "description": "Base currency: `XRP` (no issuer) or `CODE.issuer` with a valid classic-address issuer (e.g. `USD.rHb9CJAWyB4rj91VRWn96DkukG4bwdtyTh`)"
    },
    "depth": {
      "type": "string",
      "description": "Levels per side: a positive integer, rounded up to 10, 50, 100 or 200 (max 200)"
    },
    "quote": {
      "type": "string",
      "description": "Quote currency: `XRP` (no issuer) or `CODE.issuer` with a valid classic-address issuer (e.g. `USD.rHb9CJAWyB4rj91VRWn96DkukG4bwdtyTh`)"
    },
    "amount": {
      "type": "string",
      "description": "Positive decimal amount of base to buy"
    }
  }
}
    arguments 27 lines
  • xrpl_account_lines unknown never probed

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

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "address"
  ],
  "properties": {
    "peer": {
      "type": "string",
      "description": "Only lines with this counterparty (classic address)"
    },
    "limit": {
      "type": "string",
      "description": "Lines per page: an integer from 10 to 400 (default 100)"
    },
    "marker": {
      "type": "string",
      "description": "Opaque cursor from the previous page's `marker`, for the same address"
    },
    "address": {
      "type": "string",
      "description": "Valid classic XRPL account address (r..., checksum verified)"
    }
  }
}
    arguments 25 lines
  • xrpl_account_transactions unknown never probed

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

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "address"
  ],
  "properties": {
    "limit": {
      "type": "string",
      "description": "Transactions per page: an integer from 1 to 50 (default 20)"
    },
    "marker": {
      "type": "string",
      "description": "Opaque cursor from the previous page's `marker`, for the same address"
    },
    "address": {
      "type": "string",
      "description": "Valid classic XRPL account address (r..., checksum verified)"
    }
  }
}
    arguments 21 lines
  • xrpl_token unknown never probed

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

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "asset"
  ],
  "properties": {
    "asset": {
      "type": "string",
      "description": "Issued asset as CODE.issuer (3-character or 40-hex code, classic issuer address); not XRP"
    }
  }
}
    arguments 13 lines
  • xrpl_payment_readiness unknown never probed

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

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "source",
    "destination"
  ],
  "properties": {
    "asset": {
      "type": "string",
      "description": "XRP (default) or CODE.issuer (3-character or 40-hex code, classic issuer)"
    },
    "amount": {
      "type": "string",
      "description": "Positive decimal amount of asset; omit to skip amount-dependent checks"
    },
    "source": {
      "type": "string",
      "description": "Sending account: valid classic XRPL address (r..., checksum verified)"
    },
    "destination": {
      "type": "string",
      "description": "Receiving account: valid classic XRPL address, different from source"
    },
    "destination_tag": {
      "type": "string",
      "description": "Destination tag you will send: an integer from 0 to 4294967295"
    }
  }
}
    arguments 30 lines
  • xrpl_paths unknown never probed

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

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "source",
    "destination",
    "asset",
    "amount"
  ],
  "properties": {
    "asset": {
      "type": "string",
      "description": "Asset delivered: XRP or CODE.issuer (3-character or 40-hex code, classic issuer)"
    },
    "amount": {
      "type": "string",
      "description": "Positive decimal amount of asset the destination receives"
    },
    "source": {
      "type": "string",
      "description": "Sending account: valid classic XRPL address (r..., checksum verified)"
    },
    "send_max": {
      "type": "string",
      "description": "Most the source may spend, in send_max_asset; not with source_assets"
    },
    "destination": {
      "type": "string",
      "description": "Receiving account: valid classic XRPL address"
    },
    "source_assets": {
      "type": "string",
      "description": "Comma-separated assets the source may spend (1 to 4); not with send_max"
    },
    "send_max_asset": {
      "type": "string",
      "description": "Asset of send_max: XRP or CODE.issuer; give it with send_max"
    }
  }
}
    arguments 40 lines
  • xrpl_latest_ledger unknown never probed

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

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "properties": {}
}
    arguments 5 lines
  • solana_transfer_readiness unknown never probed

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

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "source",
    "destination",
    "mint",
    "amount"
  ],
  "properties": {
    "mint": {
      "type": "string",
      "description": "`SOL` for native SOL, or the mint address of an SPL Token or Token-2022 token"
    },
    "amount": {
      "type": "string",
      "description": "Positive decimal amount in UI units (SOL or tokens, not lamports or raw units)"
    },
    "source": {
      "type": "string",
      "description": "Sending wallet: Solana wallet address: a base58 string that decodes to exactly 32 bytes"
    },
    "destination": {
      "type": "string",
      "description": "Receiving wallet (not its token account): Solana wallet address: a base58 string that decodes to exactly 32 bytes"
    }
  }
}
    arguments 28 lines
  • solana_token unknown never probed

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

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "mint"
  ],
  "properties": {
    "mint": {
      "type": "string",
      "description": "Mint address of an SPL Token or Token-2022 token (base58, 32 bytes)"
    }
  }
}
    arguments 13 lines
_ try it over mcp through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id d7fc169cb4398fd3.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/d7fc169cb4398fd3/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/d7fc169cb4398fd3/badge.svg)](https://brick.blue/agent/d7fc169cb4398fd3?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we knowoff the mcp door
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
1
ok
0
failed
1
success rate
0%
median latency
410ms
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

1 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.