@xrpl-utilities/mcp
Related Servers
Alternatives to @xrpl-utilities/mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables crypto research and market intelligence through 66 read-only tools covering sentiment, whale tracking, on-chain flows, influencer accuracy, and screening across 2,300+ coins, allowing AI agents and traders to verify hype, accumulation, and momentum without an API key.MIT
- FlicenseAqualityCmaintenanceConnects AI agents to Real World Asset (RWA) data, enabling queries about tokenized assets, market trends, TVL analytics, token holders, and portfolio tracking across multiple blockchains.181-
- FlicenseNot gradedqualityBmaintenanceEnables AI agents to access 48 real-time crypto data tools including prices, DeFi, meme tokens, gas, sentiment, Solana, and agent commerce, with post-paid billing via Solana USDC.-
- AlicenseAqualityAmaintenanceEnables AI agents to access 37 read-only market-research tools for querying quotes, news, SEC filings, financial statements, ownership and insider activity, earnings, corporate calendars, options, and crypto data.4912AGPL 3.0
- AlicenseCqualityDmaintenanceEnables AI systems to interact with the XRP Ledger Testnet, supporting XRP payments, token operations, NFTs, escrow, DEX trading, and more.51MIT
- AlicenseNot gradedqualityAmaintenanceRead-only Polymarket data tools for AI agents: wallet profiles, fee-inclusive PnL cross-checks, Brier-score calibration, leaderboards, market scans and more (10 tools). No API keys, no order placement — data only. English + Chinese docs.3 npm198MIT
TDQS
Scored across 41 tools
Tools are grouped by clear domain prefixes (pulse, trust, vault, sentinel, telemetry, flows, desk) which helps distinguish purposes. Some overlap exists within pulse analytics (e.g., exchange_flow_delta vs exchange_net_flow vs entity_positioning) and between ripple_topology and cex_attribution, but descriptions are specific enough to guide selection.
The pattern is mostly xrpl_<domain>_<descriptor>, but the descriptor varies between noun phrases (e.g., recent_events, network_stats) and verb-led names (list_domains, get_domain, scan). 'scan' appears in three different domains with different meanings (vault_scan, sentinel_scan, flows_scan). While the domain prefix provides predictability, the mixed style prevents a higher score.
41 tools is a heavy load for a single server, exceeding the typical comfortable range. Even with domain organization, the sheer number increases cognitive load and reduces discoverability. Splitting into separate servers per domain (pulse, trust, flows, etc.) would improve scoping.
The server provides broad coverage across XRPL analytics: market events, whale activity, trust domains, RWA vaults, wallet classification, ETF flows, settlement volumes, and macro telemetry. Paid tool flows are properly chained (get_quote → get_status → get_results). Minor gaps include no direct account balance/transaction query and no generic token metadata tool beyond token_health, but these do not significantly hinder the stated utility.