RQM Jobs MCP Server

by rqmtechnologies Your server? Claim it

not responding

RQM Jobs MCP is listed as active in the registry but did not answer our last check. It exposes 35 tools.

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

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

Uptime history 33 days of history · worst day 0%

33 days agonow

96.7%

Uptime 24h

89 of 92 checks

Tools

read from the server

2770 ms

Response time

average over 24h

open, no key

Access

streamable-http

What changed 1

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

14 Sep a tool appeared settle_buyer_job

RQM Jobs MCP does not always answer

Over the last week it answered 76.4% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Connect this server

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

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

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

~/Library/Application Support/Claude/claude_desktop_config.json

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

~/.codex/config.toml

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

.cursor/mcp.json

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

.vscode/mcp.json

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

Available tools 35

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

robotics

robotics_analyze_force_disturbance_response_v1

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.

robotics_assess_calibration_quality_v1

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.

robotics_check_collision_constraints_v1

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.

robotics_compare_controller_responses_v1

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.

robotics_compare_digital_twin_observations_v1

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.

robotics_compare_planned_observed_trajectories_v1

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.

robotics_compare_state_estimators_v1

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.

robotics_compute_actuator_alignment_correction_v1

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.

robotics_diagnose_trajectory_instability_v1

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.

robotics_estimate_fused_state_v1

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.

robotics_frame_convention_validation_v1

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.

robotics_normalize_sensor_frames_v1

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.

robotics_optimize_disturbance_rejection_v1

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.

robotics_optimize_trajectory_to_constraints_v1

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.

robotics_reconstruct_smoothed_trajectory_v1

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.

robotics_replay_workcell_trace_v1

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.

robotics_tune_controller_to_objectives_v1

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.

robotics_validate_closed_loop_stability_v1

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.

robotics_validate_kinematic_dynamic_limits_v1

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.

robotics_validate_trajectory_timing_v1

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.

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.

job

get_job_artifact

Retrieve one principal-scoped bounded Wave result artifact.

get_job_result

Read one completed and already-settled product result.

get_job_status

Read one authorized Wave or Studio managed-simulator job.

submit

submit_quantum_job

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

submit_wave_job

Reserve an exact quote and submit one bounded catalog-approved Wave job.

account

get_account_balance

Read the authenticated canonical Account Core prepaid USD balance.

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.

funding

create_funding_session

Create an idempotent Stripe Checkout URL for human prepaid funding.

quote

quote_job

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

settle

settle_buyer_job

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.

Endpoints

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

Alternatives to RQM Jobs MCP

same job, measured the same way

RQM Studio Jobs

by rqmtechnologies

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

43 tools answering

RQM Robotics Jobs

by rqmtechnologies

Delegate 20 typed RQM Robotics jobs for validation, diagnosis, comparison, and optimization.

13 tools answering

Cannon Studio

by cannonstudio

Public Cannon Studio MCP for product, pricing, workflow, model, and API answers.

31 tools answering

Moltline Creator Studio

by moltlinestudio

20 blogging, brand-voice, copywriting, video and social skill products. 6 of 8 free.

8 tools answering

CircleCI

by circleci

CircleCI's MCP server: inspect projects, runs, workflows, jobs, logs, tests, and artifacts.

22 tools answering

Worthune Verified Financial Models

by worthune

61 verified financial models and a household planning engine: 20 MCP tools, 6 keyless, specs cited.

20 tools answering

Draftlytic MCP

by rbsoftwaresystems

Offline MCP server for planning structured project specs — validate, render, and checklist tools.

27 installs/wk local only

LLM Provider MCP

by manishiitg

Delegate asynchronous coding jobs between Claude Code, Codex, Cursor Agent, and Pi.

local only

RQM Jobs MCP — questions

Answers built from our own checks of this server.

What can RQM Jobs MCP do?

It exposes 35 tools, read directly from the server on our last check. Among them: cancel_job, create_funding_session, get_account_balance, get_capability, get_job_artifact, get_job_result and 29 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 Jobs MCP mostly used for?

Its tools cluster around robotics, job and buyer. 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 Jobs MCP working right now?

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

Is RQM Jobs MCP 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.

The registry lists RQM Jobs MCP as active — why does it not respond?

The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.

How do I connect RQM Jobs MCP?

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

Does RQM Jobs MCP need an API key?

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