
Servidor MCP de wafergraph
Qué servidores MCP son de wafergraph, del registro oficial y encontrados preguntando a su propio dominio, si responden y qué ofrecen. Un programa comprobó cada dato; nada está copiado de la página del producto.
leído el 2026-10-19
- Nombre en el registrocom.wafergraph/wafergraph-mcpverificado en el registro MCP
El nombre en el registro está bajo wafergraph.com. El registro solo permite usar ese espacio de nombres a quien demuestra control del dominio por DNS o HTTP.
- Estadorespondecomprobado el 2026-10-19
- Herramientas30
- El servidor se llamawafergraph-mcp
- Versión del servidor1.2.0
- Versión del protocolo2025-06-18
El 2026-10-19 el servidor respondió a initialize y tools/list sin iniciar sesión. Primera respuesta en 862 ms.
- Sus herramientas hacen trace which companies depend on a given supplier, pero no read the weekly chokepoint earnings brief.
Una vez conectado
- Para "trace which companies depend on a given supplier", la primera llamada probable es get_supply_chain.
Lo dicen reglas a partir de las mediciones de arriba. La primera llamada probable la elige un modelo de la lista de herramientas; lee su descripción antes de fiarte.
- Nota INITE MCP72 de 100responde 100 · hace el trabajo 50 · definiciones 83 · contexto 80 · uso 0 · conexión 100
- Qué puede hacer un agente con él1 de 2 casos de uso
- Respondióel 100% de los días10 de 10 comprobaciones diarias
- Mediana de la primera respuesta988 ms
- Espacio en el contexto del agente≈ 6322 tokenslas definiciones de todas sus herramientas (30), que el agente lleva en cada turno
- Definiciones de herramientasB · 83 de 100
- Resultados tipados0 de 30 herramientasdeclaran outputSchema: el resultado llega tipado y se lee de una vez
- Sin indicar si solo lee o puede destruir: 30 de 30
Qué puede hacer un agente con él
- puede · trace which companies depend on a given supplier
- no está claro · compare market share and chokepoint exposure by segment
- no puede · read the weekly chokepoint earnings brief
Cada caso de uso del producto se le preguntó a Jev junto con la lista de herramientas de este servidor: ¿puede un agente hacerlo con estas herramientas?
Conviene revisar
Ninguna de las cinco señales de alerta en estas definiciones.
Un programa comprueba el servidor una vez al día: initialize y tools/list, sin modelo. Los tokens son la longitud de las definiciones, a unos cuatro caracteres por token. La nota promedia seis comprobaciones del nombre, la descripción, el esquema y las anotaciones de cada herramienta; dice lo bien descritas que están, no si funcionan. La nota pondera solo lo medido: si responde (25%), si hace el trabajo del producto (25%), definiciones (20%), contexto (10%), uso (10%) y lo fácil que es conectarse (10%). Lo que no se midió queda fuera, y una instrucción oculta limita la nota a 40. El estado de los servidores MCP de los proveedores: método y números →
search_companiesSearch 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_companyFull 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…
get_segmentsThe 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…
get_supply_chainWalk 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.
get_dealsSearch 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.
compare_companiesSide-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.
get_country_exposureGeographic 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…
find_chokepointsRank 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…
analyze_portfolio_exposureGiven 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…
filter_companiesStructured 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…
list_subsegmentsEvery 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_subsegmentAll 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…
find_similar_companiesNearest 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…
rank_by_market_capTop 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…
resolve_tickerBatch-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…
list_countriesEvery 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…
get_country_profileDeep 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…
compare_countriesSide-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…
get_segment_leadersWho 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…
get_upstream_concentrationFor 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…
find_paths_betweenEvery 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…
simulate_disruptionRemove 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…
find_single_source_dependenciesScreen 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…
rank_by_connectivityRank 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…
find_common_suppliersThe 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')…
get_dealFull 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…
find_deals_by_companyEvery 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…
get_ma_activity_summaryAggregate 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…
find_consolidation_hotspotsRanks 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…
get_dataset_statsThe 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…
Cómo conectar
Añade el servidor a la configuración de tu cliente MCP. Claude Desktop, Cursor y la mayoría de los demás clientes leen este formato:
{
"mcpServers": {
"wafergraph-mcp": {
"type": "http",
"url": "https://wafergraph-mcp.jwpalm99.workers.dev/mcp"
}
}
}Añadirlo
Claude Code, en una terminal
claude mcp add --transport http wafergraph https://wafergraph-mcp.jwpalm99.workers.dev/mcpAñadir a CursorAñadir a VS Code
claude.ai, ChatGPT y otros clientes: añade https://wafergraph-mcp.jwpalm99.workers.dev/mcp como conector personalizado en los ajustes.
- https://mcp.wafergraph.com/mcpresponde, 30 herramientasno está en el registro oficial: respondió al preguntarle
Cada línea es algo que un programa encontró al buscar: la entrada del registro, la respuesta del propio servidor, una especificación que se puede leer. Si falta una línea, es que no la encontramos, no que no exista.
Cookies
Antes de contar esta visita
La analítica y la medición de anuncios nos dicen qué páginas y cuáles de nuestros anuncios cumplen su función: Google Analytics y Google Ads, el píxel de Meta, Yandex Metrica y un identificador propio. No se guarda nada hasta que respondas, y rechazar no cambia nada del sitio.