crypto_market_html_mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| COINGECKO_DEMO_API_KEY | No | Demo API key for CoinGecko when needed |
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
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| fetch_market_snapshotB | Fetch USD prices, market caps, 24h volumes/changes and global market totals; or explicit demo data. |
| build_crypto_market_htmlC | Design standalone interactive HTML with paragraph-linked insights, article dialogs, market filters and dominance scenarios. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| market_html_brief | Prepare the market and news composition workflow. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| demo_market_snapshot | Read the explicitly fictional market snapshot used in offline tests. |
TDQS
Scored across 2 tools
The two tools have completely distinct purposes: one fetches market data, the other builds HTML from it. There is no ambiguity or overlap between fetching and rendering.
Both tool names follow a consistent verb_noun snake_case pattern (fetch_market_snapshot, build_crypto_market_html), making the naming predictable and readable.
With only 2 tools, the server is on the thin side, but the tools cover the core pipeline of fetching data and generating HTML. The count is borderline for the scope, not excessive.
The domain is narrowly focused on generating crypto market HTML. The two tools provide a complete workflow from data retrieval to final output. Minor gaps like data refresh scheduling or multiple template variants exist, but agents can work around them.