A
licenseNot graded
qualityC
maintenanceEnables agents to spend funds on Visa/MasterCard prepaid cards, travel eSIMs, and gift cards, with paid KYT address screening and USDT TRC-20 funding.
MIT
IMBA Wallet Agentic MCP
Officialby IMBAwallet
Related Servers
Alternatives to IMBA Wallet Agentic MCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceEnables AI agents to spend with the user's own key by paying via USDT TRC-20 and buying Visa/Mastercard prepaid cards, travel eSIMs, and gift cards, and also provides access to policy and how-to documentation.6MIT
ASG Cardofficial
AlicenseNot gradedqualityFmaintenanceVirtual MasterCards for AI agents. Issue and manage cards via MCP.15MIT- AlicenseNot gradedqualityCmaintenanceMCP server for AgentPay — the payment gateway for autonomous AI agents. Fund a wallet once, give your agent the key, and it discovers, provisions, and pays for tool APIs on its own. One key, every tool.112 npm1MIT
- AlicenseAqualityCmaintenanceEnables AI agents to autonomously buy and operate mobile proxies via MCP, supporting both API key and on-chain USDC payments for tasks like port creation, IP rotation, and traffic management.4429 npmMIT
Agentware MCPofficial
AlicenseNot gradedqualityCmaintenanceEnables MCP clients to browse and purchase agent packages and pay per call for model inference on Robinhood Chain using USDG, with no account or API key required.MIT
TDQS
B3.2/5.0
Scored across 6 tools
Disambiguation3/5
Several tools, such as get_agent_facts, get_agent_use_cases, get_tier_policy, and get_catalog_placement, cover overlapping reference material around policy, tiers, and catalog placement. get_public_url and list_docs_urls are related but distinguishable, yet agents may still struggle to choose the right knowledge tool for a given request.
Naming Consistency4/5
Tool names consistently use snake_case with a get_ prefix, making the pattern predictable and readable. The only deviation is list_docs_urls, which uses list_ instead of get_, but this is still a minor and conventional variation.
Tool Count4/5
Six tools is a reasonable size for a read-only reference/docs MCP and fits comfortably within a well-scoped set. However, a few tools have overlapping purposes, so the count is slightly higher than strictly necessary.
Completeness4/5
The tool surface covers facts, use cases, tier policy, catalog placement, URL listing, and remote fetching, which forms a nearly complete docs-only workflow. Wallet operations are explicitly out of scope, so the lack of money-moving tools is not a gap for this server's stated purpose.
Maintenance
ActivityMaintained
ResponsivenessNo issues