Home / MCP registry index / com.rqmtechnologies/jobs
RQM Jobs MCP
com.rqmtechnologies/jobs in the official MCP registry.
Endpoint https://jobs.rqmtechnologies.com/mcp. Source: github.com/RQM-Technologies-dev/RQM-Jobs-MCP.
The registry describes it as: Delegate 60 specialist work products: 20 WaveEngine, 20 RQM Studio, and 20 RQM Robotics jobs.
On 2026-10-28 we read its 39 tools, but part of what it advertised was cut before our rules saw it: a description or schema past the size we read, more tools than we read, or a tool list split across pages. Nothing in the part we read matched, but the rest was not checked: this is not a clean result.
Tools it advertises
describe_quantum_capabilities run_account_job get_account_job list_account_jobs list_buyer_jobs search_buyer_jobs list_capabilities get_capability run_buyer_job settle_buyer_job robotics_frame_convention_validation_v1 robotics_assess_calibration_quality_v1 robotics_diagnose_trajectory_instability_v1 robotics_validate_trajectory_timing_v1 robotics_normalize_sensor_frames_v1 robotics_reconstruct_smoothed_trajectory_v1 robotics_estimate_fused_state_v1 robotics_compute_actuator_alignment_correction_v1 robotics_compare_controller_responses_v1 robotics_compare_state_estimators_v1 robotics_compare_planned_observed_trajectories_v1 robotics_compare_digital_twin_observations_v1 robotics_tune_controller_to_objectives_v1 robotics_optimize_trajectory_to_constraints_v1 robotics_validate_kinematic_dynamic_limits_v1 robotics_optimize_disturbance_rejection_v1 robotics_validate_closed_loop_stability_v1 robotics_check_collision_constraints_v1 robotics_replay_workcell_trace_v1 robotics_analyze_force_disturbance_response_v1 quote_job get_account_balance create_funding_session submit_wave_job submit_quantum_job get_job_status get_job_result cancel_job get_job_artifact
Rather than checking back: subscribe to this server's tool changes (a feed, no account and no address needed). Tool names and dates only, never what a tool says.
Run this server? Show the check in your README
The badge reflects the latest read: 
[](https://lazaretto.dev/mcp-registry/com-rqmtechnologies-jobs)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.