Robin Saige we check the tools AI agents call

gavel

io.thegavel/gavel

Oracle-free fixed-rate, fixed-term BTC credit on Arbitrum One. Data and unsigned blueprints.

— the operator's own registry description reported

Publisher io.thegavel · first seen 2026-08-27 · endpoint https://mcp.thegavel.io/mcp

allow
verdict
mid-slow-solo
cluster
ok_tools
answers
21
tools served

Dependency rating derived

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

Cluster mid-slow-solo · distinctiveness 0.436 (moderate). Every figure is a percentile or class within the 15,472-server censussee the whole spectrum.

Does it answer? Q1 · observed
answersalive_tools
latency462 ms
vs populationslow
protocolcurrent
authopen
Can it be used? Q4 · observed
tools21
vs populationmid
capabilities1
harnessA
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_ae8fe54027642763d9ff9f20 · 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 A · truth not yet run · no drift ●evidence ↓
Q5What company does it keep?mid-slow-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 (2 shown, 2026-08-30 → 2026-09-06). 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-30outcomefirst 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-public9serves public factstruth-checkable against a public source — the V-ladder applies in full
action7changes the worldno true answer exists; we check the CONTRACT (destructive/read-only/idempotent declarations, error legibility) and never fire real actions
orchestration3routes other toolsidentity + fronted-service disclosure checks (gateway vs costume)
computational2deterministic transformsself-checkable by re-computation and known-answer tests

Tools last seen observed

check_wallet_status find_auctions_matching_criteria get_address_history get_book get_gavel_indicator get_loan_status get_mvrv get_protocol_reference get_user_positions get_verification_bundle get_yield_curve list_comparables list_fiat_onramps list_gavel_indicators list_onchain_indicators list_wallet_options prepare_bid_calldata prepare_claim_collateral_calldata prepare_claim_refund_calldata prepare_create_auction_calldata prepare_repay_loan_calldata

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 A — an agent can pick and call these reliably.

legibility checktools passingok
name is clear & specific21/21
has a description21/21
description is substantive21/21
parameters are typed21/21
parameters are described21/21

21 of 21 tools graded · 21 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
0.4.0
server version aletheia-mcp

Capabilities: tools

Drift observed

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

raw probe records
probed (UTC) outcomehttpmsprotocol
2026-09-06T06:17:29Zok_tools2004622025-06-18
2026-08-30T06:17:15Zok_tools2004482025-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/io.thegavel/gavel.svg)](https://robinsaige.com/s/io.thegavel/gavel)

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 →