Home / MCP registry index / com.quantum-expectations/quantum-expectations
Quantum Expectations
com.quantum-expectations/quantum-expectations in the official MCP registry.
Endpoint https://www.quantum-expectations.com/api/mcp.
The registry describes it as: Quantum error-correction feasibility: success probability, qubit overhead, records, trends.
We read its 13 tools on 2026-10-26. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
compute_expectation compute_required_error_rate compute_fault_tolerant_resources compare_hardware_scenarios list_current_quantum_computers list_quops_scores list_hardware_timings compute_quantum_volume_rate fit_historic_series list_example_algorithms list_qldpc_codes get_historic_series get_agent_brief
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/com-quantum-expectations-quantum-expectations)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.