Robin Saige we check the tools AI agents call

bookrails

io.github.pinalmdave/bookrails

Find, compare, and book local service businesses: live availability, prices, reviews, booking.

— the operator's own registry description reported

Publisher io.github.pinalmdave · first seen 2026-08-12 · endpoint https://bookrails-api.azurewebsites.net/mcp/

allow
verdict
mid-solo
cluster
ok_tools
answers
13
tools served

Dependency rating derived

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

Cluster mid-solo · distinctiveness 0.477 (moderate). Every figure is a percentile or class within the 11,363-server censussee the whole spectrum.

Does it answer? Q1 · observed
answersalive_tools
latency295 ms
vs populationtypical
protocolcurrent
authopen
Can it be used? Q4 · observed
tools13
vs populationmid
capabilities4
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_cbf44c4a1b1bc7528439e8c4 · 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 — 3 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-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 (3 shown, 2026-08-12 → 2026-08-16). 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-08-16outcomeok_tools (was connect_error)
2026-08-12outcomefirst probe: connect_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
retrieval-public10serves public factstruth-checkable against a public source — the V-ladder applies in full
action2changes the worldno true answer exists; we check the CONTRACT (destructive/read-only/idempotent declarations, error legibility) and never fire real actions
unclassified1not classifiable from its textTier-1 only until its tools describe themselves

Tools last seen observed

ask_business_question book_appointment cancel_or_reschedule check_availability compare_businesses get_availability_now get_business_details get_local_insights get_price_estimates get_promotions get_reviews join_waitlist search_businesses

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 & specific13/13
has a description13/13
description is substantive13/13
parameters are typed13/13
parameters are described1/131/13

13 of 13 tools graded · 13 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.29.0
server version bookrails

Capabilities: experimental prompts resources tools

Drift observed

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

raw probe records
probed (UTC) outcomehttpmsprotocol
2026-08-16T06:13:33Zok_tools2002952025-06-18
2026-08-14T19:59:56Zconnect_error8
2026-08-12T05:35:12Zconnect_error6

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.github.pinalmdave/bookrails.svg)](https://robinsaige.com/s/io.github.pinalmdave/bookrails)

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 →