stim-mcp-server
Provides an MCP (Model Context Protocol) server that wraps Google’s Stim stabilizer circuit simulator, exposing multiple tools (health check, circuit creation/appending, sampling, error analysis, diagram generation, noise injection, and standard circuit generation) over MCP transports including HTTP/SSE and stdio, plus a hosted Google Cloud Run instance.
Score Breakdown
⚙ Agent Friendliness
🔒 Security
README explicitly states the shared remote server has no authentication and no access control; circuit IDs are random tokens but should not be relied on for strong privacy. Tool invocations are logged anonymously by tool name only (no arguments/circuit data). No details provided about TLS enforcement beyond using HTTPS in the hosted URL; no rate-limit details; no discussion of auth for local deployments.
⚡ Reliability
Best When
You want an experimentation/beta MCP tool for quantum circuit simulation and analysis with an LLM client that can call MCP tools over HTTP/SSE or stdio.
Avoid When
You need strong access control, circuit-data privacy on a multi-tenant remote service, or you require an explicit documented retry/idempotency contract for reliability.
Use Cases
- • LLM-assisted exploration of stabilizer quantum circuits via conversational tool calls
- • Programmatic generation and validation of Stim circuit strings
- • Sampling measurement statistics from quantum stabilizer circuits
- • Building and analyzing detector error models to find short logical error paths
- • Adding noise models (e.g., depolarizing/X error) and comparing resulting statistics
Not For
- • Processing sensitive or confidential circuit data on the shared hosted instance
- • Mission-critical workloads requiring strong availability guarantees
- • Environments that require authenticated, access-controlled API usage for compliance
Interface
Authentication
README states the shared server has no authentication and no access control; circuit IDs are UUIDv4-like tokens intended to make guessing impractical, but this is not equivalent to access control.
Pricing
No pricing information provided; hosted instance appears experimental with scale-to-zero behavior.
Agent Metadata
Known Gotchas
- ⚠ Hosted server scales to zero; first request after inactivity may take 5–10 seconds (agents may time out if they assume warm latency).
- ⚠ In-memory circuit sessions are lost on scale-down, so long-lived workflows should recreate circuits or use local deployment.
- ⚠ Remote server has no authentication/access control; avoid sensitive circuit data.
Alternatives
Full Evaluation Report
Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for stim-mcp-server.
AI-powered analysis · PDF + markdown · Delivered within 30 minutes
Package Brief
Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.
Delivered within 10 minutes
Score Monitoring
Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.
Continuous monitoring
Scores are editorial opinions as of 2026-04-04.