Alpaca Trading API integration for Model Context Protocol (MCP)
Nothing to run from here
N9T2 XRPL Agent Gateway is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
22
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
Agent-native XRPL infrastructure: 19 paid MCP tools, x402 USDC on Base, non-custodial XRPL actions.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http n9t2-xrpl-agent-gateway-mcp https://x402.n9t2.com/mcp
# 2 — ask your agent for something these tools do
# n9t2_xrpl_get_account_info, n9t2_xrpl_list_account_transactions, n9t2_xrpl_get_transaction and 19 more
N9T2 XRPL Agent Gateway costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
N9All 1 server
n9t21 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http n9t2-xrpl-agent-gateway-mcp https://x402.n9t2.com/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
22 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| account | string | yes | XRPL classic account address whose current account state should be retrieved. |
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 cur
| Parameter | Type | Required | Notes |
|---|---|---|---|
| account | string | yes | XRPL classic account address whose transaction history should be retrieved. |
| ledger_index_min | no | Optional minimum ledger index for the transaction-history range. | |
| ledger_index_max | no | Optional maximum ledger index for the transaction-history range. | |
| limit | no | Optional maximum number of transactions to return. |
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 transac
| Parameter | Type | Required | Notes |
|---|---|---|---|
| transaction | string | yes | Canonical XRPL transaction hash to retrieve. |
| binary | no | Whether to return the transaction in binary encoded form. |
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 led
| Parameter | Type | Required | Notes |
|---|---|---|---|
| ledger_index | no | Optional validated ledger index or ledger selector. Omit to use the current validated ledger. | |
| transactions | no | Whether to include transactions contained in the requested ledger. | |
| expand | no | Whether returned transactions should be expanded into full transaction objects. |
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 pa
| Parameter | Type | Required | Notes |
|---|---|---|---|
| ledger_index | no | Optional ledger index or selector identifying the ledger whose state objects should be returned. | |
| limit | no | Optional maximum number of ledger-state objects to return. | |
| marker | no | Pagination marker returned by a previous response. |
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 t
| Parameter | Type | Required | Notes |
|---|---|---|---|
| taker_gets | object | yes | Currency specification for the asset the taker receives in the XRPL DEX order book. |
| taker_pays | object | yes | Currency specification for the asset the taker pays in the XRPL DEX order book. |
| limit | no | Optional maximum number of DEX order-book offers to return. |
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 so
| Parameter | Type | Required | Notes |
|---|---|---|---|
| source_account | string | yes | XRPL classic account address used as the source of payment-path discovery. |
| destination_account | string | yes | XRPL classic account address that will receive the destination amount. |
| destination_amount | yes | Destination amount to deliver. Use a string for XRP drops or an issued-currency object containing currency, issuer, and value. |
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 mo
| Parameter | Type | Required | Notes |
|---|---|---|---|
| account | string | yes | XRPL classic account address whose trust lines should be listed. |
| peer | no | Optional XRPL classic account address used to filter trust lines to a specific peer. | |
| ledger_index | no | Optional validated ledger index or selector. | |
| limit | no | Optional maximum number of trust lines to return. | |
| marker | no | Pagination marker returned by a previous response. |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| account | string | yes | XRPL classic account address whose canonical ledger objects should be inspected. |
| ledger_index | no | Optional validated ledger index or selector. | |
| sponsored | no | Optional filter controlling sponsored ledger objects. | |
| object_type | no | Optional XRPL ledger-entry type filter. Use 'nft_offer' for account-level NFTokenOffer ledger entries. | |
| deletion_blockers_only | boolean | no | Whether to return only ledger objects that prevent account deletion. |
| limit | no | Optional maximum number of ledger objects to return. | |
| marker | no | Pagination marker returned by a previous response. |
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 t
| Parameter | Type | Required | Notes |
|---|---|---|---|
| account | string | yes | XRPL classic account address whose outstanding DEX offers should be listed. |
| ledger_index | no | Optional validated ledger index or selector. | |
| limit | no | Optional maximum number of open offers to return. | |
| marker | no | Pagination marker returned by a previous response. | |
| strict | boolean | no | Whether the account identifier should be interpreted strictly as supplied. |
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 resul
| Parameter | Type | Required | Notes |
|---|---|---|---|
| account | string | yes | XRPL classic account address whose Payment Channels should be listed. |
| destination_account | no | Optional destination account filter. When supplied, return channels whose destination is this account. | |
| ledger_index | no | Optional validated ledger index or selector. | |
| limit | integer | no | Maximum number of Payment Channel entries to return. Default is 200. |
| marker | no | Pagination marker returned by a previous response. |
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_
No parameter schema on file.
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| account | string | yes | XRPL issuing account whose issued-asset balances should be calculated. |
| ledger_index | no | Optional ledger index or selector for the balance calculation. | |
| strict | boolean | no | Whether account identifiers should be interpreted strictly as supplied. |
| hotwallet | no | Optional XRPL hot-wallet account address or list of hot-wallet addresses. |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| account | string | yes | XRPL classic account address whose owned NFTs should be listed. |
| ledger_hash | no | Optional ledger hash used to pin the NFT inventory lookup. | |
| ledger_index | no | Optional validated ledger index or selector. | |
| limit | no | Optional maximum number of owned NFT records to return. | |
| marker | no | Pagination marker returned by a previous response. |
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 a
| Parameter | Type | Required | Notes |
|---|---|---|---|
| streams | no | Optional XRPL stream names such as ledger or transactions. | |
| accounts | no | Optional list of XRPL classic account addresses whose activity should be streamed. | |
| accounts_proposed | no | Optional list of XRPL accounts for proposed transaction events. | |
| books | no | Optional list of XRPL order-book subscription descriptors. | |
| duration_seconds | integer | no | How many seconds the bounded WebSocket subscription remains open. Default is 3. |
| max_events | integer | no | Maximum number of events to capture before returning. Default is 25. |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| tx_blob | string | yes | Complete signed XRPL transaction encoded as hexadecimal. The caller must sign locally before sending it to N9T2. |
| fail_hard | boolean | no | Forward rippled's fail_hard option. When true, a transaction that fails locally is not retried or relayed to other servers. Defaults to false. |
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 sig
| Parameter | Type | Required | Notes |
|---|---|---|---|
| transaction_type | string | yes | XRPL transaction model name to prepare, selected from the supported transaction types advertised by this tool. |
| parameters | object | yes | Typed XRPL transaction fields used to build the unsigned transaction. Sequence, fee, and last_ledger_sequence may be autofilled when omitted. |
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 tok
| Parameter | Type | Required | Notes |
|---|---|---|---|
| account | no | Optional XRPL account used by the native AMM lookup when applicable. | |
| amm_account | no | Optional AMM account address identifying the specific AMM ledger object. | |
| asset | no | First AMM asset specification using an XRPL currency object. | |
| asset2 | no | Second AMM asset specification paired with asset. | |
| ledger_hash | no | Optional ledger hash used to pin the AMM lookup to a specific ledger. | |
| ledger_index | no | Optional ledger index or selector used to pin the lookup to a specific ledger. |
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 speci
| Parameter | Type | Required | Notes |
|---|---|---|---|
| nft_id | string | yes | Canonical NFTokenID identifying the NFT whose marketplace offers should be retrieved. |
| offer_type | string | no | NFT marketplace offer side to retrieve: buy, sell, or both. Default is both. |
| ledger_hash | no | Optional ledger hash used to pin the NFT-offer lookup. | |
| ledger_index | no | Optional validated ledger index or selector. | |
| limit | no | Optional maximum number of NFT offers to return. | |
| buy_marker | no | Pagination marker for the NFT buy-offer side. | |
| sell_marker | no | Pagination marker for the NFT sell-offer side. |
FREE. Get a live, firm quote to move funds between native XRP on the XRP Ledger and USDC or ETH on Base Mainnet (routes: XRP->USDC, XRP->ETH, USDC->XRP, ETH->XRP). 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 / 15
| Parameter | Type | Required | Notes |
|---|---|---|---|
| source_chain | string | yes | Chain the customer pays from: xrpl or base. |
| source_asset | string | yes | Asset the customer pays with: XRP on xrpl; USDC or ETH on base. |
| destination_chain | string | yes | Chain that receives the funds; must differ from source_chain. |
| destination_asset | string | yes | Asset delivered: XRP on xrpl; USDC or ETH on base. |
| destination_address | string | yes | Customer-controlled destination wallet: r... classic address for xrpl, 0x... address for base. |
| source_amount | no | 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 or 0.5 ETH. Omit for the live route minimum. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| quote_id | string | yes | Exact quote_id from n9t2_bridge_quote. |
| transaction_hash | string | yes | Hash of the customer's actual source-chain payment for that quote. Never a planned or fabricated hash. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| quote_id | string | yes | quote_id of the transfer to check. |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install N9T2 XRPL Agent Gateway or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
—Grade not published
No rule-by-rule report on file for this release
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.6.9.
1.6.9
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish N9T2 XRPL Agent Gateway can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.