A
licenseA
qualityC
maintenanceProvides 14 read-only tools to query USDD stablecoin protocol data across TRON, Ethereum, and BSC, enabling AI agents to fetch supply, APY, collateral, and vault configurations.
14
7 npm
1
MIT
mcp-server-usdd
OfficialRelated Servers
Alternatives to mcp-server-usdd
No user-submitted related servers found.
Related Servers
mcp-server-tronlinkofficial
AlicenseNot gradedqualityDmaintenanceEnables AI agents to interact with the TRON blockchain through browser automation (Playwright) or direct API calls, supporting transfers, staking, swaps, and multi-signature management.12 npm11MIT
onchainos MCP Serverofficial
FlicenseNot gradedqualityBmaintenanceEnables on-chain operations including token search, market data, wallet management, swap execution, and DApp interactions across 20+ blockchains.331-- FlicenseNot gradedqualityDmaintenanceEnables blockchain transactions on BSC including balance checks, transfers, token swaps, and reward claims.3-
- AlicenseNot gradedqualityDmaintenanceEnables interaction with XRP Ledger blockchain for managing wallets, creating and trading tokens, minting and managing NFTs, and executing DEX trades through 15+ comprehensive tools.11 npm2MIT
- AlicenseBqualityDmaintenanceEnables users to manage the SpherePay payment platform, including customer onboarding, bank and wallet management, and cross-chain transfers. It provides tools for executing financial workflows, tracking transfers, and configuring virtual accounts for fiat-to-stablecoin conversions.24AGPL 3.0
TDQS
B3.1/5.0
Scored across 44 tools
Disambiguation2/5
Most write/management tools are distinct, but the read-only side has several clusters with fuzzy boundaries: get_protocol_overview duplicates much of get_supported_ilks/get_psm_status, get_chain_metrics vs get_protocol_metrics are hard to distinguish, and the Smart Allocator tools (overview, proof_of_reserve, debt_overview, assets_breakdown) overlap heavily. Wallet status is also split across get_wallet_mode, get_wallet_address, and list_wallets, so misselection is plausible.
Naming Consistency4/5
Names are consistently snake_case and almost always begin with a verb such as get, set, list, import, check, prepare, confirm, approve, open, mint, repay, withdraw, or close. A few compound names like deposit_and_mint and psm_swap_to_usdd are minor deviations, but the overall convention is predictable.
Tool Count2/5
At 44 tools, the surface exceeds the comfortable range for a single MCP server. Even though the domain spans wallets, vaults, PSM, savings, and analytics, many tools are read-only report variants that add bulk and could be consolidated.
Completeness4/5
The vault lifecycle is covered end-to-end with open, mint, repay, withdraw, and close, and PSM swaps, savings, approvals, transfers, and wallet management are all represented. No obvious dead-end prevents core operations, though a few reporting endpoints feel redundant and there is no transaction-status/receipt tool, so minor gaps exist.
Maintenance
ActivityInactive
ResponsivenessNo issues