Skip to content

MCP servers › com.n9t2 › xrpl-agent-gateway

MCP server · registry snapshot 2026-10-23 · last tested 2026-10-23

com.n9t2/xrpl-agent-gateway

Agent-native XRPL infrastructure: 19 paid MCP tools, x402 USDC on Base, non-custodial XRPL actions. — the publisher's description

1 of 2 record checks metRead-only · tools listed 2026-10-23Topic: finance-and-payments · AI-classifiedPricing: usage-based · AI-classifiedversion 1.6.9streamable HTTP22 tools

Summary

com.n9t2/xrpl-agent-gateway is a remote MCP server listed in the official MCP registry at version 1.6.9. On 2026-10-23 ProtocolProbe connected to it in read-only mode and read its inventory: 22 tools, 0 resources and 0 prompts.

Record checks

1 of 2 record checks met · 7 do not apply

  • met: Registry entry is active and says how to run it
  • not met: Source repository link opens
  • not applicable: Repository is not archived
  • not applicable: Code pushed to the repository in the 90 days before our check
  • not applicable: Repository publishes a security policy (SECURITY.md)
  • not applicable: Package names its licence with a standard (SPDX) identifier
  • not applicable: The version the registry lists can be installed and is not withdrawn
  • not applicable: npm package carries build provenance (attestation)
  • not applicable: No known critical or high advisory in the package or its dependencies
  • Not ranked by downloads: a remote server publishes no download figure
  • Not ranked by stars: no public GitHub repository

From public records, not a safety rating. Each check with its reason · Is it safe to install?

Key facts

Runs
remote (hosted by the publisher)
Transport
streamable HTTP
Sign-in
none needed to open a session
Tools
22
Described as changing data
2 of 22 toolsAI-classified
Topic
finance-and-paymentsAI-classified
Pricing
usage-basedAI-classified
Last tested
2026-10-23

Add to your client

Observed fact

This server accepted a session without any credential and lists 1 tool whose name or declaration suggests it changes data (n9t2_xrpl_submit_transaction). That is our reading of the names; we did not call it. Source: our connection, 2026-10-23.

Worth knowing before you connect it

  • 2 tools are described as changing something (n9t2_xrpl_submit_transaction, n9t2_bridge_submit_payment): our AI model's reading of the descriptions, not something we tested, and the server opened a session without any credential. We did not call them.

Each line comes from a section below, with its source and date.

How fresh this is

Live-tested
yes, a real session (not a text-only review)
Last tested
2026-10-23
Mode
read-only (no tool calls)
Latest version
1.6.9, published 2026-10-06 (registry, as of the 2026-10-23 snapshot)
First listed version
2026-10-04 (earliest version still in the registry; older removed versions would be earlier)
Version history
14 versions listed, 2026-10-04 to 2026-10-06; 14 in the 90 days before the 2026-10-23 snapshot.
Most recent 12 versions
  • 1.6.9 · 2026-10-06
  • 1.6.8 · 2026-10-06
  • 1.6.7 · 2026-10-06
  • 1.6.6 · 2026-10-06
  • 1.6.5 · 2026-10-06
  • 1.6.3 · 2026-10-06
  • 1.6.1 · 2026-10-06
  • 1.6.0 · 2026-10-05
  • 1.5.0 · 2026-10-05
  • 1.4.0 · 2026-10-05
  • 1.3.0 · 2026-10-05
  • 1.2.0 · 2026-10-05
(versions still listed in the registry only)
Registry data
snapshot 2026-10-23
Package and repository
checked 2026-10-22
Engine
mcp-runtime-engine@0.1.0 · sdk@1.32.0

Changes since the last refresh

New in the registry: not in the list of 2026-10-04, listed on 2026-10-23 with version 1.6.9 (published 2026-10-06).

Source: the official MCP Registry list on 2026-10-04 and on 2026-10-23.

What it is

What does this server offer?

Observed inventory
22tools
0resources
0prompts

2 of 22 tools are described as changing something (creating, editing, deleting, sending or running).

  • n9t2_xrpl_get_account_inforeads or searches

    “Read-only XRPL current-account-state lookup for one account.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    1 input, 1 required
    • accountstringrequired“XRPL classic account address whose current account state should be retrieved.”
  • n9t2_xrpl_list_account_transactionsreads or searches

    “Read-only XRPL transaction-history lookup for one account over an optional ledger range.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    4 inputs, 1 required
    • accountstringrequired“XRPL classic account address whose transaction history should be retrieved.”
    • ledger_index_mininteger or null“Optional minimum ledger index for the transaction-history range.”
    • ledger_index_maxinteger or null“Optional maximum ledger index for the transaction-history range.”
    • limitinteger or null“Optional maximum number of transactions to return.”
  • n9t2_xrpl_get_transactionreads or searches

    “Read-only XRPL transaction lookup for one canonical transaction hash.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    2 inputs, 1 required
    • transactionstringrequired“Canonical XRPL transaction hash to retrieve.”
    • binaryboolean or null“Whether to return the transaction in binary encoded form.”
  • n9t2_xrpl_get_ledgerreads or searches

    “Read-only XRPL ledger header and metadata lookup.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    3 inputs
    • ledger_indexstring or integer or null“Optional validated ledger index or ledger selector.”
    • transactionsboolean or null“Whether to include transactions contained in the requested ledger.”
    • expandboolean or null“Whether returned transactions should be expanded into full transaction objects.”
  • n9t2_xrpl_get_ledger_datareads or searches

    “Read-only XRPL raw ledger-state lookup for a ledger.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    3 inputs
    • ledger_indexstring or integer or null“Optional ledger index or selector identifying the ledger whose state objects should be returned.”
    • limitinteger or null“Optional maximum number of ledger-state objects to return.”
    • markerobject or null“Pagination marker returned by a previous response.”
  • n9t2_xrpl_get_book_offersreads or searches

    “Read-only XRPL DEX order-book lookup for a specific trading pair.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    3 inputs, 2 required
    • taker_getsobjectrequired“Currency specification for the asset the taker receives in the XRPL DEX order book.”
    • taker_paysobjectrequired“Currency specification for the asset the taker pays in the XRPL DEX order book.”
    • limitinteger or null“Optional maximum number of DEX order-book offers to return.”
  • n9t2_xrpl_find_pathreads or searches

    “Read-only XRPL payment-path discovery for planning a Payment from source_account to destination_account.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    3 inputs, 3 required
    • source_accountstringrequired“XRPL classic account address used as the source of payment-path discovery.”
    • destination_accountstringrequired“XRPL classic account address that will receive the destination amount.”
    • destination_amountstring or objectrequired“Destination amount to deliver.”
  • n9t2_xrpl_list_account_linesreads or searches

    “Read-only XRPL trust-line lookup for one account.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    5 inputs, 1 required
    • accountstringrequired“XRPL classic account address whose trust lines should be listed.”
    • peerstring or null“Optional XRPL classic account address used to filter trust lines to a specific peer.”
    • ledger_indexstring or integer or null“Optional validated ledger index or selector.”
    • limitinteger or null“Optional maximum number of trust lines to return.”
    • markerobject or null“Pagination marker returned by a previous response.”
  • n9t2_xrpl_list_account_objectsreads or searches

    “Read-only XRPL canonical ledger-object lookup for one account.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    7 inputs, 1 required
    • accountstringrequired“XRPL classic account address whose canonical ledger objects should be inspected.”
    • ledger_indexstring or integer or null“Optional validated ledger index or selector.”
    • sponsoredboolean or null“Optional filter controlling sponsored ledger objects.”
    • object_typestring or null“Optional XRPL ledger-entry type filter.”
    • deletion_blockers_onlyboolean“Whether to return only ledger objects that prevent account deletion.”
    • limitinteger or null“Optional maximum number of ledger objects to return.”
    • markerobject or null“Pagination marker returned by a previous response.”
  • n9t2_xrpl_list_account_offersreads or searches

    “Read-only XRPL DEX account-offer lookup for one account.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    5 inputs, 1 required
    • accountstringrequired“XRPL classic account address whose outstanding DEX offers should be listed.”
    • ledger_indexstring or integer or null“Optional validated ledger index or selector.”
    • limitinteger or null“Optional maximum number of open offers to return.”
    • markerobject or null“Pagination marker returned by a previous response.”
    • strictboolean“Whether the account identifier should be interpreted strictly as supplied.”
  • n9t2_xrpl_list_account_channelsreads or searches

    “Read-only XRPL Payment Channel lookup for one account.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    5 inputs, 1 required
    • accountstringrequired“XRPL classic account address whose Payment Channels should be listed.”
    • destination_accountstring or null“Optional destination account filter.”
    • ledger_indexstring or integer or null“Optional validated ledger index or selector.”
    • limitinteger“Maximum number of Payment Channel entries to return.”
    • markerobject or null“Pagination marker returned by a previous response.”
  • n9t2_xrpl_get_server_inforeads or searches

    “Read-only XRPL `server_info` lookup for node health, server state, and validated-ledger status.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    Takes no inputs.

Show 10 more tools
  • n9t2_xrpl_get_gateway_balancesreads or searches

    “Read-only XRPL issued-asset exposure calculation for one issuing account.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    4 inputs, 1 required
    • accountstringrequired“XRPL issuing account whose issued-asset balances should be calculated.”
    • ledger_indexstring or integer or null“Optional ledger index or selector for the balance calculation.”
    • strictboolean“Whether account identifiers should be interpreted strictly as supplied.”
    • hotwalletstring or array or null“Optional XRPL hot-wallet account address or list of hot-wallet addresses.”
  • n9t2_xrpl_list_account_nftsreads or searches

    “Read-only XRPL NFT inventory lookup for one classic account using the native `account_nfts` method.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    5 inputs, 1 required
    • accountstringrequired“XRPL classic account address whose owned NFTs should be listed.”
    • ledger_hashstring or null“Optional ledger hash used to pin the NFT inventory lookup.”
    • ledger_indexstring or integer or null“Optional validated ledger index or selector.”
    • limitinteger or null“Optional maximum number of owned NFT records to return.”
    • markerobject or null“Pagination marker returned by a previous response.”
  • n9t2_xrpl_subscribereads or searches

    “Open a bounded native XRPL WebSocket subscription and capture live events for selected streams, accounts, proposed transactions, or order books.”

    Publisher declares: read-only yes · destructive no · idempotent no · open-world yes

    6 inputs
    • streamsarray or null“Optional XRPL stream names such as ledger or transactions.”
    • accountsarray or null“Optional list of XRPL classic account addresses whose activity should be streamed.”
    • accounts_proposedarray or null“Optional list of XRPL accounts for proposed transaction events.”
    • booksarray or null“Optional list of XRPL order-book subscription descriptors.”
    • duration_secondsinteger“How many seconds the bounded WebSocket subscription remains open.”
    • max_eventsinteger“Maximum number of events to capture before returning.”
  • n9t2_xrpl_submit_transactionruns code or commandsdescribed as changing data

    “Submit one already-signed XRPL transaction to the network.”

    Publisher declares: read-only no · destructive yes · idempotent no · open-world yes

    2 inputs, 1 required
    • tx_blobstringrequired“Complete signed XRPL transaction encoded as hexadecimal.”
    • fail_hardboolean“Forward rippled's fail_hard option.”
  • n9t2_xrpl_prepare_transaction

    “Prepare one unsigned XRPL transaction for agent-local signing.”

    Publisher declares: read-only yes · destructive no · idempotent no · open-world yes

    2 inputs, 2 required
    • transaction_typestringrequired“XRPL transaction model name to prepare, selected from the supported transaction types advertised by this tool.”
    • parametersobjectrequired“Typed XRPL transaction fields used to build the unsigned transaction.”
  • n9t2_xrpl_get_amm_inforeads or searches

    “Read-only XRPL Automated Market Maker (AMM) state lookup for a specific pool.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    6 inputs
    • accountstring or null“Optional XRPL account used by the native AMM lookup when applicable.”
    • amm_accountstring or null“Optional AMM account address identifying the specific AMM ledger object.”
    • assetobject or null“First AMM asset specification using an XRPL currency object.”
    • asset2object or null“Second AMM asset specification paired with asset.”
    • ledger_hashstring or null“Optional ledger hash used to pin the AMM lookup to a specific ledger.”
    • ledger_indexstring or integer or null“Optional ledger index or selector used to pin the lookup to a specific ledger.”
  • n9t2_xrpl_list_nft_offersreads or searches

    “Read-only XRPL NFT marketplace-offer lookup for one NFTokenID.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    7 inputs, 1 required
    • nft_idstringrequired“Canonical NFTokenID identifying the NFT whose marketplace offers should be retrieved.”
    • offer_typestring“NFT marketplace offer side to retrieve: buy, sell, or both.”
    • ledger_hashstring or null“Optional ledger hash used to pin the NFT-offer lookup.”
    • ledger_indexstring or integer or null“Optional validated ledger index or selector.”
    • limitinteger or null“Optional maximum number of NFT offers to return.”
    • buy_markerobject or null“Pagination marker for the NFT buy-offer side.”
    • sell_markerobject or null“Pagination marker for the NFT sell-offer side.”
  • n9t2_bridge_quote

    “FREE.”

    Publisher declares: read-only no · destructive no · idempotent no · open-world yes

    6 inputs, 5 required
    • source_chainstringrequired“Chain the customer pays from: xrpl (XRP Ledger), bitcoin, bsc (BNB Chain) or base.”
    • source_assetstringrequired“Asset the customer pays with: XRP on xrpl; BTC on bitcoin; BNB, USDT or USDC on bsc; USDC or ETH on base.”
    • destination_chainstringrequired“Chain that receives the funds; must differ from source_chain, and one of the two must be xrpl.”
    • destination_assetstringrequired“Asset delivered: XRP on xrpl; BTC on bitcoin; BNB, USDT or USDC on bsc; USDC or ETH on base.”
    • destination_addressstringrequired“Customer-controlled destination wallet: r...”
    • source_amountstring or null“Optional amount to bridge in the source asset as a decimal string, e.g.”
  • n9t2_bridge_submit_paymentdescribed as changing data

    “FREE.”

    Publisher declares: read-only no · destructive no · idempotent yes · open-world yes

    2 inputs, 2 required
    • quote_idstringrequired“Exact quote_id from n9t2_bridge_quote.”
    • transaction_hashstringrequired“Hash of the customer's actual source-chain payment for that quote.”
  • n9t2_bridge_receiptreads or searches

    “FREE.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    1 input, 1 required
    • quote_idstringrequired“quote_id of the transfer to check.”

Each quoted sentence is the first sentence of the publisher’s own description. The kind of tool and the “changes data” mark are our AI model’s reading of that description, not something we tested: two differently worded runs had to agree, otherwise no label is shown, and nobody has checked them by hand. A tool without the “changes data” mark is described as only reading, searching or calculating, or the two runs did not agree. No tool was called. Read the publisher’s full description before relying on it. “Publisher declares” lists the hints the server itself sends with the tool (MCP annotations: read-only, destructive, idempotent, open-world); they are the publisher's claims, not checked by us. Inputs are the parameters in the tool's own input schema: name, declared type, whether it is required, and the first sentence of its description. Read 2026-10-23.

How well are its tools described?

Features #4 and #5

How clearly this server's own tool descriptions say what a tool does, and how consistent its tool list is. The first part is an AI model's yes/no reading of each description; the second part is counted. We do not turn it into a grade.

Descriptions

AI reading of each description

Says what the tool does
100% of 22 tools
Says what it returns
100% of 21 tools
States limits, defaults or errors
100% of 22 tools
Says when to use it
100% of 22 tools
Items covered per tool
4.0 of 4 on average

Counted from the listing

Parameters with a description
100% of 82
Tools with a description
100% of 22
Typical description length
604 characters

The tool set

Counted from the listing

Tools
22
Size of the list
about 9,108 tokens for an agent to load (characters ÷ 4)
Naming
22 of 22 names use snake_case

AI reading: easy to mix up

No pair found.

The AI items cover 22 of 22 tools: for a tool where two differently worded runs disagreed, that item is left out. They were not checked by hand, and no tool was called. “Easy to mix up” means two tools whose names or descriptions overlap without saying how they differ; the AI found none. We do not rate whether the tool set is complete or whether side effects are spelled out, because our AI reading of those was not reliable enough.

How do I add it to my client?

Config from the registry entry

From the remote endpoint (Streamable HTTP)

We connected to this URL on 2026-10-23 (a read-only session: no tool was called).

Add to CursorAn install link in the format Cursor documents, holding the Cursor config below.

Claude Desktop or claude.ai
Settings → Connectors → Add custom connector, then paste:
https://x402.n9t2.com/mcp
Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json
{
  "mcpServers": {
    "xrpl-agent-gateway": {
      "url": "https://x402.n9t2.com/mcp"
    }
  }
}
VS Code · .vscode/mcp.json
{
  "servers": {
    "xrpl-agent-gateway": {
      "type": "http",
      "url": "https://x402.n9t2.com/mcp"
    }
  }
}
VS Code (command line) · Bash or zsh terminal (macOS, Linux)
code --add-mcp '{"name":"xrpl-agent-gateway","type":"http","url":"https://x402.n9t2.com/mcp"}'
Claude Code
claude mcp add --transport http xrpl-agent-gateway https://x402.n9t2.com/mcp
Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+
npx @modelcontextprotocol/inspector@2.11.0 --server-url https://x402.n9t2.com/mcp --transport http
  • The server runs on the operator's infrastructure; it may ask you to sign in when you first connect.
  • The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.

Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.

Does the registry listing match what we found?

Feature #6

The registry verifies a package once, when it is published, and does not re-check it. A difference below is about the listing, not a judgement of the publisher.

Registry saysWe foundResultSource · date
Remote endpoint x402.n9t2.com/mcpSession openedmatchesour test · 2026-10-23
No credential declared as requiredOpened a session without any credentialmatchesour test · 2026-10-23

Choosing

Record checks

Public records · not a safety rating

1 of 2 record checks met · 7 do not apply

  • Not ranked by downloads: a remote server publishes no download figure
  • Not ranked by stars: no public GitHub repository
  • MetRegistry entry is active and says how to run itActive, with a package or a remote address.
  • Not metSource repository link opensThe registry entry gives no repository link.
  • Does not applyRepository is not archivedNo public GitHub repository to read.
  • Does not applyCode pushed to the repository in the 90 days before our checkNo public GitHub repository to read.
  • Does not applyRepository publishes a security policy (SECURITY.md)No public GitHub repository to read.
  • Does not applyPackage names its licence with a standard (SPDX) identifierRemote server: it ships no package.
  • Does not applyThe version the registry lists can be installed and is not withdrawnRemote server: it ships no package.
  • Does not applynpm package carries build provenance (attestation)Remote server: it ships no package.
  • Does not applyNo known critical or high advisory in the package or its dependenciesRemote server: it ships no package.

Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-10-22. No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating. How each check works · Leaderboards

Common questions about com.n9t2/xrpl-agent-gateway

Answered from the data above

Is com.n9t2/xrpl-agent-gateway safe to install?

We do not rate servers as safe or unsafe. 1 of its 2 applicable record checks are met (facts from public records, each listed on this page). What the records show: 2 of its tools describe changing data (our AI model's reading of the descriptions). These are facts with their sources on this page, not a safety guarantee, and we did not run its tools.

Is com.n9t2/xrpl-agent-gateway free to use?

Its website (x402.n9t2.com/) describes a usage-based pricing model. This is an AI-classified reading of the page on 2026-10-23, so check the page itself before relying on it.

Does com.n9t2/xrpl-agent-gateway need an API key or sign-in?

It opened a session without any credential on 2026-10-23. The registry entry declares no required credential; no declaration is not a guarantee.

Has com.n9t2/xrpl-agent-gateway been security tested?

Partly. 2 of the 14 checks that apply to it were exercised. It accepted a session without any credential and lists tools whose names suggest they change data. We did not call them. No security verdict is published before verification.

What can com.n9t2/xrpl-agent-gateway do?

It lists 22 tools. In our AI model's reading of their descriptions (two runs had to agree, nobody checked it by hand), they include tools that read or search and run code or commands. We did not call any tool, so this describes the text, not the behaviour.

Can com.n9t2/xrpl-agent-gateway change or delete data?

2 of its tools say in their description that they create, edit, delete, send or run something (our AI model's reading). We did not call any tool, so we cannot say what actually happens.

Found this page useful?

Anonymous · no sign-in

A quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.

Similar servers

Same topic · AI-read

Active servers whose topic is also “finance-and-payments” and that have at least one tool of the same kind; most kinds in common first, then most GitHub stars. The topic and the tool kinds are an AI model's reading of the publishers' descriptions, not checked by hand. Similar is not a recommendation.

Compare with another server

Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.

Security testing

What did we test, and what did we leave out?

18 checks · features #1, #2

Open without sign-in

It accepted a session without any credential and lists tools whose names suggest they change data. We did not call them. No security score is given; a check we did not run is never counted as passed.

The 18 checks at a glanceour test · 2026-10-23
  1. Inventory: exercised
  2. Hidden instructions: exercised
  3. Real execution: not run · our policy
  4. Secret leak: not run · nothing to check it against
  5. Internal addresses: not run · our policy
  6. Unconfirmed changes: not run · our policy
  7. Bad input: not run · our policy
  8. Model requests: not run · nothing to check it against
  9. Sensitive questions: not run · nothing to check it against
  10. Folder boundary: not run · our policy
  11. Log leaks: not run · nothing to check it against
  12. Hidden content: not run · nothing to check it against
  13. Fake assistant turns: not applicable
  14. Token passthrough: not applicable
  15. Token audience: not applicable
  16. Sign-in redirect: not run · our policy
  17. Consent handling: not testable from outside
  18. Sign-in metadata: not applicable

2 exercised12 not run (reason given)4 not applicable

Each check ends in exactly one state: exercised, not run (with the reason), or not applicable (with the reason). 2 of the 14 checks that apply to it were exercised. We do not publish security-check outcomes for named servers.

Exercised · 2
  • 1Inventory
    tool-list
    Reads the declared tools, resources and prompts.exercised
  • 2Hidden instructions
    description-poisoning
    Looks for hidden instructions in tool descriptions.exercised
Not run, with the reason · 12
  • 3Real execution
    real-execution
    Calls a tool and checks what really happens.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 4Secret leak
    canary-leak
    Plants a fake secret and checks whether it leaks.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 5Internal addresses
    ssrf
    Checks whether a tool can be steered to internal addresses.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 6Unconfirmed changes
    write-without-confirmation
    Checks whether tools that change data act without asking.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 7Bad input
    error-handling
    Sends bad input and watches how the server answers.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 8Model requests
    sampling
    Checks whether the server asks the client's model to act for it.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 9Sensitive questions
    elicitation-sensitive-data
    Checks whether the server asks users for sensitive data.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 10Folder boundary
    root-boundary
    Checks whether the server reaches outside the folders it was given.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 11Log leaks
    logging-side-channel
    Checks whether log messages carry data they should not.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 12Hidden content
    audience-hiding
    Checks resources that hide content from the user.This check needs content the server returns, and nothing was read or called.not run · nothing to check it against
  • 16Sign-in redirect
    open-redirect
    Checks the sign-in redirect for abuse.Testing the sign-in redirect means sending probes to the operator's sign-in service, which we do not do.not run · our policy
  • 17Consent handling
    confused-deputy
    Checks consent handling when one service acts for another.Depends on the operator's own consent screen, which differs per server and cannot be tested from outside.not testable from outside
Does not apply to this server · 4
  • 13Fake assistant turns
    fake-assistant-turn
    Checks prompts that pose as the assistant's own words.The server exposes no prompts.not applicable
  • 14Token passthrough
    token-passthrough
    Checks whether the server forwards a user's token to other services.The server opened a session without sign-in, so there is no token flow to check.not applicable
  • 15Token audience
    token-audience-validation
    Checks whether tokens meant for another service are accepted.The server opened a session without sign-in, so there is no token flow to check.not applicable
  • 18Sign-in metadata
    oauth-url-scheme
    Checks the published sign-in metadata for unsafe URLs.No sign-in (OAuth) metadata is published, so there are no sign-in addresses to check.not applicable

Source: our own test, 2026-10-23, mcp-runtime-engine@0.1.0. Which checks count and why follows our published scoring model.

What happened during the test?

Feature #8

The steps in order, as the test record holds them.

  1. 0 msStarted a read-only session with the server's remote endpoint
  2. 834 msConnected after 0 redirects. No credential was sent or needed.
  3. Read the inventory: 22 tools, 0 resources, 0 prompts.
  4. 2,490 msFinished: 2 checks exercised.

Reference

How is it classified?

18 fields

One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.

TopicAI-classified
AI-classified · 2026-10-23
Pricing modelAI-classified
usage-based
read from x402.n9t2.com/ · 2026-10-23

“Transfer size N9T2 fee Up to $1,000, self-serve 1.45 XRP flat $1,000 to $25,000 0.50% $25,000 to $100,000 0.35% Above $100,000 0.25%, negotiable”

Programming language
does not apply
no existing GitHub repository (server declares no repository link, so there is nothing to fetch)
Hosting type
registry · 2026-10-23
MCP capability
experimental, prompts, resources, tools
our test · 2026-10-23
Transport
streamable HTTP
registry · 2026-10-23
Required credentials
none declared
registry · no declaration is not a guarantee
Package registry
does not apply
remote-only server: no package is shipped, so there is no package registry
Freshness
0–30 days
registry updatedAt · 2026-10-23
Lifecycle status
registry · 2026-10-23
License class
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Integrity hash
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Signature / provenance
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Dependency advisories
does not apply
ships no package, so there are no dependencies to audit
Popularity
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Publisher signals
not stated
no readable GitHub owner to describe
Maintenance
does not apply
server declares no repository link, so there is nothing to fetch
Environment
the publisher's infrastructure
where it runs, from the hosting type

“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.

Cite or correct this page

Sources and corrections

Suggested citation

ProtocolProbe. “com.n9t2/xrpl-agent-gateway: MCP server record.” Data checked 2026-10-23. https://protocolprobe.com/mcp/servers/com.n9t2/xrpl-agent-gateway

Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.

As JSON: this record in the API · API documentation.

Badge for your README

ProtocolProbe: 1 of 2 record checks met

[![ProtocolProbe](https://protocolprobe.com/api/v1/badge/com.n9t2/xrpl-agent-gateway)](https://protocolprobe.com/mcp/servers/com.n9t2/xrpl-agent-gateway)

It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.

Something wrong, or is this yours?

If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here.

Write to hello@protocolprobe.com · corrections log · methodology