Robin Saige we check the tools AI agents call

Stratalize Healthcare

com.stratalize/healthcare

CMS benchmarks, travel nurse rates, pharmacy spend, billing risk, and payer intelligence.

— the operator's own registry description reported

Publisher com.stratalize · first seen 2026-08-12 · endpoint https://www.stratalize.com/api/mcp-public?vertical=healthcare

allow
verdict
mid-shared
cluster
ok_tools
answers
29
tools served

Dependency rating derived

allow
allow — alive & usable · retrieval-public ● · V3 has answer key ◐
allow — because answers ●, 29 tools legible (band B) ●, no confirmed drift in 2 probes ●; not yet checked: truth (3 attempts unverifiable, 0 disagreements)

Cluster mid-shared · distinctiveness 0.21 (typical). Every figure is a percentile or class within the 11,094-server censussee the whole spectrum.

Does it answer? Q1 · observed
answersalive_tools
latency245 ms
vs populationtypical
protocolcurrent
authopen
Can it be used? Q4 · observed
tools29
vs populationmid
capabilities1
harnessB
Did it hold when checked? Q3–Q4 · derived
identityshared
servers on its host8
verifiabilityunassessed
duplicate inventoryno
drift events0
answers true0/0 agree

🔏 Signed receipt rr_b6553b1b3e0a49c0024e2490 · 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 — 2 probes ●evidence ↓
Q2What is it?retrieval-public ● evidence ↓
Q3Can it be checked?V3 has answer key ◐evidence ↓
Q4Did it hold?harness B · truth not yet run · no drift ●evidence ↓
Q5What company does it keep?mid-shared · 8 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 (2 shown, 2026-08-12 → 2026-08-14). 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 (1 events)
datetypewhat changed
2026-08-12outcomefirst probe: ok_tools

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
retrieval-public25serves public factstruth-checkable against a public source — the V-ladder applies in full
computational3deterministic transformsself-checkable by re-computation and known-answer tests
generative1creates contentno answer key exists; disclosure + stability checks, never truth verdicts

Tools last seen observed

get_asc_benchmark get_billing_coding_risk get_cms_facility_benchmark get_cms_open_payments_profile get_cms_star_rating get_cost_plus_price get_device_clearances get_drug_adverse_events get_drug_label_intelligence get_drug_recall_status get_ehr_cost_per_bed get_fda_recall_history get_gpo_contract_benchmark get_healthcare_category_intelligence get_healthcare_vendor_market_rate get_hospital_care_compare_quality get_hospital_supply_chain_benchmark get_irs_990_intelligence get_nadac_drug_benchmark get_npi_provider_verification get_openfda_adverse_events get_payer_intelligence get_pharmacy_spend_benchmark get_physician_group_benchmark get_provider_market_intelligence get_staffing_agency_markup_analysis get_stratalize_overview get_travel_nurse_rate_benchmark get_value_based_care_performance

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 & specific29/29
has a description29/29
description is substantive29/29
parameters are typed29/29
parameters are described2/292/29

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

claim classkeyverdictprimary source
tariff-duty0901.21.00unverifiableus-hts
tariff-duty6109.10.00unverifiableus-hts
tariff-duty8471.30.01unverifiableus-hts

Protocol conformance observed

2025-06-18
protocol version
session model
1.0.0
server version stratalize-intelligence

Capabilities: tools

Drift observed

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

raw probe records
probed (UTC) outcomehttpmsprotocol
2026-08-14T19:58:32Zok_tools2002452025-06-18
2026-08-12T05:33:47Zok_tools2001492025-06-18

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

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