list_hardware_timings — Quantum Expectations MCP Tool Read-only
list_hardware_timings
(list hardware timings) is one of 13 tools on the
Quantum Expectations
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call list_hardware_timings from your client
- Claude Code Quantum Expectations list_hardware_timings run in your project directory
- Claude Desktop Quantum Expectations list_hardware_timings ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Quantum Expectations list_hardware_timings ~/.cursor/mcp.json
- VS Code Quantum Expectations list_hardware_timings .vscode/mcp.json
- Zed Quantum Expectations list_hardware_timings ~/.config/zed/settings.json
- Windsurf Quantum Expectations list_hardware_timings ~/.codeium/windsurf/mcp_config.json
- Cline Quantum Expectations list_hardware_timings ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Quantum Expectations list_hardware_timings ~/.gemini/settings.json
- Grok Quantum Expectations list_hardware_timings .mcp.json (in your project root)
- ChatGPT Quantum Expectations list_hardware_timings Settings → Connectors → Advanced → Developer mode
- Claude.ai Quantum Expectations list_hardware_timings Settings → Connectors → Add custom connector
- LangChain Quantum Expectations list_hardware_timings pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http quantum-expectations https://www.quantum-expectations.com/api/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.