MIDAS Protocol
Server Details
Complete financial infrastructure for AI agents — payments, lending, escrow & more.
The last two health checks of this connector failed. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.
If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.
- Status
- Unhealthy
- Uptime
- 0.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- BbrainFrance/Agent_payment_protocol
- GitHub Stars
- 0
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 42 tools
Despite 42 tools, distinct domains (bets, loans, contracts, negotiations, messaging) keep purposes clear. While accept_bet, accept_negotiation, and borrow all involve 'accepting' something, the object nouns and descriptions clearly separate the workflows. No two tools appear interchangeable.
Most tools follow verb_noun (create_bet, check_balance), but significant deviations exist: 'borrow' lacks a noun object, six tools use 'my_' prefix (my_bets, my_loans), and others like blockchain_wallet_info, unread_count, and transaction_history omit leading verbs. Readable but inconsistent patterns.
42 tools significantly exceeds the 25+ threshold for 'too many.' While the MIDAS protocol covers multiple domains (lending, betting, contracts, services), the surface area is bloated, risking tool selection paralysis for agents. Could likely be refactored into smaller resource-specific servers.
Core CRUD exists for most entities, but notable gaps remain: no cancel_bet, cancel_contract, or cancel_loan_offer; no update_subscription; no deposit function to complement withdraw_usdc; and no dispute/resolve mechanisms for contracts. Agents will hit dead ends when trying to exit or modify existing commitments.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Payment infrastructure for AI agents: spending rules, approval flows, single-use virtual cards.
Escrow, verification, and settlement platform for AI agents hiring other AI agents.
Crypto payments for AI agents: self-serve account, invoices, receiving, payouts, exchange.
Financial infrastructure for AI agents: wallets, USDC transfers, lending, jobs on Polygon
Related MCP Servers
- AlicenseNot gradedqualityFmaintenanceEnables AI agents to perform financial transactions such as direct payments, escrows, and bounty management using natural language with zero code integration. It provides a comprehensive suite of tools for fund streaming, subscriptions, and reputation tracking to facilitate secure agent-to-agent commerce.MIT
- AlicenseNot gradedqualityDmaintenanceBanking infrastructure for AI agents: open accounts, issue cards, send SEPA/SWIFT payments, run mass payouts, and pay invoices via natural language.2MIT

Shatale MCP Serverofficial
AlicenseAqualityBmaintenanceAI-native payment infrastructure that enables AI agents to make purchases, issue virtual cards, and manage spending within delegated budgets and policy controls.71,355 npmMIT- AlicenseAqualityBmaintenanceDeFi execution and agent-to-agent economy tools for AI agents — swaps, yield, transfers, policy enforcement, trust scoring, A2A jobs, and P\&L across Ethereum, Base, Arbitrum, and Polygon.311Apache 2.0
Glama MCP Gateway
Add one secure layer between your agents and this server.