Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

RQM WaveEngine Jobs

REMOTE · JOBS.RQMTECHNOLOGIES.COM · SCANNED SEP 22

Delegate 20 typed, evidence-backed WaveEngine signal work products with fixed-request x402.

0 this week 81 Trust /100
Trust breakdown (7 categories)

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 Security77
Transport & Reachability100
Schema Quality & AI Usability59
  • AI-judged instruction clarity (fair).Partial
  • Tool/resource definitions use about 2878 tokens (~84/item across 34 items; 34 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 Coverage71
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
  • 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
  • All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 34 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
Install

How do I install the RQM WaveEngine Jobs MCP server?

RQM WaveEngine Jobs is a hosted endpoint at https://jobs.rqmtechnologies.com/mcp/waveengine, 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

# add to Claude Code
claude mcp add --transport http com-rqmtechnologies-waveengine 'https://jobs.rqmtechnologies.com/mcp/waveengine'
// .cursor/mcp.json
{
  "mcpServers": {
    "com-rqmtechnologies-waveengine": {
      "url": "https://jobs.rqmtechnologies.com/mcp/waveengine"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "com-rqmtechnologies-waveengine": {
      "type": "http",
      "url": "https://jobs.rqmtechnologies.com/mcp/waveengine"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.com-rqmtechnologies-waveengine]
url = "https://jobs.rqmtechnologies.com/mcp/waveengine"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-rqmtechnologies-waveengine": {
      "type": "remote",
      "url": "https://jobs.rqmtechnologies.com/mcp/waveengine",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add com-rqmtechnologies-waveengine --url 'https://jobs.rqmtechnologies.com/mcp/waveengine' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  com-rqmtechnologies-waveengine:
    url: "https://jobs.rqmtechnologies.com/mcp/waveengine"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "com-rqmtechnologies-waveengine": {
      "Transport": "http",
      "Url": "https://jobs.rqmtechnologies.com/mcp/waveengine"
    }
  }
}
# add to Vellum
assistant mcp add com-rqmtechnologies-waveengine -t streamable-http -u 'https://jobs.rqmtechnologies.com/mcp/waveengine'
// mcp.json
{
  "mcpServers": {
    "com-rqmtechnologies-waveengine": {
      "type": "http",
      "url": "https://jobs.rqmtechnologies.com/mcp/waveengine"
    }
  }
}

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

Changelog

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.

  • 17 Sept 26 0
    • Stability: 0.97 → pass security
  • 16 Sept 26 0
    • Stability: pass → 0.97 functional
  • 15 Sept 26 0
    • Stability: 0.97 → pass security
  • 14 Sept 26 +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.

  • 12 Sept 26 +8
    • Authorization: unverified → partial security
  • 9 Sept 26 +3
    • Tool “list_buyer_jobs” rewrote its description, which is the text the model reads security
    • Tool “wave_apply_verified_phase_correction_v1” rewrote its description, which is the text the model reads security
    • Tool “wave_compare_pipeline_responses_v1” rewrote its description, which is the text the model reads security
    • Tool “wave_compare_waveform_captures_v1” rewrote its description, which is the text the model reads security
    • Tool “wave_compile_curated_processing_recipe_v1” rewrote its description, which is the text the model reads security
    • Tool “wave_convert_capture_to_spectrum_v1” rewrote its description, which is the text the model reads security
    • Tool “wave_diagnose_multichannel_capture_v1” rewrote its description, which is the text the model reads security
    • Tool “wave_equalize_pilot_capture_v1” rewrote its description, which is the text the model reads security
    • Tool “wave_extract_wave_features_v1” rewrote its description, which is the text the model reads security
    • Tool “wave_fit_coupled_channel_model_v1” rewrote its description, which is the text the model reads security
    • Tool “wave_gate_signal_capture_v1” rewrote its description, which is the text the model reads security
    • Tool “wave_generate_validated_signal_fixture_v1” rewrote its description, which is the text the model reads security
    • Tool “wave_measure_phase_drift_v1” rewrote its description, which is the text the model reads security
    • Tool “wave_optimize_processing_pipeline_v1” rewrote its description, which is the text the model reads security
    • Tool “wave_reconstruct_bounded_capture_v1” rewrote its description, which is the text the model reads security
    • Tool “wave_reconstruct_time_domain_signal_v1” rewrote its description, which is the text the model reads security
    • Tool “wave_rotate_and_validate_two_channel_frame_v1” rewrote its description, which is the text the model reads security
    • Tool “wave_transport_polarization_frame_v1” rewrote its description, which is the text the model reads security
    • Tool “wave_validate_reconstruction_quality_v1” rewrote its description, which is the text the model reads security
    • Tool “wave_validate_spectral_criteria_v1” rewrote its description, which is the text the model reads security
    • Tool “wave_verify_wave_pipeline_v1” rewrote its description, which is the text the model reads security
    • Schema quality: 63 → 84 functional
    • Tool “list_buyer_jobs” changed its title: List production-live RQM buyer jobs → List RQM buyer jobs cosmetic
    • Tool “search_buyer_jobs” changed its title: Search production-live RQM buyer jobs → Search RQM buyer jobs cosmetic
    • Tool “wave_apply_verified_phase_correction_v1” changed its title: Run wave.apply-verified-phase-correction.v1 → Apply Verified Phase Correction cosmetic
    • Tool “wave_compare_pipeline_responses_v1” changed its title: Run wave.compare-pipeline-responses.v1 → Compare Pipeline Responses cosmetic
    • Tool “wave_compare_waveform_captures_v1” changed its title: Run wave.compare-waveform-captures.v1 → Compare Waveform Captures cosmetic
    • Tool “wave_compile_curated_processing_recipe_v1” changed its title: Run wave.compile-curated-processing-recipe.v1 → Compile Curated Processing Recipe cosmetic
    • Tool “wave_convert_capture_to_spectrum_v1” changed its title: Run wave.convert-capture-to-spectrum.v1 → Convert Capture To Spectrum cosmetic
    • Tool “wave_diagnose_multichannel_capture_v1” changed its title: Run diagnose-multichannel-capture-v1 → Diagnose Multichannel Capture cosmetic
    • Tool “wave_equalize_pilot_capture_v1” changed its title: Run equalize-pilot-capture-v1 → Equalize Pilot Capture cosmetic
    • Tool “wave_extract_wave_features_v1” changed its title: Run extract-wave-features-v1 → Extract Wave Features cosmetic
    • Tool “wave_fit_coupled_channel_model_v1” changed its title: Run fit-coupled-channel-model-v1 → Fit Coupled Channel Model cosmetic
    • Tool “wave_gate_signal_capture_v1” changed its title: Run gate-signal-capture-v1 → Gate Signal Capture cosmetic
    • Tool “wave_generate_validated_signal_fixture_v1” changed its title: Run generate-validated-signal-fixture-v1 → Generate Validated Signal Fixture cosmetic
    • Tool “wave_measure_phase_drift_v1” changed its title: Run wave.measure-phase-drift.v1 → Measure Phase Drift cosmetic
    • Tool “wave_optimize_processing_pipeline_v1” changed its title: Run wave.optimize-processing-pipeline.v1 → Optimize Processing Pipeline cosmetic
    • Tool “wave_reconstruct_bounded_capture_v1” changed its title: Run wave.reconstruct-bounded-capture.v1 → Reconstruct Bounded Capture cosmetic
    • Tool “wave_reconstruct_time_domain_signal_v1” changed its title: Run wave.reconstruct-time-domain-signal.v1 → Reconstruct Time Domain Signal cosmetic
    • Tool “wave_rotate_and_validate_two_channel_frame_v1” changed its title: Run wave.rotate-and-validate-two-channel-frame.v1 → Rotate And Validate Two Channel Frame cosmetic
    • Tool “wave_transport_polarization_frame_v1” changed its title: Run transport-polarization-frame-v1 → Transport Polarization Frame cosmetic
    • Tool “wave_validate_reconstruction_quality_v1” changed its title: Run wave.validate-reconstruction-quality.v1 → Validate Reconstruction Quality cosmetic
    • Tool “wave_validate_spectral_criteria_v1” changed its title: Run wave.validate-spectral-criteria.v1 → Validate Spectral Criteria cosmetic
    • Tool “wave_verify_wave_pipeline_v1” changed its title: Run verify-wave-pipeline-v1 → Verify Wave Pipeline cosmetic
  • 7 Sept 26 +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.

  • 4 Sept 26 +1

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

Diagnostics

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 22 Sept 2026 · Probed https://jobs.rqmtechnologies.com/mcp/waveengine

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 15 Aug 2026 13 Nov 2026 ECDSA 256 ECDSA-SHA256 8a11e9b2275737960e5f7202f68ffdf2
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/waveengine Verified 200
http (plaintext) http://jobs.rqmtechnologies.com/mcp/waveengine HTTPS enforced 301 https://jobs.rqmtechnologies.com/mcp/waveengine
MCP tools · 34 exposed · ~2,878 tokens

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 →

Tool Tokens
estimate_wave_job ~53

Validate a bounded request against the live catalog and return a non-binding price and duration estimate without authentication.

NameTypeReqDescription
capability_idstringyes
max_total_pricestring
requestobjectyes

Structured output declared, but exposes no named fields.

No examples provided.

get_wave_capability ~27

Return one full approved public Wave capability descriptor.

NameTypeReqDescription
capability_idstringyes

Structured output declared, but exposes no named fields.

No examples provided.

get_wave_example ~35

Return one realistic illustrative request/result shape, artifact list, expected duration, and price guard.

NameTypeReqDescription
capability_idstringyes

Structured output declared, but exposes no named fields.

No examples provided.

get_wave_job_artifact ~52

Retrieve one principal-scoped bounded Wave result artifact.

NameTypeReqDescription
artifact_idstringyes
job_idstringyes
productstringyes
schema_versionstringyes

Structured output declared, but exposes no named fields.

No examples provided.

get_wave_job_result ~21

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_wave_job_status ~21

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.

get_wave_receipt ~39

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

NameTypeReqDescription
reservation_idstringyes
schema_versionstringyes

Structured output declared, but exposes no named fields.

No examples provided.

list_buyer_jobs ~54

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

NameTypeReqDescription
productstring
schema_versionstring
surfacestring

Structured output declared, but exposes no named fields.

No examples provided.

list_wave_capabilities ~59

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

NameTypeReqDescription
categorystring
maximum_duration_msinteger
maximum_pricestring
surfacestring

Structured output declared, but exposes no named fields.

No examples provided.

run_buyer_job ~81

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

NameTypeReqDescription
capability_idstringyes
idempotency_keystringyes
max_total_pricestringyes
productstringyes
requestobjectyes
schema_versionstringyes

Structured output declared, but exposes no named fields.

No examples provided.

run_wave_example ~35

Execute the catalog-owned bounded example through the real typed WaveEngine adapter without accepting arbitrary input.

NameTypeReqDescription
capability_idstringyes

Structured output declared, but exposes no named fields.

No examples provided.

run_wave_job ~104

Pay anonymously with x402 by default, or explicitly use an authenticated Account Core balance, then submit one idempotent WaveEngine job.

NameTypeReqDescription
artifact_preferencesobject
capability_idstringyes
idempotency_keystringyes
max_total_pricestring
maximum_runtime_secondsinteger
payment_railstring
requestobjectyes
schema_versionstringyes

Structured output declared, but exposes no named fields.

No examples provided.

search_buyer_jobs ~70

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

NameTypeReqDescription
limitinteger
productstring
querystringyes
schema_versionstring
surfacestring

Structured output declared, but exposes no named fields.

No examples provided.

search_wave_capabilities ~91

Deterministically rank executable WaveEngine capabilities for a natural-language task and bounded filters.

NameTypeReqDescription
categorystring
input_formatstring
limitinteger
maximum_duration_msinteger
maximum_pricestring
querystringyes
required_artifact_media_typestring
surfacestring

Structured output declared, but exposes no named fields.

No examples provided.

wave_apply_verified_phase_correction_v1 ~103

Problem: Apply this bounded phase correction and verify the supplied preservation assertions. Input: JSON with sample rate hz, channels, angle radians, assertions. Result: corrected capture and preservation checks. Limits: Bounded signal processing only; 2 channels; 1024 samples/channel.

NameTypeReqDescription
idempotency_keystringyes
max_total_pricestringyes
requestobjectyes
schema_versionstringyes

Structured output declared, but exposes no named fields.

No examples provided.

wave_compare_pipeline_responses_v1 ~109

Problem: Compare these two supported Wave pipelines on the supplied fixture and caller tolerances. Input: JSON with left pipeline, right pipeline, fixture, maximum rmse, maximum absolute.... Result: response differences and tolerance checks. Limits: Bounded signal processing only; 8 channels; 4096 samples/channel.

NameTypeReqDescription
idempotency_keystringyes
max_total_pricestringyes
requestobjectyes
schema_versionstringyes

Structured output declared, but exposes no named fields.

No examples provided.

wave_compare_waveform_captures_v1 ~112

Problem: Compare these two bounded waveforms against the supplied alignment and numeric rules. Input: JSON with sample rate hz, channels, reference channel id, candidate channel id, rules. Result: waveform differences and caller-rule results. Limits: Bounded signal processing only; 2 channels; 1024 samples/channel.

NameTypeReqDescription
idempotency_keystringyes
max_total_pricestringyes
requestobjectyes
schema_versionstringyes

Structured output declared, but exposes no named fields.

No examples provided.

wave_compile_curated_processing_recipe_v1 ~102

Problem: Compile this curated processing recipe and return its validated pipeline and execution trace. Input: JSON with fixture, maximum round trip rmse. Result: validated pipeline and execution trace. Limits: Bounded signal processing only; 8 channels; 4096 samples/channel.

NameTypeReqDescription
idempotency_keystringyes
max_total_pricestringyes
requestobjectyes
schema_versionstringyes

Structured output declared, but exposes no named fields.

No examples provided.

wave_convert_capture_to_spectrum_v1 ~104

Problem: Convert this bounded complex capture into a checksummed spectral artifact with declared normalization. Input: JSON with sample rate hz, channel, normalization. Result: spectrum with normalization and checksums. Limits: Bounded signal processing only; 8 channels; 4096 samples/channel.

NameTypeReqDescription
idempotency_keystringyes
max_total_pricestringyes
requestobjectyes
schema_versionstringyes

Structured output declared, but exposes no named fields.

No examples provided.

wave_diagnose_multichannel_capture_v1 ~107

Problem: Diagnose this coordinated complex capture for bounded Wave-Intelligence degradation findings without inferring a physical cause. Input: JSON with sample rate hz, channels. Result: bounded capture findings and artifacts. Limits: Bounded signal processing only; 8 channels; 1024 samples/channel.

NameTypeReqDescription
idempotency_keystringyes
max_total_pricestringyes
requestobjectyes
schema_versionstringyes

Structured output declared, but exposes no named fields.

No examples provided.

wave_equalize_pilot_capture_v1 ~111

Problem: Fit a bounded quaternion NLMS equalizer to this received and desired pilot capture. Input: JSON with input channels, output channels, received, desired, pilot mask. Result: fitted equalizer and pilot-fit evidence. Limits: Bounded signal processing only; 4 channels; 1024 samples/channel.

NameTypeReqDescription
idempotency_keystringyes
max_total_pricestringyes
requestobjectyes
schema_versionstringyes

Structured output declared, but exposes no named fields.

No examples provided.

wave_extract_wave_features_v1 ~102

Problem: Convert this coordinated complex capture into the deterministic versioned Wave-Intelligence feature vector. Input: JSON with sample rate hz, channels. Result: versioned feature vector and artifacts. Limits: Bounded signal processing only; 8 channels; 1024 samples/channel.

NameTypeReqDescription
idempotency_keystringyes
max_total_pricestringyes
requestobjectyes
schema_versionstringyes

Structured output declared, but exposes no named fields.

No examples provided.

wave_fit_coupled_channel_model_v1 ~106

Problem: Fit a bounded structured quaternion ridge model to these coupled channel features and targets. Input: JSON with feature count, output count, features, targets. Result: fitted channel model and fit evidence. Limits: Bounded signal processing only; 16 channels; 512 samples/channel.

NameTypeReqDescription
idempotency_keystringyes
max_total_pricestringyes
requestobjectyes
schema_versionstringyes

Structured output declared, but exposes no named fields.

No examples provided.

wave_gate_signal_capture_v1 ~110

Problem: Accept or reject this bounded signal capture against the caller-supplied metric rules and return every measurement and violation. Input: JSON with sample rate hz, channels, rules. Result: measurements, violations and checksummed artifacts. Limits: Bounded signal processing only; 8 channels; 1024 samples/channel.

NameTypeReqDescription
idempotency_keystringyes
max_total_pricestringyes
requestobjectyes
schema_versionstringyes

Structured output declared, but exposes no named fields.

No examples provided.

wave_generate_validated_signal_fixture_v1 ~108

Problem: Generate this bounded sine or safe-formula signal fixture and return reproducibility, measurement, checksum, and validation evidence. Input: JSON with fixture. Result: signal fixture, checksums and validation evidence. Limits: Bounded signal processing only; 8 channels; 16384 samples/channel.

NameTypeReqDescription
idempotency_keystringyes
max_total_pricestringyes
requestobjectyes
schema_versionstringyes

Structured output declared, but exposes no named fields.

No examples provided.

wave_measure_phase_drift_v1 ~108

Problem: Measure phase drift in this bounded complex observation against the supplied reference and tolerances. Input: JSON with reference, observation, maximum absolute drift radians, maximum rms.... Result: phase drift measurements and tolerance checks. Limits: Bounded signal processing only; 8 channels; 4096 samples/channel.

NameTypeReqDescription
idempotency_keystringyes
max_total_pricestringyes
requestobjectyes
schema_versionstringyes

Structured output declared, but exposes no named fields.

No examples provided.

wave_optimize_processing_pipeline_v1 ~109

Problem: Optimize this supported Wave pipeline against the supplied operation-count objective and equivalence rule. Input: JSON with operations, fixture, objective, maximum operations, maximum equivalence.... Result: candidate pipeline and equivalence checks. Limits: Bounded signal processing only; 8 channels; 4096 samples/channel.

NameTypeReqDescription
idempotency_keystringyes
max_total_pricestringyes
requestobjectyes
schema_versionstringyes

Structured output declared, but exposes no named fields.

No examples provided.

wave_reconstruct_bounded_capture_v1 ~112

Problem: Reconstruct this bounded capture under the supplied transfer assumption and verify it against the reference rules. Input: JSON with observation, reference, assumed transfer, maximum rmse, maximum.... Result: reconstructed capture and reference-rule checks. Limits: Bounded signal processing only; 8 channels; 4096 samples/channel.

NameTypeReqDescription
idempotency_keystringyes
max_total_pricestringyes
requestobjectyes
schema_versionstringyes

Structured output declared, but exposes no named fields.

No examples provided.

wave_reconstruct_time_domain_signal_v1 ~111

Problem: Convert these bounded frequency bins into time-domain samples and verify the caller's round-trip rule. Input: JSON with sample rate hz, frequency bins, normalization, rules. Result: time-domain samples and round-trip verification. Limits: Bounded signal processing only; 8 channels; 4096 samples/channel.

NameTypeReqDescription
idempotency_keystringyes
max_total_pricestringyes
requestobjectyes
schema_versionstringyes

Structured output declared, but exposes no named fields.

No examples provided.

wave_rotate_and_validate_two_channel_frame_v1 ~103

Problem: Rotate these two coordinated complex channels with the supplied rotor and validate caller invariants. Input: JSON with channels, rotor, rules. Result: rotated channels and invariant checks. Limits: Bounded signal processing only; 8 channels; 4096 samples/channel.

NameTypeReqDescription
idempotency_keystringyes
max_total_pricestringyes
requestobjectyes
schema_versionstringyes

Structured output declared, but exposes no named fields.

No examples provided.

wave_transport_polarization_frame_v1 ~106

Problem: Transform these Jones vectors or channel operators between the explicitly named SU(2) frames and verify invariants. Input: JSON with mode, rotor. Result: transformed vectors/operators and invariant checks. Limits: Bounded signal processing only; 4 channels; 1024 samples/channel.

NameTypeReqDescription
idempotency_keystringyes
max_total_pricestringyes
requestobjectyes
schema_versionstringyes

Structured output declared, but exposes no named fields.

No examples provided.

wave_validate_reconstruction_quality_v1 ~96

Problem: Compare this reconstruction with the supplied reference and acceptance rules. Input: JSON with reference, reconstruction, rules. Result: reconstruction differences and rule results. Limits: Bounded signal processing only; 8 channels; 4096 samples/channel.

NameTypeReqDescription
idempotency_keystringyes
max_total_pricestringyes
requestobjectyes
schema_versionstringyes

Structured output declared, but exposes no named fields.

No examples provided.

wave_validate_spectral_criteria_v1 ~105

Problem: Accept or reject this bounded capture against the caller's supplied spectral criteria. Input: JSON with sample rate hz, channel, normalization, rules. Result: spectral metrics and caller-rule verdict. Limits: Bounded signal processing only; 8 channels; 4096 samples/channel.

NameTypeReqDescription
idempotency_keystringyes
max_total_pricestringyes
requestobjectyes
schema_versionstringyes

Structured output declared, but exposes no named fields.

No examples provided.

wave_verify_wave_pipeline_v1 ~112

Problem: Execute and verify this bounded Wave IR pipeline against the required representation, shape, and optional round-trip assertions. Input: JSON with sample rate hz, channels, operators, assertions. Result: execution result and shape/round-trip checks. Limits: Bounded signal processing only; 2 channels; 1024 samples/channel.

NameTypeReqDescription
idempotency_keystringyes
max_total_pricestringyes
requestobjectyes
schema_versionstringyes

Structured output declared, but exposes no named fields.

No examples provided.

Common questions

What is the RQM WaveEngine Jobs MCP server?

RQM WaveEngine Jobs is an MCP server listed in the public MCP registry as com.rqmtechnologies/waveengine. Delegate 20 typed, evidence-backed WaveEngine signal work products with fixed-request x402. This page covers its hosted endpoint (https://jobs.rqmtechnologies.com/mcp/waveengine).

Is the RQM WaveEngine Jobs MCP server safe to use?

RQM WaveEngine 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 WaveEngine Jobs MCP server expose?

RQM WaveEngine Jobs exposes 34 tools: list_buyer_jobs, search_buyer_jobs, list_wave_capabilities, get_wave_capability, run_buyer_job, and 29 more. Their descriptions and schemas cost roughly 2,878 tokens of context every time the server is loaded.

Does the RQM WaveEngine Jobs MCP server require authentication?

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

Is the RQM WaveEngine Jobs MCP server still maintained?

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