"Foundry Virtual Tabletop" matching MCP tools:

• calculate_chip_cost

  Silicon Analysts

  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.

  Connector

• estimate_lead_time

  Silicon Analysts

  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-n16 | tsmc-28 | samsung-3nm | samsung-5nm | samsung-7nm | samsung-14nm | intel-7 | intel-16 | gf-12lp | gf-fdx | umc-22-28 | umc-40 | smic-28). 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".

  Connector

• get_wafer_pricing

  Silicon Analysts

  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-n16, tsmc-28, samsung-3nm, samsung-5nm, samsung-7nm, samsung-14nm, intel-7, intel-16, gf-12lp, gf-fdx, umc-22-28, umc-40, smic-28. Optional `node` filter narrows to one. ALWAYS read `citation` before using a price in a cost model: it names the corroborating sources and carries the caveat that decides whether the number is usable. Some sellers report a foundry segment operating loss, so their quote is a positioning price rather than a cost-recovering one; `citation` says so explicitly, and `defectDensity`/`nreCost` are null where no public basis exists rather than being estimated. 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.

  Connector

• get_benchmark_history

  Silicon Analysts

  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".

  Connector

• remove_workspace_member

  Dock

  Remove a workspace member. Editor role required; owner-tier removals require an owner caller. Sole-owner removal is blocked; promote someone else first. Note: if the workspace visibility is `org`, removing an explicit member of the same org leaves them with virtual editor access via the org-membership branch. Consent-gated for agents: the FIRST call returns { status: 'confirmation_required', confirm_token, message, expires_in }. Surface the message to your user and, if they say yes, re-call this tool within 60s with `confirm_token` set to the same token. User callers (cookie session) skip the consent step.

  Connector

• decker.update_protective_stops

  Decker

  Axis③ (Order/Execution) — modifies the stop-loss and/or take-profit on an EXISTING open position. There is no cancel_order tool because Decker only places market orders (there is no resting order to cancel) — the actual gap this fills is modifying protective stops on a position you already hold. real: cancels the old exchange stop/take-profit order(s) and places new ones at the given price(s) (new order placed first, old one canceled only after — no unprotected window). virtual: updates the paper position's stop_loss/take_profit columns directly (polled by the paper monitor). Provide at least one of sl_price/tp_price — the other side, if omitted, is left at its current value. If both a real and a virtual position are open for this symbol, pass mode explicitly or the call is rejected asking which one.

  Connector

• get_foundry_economics

  Silicon Analysts

  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 an error). Sparse-disclosure foundries (Intel, Samsung) return nulls/low confidence rather than invented numbers. Refreshes weekly (Mon 14:30 UTC) + each earnings season. Cite as "Silicon Analysts — Foundry IR Economics".

  Connector

• virtual_event_attendees

  DC Member API

  GET /virtual-events/:sessionID/attendees — List Live Call attendees List the attendees of a Live Call — the DCers who RSVPd `yes` or `maybe` (the same set behind `attendeeCount`, mirroring how `GET /events/:eventID/attendees` counts RSVPs). Profiles use the standard other-person shape (identical to `GET /events/:eventID/attendees` and `GET /profile-match`): public fields plus privacy-gated `annualRevenue` + `teamSize` where the member shares them. Hidden and guest profiles are filtered out. **Access:** any active DCer who can see the Live Call. DC BLACK-only calls stay tier-gated — DC-tier callers get `tier_restricted` (403). **Pagination:** page with `?limit=` (1-100, default 100) plus the opaque `?cursor=` from the previous response's `nextCursor` (`null` when there are no more). See `GET /virtual-events/:sessionID` for the call itself, and `GET /events/:eventID/attendees` for the in-person equivalent.

  Connector

• get_kg_facts

  NightWatch Live Intelligence

  NightWatch Knowledge Graph lookup for a COMPANY/entity (equities & RWA universe: Samsung 'samsung-electronics', SK Hynix 'sk-hynix', 'tsmc', 'nvidia', 'asml', 'arm', ...). Returns SOURCED data only — every row carries a citation URL (the KG refuses uncited data): (1) numeric fundamentals (revenue, net income, market cap, business segments, dividend, market-share rankings), (2) typed relations (supplies / competes / customer_of / licenses — e.g. Samsung supplies NVIDIA HBM, competes with TSMC in foundry), and (3) a live HyperLiquid price block when the entity is tradable. Use this BEFORE reasoning about a company's fundamentals, competitors, supply chain, or a hedge on its equity perp. Input accepts a slug or a plain company name (fuzzy-matched).

  Connector

• create_card

  agentcard

  The one card tool: get the user a virtual debit card for a purchase. Cards are live and charged for real when used. For a FIRST-TIME user it starts by ADDING the user's OWN Visa or Mastercard — no identity verification (KYC) and no balance funding: the call returns a secure link (attach_started); send it to the user (about a minute: a one-time code from their bank plus a passkey), then call create_card again with the SAME arguments and it mints against the added card. If the user's card cannot be added (issuing_suggested), offer the fallback — an Agentcard funded from their cash balance, which requires KYC the first time — and only after the user agrees, call create_card with source "issued". Established users: the saved default decides (get_settings default_payment — their chosen added card, or the wallet balance); with no saved default, an active ADDED card wins, otherwise the cash balance. Per-call overrides: connected_card_id issues against a specific added card, source "issued" forces the cash balance, restart_setup starts a fresh add-card link. If the balance is short on the issued path, top up with add_funds. Connections through a company OAuth client have NO card count or amount limits; only first-party personal accounts have per-plan caps. Call get_plan for the limits in effect.

  Connector

• setup_payment_method

  agentcard

  Save a payment method used ONLY to pay for flight bookings (the fare is charged to it via a hold at booking; no virtual card is created for flights). It does NOT fund cards or the cash balance — cards are funded from the balance (see add_funds). Returns a secure checkout URL the user must open to save their card details.

  Connector

• start_workflow

  Ansvar: EU Compliance & Legal Intelligence

  Begin a structured workflow selected from the live workflow registry. The registry covers threat and privacy modeling; enterprise, automotive, robot, rail, OT and UAS risk/TARA; DPIA and FRIA; regulatory, medical-device, drone and machinery gap analysis; tender review and audit; document review; SORA authorisation; vulnerability prioritisation; and deferral dossiers. Call list_workflow_types first: it is the authoritative source of exact ids, deliverables, required slots, variants, and availability for this caller. When a fresh registry snapshot is available, this tool's workflow_type input schema carries a caller-authorized enum; otherwise it remains a string rather than silently falling back to a stale catalog. The workflow engine guides the process step by step with quality gates. Each step's questions_for_user is advisory — answerable from context or uploaded documents; only steps returning requires_user_input=true carry the server-enforced human-input gate. Which types you can start is tier-fenced: free and solo include seven types (1 and 2 runs a month) — threat_model, gap_analysis with its gap_analysis_nis2, gap_analysis_dora, gap_analysis_cra and gap_analysis_ai_act variants, and dpia, each reported as JSON or as a watermarked html or pdf — at those tiers the framework argument accepts only nis2, dora, cra or eu_ai_act, and the base gap_analysis needs one of them; Premium adds the rest of the interview-grounded catalog — LINDDUN, the TARA families, FRIA and the jurisdictional DPIA and gap variants, SORA, the drone and OT types, machinery conformity, and enterprise risk — with 5 runs a month; document review, the tender family and adversary tabletop require Team or Company. A start SPENDS a run from the monthly allowance, and on free and solo a cancel does not hand an unused one back — name the workflow_type you intend to the user and get their OK before calling this, and check get_my_capabilities for what is left.

  Connector

• decker.place_order

  decker

  Axis③ (Order/Execution) — unlike every other tool here, this one moves money. It places a market order through DECKER'S OWN execution engine (same path as the decker-ai.com chat trading UI, source='mcp') — it does NOT hand off to your own broker connection or exchange account; Decker executes using whatever exchange credentials this user has separately linked to their Decker account on the website. execution_mode (virtual|real) is NOT chosen by the caller — it is resolved server-side from this user's account settings (user_settings.execution_mode) AND the platform's real-trading kill switch; a real-money order requires both an explicit user opt-in AND role/tier eligibility (PRO/ENTERPRISE or admin) AND passing the tier's hard notional/leverage/daily-count caps (checked here before dispatch — violation blocks the order, does not downgrade it to virtual). The response always states which mode actually executed — treat 'virtual' in the response as authoritative even if you expected real. Restricted to the crypto-6 universe (BTCUSDT/ETHUSDT/SOLUSDT/BNBUSDT/XRPUSDT/DOGEUSDT) for this MCP path — HL-synthetic and KRX symbols are read-only via other tools. Call decker.validate_intent first to read the engine's current stance; this tool does not check it for you. Positions are tracked as ONE net row per user+symbol+mode, not per order — if you already hold a position on this symbol, this order nets into it and the response's pre_existing_position field says so. A later close_position call closes the combined total, not just what this call added.

  Connector

• get

  Costory: Your Finops MCP

  Fetch a V2 dashboard, budget, cost alert, report, or virtual dimension by ID. Response includes a `type` discriminator (`dashboard` | `budget` | `costAlert` | `report` | `virtualDimension`) — branch on it. Budgets: pass the parent budget id (from search) or a budget version id; response includes budgetVersionId for query, plus costMetricId, currency, virtualDimension (id, name, bqName, values), excludedValues, lines, includedVirtualDimensionValues, filterCelRestrictToIncludedLines, and filterCelExcludeExcludedVirtualDimensionValues for aligning query cost with budget. howToQueryAlignedCost gives concrete example payloads. Cost alerts: pass the alert id (from search or list_alerts); response includes alert configuration plus firingHistory (every stored firing day and group values that fired). Reports: config in words plus run-health (status, nextRunDate, lastRunHealth, `widgets` array, recent per-destination delivery with executionIds). Read-only. To inspect a specific delivery's content, call get_report_execution (then get_report_execution_widget for drill-down). Virtual dimensions: `id` / `virtualDimensionId` (same), `hasPendingDraft`, immutable `bqName` (BigQuery/CEL field for groupBy/filterCel — never derive from display `name`); `published` and optional `draft` (name, description, tags, computeStatus, values, rules, leftoverRule; draft may include draftValidation); `dependencies`. `values` is derived — output only. `leftoverRule` is separate from `rules` — do not put it in the `rules` array or pass it to update. For updates, copy rules from draft if pending else published, project each rule to `{ id, name, conditionCel, allocation }` (omit `position`, `isLeftovers`, and any leftover/catch-all rule), and pass that full `rules` array to update_virtual_dimension_draft. Call get_skill with skillId: "virtual-dimensions" for allocation shapes and workflow. Dashboards: call get_skill with skillId: "dashboards" before create/update. Chart widgets include `x`/`y`/`w`/`h` and resolved `queryConfig`; text widgets have `type: "text"` and `textContent`. After fetch, use get_dashboard_widget_data / get_dashboard_widget_image, or update_dashboard to mutate. Use "search" (or list tools) first to discover IDs. EXAMPLE: "Open the Kubernetes dashboard" (after search returned its ID) → { id: "clx9abc123" }

  Connector

• list_virtual_dimensions

  Costory: Your Finops MCP

  List virtual dimensions (custom cost axes) in the organization. `virtualDimensionId` in inputs equals `id` from list/get/search. Returns id, virtualDimensionId (same as id), name, bqName, description, status, computeStatus, tags (string[] of tag names), hasPendingDraft, and optionally draftValidation.ok when includeDraftStatus is true. bqName is the immutable BigQuery/CEL field name (e.g. virtual_environment) — set once at create from the initial name and never updated, even when name changes. Always use bqName (not name) for groupBy/filterCel in query. Use query to match name/bqName/description/tag; status filters DRAFT vs COMPLETED. Newly created MCP drafts typically have status DRAFT; published VDIMs are COMPLETED. Paginate with limit (default 50, max 100) and offset. Call this before get when the user refers to a VDIM by name rather than id. EXAMPLE: "Show our environment virtual dimensions" → { query: "environment" }

  Connector

• update_virtual_dimension_draft

  Costory: Your Finops MCP

  Upsert the virtual dimension draft for an existing `virtualDimensionId` — updates a pending draft or seeds one from published state when none exists (response may include `warning: "Initialized draft from published state"`). `virtualDimensionId` in inputs equals `id` from list/get/search. Use create_virtual_dimension_draft only for brand-new VDIMs. Call get_skill with skillId: "virtual-dimensions" first — see skill for allocation shapes and workflow. For a new `telemetry` allocation, discover a live integration metric via list_metrics with includeExternal: true and a specific search term, then persist inline `externalMetric` { provider, integrationId, metricName, aggregator, groupByFields }. For BigQuery/S3, also set dateColumn and metricColumn from the returned `schema` (first DATE / first NUMERIC) and gapFillingMethod (default FORWARD_FILL). Catalog-complete providers (Tsuga, Datadog, CloudWatch, Amplitude) do not need those fields. Do not set `datasource` on new reallocations (echo a leftover stored `datasource` unchanged unless the user asks to switch). `bqName` is immutable; use returned `bqName` for groupBy/filterCel in query. Declarative: `rules` is optional — omit to change only metadata (`name`, `description`, `tagNames`); when provided, fully replaces the rules array. Omitting `rules` on a published-only VDIM still persists a draft (metadata-only promotion). Carry forward each existing rule's `id` and `allocation` from get; ids are sticky — reorder by moving `id` with its rule. Do not include leftover in `rules`. Rejects invalid payloads — nothing persisted unless validation passes. On success: `values`, `draftValidation: { ok: true }`, `draftPersisted: true`. Does not publish or refresh BigQuery. Clerk MCP only. EXAMPLE: "Add staging to Environment VDIM" — `rules` is the full desired set → { virtualDimensionId: "<id from create/list>", rules: [{ id: "<uuid from get>", name: "Production", conditionCel: "cos_environment in [\"prod\"]", allocation: { allocationType: "dimensionValue", dimensionValue: "prod" } }, { name: "Staging", conditionCel: "cos_environment in [\"staging\"]", allocation: { allocationType: "dimensionValue", dimensionValue: "staging" } }] }

  Connector

• publish_virtual_dimension

  Costory: Your Finops MCP

  Validate the latest **persisted** pending virtual dimension draft, then promote it to published and kick off a BigQuery refresh. `virtualDimensionId` in inputs equals `id` from list/get/search. Requires a pending draft row — call update_virtual_dimension_draft for an existing virtualDimensionId (or create_virtual_dimension_draft for a brand-new VDIM) before publish. Preview alone does not create a draft. Rejects invalid drafts with draftValidation errors (no publish). On success returns `virtualDimensionId`, immutable `bqName`, `name`, `computeStatus`, and published rules — does not wait for the refresh job. After publish, query using returned `bqName` for groupBy/filterCel in query — bqName is immutable (set at create from the initial name) and does not change when name is renamed. `computeStatus` is `REFRESHING` when the refresh job was queued (async — poll via get or list_virtual_dimensions until `COMPLETED` before querying), or `TO_REFRESH` when the draft was promoted but queuing the refresh job failed — do not query yet; retry publish or re-check `computeStatus` until `COMPLETED`. Deletes the pending draft version. Clerk MCP only — not available on the service route. EXAMPLE: "Publish the Environment VDIM draft" → { virtualDimensionId: "<virtualDimensionId from create/list>" }

  Connector

• list_added_cards

  agentcard

  List the user's ADDED cards (their own Visa/Mastercard cards enrolled via create_card's add-card flow — the funding source that charges their own card), with ids, brand, last4, expiry, and status. The row marked isDefault is what create_card charges when no connected_card_id is given — the user's chosen default card (set with update_settings default_payment), falling back to the newest active one. Not the same as list_cards (the virtual cards Agentcard issues).

  Connector

• get_foundry_allocation

  Silicon Analysts

  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".

  Connector

• list_tables

  Drillr — The financial MCP for AI agents

  List alternative-data tables under the given categories. Returns each table's name, one-line purpose, and column names (call get_table_schema if you need column types/comments). Batch up to 5 categories in one call; omit categories, or pass ["all"], to get the category index instead. Use this BEFORE run_sql when you want to explore alt-data — run_sql alone won't tell you which tables exist. Available categories: - Energy & Power — US power plants, electricity prices, regional hourly generation/demand - Data Centers — facilities, GPU clusters, cooling - Semiconductors — AI chip specs, sales, ownership, foundry revenue, customs trade - Compute Pricing — GPU rental, cloud VM spot/on-demand, instance specs - Model Development — model specs, benchmarks, AI companies, AI polling, LLM arena - Inference Economics — LLM API pricing across providers - Macro & Trade — UN Comtrade, US Census trade flows, FRED macro series - Prediction Markets — Polymarket and Kalshi events, markets, trades, daily aggregates - Critical Minerals — USGS mineral deposits, country supply, critical materials

  Connector