Chip Intel MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | HTTP port for the Streamable HTTP server (default 3000). | 3000 |
| SEC_USER_AGENT | Yes | The SEC requires a "Name email" User-Agent and blocks requests that don't send one. Set this in production; the fallback ChipIntelMCP chip-intel-mcp@example.com is a placeholder only. |
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_chipsA | List the GPUs/AI accelerators in the curated, source-cited spec dataset (NVIDIA, AMD, Google TPU, AWS Trainium), optionally filtered by vendor. |
| chip_specsA | Spec sheet for one accelerator, where every figure has its official source URL and the exact quote from that page. Accepts an id or common name (e.g. H100, MI300X, TPU v6e). IDs: nvidia-h100-sxm, nvidia-h200-sxm, nvidia-a100-80gb-sxm, nvidia-dgx-b200, amd-mi300x, amd-mi325x, amd-mi355x, google-tpu-v5p, google-tpu-v6e, aws-trainium3. |
| compare_chipsA | Compare 2–6 accelerators side by side on memory, bandwidth, FP8/BF16/FP4 throughput (dense vs sparse kept apart), power and process. Each cell is cited; unpublished values show as —. |
| process_node_mapB | Map of leading-edge logic process nodes at TSMC, Samsung and Intel Foundry (transistor type, production status), plus which dataset chips state their process. Every entry cites the foundry's own page. |
| export_control_lookupA | Screen a company or person name against the US government's Consolidated Screening List (trade.gov; includes the BIS Entity List, Military End User list, Denied Persons, Unverified List and Treasury/State lists). Optional list and country filters. Returns license requirement/policy and Federal Register citation. Screening aid only, not legal advice. |
| chip_newsA | Recent chip/semiconductor headlines from publisher RSS feeds (Tom's Hardware, The Register, SemiWiki, ServeTheHome, EE Times). Optional keyword filter (all words must appear in the title), e.g. 'nvidia', 'tsmc 2nm', 'export'. Links go to the publisher. |
| chip_company_filingsA | Recent SEC EDGAR filings (10-K, 10-Q, 8-K, 20-F, 6-K…) and annual reported revenue for chip companies: NVDA, AMD, INTC, TSM, AVGO, MU, QCOM, ASML, ARM, SMCI. Stock prices are not included (no free official source). |
| chip_briefingA | One-shot briefing on a chip company: latest SEC filings, annual revenue trend and recent headlines mentioning it. Every item cited. |
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 8 tools
Most tools target clearly distinct resources: list_chips (enumeration), chip_specs (single detail), compare_chips (side-by-side), process_node_map, export_control_lookup, chip_news, and chip_company_filings are all separable. The main overlap is chip_briefing, which is a composite of chip_company_filings + chip_news and could be confused with them, but the 'one-shot briefing' framing distinguishes it.
The set mixes verb-first action names (list_chips, compare_chips, export_control_lookup) with noun-first resource names (chip_specs, chip_news, chip_company_filings, chip_briefing, process_node_map). The 'chip_' prefix gives some cohesion but there is no predictable verb_noun pattern throughout.
Eight tools is well-scoped for a chip intelligence domain, with each tool earning its place across listing, specs, comparison, process nodes, export screening, news, filings, and a briefing aggregator. No redundant or filler tools.
The surface covers the lifecycle well: discovery (list_chips), detail (chip_specs), comparison, adjacent context (process nodes, export control, news, filings), and an aggregation tool. Minor gaps like spec-based search/filtering or a broader company list beyond the ten hardcoded tickers exist but are workable.