N9T2 XRPL Agent Gateway

Measured conclusion: Deep-tested. L2 outcome: tools_ok.

Agent-native XRPL infrastructure: 19 paid MCP tools, x402 USDC on Base, non-custodial XRPL actions.

Add to your agent

Copy this into your MCP client config:

{
  "mcpServers": {
    "N9T2 XRPL Agent Gateway": {
      "url": "https://x402.n9t2.com/mcp",
      "transport": "streamable-http"
    }
  }
}

Measured tools (22)

• n9t2_xrpl_get_account_info read-only

  Read-only XRPL current-account-state lookup for one account. `account` must be a valid XRPL classic account address; the result returns the current balance, sequence, owner count, flags, and account settings without submitting or modifying any XRPL transaction, and calls remain subject to the configured gateway rate limits. Use this for current account state only; use n9t2_xrpl_get_transaction or n9t2_xrpl_list_account_transactions for transaction history, and n9t2_xrpl_get_ledger_data for raw ledger objects.

  Parameters:

  • account (required) — string — XRPL classic account address whose current account state should be retrieved.

  Hints: read-only yes · destructive no · idempotent yes · open-world yes

• n9t2_xrpl_list_account_transactions read-only

  Read-only XRPL transaction-history lookup for one account over an optional ledger range. Use this for multiple account transactions; use n9t2_xrpl_get_transaction when a transaction hash is already known. `ledger_index_min` and `ledger_index_max` narrow the history window, while `limit` bounds the returned records; when the response includes a pagination marker, more history remains beyond the current page. The result contains account transaction records and does not modify the ledger or submit transactions, and calls are subject to the configured gateway rate limits.

  Parameters:

  • account (required) — string — XRPL classic account address whose transaction history should be retrieved.
  • limit — Optional maximum number of transactions to return.
  • ledger_index_max — Optional maximum ledger index for the transaction-history range.
  • ledger_index_min — Optional minimum ledger index for the transaction-history range.

  Hints: read-only yes · destructive no · idempotent yes · open-world yes

• n9t2_xrpl_get_transaction read-only

  Read-only XRPL transaction lookup for one canonical transaction hash. `transaction` is the required hash; set `binary=true` only when binary-encoded transaction data is required, otherwise use the normal transaction representation. The result retrieves transaction data for that hash without modifying the ledger, and calls are subject to the configured gateway rate limits. Use this when the transaction hash is already known; use n9t2_xrpl_list_account_transactions for account-wide transaction history instead.

  Parameters:

  • transaction (required) — string — Canonical XRPL transaction hash to retrieve.
  • binary — Whether to return the transaction in binary encoded form.

  Hints: read-only yes · destructive no · idempotent yes · open-world yes

• n9t2_xrpl_get_ledger read-only

  Read-only XRPL ledger header and metadata lookup. Omit `ledger_index` to use the current validated ledger, or provide a validated ledger index/selector to pin the lookup; set `transactions=true` to include that ledger's transactions and use `expand=true` to return those transactions as full objects. The result provides ledger metadata and, when requested, transaction data without modifying the ledger, and calls are subject to the configured gateway rate limits. Use this for ledger headers, metadata, and optional ledger transactions; use n9t2_xrpl_get_ledger_data instead when you need raw ledger-state objects.

  Parameters:

  • expand — Whether returned transactions should be expanded into full transaction objects.
  • ledger_index — Optional validated ledger index or ledger selector. Omit to use the current validated ledger.
  • transactions — Whether to include transactions contained in the requested ledger.

  Hints: read-only yes · destructive no · idempotent yes · open-world yes

• n9t2_xrpl_get_ledger_data read-only

  Read-only XRPL raw ledger-state lookup for a ledger. Omit `ledger_index` to use the default ledger, or provide a ledger index/selector to pin the lookup; use `limit` to cap the number of ledger-state objects returned and pass `marker` from a previous response to continue pagination. The result returns raw canonical ledger-state entries without modifying the ledger; large state queries should be paginated, and calls are subject to the configured gateway rate limits. Use this for canonical ledger-state objects; use n9t2_xrpl_get_ledger for ledger headers and transaction-list metadata instead.

  Parameters:

  • limit — Optional maximum number of ledger-state objects to return.
  • marker — Pagination marker returned by a previous response.
  • ledger_index — Optional ledger index or selector identifying the ledger whose state objects should be returned.

  Hints: read-only yes · destructive no · idempotent yes · open-world yes

• n9t2_xrpl_get_book_offers read-only

  Read-only XRPL DEX order-book lookup for a specific trading pair. `taker_gets` and `taker_pays` are the required XRPL currency-specification objects that define the two sides of the book; `limit` optionally caps the number of offers returned. The result provides global book offers and market-depth data without modifying the ledger, and calls are subject to the configured gateway rate limits. Use this for global DEX order-book depth; use n9t2_xrpl_list_account_offers for one account's outstanding offers and n9t2_xrpl_find_path when you need payment-path discovery instead.

  Parameters:

  • taker_gets (required) — object — Currency specification for the asset the taker receives in the XRPL DEX order book.
  • taker_pays (required) — object — Currency specification for the asset the taker pays in the XRPL DEX order book.
  • limit — Optional maximum number of DEX order-book offers to return.

  Hints: read-only yes · destructive no · idempotent yes · open-world yes

• n9t2_xrpl_find_path read-only

  Read-only XRPL payment-path discovery for planning a Payment from source_account to destination_account. destination_amount is the exact amount the destination should receive, provided as XRP drops or an issued-currency object; the result returns candidate path alternatives and source-amount information to compare before constructing the payment. Use this when XRPL routing is needed between the source and destination accounts; use n9t2_xrpl_get_book_offers for DEX order-book depth instead. This tool only discovers paths and does not construct, sign, submit, or modify any XRPL transaction; after selecting a route, use n9t2_xrpl_prepare_transaction to build the unsigned payment.

  Parameters:

  • source_account (required) — string — XRPL classic account address used as the source of payment-path discovery.
  • destination_account (required) — string — XRPL classic account address that will receive the destination amount.
  • destination_amount (required) — Destination amount to deliver. Use a string for XRP drops or an issued-currency object containing currency, issuer, and value.

  Hints: read-only yes · destructive no · idempotent yes · open-world yes

• n9t2_xrpl_list_account_lines read-only

  Read-only XRPL trust-line lookup for one account. `account` is the required XRPL classic account address; use `peer` to restrict results to one counterparty, `limit` to cap returned trust lines, `marker` to continue pagination from a previous response, and `ledger_index` to pin the lookup to a validated ledger. The result lists trust-line state including issued-asset balances and limits without modifying the ledger, and calls are subject to the configured gateway rate limits. Use this for an account's trust lines and issued-asset holdings; use n9t2_xrpl_get_account_info for current account state or n9t2_xrpl_list_account_objects for other ledger objects.

  Parameters:

  • account (required) — string — XRPL classic account address whose trust lines should be listed.
  • peer — Optional XRPL classic account address used to filter trust lines to a specific peer.
  • limit — Optional maximum number of trust lines to return.
  • marker — Pagination marker returned by a previous response.
  • ledger_index — Optional validated ledger index or selector.

  Hints: read-only yes · destructive no · idempotent yes · open-world yes

• n9t2_xrpl_list_account_objects read-only

  Read-only XRPL canonical ledger-object lookup for one account. Use this low-level catch-all when raw ledger-entry objects are required or when no dedicated N9T2 view exists. Use n9t2_xrpl_list_account_nfts for NFTs owned by the account, n9t2_xrpl_list_nft_offers for marketplace buy/sell offers on a specific NFTokenID, n9t2_xrpl_list_account_offers for classic DEX offers, and n9t2_xrpl_list_account_channels for Payment Channels. Set object_type to `nft_offer` only when raw NFTokenOffer ledger entries are required; use `ledger_index` to pin the lookup and `limit`/`marker` for pagination.

  Parameters:

  • account (required) — string — XRPL classic account address whose canonical ledger objects should be inspected.
  • limit — Optional maximum number of ledger objects to return.
  • marker — Pagination marker returned by a previous response.
  • sponsored — Optional filter controlling sponsored ledger objects.
  • object_type — Optional XRPL ledger-entry type filter. Use 'nft_offer' for account-level NFTokenOffer ledger entries.
  • ledger_index — Optional validated ledger index or selector.
  • deletion_blockers_only — boolean — Whether to return only ledger objects that prevent account deletion.

  Hints: read-only yes · destructive no · idempotent yes · open-world yes

• n9t2_xrpl_list_account_offers read-only

  Read-only XRPL DEX account-offer lookup for one account. Returns that account's outstanding offers rather than global order-book depth; use n9t2_xrpl_get_book_offers for global market depth. Use `limit` to bound results and `marker` to continue pagination, `ledger_index` to pin the lookup to a validated ledger, and `strict` when the account identifier must be interpreted exactly as supplied. Use this for the account's own open offers; it does not create, cancel, or modify any XRPL offer and is subject to the configured gateway rate limits.

  Parameters:

  • account (required) — string — XRPL classic account address whose outstanding DEX offers should be listed.
  • limit — Optional maximum number of open offers to return.
  • marker — Pagination marker returned by a previous response.
  • strict — boolean — Whether the account identifier should be interpreted strictly as supplied.
  • ledger_index — Optional validated ledger index or selector.

  Hints: read-only yes · destructive no · idempotent yes · open-world yes

• n9t2_xrpl_list_account_channels read-only

  Read-only XRPL Payment Channel lookup for one account. `account` is the required XRPL classic account address; by default, the lookup returns channels where that account is the source. Use `destination_account` to filter channels by destination, `ledger_index` to pin the lookup to a validated ledger, and `marker` to continue pagination; `limit` caps returned channels and defaults to 200. The result lists Payment Channel entries without modifying the ledger, and calls are subject to the configured gateway rate limits. Use this for PaymentChannelCreate/Fund/Claim inspection; use n9t2_xrpl_list_account_objects for generic account ledger objects instead.

  Parameters:

  • account (required) — string — XRPL classic account address whose Payment Channels should be listed.
  • limit — integer — Maximum number of Payment Channel entries to return. Default is 200.
  • marker — Pagination marker returned by a previous response.
  • ledger_index — Optional validated ledger index or selector.
  • destination_account — Optional destination account filter. When supplied, return channels whose destination is this account.

  Hints: read-only yes · destructive no · idempotent yes · open-world yes

• n9t2_xrpl_get_server_info read-only

  Read-only XRPL `server_info` lookup for node health, server state, and validated-ledger status. Use this before interpreting ledger-dependent results when node health or freshness matters; the result provides the node/server status and validated-ledger information needed to assess whether subsequent ledger reads are current and usable. Use n9t2_xrpl_get_ledger for ledger metadata or n9t2_xrpl_get_ledger_data for raw ledger-state entries; this tool requires no parameters and does not modify the ledger.

  Hints: read-only yes · destructive no · idempotent yes · open-world yes

• n9t2_xrpl_get_gateway_balances read-only

  Read-only XRPL issued-asset exposure calculation for one issuing account. `account` is the required XRPL issuer address; optionally use `hotwallet` with one address or a list of operational hot-wallet addresses when those balances should be included in the calculation, and use `ledger_index` to pin the calculation to a specific ledger. `strict` controls how account identifiers are interpreted. The result reports the calculated issued-asset exposure without modifying the ledger, and calls are subject to the configured gateway rate limits. Use this for issuer-level issued-asset exposure; do not use it for trust-line holdings of a single account, where n9t2_xrpl_list_account_lines is the appropriate tool.

  Parameters:

  • account (required) — string — XRPL issuing account whose issued-asset balances should be calculated.
  • strict — boolean — Whether account identifiers should be interpreted strictly as supplied.
  • hotwallet — Optional XRPL hot-wallet account address or list of hot-wallet addresses.
  • ledger_index — Optional ledger index or selector for the balance calculation.

  Hints: read-only yes · destructive no · idempotent yes · open-world yes

• n9t2_xrpl_list_account_nfts read-only

  Read-only XRPL NFT inventory lookup for one classic account using the native `account_nfts` method. The result provides NFT-specific fields such as `NFTokenID`, `Issuer`, `NFTokenTaxon`, `URI`, and `nft_serial`; use `marker` to continue pagination and `ledger_hash` or `ledger_index` to pin the inventory lookup to a specific ledger. Calls are subject to the configured gateway rate limits. Use this for NFTs owned by an account; use n9t2_xrpl_list_nft_offers for marketplace buy/sell offers on a specific NFTokenID, or n9t2_xrpl_list_account_objects when raw account ledger objects rather than NFT-specific fields are required.

  Parameters:

  • account (required) — string — XRPL classic account address whose owned NFTs should be listed.
  • limit — Optional maximum number of owned NFT records to return.
  • marker — Pagination marker returned by a previous response.
  • ledger_hash — Optional ledger hash used to pin the NFT inventory lookup.
  • ledger_index — Optional validated ledger index or selector.

  Hints: read-only yes · destructive no · idempotent yes · open-world yes

• n9t2_xrpl_subscribe read-only

  Open a bounded native XRPL WebSocket subscription and capture live events for selected streams, accounts, proposed transactions, or order books. Use this when an agent needs event-driven updates instead of a one-time snapshot. The tool sends the XRPL subscribe command, collects events until duration_seconds expires or max_events is reached, then closes the connection and returns the subscription acknowledgement plus captured events. When subscription inputs are omitted, the default is the ledger stream for 3 seconds with up to 25 events. This is read-only: it does not submit transactions or modify ledger state. Do not request the admin-only peer_status stream unless the upstream XRPL server permits it.

  Parameters:

  • books — Optional list of XRPL order-book subscription descriptors.
  • streams — Optional XRPL stream names such as ledger or transactions.
  • accounts — Optional list of XRPL classic account addresses whose activity should be streamed.
  • max_events — integer — Maximum number of events to capture before returning. Default is 25.
  • duration_seconds — integer — How many seconds the bounded WebSocket subscription remains open. Default is 3.
  • accounts_proposed — Optional list of XRPL accounts for proposed transaction events.

  Hints: read-only yes · destructive no · idempotent no · open-world yes

• n9t2_xrpl_submit_transaction destructive

  Submit one already-signed XRPL transaction to the network. `tx_blob` must be the complete signed transaction encoded as hexadecimal; obtain it from the caller's local signing step, normally after `n9t2_xrpl_prepare_transaction`. This action mutates ledger state when the transaction is accepted into the XRPL network and must never receive private keys, seeds, or wallet secrets. `fail_hard` forwards rippled's option and defaults to false; when true, a transaction that fails locally is not retried or relayed. The result preserves the raw submit response, including `engine_result` and `engine_result_message` and, when returned, `accepted`, `queued`, `validated`, and transaction data. Submission is tentative; use `n9t2_xrpl_get_transaction` with the returned transaction hash to confirm validated-ledger inclusion. Invalid hexadecimal or XRPL-rejected blobs return an error.

  Parameters:

  • tx_blob (required) — string — Complete signed XRPL transaction encoded as hexadecimal. The caller must sign locally before sending it to N9T2.
  • fail_hard — boolean — Forward rippled's fail_hard option. When true, a transaction that fails locally is not retried or relayed to other servers. Defaults to false.

  Hints: read-only no · destructive yes · idempotent no · open-world yes

• n9t2_xrpl_prepare_transaction read-only

  Prepare one unsigned XRPL transaction for agent-local signing. Choose exactly one transaction_type and provide that transaction model's fields in parameters; unsupported transaction types or invalid builder parameters are rejected before an unsigned transaction is returned. Sequence, fee, and last_ledger_sequence may be autofilled when omitted. The result is unsigned transaction JSON for local signing; after signing, pass the signed tx_blob to n9t2_xrpl_submit_transaction. N9T2 never receives or stores private keys, seeds, or wallet secrets. Use this as the generic transaction-construction primitive for supported XRPL transaction types, including Payment, TrustSet, OfferCreate, and OfferCancel.

  Parameters:

  • transaction_type (required) — string — XRPL transaction model name to prepare, selected from the supported transaction types advertised by this tool.
  • parameters (required) — object — Typed XRPL transaction fields used to build the unsigned transaction. Sequence, fee, and last_ledger_sequence may be autofilled when omitted.

  Hints: read-only yes · destructive no · idempotent no · open-world yes

• n9t2_xrpl_get_amm_info read-only

  Read-only XRPL Automated Market Maker (AMM) state lookup for a specific pool. Identify the pool with `amm_account`, or with the paired `asset` and `asset2` currency objects; `account` is optional context used by the native AMM lookup when applicable. Use `ledger_hash` or `ledger_index` to pin the lookup to a specific ledger. The result returns native `amm_info` data including pool balances, LP token supply, trading fee, auction slot, and vote slots when present. This paid lookup does not modify the ledger and is subject to the configured gateway rate limits. Use this for AMM pool state; use n9t2_xrpl_get_book_offers for DEX order-book depth and n9t2_xrpl_get_ledger_data for raw ledger-state objects.

  Parameters:

  • asset — First AMM asset specification using an XRPL currency object.
  • asset2 — Second AMM asset specification paired with asset.
  • account — Optional XRPL account used by the native AMM lookup when applicable.
  • amm_account — Optional AMM account address identifying the specific AMM ledger object.
  • ledger_hash — Optional ledger hash used to pin the AMM lookup to a specific ledger.
  • ledger_index — Optional ledger index or selector used to pin the lookup to a specific ledger.

  Hints: read-only yes · destructive no · idempotent yes · open-world yes

• n9t2_xrpl_list_nft_offers read-only

  Read-only XRPL NFT marketplace-offer lookup for one NFTokenID. `offer_type=buy` retrieves native `nft_buy_offers`, `sell` retrieves `nft_sell_offers`, and `both` retrieves both sides; `buy_marker` and `sell_marker` paginate the two sides independently. Use `ledger_hash` or `ledger_index` to pin the lookup to a ledger, and `limit` to bound returned offers. Use this for marketplace offers on a specific NFT; use n9t2_xrpl_list_account_nfts for owned-NFT inventory and n9t2_xrpl_list_account_objects with `object_type='nft_offer'` when raw NFTokenOffer ledger entries are required.

  Parameters:

  • nft_id (required) — string — Canonical NFTokenID identifying the NFT whose marketplace offers should be retrieved.
  • limit — Optional maximum number of NFT offers to return.
  • buy_marker — Pagination marker for the NFT buy-offer side.
  • offer_type — string — NFT marketplace offer side to retrieve: buy, sell, or both. Default is both.
  • ledger_hash — Optional ledger hash used to pin the NFT-offer lookup.
  • sell_marker — Pagination marker for the NFT sell-offer side.
  • ledger_index — Optional validated ledger index or selector.

  Hints: read-only yes · destructive no · idempotent yes · open-world yes

• n9t2_bridge_quote

  FREE. Get a live, firm quote to move funds both ways between native XRP on the XRP Ledger and BTC on Bitcoin, BNB, USDT or USDC on BNB Chain (bsc), or USDC or ETH on Base (12 live routes). Returns quote_id, exact payment instructions (amount, asset, network, pay_to, expiry), the N9T2 fee (1.45 XRP equivalent) and the estimated destination amount. Creating a quote moves no funds. Optional source_amount up to 1000 USDC / 1500 XRP / 0.5 ETH / 1.5 BNB / 1000 USDT / 0.02 BTC; larger transfers go to the OTC desk ([email protected]). Next: customer approves and pays in their own wallet, then call n9t2_bridge_submit_payment.

  Parameters:

  • source_chain (required) — string — Chain the customer pays from: xrpl (XRP Ledger), bitcoin, bsc (BNB Chain) or base. Every route has xrpl on one side.
  • source_asset (required) — string — Asset the customer pays with: XRP on xrpl; BTC on bitcoin; BNB, USDT or USDC on bsc; USDC or ETH on base.
  • destination_chain (required) — string — Chain that receives the funds; must differ from source_chain, and one of the two must be xrpl.
  • destination_asset (required) — string — Asset delivered: XRP on xrpl; BTC on bitcoin; BNB, USDT or USDC on bsc; USDC or ETH on base.
  • destination_address (required) — string — Customer-controlled destination wallet: r... classic address for xrpl, bc1.../3.../1... for bitcoin, 0x... for bsc or base.
  • source_amount — Optional amount to bridge in the source asset as a decimal string, e.g. '250'. The N9T2 fee is added on top. Self-serve cap: 1000 USDC, 1500 XRP, 0.5 ETH, 1.5 BNB, 1000 USDT or 0.02 BTC. Omit for the live route minimum.

  Hints: read-only no · destructive no · idempotent no · open-world yes

• n9t2_bridge_submit_payment

  FREE. Submit the transaction hash of the customer's real payment for a bridge quote. N9T2 verifies it on-chain against the quote (exact amount, asset, recipient, expiry) and, once verified, executes the cross-chain delivery through its exactly-once worker. Resubmitting the same quote_id and hash returns the existing record. Verification is not completion: follow up with n9t2_bridge_receipt.

  Parameters:

  • quote_id (required) — string — Exact quote_id from n9t2_bridge_quote.
  • transaction_hash (required) — string — Hash of the customer's actual source-chain payment for that quote. Never a planned or fabricated hash.

  Hints: read-only no · destructive no · idempotent yes · open-world yes

• n9t2_bridge_receipt read-only

  FREE. Read the immutable, customer-safe receipt for a bridge transfer by quote_id: status, amount paid, amount delivered, N9T2 fee, route cost and the payment and delivery transaction hashes. A transfer is complete only when status is 'settled' and settlement.status is 'completed'. 404 means not ready yet.

  Parameters:

  • quote_id (required) — string — quote_id of the transfer to check.

  Hints: read-only yes · destructive no · idempotent yes · open-world yes

Publisher website

Measured by MCPYP probing. Untested fields are omitted, never estimated. Listing is always free; MCPYP never proxies calls or stores user tokens.