Robin Saige we check the tools AI agents call

Mostly Right

md.mostlyright/datasets

Search, sample and query open reproducible datasets published as immutable Parquet with schemas.

— the operator's own registry description reported

Publisher md.mostlyright · first seen 2026-09-11 · endpoint https://mostlyright.md/api/mcp

allow
verdict
rich-solo
cluster
ok_tools
answers
34
tools served

Dependency rating derived

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

Cluster rich-solo · distinctiveness 0.595 (moderate). Every figure is a percentile or class within the 19,148-server censussee the whole spectrum.

Does it answer? Q1 · observed
answersalive_tools
latency180 ms
vs populationtypical
protocolcurrent
authopen
Can it be used? Q4 · observed
tools34
vs populationhigh
capabilities3
harnessB
Did it hold when checked? Q3–Q4 · derived
identitysolo
servers on its host1
verifiabilityunassessed
duplicate inventoryno
drift events0
answers true0/0 agree

🔏 Signed receipt rr_b53b25d0a37a826c1b53cb0c · 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 — 1 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?rich-solo · 1 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 (1 shown, 2026-09-13 → 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 (1 events)
datetypewhat changed
2026-09-13outcomefirst 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-public19serves public factstruth-checkable against a public source — the V-ladder applies in full
action10changes the worldno true answer exists; we check the CONTRACT (destructive/read-only/idempotent declarations, error legibility) and never fire real actions
retrieval-private3serves the caller's own dataoutside truth-checking is impossible BY NATURE, not by failure — the operator-invited pathway applies
generative2creates contentno answer key exists; disclosure + stability checks, never truth verdicts

Tools last seen observed

cancel_run catalog_search confirm_run connect_dataset create_dataset diagnose_table fetch get_access_instructions get_artifact_download get_dataset get_download_instructions get_my_dataset get_run get_table get_table_schema list_connected_datasets list_my_datasets list_runs list_source_credentials list_tables promote_table propose_revision query_run query_table register_recipe replay_run run_artifacts run_events sample_rows search search_datasets start_run update_dataset write_note

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 & specific34/34
has a description34/34
description is substantive34/34
parameters are typed34/34
parameters are described2/342/34

34 of 34 tools graded · 34 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 — 2 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

Protocol conformance observed

2025-06-18
protocol version
session model
2.0.0
server version mostlyright

Capabilities: prompts resources 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:18:57Zok_tools2001802025-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/md.mostlyright/datasets.svg)](https://robinsaige.com/s/md.mostlyright/datasets)

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 →