mcp-server-usdd
OfficialRelated Servers
Alternatives to mcp-server-usdd
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceProvides 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.1434 npm1MIT

mcp-server-tronlinkofficial
AlicenseNot gradedqualityCmaintenanceEnables AI agents to interact with the TRON blockchain through browser automation (Playwright) or direct API calls, supporting transfers, staking, swaps, and multi-signature management.24 npm16MIT
onchainos MCP Serverofficial
AlicenseNot gradedqualityBmaintenanceEnables on-chain operations including token search, market data, wallet management, swap execution, and DApp interactions across 20+ blockchains.346MIT- FlicenseNot gradedqualityDmaintenanceEnables blockchain transactions on BSC including balance checks, transfers, token swaps, and reward claims.3-
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to query TRON account, token, block, contract, staking, and governance data and to build unsigned transactions, with optional keystore-backed signing and broadcasting in local mode.4LGPL 3.0
- AlicenseNot gradedqualityCmaintenanceEnables token creation, vesting schedule management, DEX liquidity provisioning, regulatory compliance checks, and status tracking across multiple blockchains.MIT
TDQS
Scored across 44 tools
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.
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.
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.
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.