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.846395+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/studio",
"legal_identity": null,
"lifecycle": null,
"observed_at": "2026-10-30T10:38:14.846395+00:00",
"registry_status": null,
"subject": {
"id": "com.rqmtechnologies/studio",
"kind": "mcp"
},
"tools": {
"names": [
"audit_quantum_transformation",
"cancel_job",
"check_quantum_circuit",
"classify_two_qubit_operation",
"compare_quantum_circuits",
"create_funding_session",
"describe_quantum_capabilities",
"diagnose_quantum_phase",
"diagnose_quantum_workflow",
"get_account_balance",
"get_capability",
"get_job_result",
"get_job_status",
"get_studio_receipt",
"list_buyer_jobs",
"list_capabilities",
"optimize_quantum_circuit",
"quantum_circuit_assurance_report_v1",
"quantum_cross_provider_portability_v1",
"quantum_execution_plan_select_v1",
"quantum_failed_workflow_diagnosis_v1",
"quantum_gate_basis_decomposition_v1",
"quantum_managed_simulator_v1",
"quantum_openqasm3_preflight_v1",
"quantum_openqasm3_repair_v1",
"quantum_optimization_preservation_audit_v1",
"quantum_phase_aware_rewrite_v1",
"quantum_phase_sensitive_inspection_v1",
"quantum_provider_readiness_check_v1",
"quantum_provider_result_compare_v1",
"quantum_provider_target_compile_v1",
"quantum_simulation_anomaly_diagnostic_v1",
"quantum_simulation_result_compare_v1",
"quantum_supported_circuit_equivalence_v1",
"quantum_two_qubit_local_equivalence_v1",
"quantum_two_qubit_target_synthesis_v1",
"quantum_verified_circuit_optimization_v1",
"quote_job",
"repair_openqasm3",
"run_buyer_job",
"search_buyer_jobs",
"submit_quantum_job",
"synthesize_two_qubit_target",
"translate_quantum_circuit"
],
"names_truncated": false,
"sha256": "1522208610f620a9dc43b191bf095d8d207390fc16dee4a29a22bf96dd1556a2"
},
"tools_complete": true,
"tools_observed_at": "2026-10-30T10:38:14.846395+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