get_supplier_exposure — epitaxy MCP Tool Read-only
get_supplier_exposure
(get supplier exposure) is one of 5 tools on the
epitaxy
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_supplier_exposure from your client
- Claude Code epitaxy get_supplier_exposure run in your project directory
- Claude Desktop epitaxy get_supplier_exposure ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor epitaxy get_supplier_exposure ~/.cursor/mcp.json
- VS Code epitaxy get_supplier_exposure .vscode/mcp.json
- Zed epitaxy get_supplier_exposure ~/.config/zed/settings.json
- Windsurf epitaxy get_supplier_exposure ~/.codeium/windsurf/mcp_config.json
- Cline epitaxy get_supplier_exposure ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI epitaxy get_supplier_exposure ~/.gemini/settings.json
- Grok epitaxy get_supplier_exposure .mcp.json (in your project root)
- ChatGPT epitaxy get_supplier_exposure Settings → Connectors → Advanced → Developer mode
- Claude.ai epitaxy get_supplier_exposure Settings → Connectors → Add custom connector
- LangChain epitaxy get_supplier_exposure pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http epitaxy https://drugs.crossgrain.xyz/v1/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.