get_track_record — Silicon Analysts MCP Tool Read-only
get_track_record
(get track record) is one of 21 tools on the
Silicon Analysts
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_track_record from your client
- Claude Code Silicon Analysts get_track_record run in your project directory
- Claude Desktop Silicon Analysts get_track_record ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Silicon Analysts get_track_record ~/.cursor/mcp.json
- VS Code Silicon Analysts get_track_record .vscode/mcp.json
- Zed Silicon Analysts get_track_record ~/.config/zed/settings.json
- Windsurf Silicon Analysts get_track_record ~/.codeium/windsurf/mcp_config.json
- Cline Silicon Analysts get_track_record ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Silicon Analysts get_track_record ~/.gemini/settings.json
- Grok Silicon Analysts get_track_record .mcp.json (in your project root)
- ChatGPT Silicon Analysts get_track_record Settings → Connectors → Advanced → Developer mode
- Claude.ai Silicon Analysts get_track_record Settings → Connectors → Add custom connector
- LangChain Silicon Analysts get_track_record pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http silicon-analysts https://siliconanalysts.com/api/mcp
Other tools on this server
- get_accelerator_costs
- calculate_chip_cost
- estimate_lead_time
- get_hbm_market_data
- get_market_pulse
- get_wafer_pricing
- get_packaging_costs
- get_hbm_qualification
- get_foundry_allocation
- get_foundry_economics
- get_recent_changes
- get_market_dataset
- get_market_intelligence
- get_market_advantage
- get_benchmark_history
- get_fab_capacity
- get_forecasts
- get_wfe_signals
- get_fab_events
- get_policy_events
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.