usdt-agent-skills-lite
Related Servers
Alternatives to usdt-agent-skills-lite
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceMCP server for agent-to-agent payments on the XRP Ledger — job marketplace, crypto-condition escrow, AI-verified work delivery, trust scoring, and wallet bootstrap from Coinbase.244MIT
- AlicenseAqualityDmaintenanceKeyless crypto payments for AI agents. One MCP call turns any wallet address into a non-custodial crypto payment link or tip jar, no API key and no account, with funds settling straight to your wallet at a 0% platform fee (USDC/USDT, BTC, LTC, DASH, DOGE, ZCASH).337 npmMIT
- AlicenseNot gradedqualityDmaintenanceNon-custodial payment engine for AI agents supporting BTC, ETH, USDT, USDC, XRP, XMR, and ZEC. Exposes wallet, invoice, and payment tools over MCP with per-agent spend limits, plus x402 pay-per-call support.47 npmBusiness Source 1.1
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to manage Bitcoin micropayments, service offers, and escrow contracts through MCP tools, without requiring a Lightning node.8 npmMIT
- AlicenseNot gradedqualityBmaintenanceDrop-in x402 payment middleware for MCP servers. Charge AI agents per tool call using USDC on Base chain — Python and JavaScript SDKs, no payment processor, no KYC.MIT
- AlicenseNot gradedqualityCmaintenanceMCP server enabling AI agents to browse, claim, track, and submit work on the Taskmarket decentralized task marketplace with USDC rewards.MIT
TDQS
Scored across 2 tools
check_usdt_payment verifies transfer amounts, while validate_address performs format validation—two clearly distinct purposes with no overlap. An agent can easily select the right tool based on the task.
Both tools follow a consistent verb_noun snake_case pattern (check_usdt_payment, validate_address). The naming is predictable and readable.
Two tools is thin for a server that covers USDT payments across multiple chains. While the 'lite' label suggests minimalism, the count feels borderline under-scoped for the domain.
The surface covers payment verification and address validation but lacks operations like fetching transaction details, generating payment requests, or listing supported tokens. These gaps may force agents to work around missing functionality.