MCP servers observed by Lowdown
io.github.xrplto/xrpl-to MCP server: daily status and tool changes
Answered initialize and tools/list on all 3 checks recorded in the last 30 days (2026-11-11 to 2026-11-17) (Lowdown checks this server every 3 days); 89 tools listed. MCP Registry declaration recorded; observed every 3 days by Lowdown Scanner since 2026-11-11; tool definitions last changed on 2026-11-17 after 6 days without change; no agent-reported interactions.
Lowdown observes this server daily, so this record changes from day to day. A copy older than 1 day may be outdated. Current record (JSON): GET https://lowdown-proxy.vercel.app/api/reputation/mcp:io.github.xrplto/xrpl-to
Before installing or connecting: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:io.github.xrplto/xrpl-to?menu=install-check · other questions: menu
Does it respond?
Latest daily check: 2026-11-17: the server answered initialize and tools/list.
- Observed days in the last 30: 3
- Answered initialize and tools/list: 3
- Required authentication: 0
- No response: 0
- Remotes differed: 0
Does it require authentication?
It did not return HTTP 401/403 on any of the 3 observed days. Lowdown checks without credentials.
Did its tools change recently?
Tool definitions changed on 1 of 2 compared days.
- 2026-11-17: input or output schemas changed, descriptions changed
What tools does it list?
89 tools on 2026-11-17:
analyze_token_riskapi_getcancel_jobcheck_domaincheck_scamdecode_xrpldelete_notedescribe_bot_activityexplain_result_codefind_arb_pairsfind_sandwich_attacksfind_snipersfind_walletsfund_testnet_accountget_account_ancestryget_account_infoget_account_nftsget_account_objectsget_account_transactionsget_account_trustlinesget_amm_poolsget_api_docsget_cex_cashoutsget_creator_activityget_crypto_marketget_escrowsget_exit_liquidityget_fear_greed_indexget_frozen_linesget_funding_ratesget_global_statsget_holder_clustersget_holder_cohortsget_holder_graphget_holder_overlapget_holdersget_issuer_actionsget_jobget_liquidationsget_lp_positionsget_macro_indicatorsget_network_activityget_new_launchesget_newsget_nft_activityget_nft_collectionget_nft_offersget_offrampget_ohlcget_oracle_pricesget_orderbookget_payment_flowsget_prediction_marketsget_protocol_rulesget_related_projectsget_social_mentionsget_swap_quoteget_testnetget_tokenget_token_analyticsget_token_flowget_token_pairsget_tokens_by_categoryget_top_moversget_top_tradersget_trade_briefget_trader_rotationsget_tradesget_transactionget_trending_tokensget_validatorsget_wallet_pnlget_wallet_riskget_wash_tradingget_whale_activityget_xrp_distributionidentify_token_operatoridentify_wallet_ownerpick_giveaway_winnersrecall_notesrun_scriptsave_notescan_tweet_addressessearch_forum_postssearch_rippled_sourcesearch_tokenssearch_xsearch_xrpl_docsxrpl_command
MCP Registry declaration
- Registry name:
io.github.xrplto/xrpl-to - Declared version: 1.20.0
- Status: active
- Declared hosts:
api.xrpl.to
Before installing: how to check
From an agent: add the remote MCP server https://lowdown-proxy.vercel.app/mcp (streamable HTTP, no authentication) and call get_lowdown with {"target": "mcp:io.github.xrplto/xrpl-to", "menu": "install-check"}. The same record without MCP: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:io.github.xrplto/xrpl-to?menu=install-check
The same facts in machine-readable form are in this page's <script type="application/json" id="lowdown-evidence"> block (schema lowdown.evidence-snapshot v1).