Robin Saige we check the tools AI agents call

RQM Studio Jobs

com.rqmtechnologies/studio

Delegate 20 fail-closed RQM Studio quantum work products with fixed-request x402.

— the operator's own registry description reported

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

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

Dependency rating derived

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

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

Does it answer? Q1 · observed
answersalive_tools
latency2231 ms
vs populationslow
protocolcurrent
authopen
Can it be used? Q4 · observed
tools43
vs populationhigh
capabilities1
harnessB
Did it hold when checked? Q3–Q4 · derived
identityshared
servers on its host4
verifiabilityunassessed
duplicate inventoryno
drift events0
answers true0/0 agree

🔏 Signed receipt rr_6835e35186210144823ac719 · 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
unclassified20not classifiable from its textTier-1 only until its tools describe themselves
action9changes the worldno true answer exists; we check the CONTRACT (destructive/read-only/idempotent declarations, error legibility) and never fire real actions
retrieval-public9serves public factstruth-checkable against a public source — the V-ladder applies in full
generative4creates contentno answer key exists; disclosure + stability checks, never truth verdicts
orchestration1routes other toolsidentity + fronted-service disclosure checks (gateway vs costume)

Tools last seen observed

audit_quantum_transformation cancel_job check_quantum_circuit classify_two_qubit_operation compare_quantum_circuits create_funding_session 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

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 & specific43/43
has a description43/43
description is substantive43/43
parameters are typed43/43
parameters are described7/437/43

43 of 43 tools graded · 43 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 yet confirmed — 1 attempt(s) currently unverifiable (rate limits, walls, or unmappable schemas — never counted against the server) · 0 disagreements.

claim classkeyverdictprimary source
tariff-dutyunmappedunverifiableus-hts

Protocol conformance observed

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

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_tools20022312025-06-18
2026-09-06T06:12:56Zhttp_error400117
2026-08-30T06:12:38Zhttp_error400398
2026-08-23T06:12:11Zhttp_error40022

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/studio.svg)](https://robinsaige.com/s/com.rqmtechnologies/studio)

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 →