# RQM Studio Jobs (remote · jobs.rqmtechnologies.com)

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

- Trust score: 81/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- remote · `jobs.rqmtechnologies.com`: 81/100 (this document), [markdown](https://verifymcp.io/servers/com-rqmtechnologies-studio/mcp-studio.md), [page](https://verifymcp.io/servers/com-rqmtechnologies-studio/mcp-studio)

## Channel facts

- Endpoint: `https://jobs.rqmtechnologies.com/mcp/studio`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.6.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-20.

- **Endpoint Security**: 77/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 60/100
  - AI-judged instruction clarity (fair).
  - Tool/resource definitions use about 3231 tokens (~75/item across 43 items; 43 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 100/100
  - No destabilizing schema changes in the last 30 days.
- **Tool Coverage**: 71/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 43 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 43 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the RQM Studio Jobs MCP server?

RQM Studio Jobs is a hosted endpoint at https://jobs.rqmtechnologies.com/mcp/studio, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

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

### Cursor

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

### VS Code

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

### Codex

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

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-rqmtechnologies-studio": {
      "type": "remote",
      "url": "https://jobs.rqmtechnologies.com/mcp/studio",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-rqmtechnologies-studio --url 'https://jobs.rqmtechnologies.com/mcp/studio' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-rqmtechnologies-studio:
    url: "https://jobs.rqmtechnologies.com/mcp/studio"
```

### Netclaw

```json
{
  "McpServers": {
    "com-rqmtechnologies-studio": {
      "Transport": "http",
      "Url": "https://jobs.rqmtechnologies.com/mcp/studio"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-rqmtechnologies-studio -t streamable-http -u 'https://jobs.rqmtechnologies.com/mcp/studio'
```

### Other

```json
{
  "mcpServers": {
    "com-rqmtechnologies-studio": {
      "type": "http",
      "url": "https://jobs.rqmtechnologies.com/mcp/studio"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-19 (score 81, 0)

- [security] Stability: 0.97 → pass

### 2026-09-18 (score 81, +1)

No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-16 (score 80, +1)

No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-14 (score 79, +1)

No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-12 (score 78, +7)

- [security improvement] Authorization: unverified → partial

### 2026-09-11 (score 71, +1)

No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-09 (score 70, +2)

- [security] Tool “list_buyer_jobs” rewrote its description, which is the text the model reads
- [security] Tool “quantum_circuit_assurance_report_v1” rewrote its description, which is the text the model reads
- [security] Tool “quantum_cross_provider_portability_v1” rewrote its description, which is the text the model reads
- [security] Tool “quantum_execution_plan_select_v1” rewrote its description, which is the text the model reads
- [security] Tool “quantum_failed_workflow_diagnosis_v1” rewrote its description, which is the text the model reads
- [security] Tool “quantum_gate_basis_decomposition_v1” rewrote its description, which is the text the model reads
- [security] Tool “quantum_managed_simulator_v1” rewrote its description, which is the text the model reads
- [security] Tool “quantum_openqasm3_preflight_v1” rewrote its description, which is the text the model reads
- [security] Tool “quantum_openqasm3_repair_v1” rewrote its description, which is the text the model reads
- [security] Tool “quantum_optimization_preservation_audit_v1” rewrote its description, which is the text the model reads
- [security] Tool “quantum_phase_aware_rewrite_v1” rewrote its description, which is the text the model reads
- [security] Tool “quantum_phase_sensitive_inspection_v1” rewrote its description, which is the text the model reads
- [security] Tool “quantum_provider_readiness_check_v1” rewrote its description, which is the text the model reads
- [security] Tool “quantum_provider_result_compare_v1” rewrote its description, which is the text the model reads
- [security] Tool “quantum_provider_target_compile_v1” rewrote its description, which is the text the model reads
- [security] Tool “quantum_simulation_anomaly_diagnostic_v1” rewrote its description, which is the text the model reads
- [security] Tool “quantum_simulation_result_compare_v1” rewrote its description, which is the text the model reads
- [security] Tool “quantum_supported_circuit_equivalence_v1” rewrote its description, which is the text the model reads
- [security] Tool “quantum_two_qubit_local_equivalence_v1” rewrote its description, which is the text the model reads
- [security] Tool “quantum_two_qubit_target_synthesis_v1” rewrote its description, which is the text the model reads
- [security] Tool “quantum_verified_circuit_optimization_v1” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 58 → 75
- [cosmetic] Tool “list_buyer_jobs” changed its title: List production-live RQM buyer jobs → List RQM buyer jobs
- [cosmetic] Tool “quantum_circuit_assurance_report_v1” changed its title: Run circuit-assurance-report-v1 → Circuit assurance report
- [cosmetic] Tool “quantum_cross_provider_portability_v1” changed its title: Run cross-provider-portability-v1 → Cross Provider Portability
- [cosmetic] Tool “quantum_execution_plan_select_v1” changed its title: Run quantum.execution-plan-select.v1 → Execution Plan Select
- [cosmetic] Tool “quantum_failed_workflow_diagnosis_v1” changed its title: Run failed-workflow-diagnosis-v1 → Failed Workflow Diagnosis
- [cosmetic] Tool “quantum_gate_basis_decomposition_v1” changed its title: Run quantum.gate-basis-decomposition.v1 → Gate Basis Decomposition
- [cosmetic] Tool “quantum_managed_simulator_v1” changed its title: Run managed-simulator-v1 → Managed simulator
- [cosmetic] Tool “quantum_openqasm3_preflight_v1” changed its title: Run openqasm3-preflight-v1 → OpenQASM 3 preflight
- [cosmetic] Tool “quantum_openqasm3_repair_v1” changed its title: Run openqasm3-repair-v1 → Openqasm3 Repair
- [cosmetic] Tool “quantum_optimization_preservation_audit_v1” changed its title: Run optimization-preservation-audit-v1 → Optimization preservation audit
- [cosmetic] Tool “quantum_phase_aware_rewrite_v1” changed its title: Run quantum.phase-aware-rewrite.v1 → Phase Aware Rewrite
- [cosmetic] Tool “quantum_phase_sensitive_inspection_v1” changed its title: Run phase-sensitive-inspection-v1 → Phase Sensitive Inspection
- [cosmetic] Tool “quantum_provider_readiness_check_v1” changed its title: Run quantum.provider-readiness-check.v1 → Provider Readiness Check
- [cosmetic] Tool “quantum_provider_result_compare_v1” changed its title: Run quantum.provider-result-compare.v1 → Provider Result Compare
- [cosmetic] Tool “quantum_provider_target_compile_v1” changed its title: Run quantum.provider-target-compile.v1 → Provider Target Compile
- [cosmetic] Tool “quantum_simulation_anomaly_diagnostic_v1” changed its title: Run quantum.simulation-anomaly-diagnostic.v1 → Simulation Anomaly Diagnostic
- [cosmetic] Tool “quantum_simulation_result_compare_v1” changed its title: Run quantum.simulation-result-compare.v1 → Simulation Result Compare
- [cosmetic] Tool “quantum_supported_circuit_equivalence_v1” changed its title: Run supported-circuit-equivalence-v1 → Supported circuit equivalence
- [cosmetic] Tool “quantum_two_qubit_local_equivalence_v1” changed its title: Run two-qubit-local-equivalence-v1 → Two Qubit Local Equivalence
- [cosmetic] Tool “quantum_two_qubit_target_synthesis_v1” changed its title: Run two-qubit-target-synthesis-v1 → Two Qubit Target Synthesis
- [cosmetic] Tool “quantum_verified_circuit_optimization_v1” changed its title: Run verified-circuit-optimization-v1 → Verified circuit optimization
- [cosmetic] Tool “search_buyer_jobs” changed its title: Search production-live RQM buyer jobs → Search RQM buyer jobs

### 2026-09-07 (score 68, +1)

No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (43)

### `list_buyer_jobs` (~54 tokens)

List RQM buyer jobs

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

Input parameters:

- `product` (string)
- `schema_version` (string)
- `surface` (string)

### `search_buyer_jobs` (~70 tokens)

Search RQM buyer jobs

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

Input parameters:

- `limit` (integer)
- `product` (string)
- `query` (string, required)
- `schema_version` (string)
- `surface` (string)

### `list_capabilities` (~27 tokens)

List RQM job capabilities

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

### `get_capability` (~18 tokens)

Get one RQM job capability

Return one full approved public Wave capability descriptor.

### `run_buyer_job` (~81 tokens)

Run any RQM buyer job

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

Input parameters:

- `capability_id` (string, required)
- `idempotency_key` (string, required)
- `max_total_price` (string, required)
- `product` (string, required)
- `request` (object, required)
- `schema_version` (string, required)

### `quantum_failed_workflow_diagnosis_v1` (~98 tokens)

Failed Workflow Diagnosis

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.

Input parameters:

- `idempotency_key` (string, required)
- `max_total_price` (string, required)
- `request` (object, required)
- `schema_version` (string, required)

### `quantum_phase_sensitive_inspection_v1` (~100 tokens)

Phase Sensitive Inspection

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.

Input parameters:

- `idempotency_key` (string, required)
- `max_total_price` (string, required)
- `request` (object, required)
- `schema_version` (string, required)

### `quantum_openqasm3_preflight_v1` (~109 tokens)

OpenQASM 3 preflight

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.

Input parameters:

- `idempotency_key` (string, required)
- `max_total_price` (string, required)
- `request` (object, required)
- `schema_version` (string, required)

### `quantum_simulation_anomaly_diagnostic_v1` (~107 tokens)

Simulation Anomaly Diagnostic

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.

Input parameters:

- `idempotency_key` (string, required)
- `max_total_price` (string, required)
- `request` (object, required)
- `schema_version` (string, required)

### `quantum_openqasm3_repair_v1` (~107 tokens)

Openqasm3 Repair

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.

Input parameters:

- `idempotency_key` (string, required)
- `max_total_price` (string, required)
- `request` (object, required)
- `schema_version` (string, required)

### `quantum_gate_basis_decomposition_v1` (~105 tokens)

Gate Basis Decomposition

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.

Input parameters:

- `idempotency_key` (string, required)
- `max_total_price` (string, required)
- `request` (object, required)
- `schema_version` (string, required)

### `quantum_cross_provider_portability_v1` (~108 tokens)

Cross Provider Portability

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.

Input parameters:

- `idempotency_key` (string, required)
- `max_total_price` (string, required)
- `request` (object, required)
- `schema_version` (string, required)

### `quantum_phase_aware_rewrite_v1` (~102 tokens)

Phase Aware Rewrite

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.

Input parameters:

- `idempotency_key` (string, required)
- `max_total_price` (string, required)
- `request` (object, required)
- `schema_version` (string, required)

### `quantum_supported_circuit_equivalence_v1` (~109 tokens)

Supported circuit equivalence

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.

Input parameters:

- `idempotency_key` (string, required)
- `max_total_price` (string, required)
- `request` (object, required)
- `schema_version` (string, required)

### `quantum_provider_result_compare_v1` (~106 tokens)

Provider Result Compare

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.

Input parameters:

- `idempotency_key` (string, required)
- `max_total_price` (string, required)
- `request` (object, required)
- `schema_version` (string, required)

### `quantum_simulation_result_compare_v1` (~103 tokens)

Simulation Result Compare

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.

Input parameters:

- `idempotency_key` (string, required)
- `max_total_price` (string, required)
- `request` (object, required)
- `schema_version` (string, required)

### `quantum_two_qubit_local_equivalence_v1` (~105 tokens)

Two Qubit Local Equivalence

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.

Input parameters:

- `idempotency_key` (string, required)
- `max_total_price` (string, required)
- `request` (object, required)
- `schema_version` (string, required)

### `quantum_verified_circuit_optimization_v1` (~104 tokens)

Verified circuit optimization

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.

Input parameters:

- `idempotency_key` (string, required)
- `max_total_price` (string, required)
- `request` (object, required)
- `schema_version` (string, required)

### `quantum_two_qubit_target_synthesis_v1` (~115 tokens)

Two Qubit Target Synthesis

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.

Input parameters:

- `idempotency_key` (string, required)
- `max_total_price` (string, required)
- `request` (object, required)
- `schema_version` (string, required)

### `quantum_provider_target_compile_v1` (~107 tokens)

Provider Target Compile

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.

Input parameters:

- `idempotency_key` (string, required)
- `max_total_price` (string, required)
- `request` (object, required)
- `schema_version` (string, required)

### `quantum_execution_plan_select_v1` (~116 tokens)

Execution Plan Select

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.

Input parameters:

- `idempotency_key` (string, required)
- `max_total_price` (string, required)
- `request` (object, required)
- `schema_version` (string, required)

### `quantum_circuit_assurance_report_v1` (~103 tokens)

Circuit assurance report

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.

Input parameters:

- `idempotency_key` (string, required)
- `max_total_price` (string, required)
- `request` (object, required)
- `schema_version` (string, required)

### `quantum_optimization_preservation_audit_v1` (~107 tokens)

Optimization preservation audit

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.

Input parameters:

- `idempotency_key` (string, required)
- `max_total_price` (string, required)
- `request` (object, required)
- `schema_version` (string, required)

### `quantum_managed_simulator_v1` (~99 tokens)

Managed simulator

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.

Input parameters:

- `idempotency_key` (string, required)
- `max_total_price` (string, required)
- `request` (object, required)
- `schema_version` (string, required)

### `quantum_provider_readiness_check_v1` (~110 tokens)

Provider Readiness Check

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.

Input parameters:

- `idempotency_key` (string, required)
- `max_total_price` (string, required)
- `request` (object, required)
- `schema_version` (string, required)

### `quote_job` (~24 tokens)

Quote an RQM job

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

### `check_quantum_circuit` (~72 tokens)

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

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

Input parameters:

- `idempotency_key` (string, required)
- `max_total_price` (string, required)
- `payment_rail` (string)
- `request` (object, required)

### `compare_quantum_circuits` (~64 tokens)

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

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

Input parameters:

- `idempotency_key` (string, required)
- `max_total_price` (string, required)
- `payment_rail` (string)
- `request` (object, required)

### `repair_openqasm3` (~70 tokens)

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

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

Input parameters:

- `idempotency_key` (string, required)
- `max_total_price` (string, required)
- `payment_rail` (string)
- `request` (object, required)

### `optimize_quantum_circuit` (~62 tokens)

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

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

Input parameters:

- `idempotency_key` (string, required)
- `max_total_price` (string, required)
- `payment_rail` (string)
- `request` (object, required)

### `diagnose_quantum_workflow` (~58 tokens)

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

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

Input parameters:

- `idempotency_key` (string, required)
- `max_total_price` (string, required)
- `payment_rail` (string)
- `request` (object, required)

### `audit_quantum_transformation` (~64 tokens)

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

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

Input parameters:

- `idempotency_key` (string, required)
- `max_total_price` (string, required)
- `payment_rail` (string)
- `request` (object, required)

### `translate_quantum_circuit` (~68 tokens)

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

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

Input parameters:

- `idempotency_key` (string, required)
- `max_total_price` (string, required)
- `payment_rail` (string)
- `request` (object, required)

### `diagnose_quantum_phase` (~61 tokens)

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

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

Input parameters:

- `idempotency_key` (string, required)
- `max_total_price` (string, required)
- `payment_rail` (string)
- `request` (object, required)

### `synthesize_two_qubit_target` (~61 tokens)

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

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

Input parameters:

- `idempotency_key` (string, required)
- `max_total_price` (string, required)
- `payment_rail` (string)
- `request` (object, required)

### `classify_two_qubit_operation` (~64 tokens)

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

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

Input parameters:

- `idempotency_key` (string, required)
- `max_total_price` (string, required)
- `payment_rail` (string)
- `request` (object, required)

### `get_account_balance` (~27 tokens)

Get RQM MCP account balance

Read the authenticated canonical Account Core prepaid USD balance.

Input parameters:

- `schema_version` (string, required)

### `get_studio_receipt` (~39 tokens)

Get Studio payment receipt

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

Input parameters:

- `reservation_id` (string, required)
- `schema_version` (string, required)

### `create_funding_session` (~48 tokens)

Create an RQM MCP funding session

Create an idempotent Stripe Checkout URL for human prepaid funding.

Input parameters:

- `amount` (string, required)
- `idempotency_key` (string, required)
- `schema_version` (string, required)

### `submit_quantum_job` (~23 tokens)

Submit an RQM Studio job

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

### `get_job_status` (~20 tokens)

Get RQM job status

Read one authorized Wave or Studio managed-simulator job.

### `get_job_result` (~20 tokens)

Get RQM job result

Read one completed and already-settled product result.

### `cancel_job` (~16 tokens)

Cancel an RQM job

Request cancellation of one authorized product job.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-rqmtechnologies-studio/mcp-studio#diagnostics

## Score history

- 2026-09-20: 81
- 2026-09-19: 81
- 2026-09-18: 81
- 2026-09-17: 80
- 2026-09-16: 80
- 2026-09-15: 79
- 2026-09-14: 79
- 2026-09-13: 78
- 2026-09-12: 78
- 2026-09-11: 71
- 2026-09-10: 70
- 2026-09-09: 70
- 2026-09-08: 68
- 2026-09-07: 68
- 2026-09-06: 67
- 2026-09-05: 67
- 2026-09-04: 66
- 2026-09-03: 66
- 2026-09-02: 66
- 2026-09-01: 65
- 2026-08-31: 65
- 2026-08-30: 64
- 2026-08-29: 64
- 2026-08-28: 63
- 2026-08-27: 63
- 2026-08-26: 62
- 2026-08-25: 60
- 2026-08-24: 59
- 2026-08-23: 59
- 2026-08-22: 58

## Common questions

### What is the RQM Studio Jobs MCP server?

RQM Studio Jobs is an MCP server listed in the public MCP registry as com.rqmtechnologies/studio. Delegate 20 fail-closed RQM Studio quantum work products with fixed-request x402. This page covers its hosted endpoint (https://jobs.rqmtechnologies.com/mcp/studio).

### Is the RQM Studio Jobs MCP server safe to use?

RQM Studio Jobs scores 81 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the RQM Studio Jobs MCP server expose?

RQM Studio Jobs exposes 43 tools: list_buyer_jobs, search_buyer_jobs, list_capabilities, get_capability, run_buyer_job, and 38 more. Their descriptions and schemas cost roughly 3,231 tokens of context every time the server is loaded.

### Does the RQM Studio Jobs MCP server require authentication?

No. We connected to RQM Studio Jobs without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the RQM Studio Jobs MCP server still maintained?

RQM Studio Jobs is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://jobs.rqmtechnologies.com/mcp/studio
- Repository: https://github.com/RQM-Technologies-dev/RQM-Jobs-MCP
- Website: https://www.rqmtechnologies.com/rqm-studio
- Changelog RSS feed: https://verifymcp.io/servers/com-rqmtechnologies-studio/mcp-studio.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-rqmtechnologies-studio/mcp-studio.json
- HTML version of this page: https://verifymcp.io/servers/com-rqmtechnologies-studio/mcp-studio