mcp-chipradar
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CHIPRADAR_API_KEY | No | API key for live ChipRadar B2B data. Optional; without it the server runs in demo mode with public sample data. | |
| CHIPRADAR_API_BASE | No | Optional base URL for the ChipRadar API, e.g. https://chipradar.io/api/v1. |
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 |
|---|---|
| get_boardsC | List tracked boards with specs and current best vendor price. |
| get_board_historyC | Get historical vendor price points for a board (ASIN). |
| get_dealsC | Get current deals sorted by deal score. |
| get_restock_alertsC | Get aggregated public restock signals. |
| get_best_inference_providerC | Recommend the best cloud inference provider for a model. |
| calculate_cloud_vs_local_breakevenC | Compare cloud inference cost vs buying and running a local board. |
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 6 tools
The six tools have mostly distinct purposes: board listing, board history, deals, restock alerts, inference provider recommendation, and cloud-vs-local breakeven. The only mild overlap is between get_boards and get_deals, since both surface current pricing, but their descriptions distinguish them adequately.
Five tools follow a clear get_* snake_case retrieval pattern, and all names are readable. The lone calculate_cloud_vs_local_breakeven uses a different verb style, but the deviation is minor and semantically appropriate.
Six tools is a well-scoped set for a chip price and inference-economics radar. Each tool covers a distinct query type without obvious redundancy.
The surface covers board discovery, price history, deals, restock signals, and inference cost comparison well. Minor gaps remain around managing the tracked-board watchlist or fetching a single current board snapshot, but agents can work around these using get_boards and get_board_history.