Complete financial infrastructure for AI agents — payments, lending, escrow & more.
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Average 2.7/5 across 38 of 42 tools scored. Lowest: 1.3/5.
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.
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
No comments yet. Be the first to start the discussion!
