RQM Studio Jobs MCP Server

by rqmtechnologies Your server? Claim it

answering

RQM Studio Jobs is answering right now. Last checked 14 min ago. It exposes 44 tools.

Delegate 20 fail-closed RQM Studio quantum work products with fixed-request x402.

The linked repository no longer exists on GitHub — it was deleted or made private.

Uptime history 81 days of history · worst day 0%

81 days agonow

100.0%

Uptime 24h

91 of 91 checks

Tools

read from the server

199 ms

Response time

average over 24h

open, no key

Access

streamable-http

What changed 4

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 11 October 2026. No other catalogue keeps this.

25 Oct 3 tools changed the parameters they ask for diagnose_quantum_workflow, synthesize_two_qubit_target, translate_quantum_circuit

11 Oct a tool appeared describe_quantum_capabilities

This one has been quiet for a while

Quiet is not dead — but it is worth knowing when it wakes up, or when someone else takes it over. We watch the repository and tell you either way.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 14 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add studio --transport http https://jobs.rqmtechnologies.com/mcp/studio

Settings → Connectors → Add custom connector, then paste this address

https://jobs.rqmtechnologies.com/mcp/studio

~/.codex/config.toml

[mcp_servers.studio]
url = "https://jobs.rqmtechnologies.com/mcp/studio"

.cursor/mcp.json

{
  "mcpServers": {
    "studio": {
      "url": "https://jobs.rqmtechnologies.com/mcp/studio"
    }
  }
}

.vscode/mcp.json

{
  "servers": {
    "studio": {
      "type": "http",
      "url": "https://jobs.rqmtechnologies.com/mcp/studio"
    }
  }
}

Available tools 44

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

quantum

check_quantum_circuit

Check whether this quantum circuit is safe to send downstream, and return a bounded go, no-go, or unsupported decision with evidence.

quantum_circuit_assurance_report_v1

Problem: Validate, compile, and report bounded assurance evidence for OpenQASM 3. Input: JSON with source. Result: assurance outcome, warnings, normalized source and evidence. Limits: Local software evidence only; 3 verification qubits; 65536 source bytes.

quantum_cross_provider_portability_v1

Problem: Translate this supported OpenQASM 3 circuit to the supplied local toolchain format without silent gate substitution. Input: JSON with source, target format. Result: translated target artifact, explicit gate mapping, source and artifact digests. Limits: Local software evidence only; 65536 source bytes.

quantum_execution_plan_select_v1

Problem: Select a supported execution plan against the supplied cost, depth, duration limits, and weights. Input: JSON with plans, weights, maximum cost usd, maximum depth, maximum duration seconds. Result: ranked feasible plans, objective scores, selected plan identity. Limits: Local software evidence only; 4096 operations; 65536 request bytes.

quantum_failed_workflow_diagnosis_v1

Problem: Diagnose why this bounded quantum workflow failed and return supported corrective actions. Input: JSON with stage, error text. Result: failure class, evidence terms, bounded corrective actions. Limits: Local software evidence only; 65536 request bytes.

quantum_gate_basis_decomposition_v1

Problem: Decompose this supported circuit operation into the supplied bounded gate basis and verify the declared relation. Input: JSON with operation, target basis, phase context. Result: decomposition or withheld candidate, gate list, verification status. Limits: Local software evidence only; 65536 request bytes.

quantum_managed_simulator_v1

Problem: Execute a bounded RQM Circuit IR circuit on the managed local statevector simulator. Input: JSON with circuit ir. Result: typed counts, probabilities, simulation configuration evidence. Limits: Local software evidence only; 16 qubits; 250 operations.

quantum_openqasm3_preflight_v1

Problem: Parse, normalize, and assess OpenQASM 3 before downstream execution. Input: JSON with source. Result: go, no-go, or unsupported verdict, normalized source, warnings and evidence. Limits: Local software evidence only; 3 verification qubits; 65536 source bytes.

quantum_openqasm3_repair_v1

Problem: Repair this bounded OpenQASM 3 program only with the supplied conservative repair policy. Input: JSON with source, allowed repairs. Result: repaired or withheld source, exact edit list, post-repair validation verdict. Limits: Local software evidence only; 65536 source bytes.

quantum_optimization_preservation_audit_v1

Problem: Audit candidate optimization equivalence and qualitative coupling preservation. Input: JSON with original circuit, candidate circuit. Result: preserved or candidate-withheld outcome, input and output hashes, metric and.... Limits: Local software evidence only; 3 verification qubits; 65536 request bytes.

quantum_phase_aware_rewrite_v1

Problem: Rewrite this supported circuit under the supplied phase-equivalence and target constraints. Input: JSON with operation, target gate, phase context. Result: rewritten operation or original, candidate withholding, verification status. Limits: Local software evidence only; 65536 request bytes.

quantum_phase_sensitive_inspection_v1

Problem: Diagnose the phase, rotation, ordering, or convention difference between these supported operations. Input: JSON with reference, candidate, phase context. Result: difference kind, angle delta, correction hint. Limits: Local software evidence only; 65536 request bytes.

quantum_provider_readiness_check_v1

Problem: Accept or reject this bounded circuit for the supplied pinned provider target and readiness rules. Input: JSON with qubit count, operations, target, rules. Result: readiness verdict, rule results and blockers, target provenance. Limits: Local software evidence only; 4096 operations; 65536 request bytes.

quantum_provider_result_compare_v1

Problem: Compare these bounded provider results using the supplied normalization and difference rules. Input: JSON with left counts, right counts, normalization, rules. Result: normalized deltas, probability metrics, caller-rule verdict. Limits: Local software evidence only; 4096 operations; 65536 request bytes.

quantum_provider_target_compile_v1

Problem: Compile this bounded circuit to the supplied pinned provider target and return compatibility evidence. Input: JSON with qubit count, operations, target. Result: compiled artifact, gate mapping, pinned target snapshot and blockers. Limits: Local software evidence only; 4096 operations; 65536 request bytes.

quantum_simulation_anomaly_diagnostic_v1

Problem: Compare this bounded simulation result with the supplied expectation and anomaly rules. Input: JSON with observed probabilities, expected probabilities, maximum l1 error.... Result: L1 and bin deltas, violating outcomes, anomaly verdict. Limits: Local software evidence only; 65536 request bytes.

quantum_simulation_result_compare_v1

Problem: Compare these bounded simulation results using the supplied deterministic probability rules. Input: JSON with left probabilities, right probabilities, rules. Result: probability deltas, distance metrics, threshold verdict. Limits: Local software evidence only; 4096 operations; 65536 request bytes.

quantum_supported_circuit_equivalence_v1

Problem: Compare two RQM Circuit IR circuits within the supported verifier scope. Input: JSON with original circuit, candidate circuit. Result: equivalent, not-equivalent, or unsupported verdict, verification evidence, input.... Limits: Local software evidence only; 3 verification qubits; 65536 request bytes.

quantum_two_qubit_local_equivalence_v1

Problem: Classify this supported two-qubit operation by its bounded local-equivalence class and phase context. Input: JSON with operation, phase context. Result: local-equivalence class, canonical coordinates, explicit phase treatment. Limits: Local software evidence only; 2 qubits.

quantum_two_qubit_target_synthesis_v1

Problem: Choose and verify a bounded target-basis implementation for this supported two-qubit operation under supplied objectives. Input: JSON with operation, target basis, phase context, objectives. Result: verified circuit or original-retained outcome, gate count and depth, class and.... Limits: Local software evidence only; 2 qubits.

quantum_verified_circuit_optimization_v1

Problem: Optimize RQM Circuit IR and return the original unless preservation is verified. Input: JSON with circuit. Result: verified candidate or original fallback, metric deltas, preservation evidence. Limits: Local software evidence only; 3 verification qubits; 65536 request bytes.

buyer

list_buyer_jobs

Return complete agent discovery contracts and readiness for the exact 20/20/20 RQM specialist work portfolio.

run_buyer_job

Quote, settle, and submit one allowlisted WaveEngine, Studio, or Robotics buyer job using x402.

search_buyer_jobs

Select RQM buyer jobs from work-language requests using deterministic semantic scoring over instructions, examples, outputs, and next steps.

diagnose

diagnose_quantum_phase

Find the phase, rotation, ordering, or convention bug in this quantum operation.

diagnose_quantum_workflow

Diagnose why this quantum workflow failed and return bounded corrective actions.

job

get_job_result

Read one completed and already-settled product result.

get_job_status

Read one authorized Wave or Studio managed-simulator job.

account

get_account_balance

Read the authenticated canonical Account Core prepaid USD balance.

audit

audit_quantum_transformation

Audit what another compiler or AI changed, and withhold the candidate unless preservation is verified.

cancel

cancel_job

Request cancellation of one authorized product job.

capabilities

list_capabilities

Describe the preserved v0/v1 surface or the dynamic v2/v3 Wave catalog.

capability

get_capability

Return one full approved public Wave capability descriptor.

classify

classify_two_qubit_operation

Classify this two-qubit operation by its nonlocal content and local-equivalence class.

compare

compare_quantum_circuits

Tell me whether these two quantum circuits implement the same operation within the stated phase context.

describe

describe_quantum_capabilities

Free, anonymous API-owned scientific capability contracts and domain suggestions. Start here before choosing or funding a quantum job. Inspect separate source, installed, hosted, simulator, live-QPU and public coverage; unknown means unverified. Read schemas, examples and limits; unavailable chemistry, cryptography or hybrid workflows must not be replaced with Bell or promised as execution. This finite registry is not the complete roadmap. Workflow tool references do not promise availability on this endpoint or eligibility for the caller. No account, balance, job, private policy, quote, reservation or hardware execution is accessed. Existing authenticated tools own those operations.

funding

create_funding_session

Create an idempotent Stripe Checkout URL for human prepaid funding.

optimize

optimize_quantum_circuit

Make this quantum circuit smaller, but return the original unless equivalence is verified.

quote

quote_job

Return a preserved v0 placeholder or a durable v1 Account Core USD quote.

repair

repair_openqasm3

Repair this invalid OpenQASM 3 program conservatively, or tell me exactly why a safe repair cannot be made.

studio

get_studio_receipt

Retrieve the durable Account Core receipt for one settled Studio reservation.

submit

submit_quantum_job

Reserve an exact quote and submit one bounded managed-simulator job.

synthesize

synthesize_two_qubit_target

Choose the best verified target-native implementation of this two-qubit block.

translate

translate_quantum_circuit

Translate this circuit to Qiskit/OpenQASM 3 or Braket without silently changing its supported semantics.

Endpoints

URL	Transport	State	Latency	Checked
https://jobs.rqmtechnologies.com/mcp/studio	streamable-http	answering	268 ms	14 min ago

Alternatives to RQM Studio Jobs

same job, measured the same way

RQM WaveEngine Jobs

by rqmtechnologies

Delegate 20 typed, evidence-backed WaveEngine signal work products with fixed-request x402.

34 tools answering

RQM Jobs MCP

by rqmtechnologies

Delegate 60 specialist work products: 20 WaveEngine, 20 RQM Studio, and 20 RQM Robotics jobs.

39 tools answering

Aivonic

by aivonic

Do business with Aivonic: pricing, products, check availability, book a demo, request a quote.

5 tools answering

Sabag 3D Studio

by co-sabag3d

3D printing studio in Israel: services, past projects, products, FAQ, search and quote requests.

11 tools answering

Taskbounty MCP Server

by eliottreich

Hire agents, request quotes, delegate funded tasks, submit work, and collaborate on missions.

211 installs/wk local only

socseal settlement door

by socseal

Read-only settlement proof for agents: prove a txid MINED, post-quantum signed. Fail-closed.

local only

Standup Mr

by jubstaaa

Standup notes from merge request state, with the failed job's error lines.

75 installs/wk answering

Telegram Bridge

by antonio-castellon

Stdio MCP bridge to Telegram with scrubbing and a fail-closed allowlist.

335 installs/wk local only

RQM Studio Jobs — questions

Answers built from our own checks of this server.

What can RQM Studio Jobs do?

It exposes 44 tools, read directly from the server on our last check. Among them: audit_quantum_transformation, cancel_job, check_quantum_circuit, classify_two_qubit_operation, compare_quantum_circuits, create_funding_session and 38 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

What is RQM Studio Jobs mostly used for?

Its tools cluster around quantum, buyer and diagnose. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.

Is RQM Studio Jobs working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 199 ms. The bar chart above shows every period we have measured.

Is RQM Studio Jobs still maintained?

The linked repository no longer exists on GitHub — it was deleted or made private. We show this because it changes what you can expect: an unmaintained server may keep answering for months and then stop without warning.

How do I connect RQM Studio Jobs?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does RQM Studio Jobs need an API key?

No. RQM Studio Jobs completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 44 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is RQM Studio Jobs?

It answers our handshake in 199 ms on average, which is faster than 67% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.