Name: Wafergraph
Author: wafergraph

Wafergraph MCP

Read-only MCP server for wafergraph.com's semiconductor & AI supply-chain data: 30 tools, no auth.

Tool-list grade A Remote · Streamable HTTP No auth needed 30 tools v1.2.0

No reviews yet by wafergraphGitHub The publisher’s own endpoint — this marketplace is not in the path

96/100

tool-list score

tools declared

remote

at its publisher

—

calls last 7d

What it does

Read-only MCP server for wafergraph.com's semiconductor & AI supply-chain data: 30 tools, no auth.

Quickstart

# 1 — add it to Claude Code
claude mcp add --scope user --transport http wafergraph-mcp https://wafergraph-mcp.jwpalm99.workers.dev/mcp

# 2 — ask your agent for something these tools do
#   search_companies, get_company, get_segments and 27 more

Wafergraph costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.

Publishernot claimed

wafergraph1 server

1 category

All 1 server

Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.

Tool surface

What the model actually sees. Descriptions are diffed on every release — see version history.

Only tools that write or reach the network

Search wafergraph's semiconductor & AI supply-chain company dataset (615 companies across 12 segments) by name/one_liner substring and/or segment and/or country. Returns a compact list capped at 25 with a total match count. Use get_segments first if you don't know valid segment ids.

Parameter	Type	Required	Notes
query	string	no	Case-insensitive substring match against company name and one_liner.
segment	string	no	Filter to companies with this taxonomy segment id, e.g. 'foundry', 'equipment_front_end' (see get_segments).
country	string	no	Filter to companies headquartered in this country, e.g. 'Taiwan' (case-insensitive).

Full allowed profile for one company (by id or exact name) plus its supplier/customer supply-chain edges. Includes key_products (short list of named products/lines). Fields are deliberately limited to established/trust-checked data (see README field-discipline note).

Parameter	Type	Required	Notes
id	string	yes	Company id, snake_case (e.g. 'tsmc', 'asml') or exact company name.

The wafergraph taxonomy: 12 top-level supply-chain segments (materials through ai_datacenter) and their subsegments, each with a live company count, plus the market_position enum. Use this to discover valid segment values for search_companies/get_deals. Segment definitions are a versioned snapshot (see data.taxonomy_snapshot_date) while company counts are computed live.

No parameter schema on file.

Walk the supplier/customer graph from one focal company, up to 2 tiers up (suppliers), down (customers), or both. Mirrors the chain view on wafergraph.com's Explorer. Returns companies grouped by tier plus the edges between them.

Parameter	Type	Required	Notes
id	string	yes	Focal company id or name.
direction	string	no	up = walk suppliers only, down = walk customers only, both = walk both directions.
depth	integer	no	Number of tiers to walk, capped at 2.

Search wafergraph's semiconductor & AI supply-chain M&A corpus (74 acquisitions/mergers, including notable terminated attempts) by title/summary substring and/or segment. Returns a compact list capped at 30 with a total match count.

Parameter	Type	Required	Notes
query	string	no	Case-insensitive substring match against deal title and summary.
segment	string	no	Filter to deals where at least one named party is a company in this taxonomy segment id.

Side-by-side comparison of 2-6 companies on the same fields, plus their shared and unique supply-chain counterparties. Cheaper and more aligned than several get_company calls when the question is comparative.

Parameter	Type	Required	Notes
ids	array	yes	Company ids (snake_case, e.g. ['tsmc','samsung_foundry']) or exact names. 2-6 of them.

Geographic concentration of the supply chain: which countries host the companies in a given segment (or across all 12 segments), ranked by company count. Answers 'how concentrated in Taiwan is advanced lithography' style questions. Country is recorded for all 615 companies.

Parameter	Type	Required	Notes
segment	string	no	Restrict to one taxonomy segment id (see get_segments). Omit for the whole dataset.

Rank supply-chain chokepoints: companies many others depend on, weighted by how concentrated their market position is. A chokepoint here means high downstream dependency plus monopoly/leader position, i.e. few substitutes. Scoring is a transparent heuristic over the public dataset, not a proprietary risk model.

Parameter	Type	Required	Notes
segment	string	no	Restrict to one taxonomy segment id (see get_segments).
limit	integer	no	How many to return (1-25, default 10).

Given a list of tickers or company ids, report that basket's aggregate exposure across supply-chain segments and countries, and flag where holdings share the same upstream suppliers (correlated single points of failure). Informational supply-chain analysis over public data, not investment advice.

Parameter	Type	Required	Notes
holdings	array	yes	Tickers (e.g. ['NVDA','TSM']) or company ids. Up to 40.

Structured multi-criteria screen over all 615 companies: exact segment/subsegment/country/market_position/public filters plus a market-cap range, sortable and paginated. Use this instead of search_companies when the question is a precise filter ('leader-position analog companies in Japan under $20B') rather than a free-text match. Unknown segment/subsegment/country values just return zero results

Parameter	Type	Required	Notes
segment	string	no	Exact taxonomy segment id, e.g. 'foundry' (see get_segments).
subsegment	string	no	Exact taxonomy subsegment id, e.g. 'litho' (see list_subsegments).
country	string	no	Headquarters country, exact match, case-insensitive, e.g. 'Japan'.
market_position	string	no	Exact market_position: monopoly \| leader \| major \| challenger \| niche.
public	boolean	no	true = only publicly traded companies, false = only private ones. Omit for both.
min_market_cap_usd_b	number	no	Minimum market cap in USD billions (inclusive). Only ~72% of companies have a cap on file — see the response note when this is set.
max_market_cap_usd_b	number	no	Maximum market cap in USD billions (inclusive). Only ~72% of companies have a cap on file — see the response note when this is set.
has_ticker	boolean	no	true = only companies with a public ticker on file, false = only companies without one.
sort_by	string	no	Sort field. 'market_cap' sorts descending with unpriced companies last; 'name'/'country' sort ascending. Default 'market_cap'.
limit	integer	no	Max rows to return, 1-100. Default 25.
offset	integer	no	Rows to skip, for paging past the first limit. Default 0.

Every subsegment across wafergraph's 12-segment taxonomy, each with its live company count and parent segment id/name, optionally filtered to one segment. Use this (or get_segments) to discover valid subsegment values before calling get_subsegment or filter_companies. Segment/subsegment names come from a versioned taxonomy snapshot; company counts are computed live and can include subsegment ids

Parameter	Type	Required	Notes
segment	string	no	Restrict to subsegments of this taxonomy segment id, e.g. 'materials'. Omit for all 12 segments.

All companies in one segment+subsegment pair, as compact refs sorted by market cap descending, plus a market_position breakdown and a country breakdown computed over the FULL matching set (not just the returned page). Use list_subsegments first if you don't know valid segment/subsegment ids.

Parameter	Type	Required	Notes
segment	string	yes	Taxonomy segment id, e.g. 'equipment_front_end' (see get_segments).
subsegment	string	yes	Taxonomy subsegment id within that segment, e.g. 'litho' (see list_subsegments).
limit	integer	no	Max companies to return, 1-100. Default 50.
offset	integer	no	Companies to skip, for paging past the first limit. Default 0.

Nearest structural neighbours to one focal company, ranked by a transparent Jaccard-similarity score — not a market or competitive judgment. Use search_companies or resolve_ticker first if you only have a ticker or an approximate name, then pass the resolved id here.

Parameter	Type	Required	Notes
id	string	yes	Focal company id (snake_case, e.g. 'tsmc') or exact name to find neighbours for.
limit	integer	no	How many similar companies to return, 1-25. Default 10.

Top N companies by market cap, optionally restricted to a segment/country/market_position, with the priced-coverage ratio for that scope attached — about 28% of companies dataset-wide have no market_cap_usd_b on file, so a plain top-N list without the coverage number would look more complete than it is.

Parameter	Type	Required	Notes
limit	integer	no	How many companies to return, ranked highest market cap first, 1-100. Default 10.
segment	string	no	Restrict to one taxonomy segment id (see get_segments).
country	string	no	Restrict to companies headquartered in this country, case-insensitive.
market_position	string	no	Restrict to companies at this market_position.

Batch-resolve up to 25 strings — tickers, company names, or ids, in any mix — to canonical company refs. Call this FIRST whenever you have raw user input (a ticker list, pasted names) and need valid ids before calling other tools; unresolved entries come back with up to 3 suggested close matches instead of just null.

Parameter	Type	Required	Notes
queries	array	yes	Up to 25 strings to resolve, e.g. ['NVDA', 'TSMC', 'asml']. Each may be a ticker, an exact/partial company name, or a company id.

Every country in wafergraph's semiconductor & AI supply-chain dataset (29 countries across 615 companies) with company count, which segments are present there (with counts), public/private split, and priced market-cap totals. Sorted by company count descending. Optional segment filter. country is the company's HEADQUARTERS country only, not a manufacturing-footprint field. A company headquartered

Parameter	Type	Required	Notes
segment	string	no	Restrict to companies with this taxonomy segment id, e.g. 'foundry', 'memory' (see get_segments). Case-insensitive. Omit for all segments.

Deep profile of one country's presence in wafergraph's semiconductor & AI supply-chain dataset: company count, segment breakdown, market-position breakdown, top companies by market cap, notable monopoly/leader companies, and inbound/outbound supplier-relationship edge counts across this country's border (computed from the supply-chain graph). country is the company's HEADQUARTERS country only, not

Parameter	Type	Required	Notes
country	string	yes	Country name, e.g. 'Taiwan', 'United States', 'South Korea'. Case-insensitive; common short forms (USA, UK, Korea) are recognized.

Side-by-side comparison of 2-5 countries: aligned rows for company count, segment mix, market-position mix, and priced market cap, plus which segments each country is uniquely present in or dominant in, and which segments they all share. country is the company's HEADQUARTERS country only, not a manufacturing-footprint field. A company headquartered here may fabricate, assemble, or test elsewhere —

Parameter	Type	Required	Notes
countries	array	yes	2-5 country names, e.g. ['Taiwan','South Korea','United States']. Case-insensitive; common short forms recognized.

Who runs a given layer of the semiconductor & AI supply chain: the companies at monopoly/leader market position in one taxonomy segment (or all 12 if none given), with country and market cap, plus a count of how many companies sit at each position (monopoly/leader/major/challenger/niche) in that segment. country is the company's HEADQUARTERS country only, not a manufacturing-footprint field. A com

Parameter	Type	Required	Notes
segment	string	no	A taxonomy segment id, e.g. 'foundry', 'eda_ip' (see get_segments). Case-insensitive. Omit to cover all 12 segments.

For one focal company: break its suppliers down by headquarters country and by segment, report an HHI concentration index (0 = spread evenly, 1 = fully concentrated in one bucket) for each dimension, and name the single most concentrated one. Always reports supplier_edge_coverage because key_suppliers is only ~58% filled dataset-wide — a company with few listed suppliers here may be under-document

Parameter	Type	Required	Notes
id	string	yes	Focal company id (snake_case, e.g. 'tsmc') or exact company name.

Every documented supply path between two companies, following supplier->customer edges (e.g. 'how does NVIDIA actually depend on Shin-Etsu'). Searches up to max_depth hops in one or both directions and returns each path as an ordered list of companies, shortest first. Capped for combinatorial safety; absence of a path means undocumented, not disproven — see edge_coverage.

Parameter	Type	Required	Notes
from	string	yes	Starting company id, name, or ticker.
to	string	yes	Target company id, name, or ticker.
max_depth	integer	no	Maximum path length in hops (edges). Default 3, hard-capped at 4 to bound the search.
direction	string	no	'downstream': paths where from supplies (directly or via intermediaries) to to. 'upstream': paths where from depends on to as a supplier. 'either': search both directions and label each path.
limit	integer	no	Max number of paths to return (1-50, default 10).

Remove one company, every company in one country, or every company in one segment from the documented supply graph and report the blast radius: which companies lose a documented supplier, how many alternative suppliers they retain in the same subsegment, and which are left with zero documented alternative (ranked first). This is a documented-edge simulation, not a forecast — see the caveat field.

Parameter	Type	Required	Notes
company_id	string	no	Remove a single company by id, name, or ticker. Exactly one of company_id/country/segment is required.
country	string	no	Remove every company headquartered in this country (case-insensitive exact match, e.g. 'Taiwan').
segment	string	no	Remove every company in this taxonomy segment id (see get_segments).
limit	integer	no	Max number of affected companies to return, zero-alternative ones first (1-100, default 20).

Screen for (customer, subsegment) pairs where the customer has exactly ONE documented supplier in that subsegment — the highest-value documented-concentration risk screen in the dataset. Optionally scoped to customers in one segment or country. Ranked by the sole supplier's downstream importance (its total documented customer count).

Parameter	Type	Required	Notes
segment	string	no	Restrict to customers in this taxonomy segment id (see get_segments). Omit for the whole dataset.
country	string	no	Restrict to customers headquartered in this country (case-insensitive exact match).
limit	integer	no	Max number of single-source pairs to return (1-100, default 25).

Rank companies by documented supply-chain degree: customer count (downstream reach), supplier count (upstream dependence), or total. CRITICAL: degree measures how well a relationship is DOCUMENTED in this curated dataset, not how critical the company actually is — a well-covered firm can outrank a more essential but obscure one. See the caveat field in every response.

Parameter	Type	Required	Notes
metric	string	no	'customers' = downstream reach, 'suppliers' = upstream dependence, 'total' = sum of both.
segment	string	no	Restrict to companies in this taxonomy segment id (see get_segments).
country	string	no	Restrict to companies headquartered in this country (case-insensitive exact match).
limit	integer	no	Max number of companies to return (1-50, default 15).

The shared-upstream question over a set of companies: given 2-15 company ids/tickers, or a segment id (uses every company in that segment), rank suppliers by how many of the input companies they documentedly serve (e.g. 'serves 9 of 12'), with each supplier's market position and country. Also reports how many input companies had no documented suppliers at all, since that makes a low overlap number

Parameter	Type	Required	Notes
company_ids	array	no	2-15 company ids, names, or tickers. Exactly one of company_ids/segment is required.
segment	string	no	Use every company in this taxonomy segment id instead of an explicit list (see get_segments).
limit	integer	no	Max number of ranked suppliers to return (1-100, default 20).

Full record for one M&A deal by id: title, type, value, announced date, status, all parties with their resolved company refs where a dataset id exists (and the raw party name where it does not), summary, sources, and the per-deal confidence flag. Use get_deals or find_deals_by_company to find a deal id first.

Parameter	Type	Required	Notes
id	string	yes	Deal id as returned by get_deals/find_deals_by_company, e.g. 'amd_xilinx_2020'.

Every M&A deal a company took part in, split by role (as acquirer, as target, or other). Matches by dataset id first, then falls back to case-insensitive name matching — necessary because a deal's target is frequently not itself a company in this dataset and carries a null id (e.g. AMD's acquisition of Xilinx lists acquirer id 'amd' but target id null, name 'Xilinx'). Each matched deal carries a m

Parameter	Type	Required	Notes
company	string	yes	Company id, exact name, or ticker to search for across all deal parties, e.g. 'amd', 'Xilinx', 'AMD'.

Aggregate view of the full 74-deal M&A corpus: counts by year (from announced date), by deal type, and by status; total and median disclosed value; and the largest deals by value. Value figures are computed only over the subset of deals with a disclosed value_usd and are never extrapolated to cover the undisclosed ones.

Parameter	Type	Required	Notes
top_n	integer	no	How many largest-by-value deals to return, 1-25 (default 10).

Ranks taxonomy segments by M&A activity by mapping each deal's parties onto their companies' segments (matching by id, then falling back to case-insensitive name), then aggregating deal count and disclosed value per segment. Deals whose parties cannot be resolved to any dataset company are counted in unmapped_deals rather than dropped, so thinly-covered segments aren't silently underrepresented.

Parameter	Type	Required	Notes
limit	integer	no	How many ranked segments to return, 1-12 (there are 12 segments total).
sort_by	string	no	Rank segments by number of deals ('deal_count') or by summed disclosed deal value ('value').

The honesty tool: what this dataset actually contains and where it is thin. Live-computed per-field coverage for companies and deals, last_verified staleness distribution, supply-chain edge coverage, data source mode, and a plain-words list of known limitations. Call this before treating an absence of a company, deal, or edge as evidence it doesn't exist in the real market.

No parameter schema on file.

Free

$0 forever

Every tool — any call limit is its publisher’s, not ours
No card, and mcprush charges nothing for it
Runs at its publisher’s own address — this marketplace is not in the path
Nothing to cap, because mcprush bills nothing

Nothing here is billable: mcprush charges nothing to install Wafergraph or to call it, at any volume.

ATool-list grade · score 96 / 100

Release 1.2.0 · scanned 20 Oct 2026

Graded from the tools this server lists, not from its source code.

Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.

Threat score100

Client score96

Findings0 threat · 0 capability

Capabilityminimal

Coveragemanifest

Verificationnot in this report

Surface digest8b7361c93aafd5366866c3fd164b4afe6be6c0a017acc17aa3cd3a12bbac9b71

Score vectorthreat 100 → client 96

Term	Level	What it prices	Points
capability-exposure	minimal	capability blast radius (minimal) — client exposure if the model is manipulated	−0
coverage-honesty	manifest	inspection depth (manifest) — how much of the target the scan could see	−4

score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.

What the scan could actually read

A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.

The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.

Tool surfaceread

Implementation sourcenot available

Package metadatanot available

Live transportnot available

The implementation source was not read — this reflects the declared tool metadata only.

Capability — what it could do if the model were manipulated

Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.

Tool	Capability tags	Why the tag was assigned
search_companies	no tags
get_company	no tags
get_segments	no tags
get_supply_chain	no tags
get_deals	no tags
compare_companies	no tags
get_country_exposure	no tags
find_chokepoints	no tags
analyze_portfolio_exposure	no tags
filter_companies	no tags
list_subsegments	no tags
get_subsegment	no tags
find_similar_companies	no tags
rank_by_market_cap	no tags
resolve_ticker	no tags
list_countries	no tags
get_country_profile	no tags
compare_countries	no tags
get_segment_leaders	no tags
get_upstream_concentration	no tags
find_paths_between	no tags
simulate_disruption	no tags
find_single_source_dependencies	no tags
rank_by_connectivity	no tags
find_common_suppliers	no tags
get_deal	no tags
find_deals_by_company	no tags
get_ma_activity_summary	no tags
find_consolidation_hotspots	no tags
get_dataset_stats	no tags

Toxic-flow graph

The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.

The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.

Supply chain and provenance

Integrityfirst-seen

Surface digest8b7361c93aafd536

Scanned2026-10-20

This is the first scan of this surface here, so there is nothing yet to compare it against.

Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.

Where are you running it?

Tool surface

Release history

Wafergraph MCP

What it does

Quickstart

Where are you running it?

Tool surface

What counts against your monthly calls

What the scan could actually read

Capability — what it could do if the model were manipulated

Toxic-flow graph

Supply chain and provenance

Release history

See also