Mantle Yield MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MANTLE_YIELD_API_TOKEN | No | Optional bearer token | |
| MANTLE_YIELD_API_BASE_URL | No | Override backend API base URL | https://mantle-yield.asterworks.cc |
| MANTLE_YIELD_API_TIMEOUT_MS | No | HTTP timeout in milliseconds | 10000 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| mantle_get_healthA | Get the technical health status of the Mantle Yield backend service. Calls GET /api/health. Returns status, lastSync, sourcesRefreshed, failedSources. Note: some fields described in the spec (syncedAt, nextRefresh, source, itemCount, fileExists, snapshotPath) are not yet present in the backend response. |
| mantle_get_summaryA | Get the Mantle Yield dashboard summary. Calls GET /api/summary. Returns opportunitiesTracked, protocols, assetsIndexed, lastSync, status. |
| mantle_list_opportunitiesA | List yield opportunities from the Mantle Yield backend. Calls GET /api/opportunities. Supports filtering, sorting and pagination. |
| mantle_get_opportunityA | Get full details for a single yield opportunity by its ID. Calls GET /api/opportunities/:id. |
| mantle_get_opportunity_chartA | Get historical chart data (APY / TVL over time) for a yield opportunity. Calls GET /api/opportunities/:id/chart. NOTE: This backend endpoint is not yet implemented and will return a backend_gap status. |
| mantle_compare_opportunitiesA | Compare 2 or 3 yield opportunities side by side. Fetches each opportunity via GET /api/opportunities/:id and returns a unified comparison structure. |
| mantle_refresh_dataA | Trigger a manual data refresh on the backend. Calls POST /api/refresh. NOTE: This backend endpoint is not yet implemented and will return a backend_gap status. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
Each tool serves a clearly distinct purpose: health checks, dashboard summary, individual opportunity details, historical charts, listing with filters, comparison, and manual refresh. There is no overlap or ambiguity between tool boundaries.
All tool names follow the same 'mantle_verb_noun' pattern with snake_case throughout. The consistent use of get/list/compare/refresh clearly communicates the action and object for each tool.
With 7 tools, the server is well-scoped for a yield data platform. Each tool covers a distinct aspect of the domain without redundancy or bloat, fitting the ideal 3-15 tool range.
The tool set covers the full read-only lifecycle of yield opportunities: listing, retrieving details, historical charts, comparison, and summary/health status. The included refresh action adds operational coverage, leaving no obvious gaps for the stated purpose.