Home / MCP registry index / com.rqmtechnologies/studio
RQM Studio Jobs
com.rqmtechnologies/studio in the official MCP registry.
Endpoint https://jobs.rqmtechnologies.com/mcp/studio. Source: github.com/RQM-Technologies-dev/RQM-Jobs-MCP.
The registry describes it as: Delegate 20 fail-closed RQM Studio quantum work products with fixed-request x402.
On 2026-10-28 we read its 44 tools, but part of what it advertised was cut before our rules saw it: a description or schema past the size we read, more tools than we read, or a tool list split across pages. Nothing in the part we read matched, but the rest was not checked: this is not a clean result.
Tools it advertises
describe_quantum_capabilities list_buyer_jobs search_buyer_jobs list_capabilities get_capability run_buyer_job quantum_failed_workflow_diagnosis_v1 quantum_phase_sensitive_inspection_v1 quantum_openqasm3_preflight_v1 quantum_simulation_anomaly_diagnostic_v1 quantum_openqasm3_repair_v1 quantum_gate_basis_decomposition_v1 quantum_cross_provider_portability_v1 quantum_phase_aware_rewrite_v1 quantum_supported_circuit_equivalence_v1 quantum_provider_result_compare_v1 quantum_simulation_result_compare_v1 quantum_two_qubit_local_equivalence_v1 quantum_verified_circuit_optimization_v1 quantum_two_qubit_target_synthesis_v1 quantum_provider_target_compile_v1 quantum_execution_plan_select_v1 quantum_circuit_assurance_report_v1 quantum_optimization_preservation_audit_v1 quantum_managed_simulator_v1 quantum_provider_readiness_check_v1 quote_job check_quantum_circuit compare_quantum_circuits repair_openqasm3 optimize_quantum_circuit diagnose_quantum_workflow audit_quantum_transformation translate_quantum_circuit diagnose_quantum_phase synthesize_two_qubit_target classify_two_qubit_operation get_account_balance get_studio_receipt create_funding_session submit_quantum_job get_job_status get_job_result cancel_job
Rather than checking back: subscribe to this server's tool changes (a feed, no account and no address needed). Tool names and dates only, never what a tool says.
Run this server? Show the check in your README
The badge reflects the latest read: 
[](https://lazaretto.dev/mcp-registry/com-rqmtechnologies-studio)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.
Related
| The Stall ai.intuitek.the-stall/the-stall | 200 tools, nothing matched 2026-10-22 |
| SAP MCP Server ai.oobeprotocol.sap.mcp/sap-mcp | 200 tools, nothing matched 2026-10-22 |
| Citiview Agent Market com.citiviewgroup.mcp/agent-market | 200 tools, nothing matched 2026-10-26 |
| ScorpTech x402 API com.it.scorptech/x402 | 200 tools, nothing matched 2026-10-26 |
| Apex Edge — x402-paid machine services dev.pages.nonsynthetic/apex-edge | 200 tools, nothing matched 2026-10-23 |
| x402 Factory io.github.praneeth12098/x402-factory | 200 tools, nothing matched 2026-10-26 |