Robin Saige we check the tools AI agents call

RQM WaveEngine Jobs

com.rqmtechnologies/waveengine

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

— the operator's own registry description reported

Publisher com.rqmtechnologies · first seen 2026-08-17 · endpoint https://jobs.rqmtechnologies.com/mcp/waveengine

allow
verdict
rich-slow-shared
cluster
ok_tools
answers
34
tools served

Dependency rating derived

allow
allow — alive & usable · kind unknown · V n/a
allow — because answers ●, 34 tools legible (band B) ●, no confirmed drift in 4 probes ●; not yet checked: truth (0 runs)

Cluster rich-slow-shared · distinctiveness 0.709 (unusual). Every figure is a percentile or class within the 19,148-server censussee the whole spectrum.

Does it answer? Q1 · observed
answersalive_tools
latency3024 ms
vs populationslow
protocolcurrent
authopen
Can it be used? Q4 · observed
tools34
vs populationhigh
capabilities1
harnessB
Did it hold when checked? Q3–Q4 · derived
identityshared
servers on its host4
verifiabilityunassessed
duplicate inventoryno
drift events0
answers trueno primary

🔏 Signed receipt rr_e0390c69a7963034034fc0ec · ed25519 · key rs-rcpt-2026-08 — this rating is tamper-evident; an agent gets the full signature from check_server and can verify it against the published key.

Q1Does it answer?alive & usable — 4 probes ●evidence ↓
Q2What is it?kind unknown ● evidence ↓
Q3Can it be checked?V n/a for this kind ◐evidence ↓
Q4Did it hold?harness B · truth not yet run · no drift ●evidence ↓
Q5What company does it keep?rich-slow-shared · 4 on its host (context, not verdict) ◐evidence ↓

● observed · ◐ derived · ○ reported — the verdict synthesizes Q1–Q4; Q5 is context. Methodology →

History observed

Every probe we made, oldest → newest (4 shown, 2026-08-23 → 2026-09-13). Green answered · amber answered-but-walled · red no useful answer. A gap in our cadence is a gap in coverage, not evidence about the server.

changelog (2 events)
datetypewhat changed
2026-09-13outcomeok_tools (was http_error)
2026-08-23outcomefirst probe: http_error

What kind of tools these are derived

Verification only means something relative to a tool's NATURE — an email-sender has no "true answer", a generator has no answer key. Classification evidence: classified from tool names/descriptions/annotations WE OBSERVED. What checking applies to each kind (the full methodology →):

naturetoolsmeaning what checking applies
unclassified13not classifiable from its textTier-1 only until its tools describe themselves
retrieval-public12serves public factstruth-checkable against a public source — the V-ladder applies in full
action4changes the worldno true answer exists; we check the CONTRACT (destructive/read-only/idempotent declarations, error legibility) and never fire real actions
computational4deterministic transformsself-checkable by re-computation and known-answer tests
generative1creates contentno answer key exists; disclosure + stability checks, never truth verdicts

Tools last seen observed

estimate_wave_job get_wave_capability get_wave_example get_wave_job_artifact get_wave_job_result get_wave_job_status get_wave_receipt list_buyer_jobs list_wave_capabilities run_buyer_job run_wave_example run_wave_job search_buyer_jobs search_wave_capabilities wave_apply_verified_phase_correction_v1 wave_compare_pipeline_responses_v1 wave_compare_waveform_captures_v1 wave_compile_curated_processing_recipe_v1 wave_convert_capture_to_spectrum_v1 wave_diagnose_multichannel_capture_v1 wave_equalize_pilot_capture_v1 wave_extract_wave_features_v1 wave_fit_coupled_channel_model_v1 wave_gate_signal_capture_v1 wave_generate_validated_signal_fixture_v1 wave_measure_phase_drift_v1 wave_optimize_processing_pipeline_v1 wave_reconstruct_bounded_capture_v1 wave_reconstruct_time_domain_signal_v1 wave_rotate_and_validate_two_channel_frame_v1 wave_transport_polarization_frame_v1 wave_validate_reconstruction_quality_v1 wave_validate_spectral_criteria_v1 wave_verify_wave_pipeline_v1

Harness readiness observed

Can an agent's harness pick this tool and call it correctly? Graded on the three things an agent reads — name, description, typed parameters. Band B — usable, with rough edges.

legibility checktools passingok
name is clear & specific34/34
has a description34/34
description is substantive34/34
parameters are typed34/34
parameters are described2/342/34

34 of 34 tools graded · 34 with a captured input schema. RS-008, Tier-1 — no domain knowledge, applies to any tool. “Alive” is not the same as “usable”.

Truth checks observed

Not in the Tier-2 trade lane, or not yet checked. Tier-2 re-derives a server's answers against published primary sources — see truth checks.

Protocol conformance observed

2025-06-18
protocol version
session model
1.7.0
server version com.rqmtechnologies/waveengine

Capabilities: tools

Drift observed

No confirmed drift on record. Baseline set 2026-09-13; changes appear here after human review.

raw probe records
probed (UTC) outcomehttpmsprotocol
2026-09-13T06:13:37Zok_tools20030242025-06-18
2026-09-06T06:12:56Zhttp_error40083
2026-08-30T06:12:38Zhttp_error400396
2026-08-23T06:12:11Zhttp_error40031

Watch or embed this verdict

verdict badge

Operators: put the live verdict in your README — it updates with every census, links back here, and is a dated observation, never a warranty:

[![Robin Saige verdict](https://robinsaige.com/badge/com.rqmtechnologies/waveengine.svg)](https://robinsaige.com/s/com.rqmtechnologies/waveengine)

Depend on it? Subscribe to its change feed — outcome changes and confirmed drift, no account needed. Building on it? The full dossier as JSON — verdict, rating, truth checks, history — stable enough to gate CI on.

← overview

Operator of this server? Everything we hold about it is on this page — free, no account, for anyone. Wrong attribution, stale probe, misclassification? Dispute this record →