MCP server list / Wafergraph MCP
Read-only MCP server for wafergraph.com's semiconductor & AI supply-chain data: 5 tools, no auth.
Answered:
4 of 4 checks
- Status
- responds
- Typical response time
- 1,036.5 ms
- Last checked
- Latest check:
- This server answered at its latest check.Last checked · MCP initialize · 8s limit · HTTP 200 · answered in 1,304 ms.
- Address
- https://wafergraph-mcp.jwpalm99.workers.dev/
mcp - Listed in:
- official MCP registry
mcp_registry - Registry name
- com.wafergraph/
wafergraph-mcp - Transport
- streamable HTTP
streamable-http - Host
wafergraph-mcp.jwpalm99.workers.dev
An outside server from a public listing, not run by Licium; being listed here is not an endorsement.
What the server says about itself
We have not checked it.- Server name:
- wafergraph-mcp
- Version:
- 1.2.0
- MCP features it lists:
- tools
- Tool names:
search_companiesget_companyget_segmentsget_supply_chainget_dealscompare_companiesget_country_exposurefind_chokepointsanalyze_portfolio_exposurefilter_companieslist_subsegmentsget_subsegmentand 18 more
find_similar_companiesrank_by_market_capresolve_tickerlist_countriesget_country_profilecompare_countriesget_segment_leadersget_upstream_concentrationfind_paths_betweensimulate_disruptionfind_single_source_dependenciesrank_by_connectivityfind_common_suppliersget_dealfind_deals_by_companyget_ma_activity_summaryfind_consolidation_hotspotsget_dataset_stats
Reported Aug 17, 2026, 05:08 AM UTC.
Check history
oldest to newest; each row is one recorded check| Checked | Status | Took | Check |
|---|---|---|---|
| responds | 828 ms | MCP initialize · 8s limit · HTTP 200 | |
| responds | 1,090 ms | MCP initialize · 8s limit · HTTP 200 | |
| responds | 983 ms | MCP initialize · 8s limit · HTTP 200 | |
| responds | 1,304 ms | MCP initialize · 8s limit · HTTP 200 |
Need a different server, page or part?
Say what you need. We log your request. It can then go on the bounty board, where anyone can add money toward it. Or put a price on it and start today. Your words go with it.
Agents do the same with request_source or POST /v1/requests; this record is GET /v1/directory/{slug} with the slug from this page's address. Run this server? Register it as a part.
Latest recorded check ; every row above is one recorded call.