MCP servers observed by Lowdown
io.github.XRPL-Utilities/mcp MCP server: daily status and tool changes
Answered initialize and tools/list on all 3 checks recorded in the last 30 days (2026-11-10 to 2026-11-16) (Lowdown checks this server every 3 days); 64 tools listed. MCP Registry declaration recorded; observed every 3 days by Lowdown Scanner since 2026-11-10; no tool definition change in 2 compared days; 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.XRPL-Utilities/mcp
Before installing or connecting: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:io.github.XRPL-Utilities/mcp?menu=install-check · other questions: menu
Does it respond?
Latest daily check: 2026-11-16: 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?
No change in tool schemas, descriptions or names across 2 compared days.
What tools does it list?
64 tools on 2026-11-16:
xrpl_desk_briefingxrpl_flows_correlationxrpl_flows_cross_border_flowxrpl_flows_etf_candidatesxrpl_flows_etf_flow_summaryxrpl_flows_launch_impactxrpl_flows_scanxrpl_fund_flow_reportxrpl_ledger_schemaxrpl_ledger_statementxrpl_network_snapshotxrpl_permissioned_venue_reportxrpl_pulse_cex_attributionxrpl_pulse_entity_positioningxrpl_pulse_escrow_calendarxrpl_pulse_events_by_addressxrpl_pulse_exchange_flow_deltaxrpl_pulse_exchange_net_flowxrpl_pulse_moex_xrp_indexxrpl_pulse_network_statsxrpl_pulse_recent_choreographiesxrpl_pulse_recent_eventsxrpl_pulse_ripple_counterpartiesxrpl_pulse_ripple_counterparty_graphxrpl_pulse_ripple_topologyxrpl_pulse_rlusd_distributionxrpl_pulse_rwa_summaryxrpl_pulse_rwa_supply_historyxrpl_pulse_stream_purchasexrpl_pulse_token_healthxrpl_pulse_top_destinationsxrpl_pulse_whale_censusxrpl_pulse_whale_flow_24hxrpl_pulse_whale_flow_historyxrpl_pulse_xls85_totalsxrpl_pulse_xrpl_primitivesxrpl_rwa_token_reportxrpl_sentinel_scanxrpl_sentinel_scan_historyxrpl_sentinel_verify_originxrpl_telemetry_dex_pair_volumexrpl_telemetry_exchange_flow_historyxrpl_telemetry_get_quotexrpl_telemetry_get_resultsxrpl_telemetry_get_statusxrpl_telemetry_liquidityxrpl_telemetry_settlement_seriesxrpl_telemetry_settlement_totalsxrpl_telemetry_snapshotxrpl_trust_credential_issuersxrpl_trust_get_domainxrpl_trust_jurisdictionsxrpl_trust_list_domainsxrpl_trust_list_operators_indexxrpl_trust_operator_attributionxrpl_trust_operator_drilldownxrpl_trust_permissioned_activityxrpl_trust_recent_eventsxrpl_trust_usage_summaryxrpl_vault_daily_flowxrpl_vault_daily_flow_historyxrpl_vault_scanxrpl_wallet_checkxrpl_xrp_market_briefing
MCP Registry declaration
- Registry name:
io.github.XRPL-Utilities/mcp - Declared version: 0.2.244
- Status: active
- Declared hosts:
mcp.xrpl-utilities.io
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.XRPL-Utilities/mcp", "menu": "install-check"}. The same record without MCP: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:io.github.XRPL-Utilities/mcp?menu=install-check
When running its declared package, wrap it with the stdio proxy. Since lowdown-proxy 0.1.22 the proxy adds this record (install-check) to the server's initialize response; it changes no tool result and blocks nothing:
npx -y lowdown-proxy --target mcp:io.github.XRPL-Utilities/mcp -- npx -y @xrpl-utilities/mcp
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).