RQM Jobs MCP
REMOTE · JOBS.RQMTECHNOLOGIES.COM
Delegate 60 specialist work products: 20 WaveEngine, 20 RQM Studio, and 20 RQM Robotics jobs.
Available components
Last scanned (9 hours ago)
Scores higher than 61% of remote servers
Reachable. Last reached 5 Nov 2026.
Category IoT and Hardware
Recent critical change
Authorization (26 Sept 2026). See the changelog before you install this server.
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. How we score → Why this is hard to score →
Endpoint Security60
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (run_account_job). See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability56
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 3515 tokens (~90/item across 39 items; 39 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage73
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 6% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 39 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 39 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 13 Oct 26 0
- Stability: 0.97 → pass security
- 12 Oct 26 0
- Stability: pass → 0.97 functional
- New tool “describe_quantum_capabilities” functional
- 10 Oct 26 0
- Schema quality: 78 → 89 ▼ functional
- 4 Oct 26 +1
- Tool coverage: 92% → 100% ▲ functional
- Tool “get_account_job” now declares an output schema ▲ functional
- Tool “list_account_jobs” now declares an output schema ▲ functional
- Tool “run_account_job” now declares an output schema ▲ functional
- “run_account_job” reworded the description of “capability_id” cosmetic
- “run_account_job” reworded the description of “idempotency_key” cosmetic
- “run_account_job” reworded the description of “max_total_price” cosmetic
- “run_account_job” reworded the description of “request” cosmetic
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Sept 26 0
- Authorization: partial → fail ▼ critical
- New tool “run_account_job”, which the server declares destructive security
- Tool coverage: 100% → 92% ▼ functional
- New tool “get_account_job” functional
- New tool “list_account_jobs” functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 15 Sept 26 0
- New tool “settle_buyer_job” functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://jobs.rqmtechnologies.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=jobs.rqmtechnologies.com | CN=WE1,O=Google Trust Services,C=US | 13 Oct 2026 | 11 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | ebf66b9aeb430c870e54678b69edbe27 |
| SANs: jobs.rqmtechnologies.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of jobs.rqmtechnologies.com. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| rqmtechnologies.com. | present | 24611, 24611 | 13, 13 | Verified |
| jobs.rqmtechnologies.com. | Verified address RRset verified with the apex keys |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://jobs.rqmtechnologies.com/mcp | Verified | 200 | |
| http (plaintext) | http://jobs.rqmtechnologies.com/mcp | HTTPS enforced | 301 | https://jobs.rqmtechnologies.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
cancel_job Cancel an RQM job ~16
Request cancellation of one authorized product job.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
create_funding_session Create an RQM MCP funding session ~48
Create an idempotent Stripe Checkout URL for human prepaid funding.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | string | yes | – |
| idempotency_key | string | yes | – |
| schema_version | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
describe_quantum_capabilities Discover RQM quantum capabilities and domain guidance ~132
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.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
get_account_balance Get RQM MCP account balance ~27
Read the authenticated canonical Account Core prepaid USD balance.
| Name | Type | Req | Description |
|---|---|---|---|
| schema_version | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_account_job Recover an account-funded job ~129
Read this agent's saved account-funded job by its returned job ID to check status and recover available result and receipt. Use after submission or when following up on an existing purchase; acceptance is not completion. Report the saved state and only available results, with their limitations. If the job ID was lost, use list_account_jobs with the original idempotency key first. Never authorizes another purchase.
| Name | Type | Req | Description |
|---|---|---|---|
| job_id | string | yes | UUID returned for the saved account job. Recover a missing ID with list_account_jobs using the original purchase idempotency key; do not invent an ID or submit again. |
Structured output declared, but exposes no named fields.
No examples provided.
get_capability Get one RQM job capability ~18
Return one full approved public Wave capability descriptor.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
get_job_artifact Get one Wave job artifact ~51
Retrieve one principal-scoped bounded Wave result artifact.
| Name | Type | Req | Description |
|---|---|---|---|
| artifact_id | string | yes | – |
| job_id | string | yes | – |
| product | string | yes | – |
| schema_version | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_job_result Get RQM job result ~20
Read one completed and already-settled product result.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
get_job_status Get RQM job status ~20
Read one authorized Wave or Studio managed-simulator job.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
list_account_jobs Find this agent's purchases ~175
List up to 100 recent jobs for this agent, or find the original account-funded purchase using its idempotency key. Use for purchase history and recovery before retrying an uncertain submission; use list_buyer_jobs or search_buyer_jobs for available services. Omit the key for recent history, or pass the exact original key to recover one purchase. Use a returned job ID with get_account_job for saved status, result and receipt. An empty response does not prove that a timed-out submission cannot still be accepted; preserve the original key and inputs on any retry. This read never purchases or reruns a job.
| Name | Type | Req | Description |
|---|---|---|---|
| idempotency_key | string | – | Exact original purchase key used with run_account_job. Supply it to recover an uncertain submission; omit to list recent jobs. Do not generate a replacement key for recovery. |
Structured output declared, but exposes no named fields.
No examples provided.
list_buyer_jobs List RQM buyer jobs ~54
Return complete agent discovery contracts and readiness for the exact 20/20/20 RQM specialist work portfolio.
| Name | Type | Req | Description |
|---|---|---|---|
| product | string | – | – |
| schema_version | string | – | – |
| surface | string | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
list_capabilities List RQM job capabilities ~27
Describe the preserved v0/v1 surface or the dynamic v2/v3 Wave catalog.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
quote_job Quote an RQM job ~24
Return a preserved v0 placeholder or a durable v1 Account Core USD quote.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
robotics_analyze_force_disturbance_response_v1 Analyze Force Disturbance Response ~117
Problem: Analyze these bounded force and disturbance inputs against the supplied response model and criteria. Input: JSON with mass kg, damping n s per m, stiffness n per m, time step seconds.... Result: modeled response, metrics and rule results. Limits: Software/model evidence only; 65536 request bytes; 5 s execution.
| Name | Type | Req | Description |
|---|---|---|---|
| idempotency_key | string | yes | – |
| max_total_price | string | yes | – |
| request | object | yes | – |
| schema_version | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
robotics_assess_calibration_quality_v1 Calibration quality assessment ~113
Problem: Assess this bounded calibration dataset against the supplied residual, coverage, and consistency rules. Input: JSON with length unit, observations, rules. Result: pass, fail, or indeterminate verdict, residual metrics, per-rule evaluations. Limits: Software/model evidence only; 65536 request bytes; 5 s execution.
| Name | Type | Req | Description |
|---|---|---|---|
| idempotency_key | string | yes | – |
| max_total_price | string | yes | – |
| request | object | yes | – |
| schema_version | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
robotics_check_collision_constraints_v1 Check Collision Constraints ~104
Problem: Check this bounded geometry and trajectory against the supplied collision and clearance constraints. Input: JSON with trajectory, obstacles, robot radius, minimum clearance. Result: clearance, collision candidates and constraint results. Limits: Software/model evidence only; 65536 request bytes; 5 s execution.
| Name | Type | Req | Description |
|---|---|---|---|
| idempotency_key | string | yes | – |
| max_total_price | string | yes | – |
| request | object | yes | – |
| schema_version | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
robotics_compare_controller_responses_v1 Compare Controller Responses ~103
Problem: Compare these bounded controller responses on identical traces using the supplied objective rules. Input: JSON with baseline, candidate, rules. Result: metric values, threshold verdicts, difference series. Limits: Software/model evidence only; 65536 request bytes; 5 s execution.
| Name | Type | Req | Description |
|---|---|---|---|
| idempotency_key | string | yes | – |
| max_total_price | string | yes | – |
| request | object | yes | – |
| schema_version | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
robotics_compare_digital_twin_observations_v1 Compare Digital Twin Observations ~110
Problem: Compare digital-twin output with mapped observations against caller tolerances. Input: JSON with predicted, observed, declared mapping, rules. Result: typed verdict, measured metrics, candidate only when verified. Limits: Software/model evidence only; 65536 request bytes; 5 s execution.
| Name | Type | Req | Description |
|---|---|---|---|
| idempotency_key | string | yes | – |
| max_total_price | string | yes | – |
| request | object | yes | – |
| schema_version | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
robotics_compare_planned_observed_trajectories_v1 Compare Planned Observed Trajectories ~105
Problem: Compare planned and observed trajectories against caller tolerances. Input: JSON with planned, observed, rules. Result: typed verdict, measured metrics, candidate only when verified. Limits: Software/model evidence only; 65536 request bytes; 5 s execution.
| Name | Type | Req | Description |
|---|---|---|---|
| idempotency_key | string | yes | – |
| max_total_price | string | yes | – |
| request | object | yes | – |
| schema_version | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
robotics_compare_state_estimators_v1 Compare State Estimators ~107
Problem: Compare these bounded estimator outputs against the supplied reference and objective rules. Input: JSON with reference, estimators, rules. Result: per-estimator metrics, rule verdicts, deterministic selected estimator or.... Limits: Software/model evidence only; 65536 request bytes; 5 s execution.
| Name | Type | Req | Description |
|---|---|---|---|
| idempotency_key | string | yes | – |
| max_total_price | string | yes | – |
| request | object | yes | – |
| schema_version | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
robotics_compute_actuator_alignment_correction_v1 Compute Actuator Alignment Correction ~106
Problem: Compute a bounded actuator alignment correction from these observations and caller acceptance limits. Input: JSON with observations, model, rules. Result: correction parameters, pre/post residuals, applicability verdict. Limits: Software/model evidence only; 65536 request bytes; 5 s execution.
| Name | Type | Req | Description |
|---|---|---|---|
| idempotency_key | string | yes | – |
| max_total_price | string | yes | – |
| request | object | yes | – |
| schema_version | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
robotics_diagnose_trajectory_instability_v1 Trajectory instability diagnosis ~116
Problem: Diagnose this bounded trajectory for the supplied oscillation, divergence, and stability indicators. Input: JSON with frame id, length unit, samples, rules. Result: pass, fail, or unsupported verdict, indicator series, violation windows. Limits: Software/model evidence only; 65536 request bytes; 5 s execution.
| Name | Type | Req | Description |
|---|---|---|---|
| idempotency_key | string | yes | – |
| max_total_price | string | yes | – |
| request | object | yes | – |
| schema_version | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
robotics_estimate_fused_state_v1 Estimate Fused State ~107
Problem: Fuse these bounded synchronized sensor observations under the supplied diagonal uncertainty model and rules. Input: JSON with observations, model, rules. Result: fused state, diagonal covariance, sensor residuals and verdict. Limits: Software/model evidence only; 65536 request bytes; 5 s execution.
| Name | Type | Req | Description |
|---|---|---|---|
| idempotency_key | string | yes | – |
| max_total_price | string | yes | – |
| request | object | yes | – |
| schema_version | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
robotics_frame_convention_validation_v1 Frame and convention validation ~120
Problem: Validate this bounded frame graph and report unit, axis, handedness, rotation, and transform-direction violations. Input: JSON with frames, declared length unit, declared transform direction, declared.... Result: pass, fail, or unsupported verdict, exact findings, normalized evidence. Limits: Software/model evidence only; 65536 request bytes; 5 s execution.
| Name | Type | Req | Description |
|---|---|---|---|
| idempotency_key | string | yes | – |
| max_total_price | string | yes | – |
| request | object | yes | – |
| schema_version | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
robotics_normalize_sensor_frames_v1 Sensor frame normalization ~107
Problem: Convert these bounded sensor observations into the supplied target frame and unit convention. Input: JSON with frame graph, target frame id, observations. Result: normalized or unsupported verdict, normalized observations, transform paths. Limits: Software/model evidence only; 65536 request bytes; 5 s execution.
| Name | Type | Req | Description |
|---|---|---|---|
| idempotency_key | string | yes | – |
| max_total_price | string | yes | – |
| request | object | yes | – |
| schema_version | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
robotics_optimize_disturbance_rejection_v1 Optimize Disturbance Rejection ~114
Problem: Tune supported control parameters against this bounded disturbance model and supplied response objectives. Input: JSON with mass, damping, disturbance, time step seconds, baseline kp, baseline.... Result: candidate parameters, comparative metrics and constraint results. Limits: Software/model evidence only; 65536 request bytes; 5 s execution.
| Name | Type | Req | Description |
|---|---|---|---|
| idempotency_key | string | yes | – |
| max_total_price | string | yes | – |
| request | object | yes | – |
| schema_version | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
robotics_optimize_trajectory_to_constraints_v1 Optimize Trajectory To Constraints ~107
Problem: Optimize a bounded trajectory only when speed and duration constraints pass. Input: JSON with trajectory, maximum speed, maximum duration s. Result: typed verdict, measured metrics, candidate only when verified. Limits: Software/model evidence only; 65536 request bytes; 5 s execution.
| Name | Type | Req | Description |
|---|---|---|---|
| idempotency_key | string | yes | – |
| max_total_price | string | yes | – |
| request | object | yes | – |
| schema_version | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
robotics_reconstruct_smoothed_trajectory_v1 Reconstruct Smoothed Trajectory ~107
Problem: Reconstruct this bounded trajectory under the supplied smoothing model and residual rule. Input: JSON with samples, model, rules. Result: smoothed trajectory, residual RMSE, caller-rule verdict. Limits: Software/model evidence only; 65536 request bytes; 5 s execution.
| Name | Type | Req | Description |
|---|---|---|---|
| idempotency_key | string | yes | – |
| max_total_price | string | yes | – |
| request | object | yes | – |
| schema_version | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
robotics_replay_workcell_trace_v1 Replay Workcell Trace ~101
Problem: Replay this bounded workcell trace against the supplied event assertions. Input: JSON with model id, events, assertions. Result: timeline, assertion results and trace digest. Limits: Software/model evidence only; 65536 request bytes; 5 s execution.
| Name | Type | Req | Description |
|---|---|---|---|
| idempotency_key | string | yes | – |
| max_total_price | string | yes | – |
| request | object | yes | – |
| schema_version | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
robotics_tune_controller_to_objectives_v1 Tune Controller To Objectives ~110
Problem: Tune a supported controller only within supplied bounds and safety limits. Input: JSON with supported controller, current gain, fixture error, target error.... Result: typed verdict, measured metrics, candidate only when verified. Limits: Software/model evidence only; 65536 request bytes; 5 s execution.
| Name | Type | Req | Description |
|---|---|---|---|
| idempotency_key | string | yes | – |
| max_total_price | string | yes | – |
| request | object | yes | – |
| schema_version | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
robotics_validate_closed_loop_stability_v1 Validate Closed Loop Stability ~103
Problem: Accept or reject this bounded closed-loop model under the supplied stability criteria. Input: JSON with discrete state matrix, criteria. Result: eigenvalues, spectral radius and rule results. Limits: Software/model evidence only; 65536 request bytes; 5 s execution.
| Name | Type | Req | Description |
|---|---|---|---|
| idempotency_key | string | yes | – |
| max_total_price | string | yes | – |
| request | object | yes | – |
| schema_version | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
robotics_validate_kinematic_dynamic_limits_v1 Validate Kinematic Dynamic Limits ~106
Problem: Accept or reject a bounded trajectory against caller kinematic limits. Input: JSON with trajectory, maximum speed, maximum acceleration. Result: typed verdict, measured metrics, candidate only when verified. Limits: Software/model evidence only; 65536 request bytes; 5 s execution.
| Name | Type | Req | Description |
|---|---|---|---|
| idempotency_key | string | yes | – |
| max_total_price | string | yes | – |
| request | object | yes | – |
| schema_version | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
robotics_validate_trajectory_timing_v1 Trajectory and sensor timing validation ~112
Problem: Validate timestamps, ordering, rates, gaps, and synchronization in this bounded trajectory or sensor trace. Input: JSON with clock id, samples, rules. Result: pass or fail verdict, normalized timeline, exact timing defects. Limits: Software/model evidence only; 65536 request bytes; 5 s execution.
| Name | Type | Req | Description |
|---|---|---|---|
| idempotency_key | string | yes | – |
| max_total_price | string | yes | – |
| request | object | yes | – |
| schema_version | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
run_account_job Run a job using prepaid RQM credits ~353
Purchase one discovered service using prepaid credits within the account owner's saved spending policy. First search_buyer_jobs for the task and inspect the selected request_schema, required inputs, limits, examples and evidence boundaries. Use its buyer service_id as capability_id; validate the user's inputs and ask for missing data rather than substituting an example. Set max_total_price to the caller-approved USD ceiling; discovery is not a binding quote and balance alone is not policy authorization. Acceptance or a queued job is not completion: retain the returned job ID and use get_account_job to read saved status, result and receipt. If submission times out or its outcome is uncertain, first recover with list_account_jobs using the original idempotency_key. Any retry must preserve the same key, capability, request and price ceiling; never create a new purchase or switch payment rails to recover. This tool never signs x402 or funds the account. Report only observed completion and findings within the service's evidence boundaries.
| Name | Type | Req | Description |
|---|---|---|---|
| capability_id | string | yes | Buyer service_id returned by discovery, not an implementation_capability_id. Select a supported service before submitting. |
| idempotency_key | string | yes | Stable caller-chosen identifier for one purchase. Preserve the exact key and request on retries; recover uncertain submissions with list_account_jobs using this key. |
| max_total_price | string | yes | Caller-approved total price ceiling in USD as a decimal string with up to six fractional digits. Not a quote, funding instruction or policy authorization; the saved spending policy must also permit t… |
| request | object | yes | User inputs matching the selected service request_schema. Consult its required fields and example; ask for missing data, units, rules or tolerances rather than inventing them. |
Structured output declared, but exposes no named fields.
No examples provided.
run_buyer_job Run any RQM buyer job ~81
Quote, settle, and submit one allowlisted WaveEngine, Studio, or Robotics buyer job using x402.
| Name | Type | Req | Description |
|---|---|---|---|
| capability_id | string | yes | – |
| idempotency_key | string | yes | – |
| max_total_price | string | yes | – |
| product | string | yes | – |
| request | object | yes | – |
| schema_version | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
search_buyer_jobs Search RQM buyer jobs ~70
Select RQM buyer jobs from work-language requests using deterministic semantic scoring over instructions, examples, outputs, and next steps.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| product | string | – | – |
| query | string | yes | – |
| schema_version | string | – | – |
| surface | string | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
settle_buyer_job Auto-settle a Jobs buyer 402 ~50
Server-side Jobs-rail x402 settle for connector hosts that cannot sign. Replays the same idempotency key with PAYMENT-SIGNATURE. An RQM-owned operator signer is not external revenue.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
submit_quantum_job Submit an RQM Studio job ~23
Reserve an exact quote and submit one bounded managed-simulator job.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
submit_wave_job Submit a WaveEngine job ~22
Reserve an exact quote and submit one bounded catalog-approved Wave job.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
How do I install the RQM Jobs MCP server?
RQM Jobs MCP is a hosted endpoint at https://jobs.rqmtechnologies.com/mcp, 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.
remote · jobs.rqmtechnologies.com
claude mcp add --transport http com-rqmtechnologies-jobs 'https://jobs.rqmtechnologies.com/mcp'
What is the RQM Jobs MCP server?
RQM Jobs MCP is listed in the public MCP registry as com.rqmtechnologies/jobs. Delegate 60 specialist work products: 20 WaveEngine, 20 RQM Studio, and 20 RQM Robotics jobs. This page covers its hosted endpoint (https://jobs.rqmtechnologies.com/mcp).
Is the RQM Jobs MCP server safe to use?
RQM Jobs MCP scores 74 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 Jobs MCP server expose?
RQM Jobs MCP exposes 39 tools: describe_quantum_capabilities, run_account_job, get_account_job, list_account_jobs, list_buyer_jobs, and 34 more. Their descriptions and schemas cost roughly 3,515 tokens of context every time the server is loaded.
Does the RQM Jobs MCP server require authentication?
No. We connected to RQM Jobs MCP without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the RQM Jobs MCP server still maintained?
RQM Jobs MCP is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.