keel-mcp
Related Servers
Alternatives to keel-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.6538 npmMIT
- AlicenseBqualityBmaintenanceExposes 17 read-only tools from six XRPL-Utilities services so AI agents can access XRPL wallet analysis, signal feeds, macro telemetry, permissioned asset stacks, RWA tracking, and ETF flow data.412,340 npmMIT
- AlicenseAqualityDmaintenanceRead-only XRPL token and wallet checks with issuer-aware explanations, impersonation checks and spoken summaries. Built for Zach Riehn's XRP Ledger Trading Lab by AI coding agents under Zach's direction. Never signs or sends transactions; findings describe observed ledger evidence, not a guarantee of safety or investment advice. Try it: https://cocoeatsai.com/trading-lab/token-guard/3MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to check DeFi liquidation risk levels for lending protocols like Aave, Compound, and Morpho, including at-risk positions, liquidation prices, current prices, and aggregate exposure. Access is pay-per-call via x402 micropayments with USDC on Base, requiring no API key or signup.MIT
- FlicenseNot gradedqualityDmaintenanceEnables AI agents to access real-time crypto risk intelligence with two tools: Flare for precursor detection and Core for overall risk environment assessment.4-
- AlicenseAqualityDmaintenanceProvides DeFi vault risk analytics for AI agents to search, compare, and perform due diligence on over 700 vaults across major protocols like Morpho and Aave. It enables natural language analysis of risk scores, platform security, and portfolio-level risk assessments.95MIT
TDQS
Scored across 9 tools
Each tool targets a distinct query: engine status, asset inventory, code resolution, per-asset risk, collateral comparison, trade depth, history, comparison, and methodology. The only mild overlap is between get_asset_risk (full reading including depth rungs) and estimate_trade_depth (bracket for a given size), but their stated purposes differ enough to guide selection.
Nearly all names follow a verb_noun pattern (list_assets, find_asset, get_asset_risk, check_collateral_size, estimate_trade_depth, get_risk_history, compare_assets, get_methodology). The lone exception is keel_status, which uses a server-name prefix instead of a verb, a minor deviation.
Nine tools is well-scoped for a read-only risk analytics server, with each tool covering a distinct query type (inventory, detail, history, comparison, methodology). No redundant or filler tools.
The surface covers the full read lifecycle for the domain: health, asset discovery, resolution, risk readings, historical reconstruction, comparison, collateral sizing, depth estimation, and methodology. There is no alert/watchlist or portfolio-level monitoring capability, but for a query-oriented analytics server the coverage is strong.