For teams using external agents and MCP servers: inspect measured evidence, watch changes, and keep a record of what your team accepted. Unknown evidence stays explicit.
Have a client configuration? Extract and check its public endpoints locally. Maintaining integrations for clients? Explore the agency pilot.
Runtime observation: 2026-10-30T10:38:15.210986+00:00 · State: live
Watch availability, tools and parameter schemas, authentication access, endpoint changes and lifecycle notices. Only complete observed schemas are compared. OAuth scope and consent-screen changes are not currently measured.
Sign in to watch this MCP serverSign-in required. Agent and MCP watches share the existing Free / Pro / Enterprise budget. Manage watches.
{
"auth": "anonymous",
"availability": "live",
"endpoint": "https://jobs.rqmtechnologies.com/mcp/waveengine",
"legal_identity": null,
"lifecycle": null,
"observed_at": "2026-10-30T10:38:15.210986+00:00",
"registry_status": null,
"subject": {
"id": "com.rqmtechnologies/waveengine",
"kind": "mcp"
},
"tools": {
"names": [
"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"
],
"names_truncated": false,
"sha256": "d35d48821ea7f3e2130b1e1adf3b864c8023eb1d650d040e005432abb5ed56e0"
},
"tools_complete": true,
"tools_observed_at": "2026-10-30T10:38:15.210986+00:00",
"version": null
}Keep an accepted snapshot in agents.lock.json. CI compares it with current evidence and returns allow, review or block with reasons, before/after data and policy hashes.
Default gaps require review. Configure stricter handling explicitly. A lock records your acceptance; it is not a supplier attestation.
API referenceVerified domain owners can publish up to five exact-match sandbox fixtures and opt in to a test run. Results include fixture version, latency, output hashes and comparable regressions. Cost remains unknown when unobserved.
Run with POST /api/v1/dependencies/task-checks?domain=… while signed in. Read the schema and example in the integration guide.
Domain control, a declared business identifier and an active name-matched company record are separate evidence. Zero verified records means zero recorded proof.
Current coverage and measurement date · Verify your domainVerify issuer signatures, subject and credential freshness using the public key document. Keep its task evidence categories separate from Agenstry measurements.
A valid SEAL does not establish domain ownership, legal identity, key possession or execution permission.
Credential verification API · Issuer documentationSmithery endpoint migration · Agent monitoring · Methodology