Home / MCP registry index / com.rqmtechnologies/waveengine
RQM WaveEngine Jobs
com.rqmtechnologies/waveengine in the official MCP registry.
Endpoint https://jobs.rqmtechnologies.com/mcp/waveengine. Source: github.com/RQM-Technologies-dev/RQM-Jobs-MCP.
The registry describes it as: Delegate 20 typed, evidence-backed WaveEngine signal work products with fixed-request x402.
On 2026-10-28 we read its 34 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
list_buyer_jobs search_buyer_jobs list_wave_capabilities get_wave_capability run_buyer_job wave_gate_signal_capture_v1 wave_diagnose_multichannel_capture_v1 wave_measure_phase_drift_v1 wave_extract_wave_features_v1 wave_reconstruct_bounded_capture_v1 wave_equalize_pilot_capture_v1 wave_transport_polarization_frame_v1 wave_generate_validated_signal_fixture_v1 wave_compare_waveform_captures_v1 wave_fit_coupled_channel_model_v1 wave_verify_wave_pipeline_v1 wave_rotate_and_validate_two_channel_frame_v1 wave_convert_capture_to_spectrum_v1 wave_reconstruct_time_domain_signal_v1 wave_optimize_processing_pipeline_v1 wave_compile_curated_processing_recipe_v1 wave_apply_verified_phase_correction_v1 wave_validate_spectral_criteria_v1 wave_validate_reconstruction_quality_v1 wave_compare_pipeline_responses_v1 search_wave_capabilities get_wave_example run_wave_example estimate_wave_job run_wave_job get_wave_receipt get_wave_job_status get_wave_job_result get_wave_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-waveengine)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.
Related
| The Stall ai.intuitek.the-stall/the-stall | 200 tools, nothing matched 2026-10-22 |
| SAP MCP Server ai.oobeprotocol.sap.mcp/sap-mcp | 200 tools, nothing matched 2026-10-22 |
| Citiview Agent Market com.citiviewgroup.mcp/agent-market | 200 tools, nothing matched 2026-10-26 |
| ScorpTech x402 API com.it.scorptech/x402 | 200 tools, nothing matched 2026-10-26 |
| Apex Edge — x402-paid machine services dev.pages.nonsynthetic/apex-edge | 200 tools, nothing matched 2026-10-23 |
| x402 Factory io.github.praneeth12098/x402-factory | 200 tools, nothing matched 2026-10-26 |