@xrpl-utilities/mcp
Related Servers
Alternatives to @xrpl-utilities/mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceEnables AI assistants to query read-only Stellar analytics over MCP: network status and fees, asset data with look-alike warnings, SDEX order books, account balances with spendable XLM, and DeFi TVL. It requires no API keys and refuses secret keys, answering from public APIs like Horizon, StellarExpert and DefiLlama.670 npmMIT
- AlicenseNot gradedqualityAmaintenanceExposes 250+ financial data tools to AI assistants, enabling access and analysis of stocks, company fundamentals, ETFs, crypto, forex, commodities, economic indicators, and market insights.624 npmApache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to query liquidation radar for seven tokens, inspect recorded BTC/ETH order book depth with wall history and aggressor flow, and request Li.Fi cross-chain swap routes that agents sign themselves.MIT
- AlicenseNot gradedqualityAmaintenanceExposes 250+ financial data tools to AI assistants, enabling access and analysis of stocks, company fundamentals, ETFs, crypto, forex, commodities, economics, and market insights.624 npmApache 2.0
- 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
- AlicenseAqualityCmaintenanceEnables AI agents to query Keel's Stellar liquidity risk engine for executable order-book and AMM depth, maximum safe collateral sizes, asset risk bands, flags, and historical readings, with ledger and methodology provenance on every answer. All tools are read-only, so agents can assess collateral and trade depth without signing or submitting transactions.99 npmMIT
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.