Home / MCP registry index / com.wafergraph/wafergraph-mcp
Wafergraph MCP
com.wafergraph/wafergraph-mcp in the official MCP registry.
Endpoint https://wafergraph-mcp.jwpalm99.workers.dev/mcp. Source: github.com/jasonpalmer1/wafergraph-mcp.
The registry describes it as: Read-only MCP server for wafergraph.com's semiconductor & AI supply-chain data: 30 tools, no auth.
We read its 30 tools on 2026-10-22. Nothing in them matched our tool-poisoning rules.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
search_companies get_company get_segments get_supply_chain get_deals compare_companies get_country_exposure find_chokepoints analyze_portfolio_exposure filter_companies list_subsegments get_subsegment find_similar_companies rank_by_market_cap resolve_ticker list_countries get_country_profile compare_countries get_segment_leaders get_upstream_concentration find_paths_between simulate_disruption find_single_source_dependencies rank_by_connectivity find_common_suppliers get_deal find_deals_by_company get_ma_activity_summary find_consolidation_hotspots get_dataset_stats
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/com-wafergraph-wafergraph-mcp)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.