Maker - 10 tools for lending rates, supply, and borrow data
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 3.2/5 across 10 of 10 tools scored. Lowest: 2.6/5.
Each tool has a clearly distinct purpose with no ambiguity. The tools map directly to specific smart contract functions (e.g., cage, dai, deny, exit, join, live, rely, vat, wards) and one event (LogNote), each performing unique operations like read-only calls, write functions, or event logging. There is no overlap in functionality.
Tool names follow a highly consistent pattern, using lowercase verbs or function names that match the smart contract interface (e.g., cage, dai, deny, exit, join, live, rely, vat, wards). The naming is uniform throughout, with no mixing of conventions or styles, making it predictable and easy to understand.
The tool count of 10 is well-scoped and appropriate for interacting with a smart contract, covering essential read and write operations, access control functions, and event handling. Each tool earns its place by providing necessary functionality without redundancy or bloat.
The tool set offers complete coverage for interacting with the smart contract domain, including read-only functions (dai, live, vat, wards), write functions with access control (cage, deny, exit, join, rely), and event logging (LogNote). There are no obvious gaps, and the surface supports full lifecycle operations for contract management.
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!