chainlink-feeds-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| getLatestPriceB | Fetches the latest price for a given pair on a specified chain |
| queryPriceByRoundC | Queries the price for a given pair and round ID on a specified chain (placeholder due to historical data limitations) |
| listSupportedChainsB | Returns a comma-separated list of all supported blockchain networks |
| listSupportedFeedsByChainB | Returns a comma-separated list of price feed names for a specified blockchain network |
| listSupportedFeedsA | Returns a Markdown list of all supported chains and their price feed names |
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 5 tools
Each tool has a clearly distinct purpose with no ambiguity. getLatestPrice fetches current prices, listSupportedChains lists networks, listSupportedFeeds provides detailed feed information, listSupportedFeedsByChain filters feeds by chain, and queryPriceByRound handles historical queries. The descriptions clearly differentiate their scopes and use cases.
The naming is mostly consistent with a clear verb_noun pattern (e.g., getLatestPrice, listSupportedChains), but there is a minor deviation with queryPriceByRound which uses 'query' instead of 'get' or 'list'. This slight inconsistency does not significantly hinder readability or predictability.
With 5 tools, the count is well-scoped for a Chainlink price feeds server. Each tool earns its place by covering essential operations like fetching prices, listing supported chains and feeds, and querying historical data, without being overly sparse or bloated.
The tool set provides strong coverage for the domain of Chainlink price feeds, including current and historical price queries, and listing supported networks and feeds. A minor gap exists in the placeholder note for queryPriceByRound due to historical data limitations, but core workflows are well-covered without significant dead ends.