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:14.700131+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",
"legal_identity": null,
"lifecycle": null,
"observed_at": "2026-10-30T10:38:14.700131+00:00",
"registry_status": null,
"subject": {
"id": "com.rqmtechnologies/jobs",
"kind": "mcp"
},
"tools": {
"names": [
"cancel_job",
"create_funding_session",
"describe_quantum_capabilities",
"get_account_balance",
"get_account_job",
"get_capability",
"get_job_artifact",
"get_job_result",
"get_job_status",
"list_account_jobs",
"list_buyer_jobs",
"list_capabilities",
"quote_job",
"robotics_analyze_force_disturbance_response_v1",
"robotics_assess_calibration_quality_v1",
"robotics_check_collision_constraints_v1",
"robotics_compare_controller_responses_v1",
"robotics_compare_digital_twin_observations_v1",
"robotics_compare_planned_observed_trajectories_v1",
"robotics_compare_state_estimators_v1",
"robotics_compute_actuator_alignment_correction_v1",
"robotics_diagnose_trajectory_instability_v1",
"robotics_estimate_fused_state_v1",
"robotics_frame_convention_validation_v1",
"robotics_normalize_sensor_frames_v1",
"robotics_optimize_disturbance_rejection_v1",
"robotics_optimize_trajectory_to_constraints_v1",
"robotics_reconstruct_smoothed_trajectory_v1",
"robotics_replay_workcell_trace_v1",
"robotics_tune_controller_to_objectives_v1",
"robotics_validate_closed_loop_stability_v1",
"robotics_validate_kinematic_dynamic_limits_v1",
"robotics_validate_trajectory_timing_v1",
"run_account_job",
"run_buyer_job",
"search_buyer_jobs",
"settle_buyer_job",
"submit_quantum_job",
"submit_wave_job"
],
"names_truncated": false,
"sha256": "5ea856c3017988cd65b85dd6b5ff424c1fac3d8f094dca67a3dcadab2ab194e1"
},
"tools_complete": true,
"tools_observed_at": "2026-10-30T10:38:14.700131+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