# Silicon Analysts (remote · siliconanalysts.com)

Dated, sourced semiconductor data: chip costs, HBM/wafer pricing, fab capacity, policy, forecasts.

- Trust score: 69/100 (medium)
- Change this week: +10
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `siliconanalysts.com`: 69/100 (this document), [markdown](https://verifymcp.io/servers/siliconanalysts-silicon-analysts/api-mcp.md), [page](https://verifymcp.io/servers/siliconanalysts-silicon-analysts/api-mcp)

## Channel facts

- Endpoint: `https://siliconanalysts.com/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.2.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 55/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 7190 tokens (~359/item across 20 items; 20 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 67/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 2% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http siliconanalysts-silicon-analysts https://siliconanalysts.com/api/mcp
```

### Codex

```toml
[mcp_servers.siliconanalysts-silicon-analysts]
url = "https://siliconanalysts.com/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "siliconanalysts-silicon-analysts": {
      "type": "remote",
      "url": "https://siliconanalysts.com/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add siliconanalysts-silicon-analysts --url https://siliconanalysts.com/api/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  siliconanalysts-silicon-analysts:
    url: "https://siliconanalysts.com/api/mcp"
```

### Other

```json
{
  "mcpServers": {
    "siliconanalysts-silicon-analysts": {
      "type": "http",
      "url": "https://siliconanalysts.com/api/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-03 (score 69, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-01 (score 68, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-31 (score 67, +6)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 61, +1)

- [security] Tool “get_market_dataset” rewrote its description, which is the text the model reads

### 2026-07-29 (score 60, +1)

- [security] Tool “get_foundry_economics” rewrote its description, which is the text the model reads
- [functional] New tool “get_market_dataset”

### 2026-07-27 (score 59, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 58)

First indexed and scored.

## MCP tools (20)

### `get_accelerator_costs` (~268 tokens)

Returns 13 specific AI accelerators (H100/H200/B100/B200/GB200, MI300X/MI355X, Gaudi 3, TPU v5p, Trainium 2, Maia 100, MTIA v2) with structured fields: chip, vendor, processNode, dieSizeMm2, memoryType, memoryCapacityGb, memoryBandwidthTbS, fp8TflopsSparse, bf16TflopsDense, packageType, estMfgCostUsd, estSellPriceUsd, chipGrossMarginPct, costBreakdown.{logicDie, hbm, packaging, testAssembly}, interconnect.

USE THIS for: comparing manufacturing cost or sell price across vendors; looking up published specs of a specific shipping accelerator.

DO NOT USE for: chips not yet shipping (use get_market_pulse for forecasts); custom chip cost modeling (use calculate_chip_cost); HBM market dynamics (use get_hbm_market_data).

Filters: vendor (enum), chip (substring match), fields (projection list). Returns empty array if filters match nothing — does not error. Each chip record carries provenance.last_updated; data refreshes monthly.

Input parameters:

- `chip` (string)
- `fields` (string)
- `vendor` (string)

### `calculate_chip_cost` (~516 tokens)

Pure-function chip cost estimator. Given die dimensions (mm), process node, and optional packaging/HBM parameters, returns: estimatedChipCost (USD), dieArea (mm²), grossDiesPerWafer, frontendYield (%), totalYield (%), and a costBreakdown {waferCostPerGoodDie, packagingAndTestCost, hbmCost, marginCost}.

USE THIS for: hypothetical chip cost modeling, sensitivity analysis, fabless tapeout decisions.

DO NOT USE for: published cost of an existing accelerator (use get_accelerator_costs); wafer pricing only (use get_wafer_pricing).

Required: dieWidth, dieHeight (1–33 mm reticle limit). Errors with INVALID_PARAMS if outside bounds. processNode defaults to tsmc-n5; valid nodes via get_wafer_pricing. Estimates are directional ±15–20%.

Optional energy adder: pass energyRegion (texas|ohio|arizona|china|korea|taiwan|germany) to get a conditional `energy` block — regional manufacturing-electricity cost per die (SA estimate; wafer price already embeds foundry energy, so treat it as a scenario delta). energyFacilityOverhead=false drops the ~1.75× facility multiplier.

Optional substrate scenario: pass substrate=panel-310x310 to model CoPoS panel-level assembly — applies the midpoint of Yole's realistic 20–30% panel cost-savings band to the packaging cost ONLY (silicon GDPW unchanged; panels are back-end). Conditional `substrateScenario` block + SA-scenario meta note. TSMC CoPoS: pilot ~June 2026, mass production 2028–29 — a forward-looking scenario, not a quote.

Input parameters:

- `backendYield` (number)
- `defectDensity` (number)
- `dieHeight` (number, required)
- `dieWidth` (number, required)
- `energyFacilityOverhead` (boolean)
- `energyRegion` (string)
- `hbmCost` (number)
- `hbmStacks` (number)
- `kgdTestCoverage` (number)
- `marginTarget` (number)
- `packagingCost` (number)
- `packagingType` (string)
- `processNode` (string)
- `substrate` (string)
- `testCost` (number)
- `volume` (number)
- `waferCost` (number)
- `yieldModel` (string)

### `estimate_lead_time` (~404 tokens)

Heuristic chip manufacturing LEAD TIME estimator (MANUFACTURING CYCLE TIME). Given total mask layers (or a processNode to default them), foundry utilization % (optional — defaults from live foundry-allocation data), and packagingType, returns min/max bands: fabDays, fabWeeks, packagingWeeks, totalWeeks, plus effectiveDpml (days per mask layer), the operating-curve weight, a resolved-inputs echo, assumptions, methodology, and public-source citations.

USE THIS for: "how long to manufacture this chip" — wafer-fab cycle time + packaging assembly/test time for hypothetical chips; cycle-time sensitivity to fab utilization or packaging class (conventional vs flip-chip vs CoWoS).

DO NOT USE for: booking windows / allocation lead time — how long until a booked-out foundry STARTS wafers, publicly 52–156+ weeks at N3-class nodes and CoWoS (use get_foundry_allocation); chip cost (use calculate_chip_cost / get_accelerator_costs).

Provide maskLayers (integer 10–200) or processNode (tsmc-n3 | tsmc-n5 | tsmc-n7 | tsmc-28 | samsung-3nm | samsung-5nm | intel-16). packagingType accepts coarse classes (conventional | flip-chip | cowos, default flip-chip) or any platform packaging id (fc-bga, wirebond-bga, cowos-l, copos, ...). Utilization ≤80% settles at the best-case band; ≥95% converges to the worst-case bound (FabTime operating-curve shape). Heuristic from public DPML benchmarks — directional, confidence LOW, not a foundry quote. Cite as "Silicon Analysts — Lead Time Estimator".

Input parameters:

- `maskLayers` (integer)
- `packagingType` (string)
- `processNode` (string)
- `utilization` (number)

### `get_hbm_market_data` (~262 tokens)

Returns 10 HBM market sub-tables: accelerators, specs, marketShare, spotPrices, leadingIndicators, qualificationFeed, revenueForecast, supplierRevenue, validationChecks, bitDemand. Optional `table` parameter narrows to a single sub-table; omitting returns all 10.

USE THIS for: HBM3/3e/4 generation specs, SK Hynix/Samsung/Micron market share, spot vs. contract pricing, derived HBM bit demand by SKU class and customer type (bitDemand, EB ranges, monthly).

bitDemand is NOT a workload split — it is a SKU-class/customer-type cut. Dominant HBM SKUs are dual-use, so a training-vs-inference HBM attribution would be dishonest; no public source publishes one.

DO NOT USE for: per-accelerator HBM cost in a specific chip (use get_accelerator_costs.costBreakdown.hbmCostUsd); HBM cost in a hypothetical chip cost calc (use calculate_chip_cost with hbmStacks/hbmCost).

Returns INTERNAL_ERROR if the upstream Supabase HBM tables are unreachable. Research tables refresh Mon/Wed/Fri; bitDemand refreshes monthly (1st).

Input parameters:

- `table` (string)

### `get_market_pulse` (~187 tokens)

Returns curated supply-chain headlines with trend direction (up/down/neutral), source attribution, and impact analysis. Categories: logic, memory, packaging, connectivity, power, geopolitics. Defaults to all categories, all trends, no limit.

USE THIS for: "what's happening in HBM this quarter?", "any geopolitical moves affecting TSMC?", recent supply/demand inflections.

DO NOT USE for: structured pricing data (use get_wafer_pricing, get_hbm_market_data); published cost of a specific chip (use get_accelerator_costs).

Per-item dates are formatted strings (e.g., "Jan 2026") — not ISO 8601. Cache: 5 minutes server-side. Returns empty array if all items filtered out.

Input parameters:

- `category` (string)
- `limit` (integer)
- `trend` (string)

### `get_wafer_pricing` (~172 tokens)

Returns 300mm wafer price ranges (min/avg/max USD), defect density, NRE/mask-set cost, and node maturity for: tsmc-n3, tsmc-n5, tsmc-n7, tsmc-28, samsung-3nm, samsung-5nm, intel-16. Optional `node` filter narrows to one.

USE THIS for: looking up wafer cost for cost modeling, comparing foundries at the same node.

DO NOT USE for: per-chip cost (use get_accelerator_costs or calculate_chip_cost); packaging-related cost (use get_packaging_costs).

Returns INVALID_PARAMS if node is not in the valid set. Each record carries the source attribution string. Refreshes monthly.

Input parameters:

- `node` (string)

### `get_packaging_costs` (~176 tokens)

Returns two sub-arrays: `packaging` (per-tech cost benchmark + capability matrix for CoWoS-S/L, EMIB, SoIC, InFO-PoP, FC-BGA, FC-CSP, etc.) and `hbmSpecs` (HBM2 through HBM4 cost per stack + bandwidth/capacity). Optional `type` filter narrows packaging array to one technology.

USE THIS for: packaging cost lookup, comparing CoWoS variants, getting HBM stack pricing for cost modeling.

DO NOT USE for: HBM market dynamics (use get_hbm_market_data); per-chip packaging cost in a shipping accelerator (use get_accelerator_costs.costBreakdown.packagingCostUsd).

Returns INVALID_PARAMS for unknown type. Refreshes monthly.

Input parameters:

- `type` (string)

### `get_hbm_qualification` (~316 tokens)

Sourced HBM qualification tracker: which memory vendor (SK Hynix, Samsung, Micron) passed which AI-accelerator customer's qualification (NVIDIA Vera Rubin/GB300/B300/H200, AMD MI350/MI325X, Broadcom), by generation (HBM3/HBM3E/HBM4) and stack height. Returns `matrix` (current status per vendor×customer×generation, each row dated + source URL + confidence) and `timelines` (per-relationship status-change history back to 2022, e.g. sampling → in_qualification → qualified → volume_shipping). Refreshed daily; status changes human-reviewed.

USE THIS for: "who supplies HBM4 for Vera Rubin?", "did Samsung pass NVIDIA qualification?", "Micron HBM4 status", qualification timeline/history questions, HBM supply-eligibility analysis.

DO NOT USE for: HBM pricing/market share (use get_hbm_market_data); per-chip HBM cost (use get_accelerator_costs).

Filters: vendor (enum), customer (substring), generation (enum), include_timelines (boolean). Anonymous callers may receive timelines truncated to the latest event per relationship — full history with a free API key (https://siliconanalysts.com/developers). Cite as "Silicon Analysts — HBM Qualification Tracker".

Input parameters:

- `customer` (string)
- `generation` (string)
- `include_timelines` (boolean)
- `vendor` (string)

### `get_foundry_allocation` (~382 tokens)

Foundry & advanced-packaging ALLOCATION — the current-state snapshot per node/tech (TSMC/Samsung/Intel/... × N2/N3/CoWoS-L/SoIC/...) plus optional time-series HISTORY. Current fields: allocation_status (fully_booked → available), lead_time_weeks_min/max + trend, utilization, price_trend, geo_risk, customers, capacity_current/target, customer_shares, allocation_note. With include_history=true, returns the tracked series from capacity_signals: lead_time / booking-window, pct_locked (%-capacity-locked), customer_allocation (publicly-reported per-customer share), cowos_capacity, foundry_utilization — each point dated (as_of) with provenance. No competitor publishes allocation as a structured, queryable feed.

USE THIS for: "who has CoWoS allocation and how much?", "what's the booking lead time for N2?", "how locked is 2026 CoWoS capacity?", allocation/lead-time trend over time.

DO NOT USE for: per-chip cost (use get_accelerator_costs / calculate_chip_cost); HBM market share/pricing (use get_hbm_market_data); HBM qual status (use get_hbm_qualification).

Filters: foundry, node, category, customer, history_metric, include_history (bool), limit. Sourced public estimates (analyst/press/earnings), human-reviewed; every record carries provenance.confidence_tier. wafer_price is intentionally omitted. Cite as "Silicon Analysts — Foundry Allocation".

Input parameters:

- `category` (string)
- `customer` (string)
- `foundry` (string)
- `history_metric` (string)
- `include_history` (boolean)
- `limit` (integer)
- `node` (string)

### `get_foundry_economics` (~621 tokens)

Foundry IR ECONOMICS — per-foundry, per-process-node, per-fiscal-quarter wafer ASP (min/max/blended, USD per 300mm-equivalent wafer, $250-grained) and fab UTILIZATION (%), derived exclusively from PUBLIC IR materials (earnings releases/transcripts/decks, trade press) via a documented scaling calculation (rev-mix-v1): reported revenue × reported node revenue-shares × reported wafer shipments, allocated on pinned analyst prior ratios. Covers tsmc | umc | intel | samsung | smic | gf. Every row carries source_urls + release_dates + confidence (high/medium/low); utilization is 'stated' (company said it — UMC/SMIC style) or 'derived' (shipments vs capacity estimate, capped medium) and NEVER fabricated per node. include_facts=true returns the underlying evidence facts (verbatim quote + source per datum).

Also returns node_margin_estimates for TSMC: per-node est. wafer price / est. wafer cost / est. GROSS MARGIN % with ranges (N3/N5/N7/N16/N28+/N2) — single-vintage Silicon Analysts ESTIMATES from public analysis, explicitly labelled (TSMC does not disclose per-node margin; company-level GM is quarterly IR).

USE THIS for: "what does a TSMC 3nm wafer sell for and how has it moved by quarter?", "TSMC blended ASP trend", "UMC utilization last quarter", "N3 share of TSMC revenue over time", "estimated gross margin by node", node-economics history for models.

DO NOT USE for: the current spot wafer price band only (use get_wafer_pricing — that is the live analyst-consensus band this dataset cross-validates against); allocation/lead-time/booking (use get_foundry_allocation); chip-level cost (use calculate_chip_cost / get_accelerator_costs).

Filters: foundry, node (canonical token, e.g. n3 | 22-28nm | 18a), node_group (leading_3nm | class_5nm | ...), quarter (2026Q1 | 2025FY), from/to range, include_facts, limit. LATEST period per foundry is free; multi-period HISTORY (quarter/from/to) requires a Pro key — free callers are clamped to latest with an explanatory meta.note (never…

Input parameters:

- `foundry` (string)
- `from` (string)
- `include_facts` (boolean)
- `limit` (integer)
- `node` (string)
- `node_group` (string)
- `quarter` (string)
- `to` (string)

### `get_recent_changes` (~356 tokens)

"What Changed" — recent MOVEMENTS in Silicon Analysts' public data over a 7d/30d window, derived from the daily snapshot ledger. Each moved metric returns direction (up/down), magnitude (pct_delta for value metrics, pp_delta for percentage metrics), old/new values, the two snapshot dates compared (as_of, prior_as_of), window_days_actual (the REAL lookback — the ledger is young, so a 30d window clamps to available history), and per-record provenance. Domains: wafer_pricing, chip_cost, margin_benchmark, foundry_capacity, defect_density, nre_cost.

USE THIS for: "what moved in semiconductor costs this week?", "did any wafer prices change recently?", "what changed since my last fetch on June 20?" (use since), building a market-change digest, monitoring deltas across the data layer over time.

DO NOT USE for: current absolute values (use get_wafer_pricing / get_accelerator_costs / get_foundry_allocation); allocation lead-time trend specifically (use get_foundry_allocation with include_history).

Filters: window (7d|30d), since (ISO date — compare the latest snapshot against the newest snapshot at/before it; overrides window for baseline selection), datasetId (one domain), minDelta (override the significance threshold), limit. N2/Apple omitted (conflict-safe). Returns an empty array when nothing moved past the significance gate — does not error. Cite as "Silicon Analysts — What Changed".

Input parameters:

- `datasetId` (string)
- `limit` (integer)
- `minDelta` (number)
- `since` (string)
- `window` (string)

### `get_market_dataset` (~557 tokens)

Curated market-data TIME SERIES with per-point sourcing — the datasets behind siliconanalysts.com/market-data. Includes: hbm-pricing (HBM contract + blended $/GB by generation, HBM2→HBM4, anchors 2017→2026 — series_keys like 'hbm3e-contract'; NOTE: no public HBM spot market exists — HBM sells via LTAs, and the dataset says so rather than fabricating a spot curve), component-lead-times (CoWoS-S/CoWoS-L/HBM3E/TSMC-N3 lead times in weeks back to 2022), wafer-price-tsmc (wafer price by node back to 65nm), semiconductor capex, DRAM/NAND pricing, and more. Every point carries value_low/mid/high, confidence, data_type (Confirmed|Estimate|Projection), source_name, source_date, source_note — estimates are typed as estimates, never dressed as observations.

USE THIS for: HBM contract price history by generation and basis ("what did HBM3E contract $/GB do through the 2023 shortage?" — note the revenue-implied vs per-stack bases are ~1.7x apart and must not be compared across series), lead-time trend series, wafer price history by node, memory price cycles — any question needing the dated SERIES rather than the current snapshot.

DO NOT USE for: current HBM market snapshot (use get_hbm_market_data); current wafer price bands (use get_wafer_pricing); IR-derived per-node ASP/utilization (use get_foundry_economics); allocation status (use get_foundry_allocation).

Params: dataset (id; pass 'list' to enumerate the catalog), series_key (optional filter, e.g. 'hbm3e-contract'). Tiering: anonymous → recent points; free key → recent + newest-3-per-series history preview; Pro → complete series. Each dataset returns `methodUrl` — a published page describing HOW the series was built (typing rules, derivations, deliberate gaps) — or null; read it before reasoning about modelled points. Pro callers can pull the whole series as flat CSV/JSONL in one call: GET /api/v1/export?dataset=<id>&format=csv. Cite as "Silicon Analysts — Market Data".

Input parameters:

- `dataset` (string, required): Dataset id, e.g. 'hbm-pricing', 'component-lead-times', 'wafer-price-tsmc'. List ids via get_market_dataset with dataset='list'.
- `series_key` (string): Optional series filter, e.g. 'hbm3e-contract' or 'hbm4-contract'.

### `get_market_intelligence` (~439 tokens)

Market Intelligence — the freshest SOURCED semiconductor market briefs, generated daily from a Tavily + Claude scan of primary press, earnings, and trade outlets. Each brief returns title, severity (Critical/High/Medium/Low), confidence_score (0-100), quantitative_impact (e.g. "Est. BOM increase: +$500"), an executive summary, a short analysis, a category (Logic/Memory/Packaging/Connectivity/Power/Geopolitics), and a curated sources[] list — plus per-record provenance. UNIQUELY: each brief also carries `entities` (the chips/nodes/packaging/HBM-gen/companies it concerns), `impact` (when it's a cost move, the per-chip BOM dollar deltas computed from Silicon Analysts' cost models — e.g. "HBM +20% → +$580 on B200" with a pre-filled calculator URL), and `related` (cross-links to the live datapoints + tools). No pure-news source does this. The machine feed returns ALL severities; `published` flags the Critical/High briefs that also have a public page. Public sources only; no insider data.

USE THIS for: "what's the latest in HBM / CoWoS / TSMC supply this week?", "any recent semiconductor price hikes, yield news, or capacity moves?", building a sourced market-news digest, grounding a claim about a recent supply-chain event.

DO NOT USE for: current absolute cost/pricing values (use get_accelerator_costs / get_wafer_pricing / calculate_chip_cost); structured data movements over time (use get_recent_changes); allocation/lead-time status (use get_foundry_allocation).

Filters: severity, category, since (ISO timestamp), publishedOnly (bool), limit (1-100, default 25). N2/Apple omitted (conflict-safe). Cite as "Silicon Analysts — Market Intelligence".

Input parameters:

- `category` (string)
- `limit` (integer)
- `publishedOnly` (boolean)
- `severity` (string)
- `since` (string)

### `get_market_advantage` (~286 tokens)

Market Advantage — human-vetted TIME-ADVANTAGE evidence: dated, immutable proof that Silicon Analysts recorded a semiconductor supply-chain event BEFORE the first English-language coverage of it. For each win: our first-seen timestamp (immutable), the cited source's own publication time, the first English coverage's timestamp + its public URL/publisher, and the lead in hours (lead_time_hours_vs_detection). Only wins a human has CONFIRMED for citation are returned; nothing unvetted is ever exposed.

USE THIS for: "where has Silicon Analysts led mainstream financial/English-language coverage on chip supply-chain events?", "show the last few supply shocks this feed flagged before Bloomberg/Reuters", proving the feed's Asia-hours latency edge to a fund or procurement team.

DO NOT USE for: the underlying data itself (use get_recent_changes / get_market_intelligence / get_hbm_qualification); unconfirmed or pending races (not exposed by design).

Filters: limit (1-100, default 25), order_by (lead_time|recent), event_kind (hbm_qual|capacity_signal|market_intelligence). Returns facts (timestamps + public URLs), not claims. Empty until a win is confirmed. Cite as "Silicon Analysts — Market Advantage".

Input parameters:

- `event_kind` (string)
- `limit` (integer)
- `order_by` (string)

### `get_benchmark_history` (~460 tokens)

Historical Benchmarks — the bitemporal benchmark-observations ledger behind the Chip Cost Calculator: wafer cost by node/foundry (deflationary curves), defect-density (D0) learning curves per node, advanced-packaging costs incl. the broken-out CoWoS interposer entity, test cost, backend yield, and HBM $/GB. Each observation carries as_of (the date the reading reflects — curated backfill from dated public archives extends history), detected_at (capture time), and full sourcing metadata (source_type taxonomy: foundry_ir | wfe_vendor_earnings | government_filing | press_release | analyst_report | company_announcement | trade_press | public_web; source_url; confidence high/medium/low). grain=month|quarter returns median/min/max rollups per period; grain=raw returns per-source observations. Access tiers: free key → preview, Pro/Enterprise → full ledger, anonymous → none.

USE THIS for: "how has TSMC N5 wafer pricing moved over 24 months?", "is our internal D0 ramp tracking the market's learning curve?", "CoWoS interposer cost trend", benchmarking product-lifecycle cost projections.

DO NOT USE for: current point values (use get_wafer_pricing / get_packaging_costs); the daily PIT ledger replay (use /api/v1/snapshot-series); margin history (use /api/v1/margin-trends).

Filters: benchmark_type (required: wafer_cost|defect_density|packaging_cost|interposer_cost|test_cost|backend_yield|hbm_cost_per_gb), entity_id, foundry, from/to (as_of bounds), grain (raw|month|quarter), limit. Access: a free API key returns a short preview (latest few observations); Pro/Enterprise unlock the full ledger; anonymous callers get none (empty + a get-a-key note). Cite as "Silicon Analysts — Historical Benchmarks".

Input parameters:

- `benchmark_type` (string, required)
- `entity_id` (string)
- `foundry` (string)
- `from` (string)
- `grain` (string)
- `limit` (integer)
- `to` (string)

### `get_fab_capacity` (~444 tokens)

Fab Capacity — per-fab, per-tech-node-class capacity from the fabs + fab_capacity_snapshots time-series (65 fabs: TSMC, Samsung, Intel, SMIC, GlobalFoundries, and more; Frontend in kwspm, Backend advanced-packaging in k units/month). Default mode returns the LATEST state per (fab, node class) at/before as_of, joined with fab metadata (name, foundry, country, status) and availability_status (fully_booked → available). series=true returns the full dated series — node conversions appear as capacity shifting between node-class rows across effective_dates (e.g. 28nm shrinking while 7nm grows). Every reading carries sourcing metadata (foundry_ir / wfe_vendor_earnings / government_filing taxonomy + citation + confidence) and is_projection for forward-looking guidance. Latest state: all tiers (incl. anonymous). series=true: free key → preview, Pro/Enterprise → full series.

USE THIS for: "what is TSMC's 3nm-class installed capacity by fab?", "which fabs are fully booked?", "how is Fab 14's mature-node capacity being converted over time?", country-level capacity aggregation.

DO NOT USE for: node-level annual wafer starts (use get_wafer_pricing's foundry context or /api/v1/foundry endpoints — different granularity, deliberately separate); allocation/lead-time status per node (use get_foundry_allocation).

Filters: fab_id, foundry, country, tech_node_class, as_of (latest-state cutoff), series (bool), limit. Access: latest state is free for all tiers (incl. anonymous); series=true returns a preview on a free key and the full series for Pro/Enterprise (anonymous gets an empty series + a get-a-key note). Cite as "Silicon Analysts — Fab Capacity".

Input parameters:

- `as_of` (string)
- `country` (string)
- `fab_id` (string)
- `foundry` (string)
- `limit` (integer)
- `series` (boolean)
- `tech_node_class` (string)

### `get_forecasts` (~389 tokens)

Forecast Vintages — third-party forecasts (research firms like TrendForce/WSTS/SEMI, and company capex/bit-growth guidance) archived with their ORIGINAL publication date. Query the REVISION HISTORY, not just the latest number: "what did TrendForce say about 2026 HBM bit growth in January vs July?". Each row: originator, originator_type, metric, target_period (e.g. CY2026, 2027H1), value (num or low/high), unit, as_of (publication date), a source URL, and a verbatim quote. This is the vintage archive of OTHER organizations' forecasts — distinct from our own scenario models.

USE THIS for: forecast revision tracking, "how has the 2026 capex outlook moved across TSMC's earnings calls?", comparing what different firms projected for the same target period, building a consensus-vs-time view.

DO NOT USE for: current cost/pricing values (use get_wafer_pricing / get_accelerator_costs); our own scenario projections (those live on /market-data/*/forecast).

Filters: originator, originator_type (research_firm|company_guidance|government|bank|industry_body|other), metric, target_period, entity_id. Latest slice for all tiers; full history (from/to/since/all) needs a Pro key — free callers get the latest slice with a note, never an error. Cite as "Silicon Analysts — Forecast Vintages".

Input parameters:

- `all` (boolean)
- `entity_id` (string)
- `from` (string)
- `limit` (integer)
- `metric` (string)
- `originator` (string)
- `originator_type` (string)
- `since` (string)
- `target_period` (string)
- `to` (string)

### `get_wfe_signals` (~324 tokens)

WFE Order-Book — wafer-fab-equipment maker disclosures (ASML, Applied Materials, Lam Research, KLA, Tokyo Electron) from quarterly IR: bookings, backlog, segment revenue, and guidance, in the STATED currency (EUR for ASML, JPY for TEL, USD for the rest — never converted). The 12–24-month leading indicator for fab capacity. Each row: company, fiscal_period, metric, value(s), unit, as_of (release date), source URL, verbatim quote.

USE THIS for: "is the equipment order-book turning up or down?", ASML bookings trend, AMAT segment revenue by quarter, reading WFE demand ahead of fab-capacity changes.

DO NOT USE for: fab capacity itself (use get_fab_capacity); foundry wafer ASP (use get_foundry_economics).

Filters: company (asml|amat|lam|kla|tel), metric (bookings|backlog|deferred_revenue|segment_revenue|guidance_revenue|lead_time_weeks), segment, fiscal_period. Latest slice for all tiers; full history Pro (never a 403). Cite as "Silicon Analysts — WFE Equipment Order-Book".

Input parameters:

- `all` (boolean)
- `company` (string)
- `fiscal_period` (string)
- `from` (string)
- `limit` (integer)
- `metric` (string)
- `segment` (string)
- `since` (string)
- `to` (string)

### `get_fab_events` (~309 tokens)

Fab Milestones — the dated construction & ramp event log: announcement → groundbreaking → equipment move-in → risk production → HVM, plus expansions and SCHEDULE SLIPS recorded as their own events (a delay never overwrites the original plan). Back to 2020. Each row: foundry, fab_name, event_type, event_date, announced_date, a summary, source URL, verbatim quote, and is_projection for forward-dated milestones.

USE THIS for: "which fabs hit a milestone recently?", tracking TSMC Arizona / Samsung Taylor / Intel Ohio / Micron / SK hynix timelines, "which projects have slipped?", validating fab-capacity projections against construction reality.

DO NOT USE for: current capacity numbers (use get_fab_capacity); allocation/lead-time (use get_foundry_allocation).

Filters: foundry, fab_id, event_type (announced|groundbreaking|equipment_move_in|risk_production|hvm_start|expansion|delay|cancellation|conversion), country. Latest slice for all tiers; full history Pro (never a 403). Cite as "Silicon Analysts — Fab Construction Milestones".

Input parameters:

- `all` (boolean)
- `country` (string)
- `event_type` (string)
- `fab_id` (string)
- `foundry` (string)
- `from` (string)
- `limit` (integer)
- `since` (string)
- `to` (string)

### `get_policy_events` (~322 tokens)

Trade-Policy Timeline — the dated log of semiconductor trade-policy actions (export controls, entity listings, license policies, tariffs, subsidies, retaliation) anchored to GOVERNMENT PRIMARY documents (Federal Register / BIS, USTR, MOFCOM, METI, EU, Netherlands…), back to the Oct 2022 BIS advanced-computing rule. Each row: jurisdiction, agency, event_type, title, published/effective dates, affected_entities, node_threshold, a document reference (e.g. Federal Register cite), source URL, verbatim quote.

USE THIS for: "what export-control rule changed in December 2024?", building a policy timeline, "which actions named SMIC?", grounding a geopolitics/supply analysis in the actual published action.

DO NOT USE for: analysis/commentary on policy (use get_market_intelligence); rumored or anticipated actions (only PUBLISHED actions are recorded).

Filters: jurisdiction (us|china|japan|netherlands|korea|taiwan|eu|uk|other), agency (BIS|USTR|MOFCOM|METI|EU-COM…), event_type. Latest slice for all tiers; full history Pro (never a 403). Cite as "Silicon Analysts — Trade-Policy Timeline".

Input parameters:

- `agency` (string)
- `all` (boolean)
- `event_type` (string)
- `from` (string)
- `jurisdiction` (string)
- `limit` (integer)
- `since` (string)
- `to` (string)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/siliconanalysts-silicon-analysts/api-mcp#diagnostics

## Score history

- 2026-08-03: 69
- 2026-08-02: 68
- 2026-08-01: 68
- 2026-07-31: 67
- 2026-07-30: 61
- 2026-07-29: 60
- 2026-07-28: 59
- 2026-07-27: 59
- 2026-07-26: 58

## Links

- Remote endpoint: https://siliconanalysts.com/api/mcp
- Repository: https://github.com/SiliconAnalysts/silicon-analysts-nextjs
- Website: https://siliconanalysts.com/
- Changelog RSS feed: https://verifymcp.io/servers/siliconanalysts-silicon-analysts/api-mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/siliconanalysts-silicon-analysts/api-mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/siliconanalysts-silicon-analysts/api-mcp