Robin Saige we check the tools AI agents call

Agent Broker

io.github.basilalshukaili/agent-broker

AI agents find, message & book SMBs; pay per call in USDC on Base via x402. 14 tools, compliant.

— the operator's own registry description reported

Publisher io.github.basilalshukaili · first seen 2026-08-12 · endpoint https://agent-broker-edge.basil-agent.workers.dev/mcp

allow
verdict
stale-mid-solo
cluster
ok_tools
answers
14
tools served

Dependency rating derived

allow
allow — alive & usable · action ● · V n/a
allow — because answers ●, 14 tools legible (band B) ●, no confirmed drift in 2 probes ●; not yet checked: truth (0 runs)

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

Does it answer? Q1 · observed
answersalive_tools
latency107 ms
vs populationtypical
protocolstale
authopen
Can it be used? Q4 · observed
tools14
vs populationmid
capabilities4
harnessB
Did it hold when checked? Q3–Q4 · derived
identitysolo
servers on its host1
verifiabilityunassessed
duplicate inventoryno
drift events0
answers trueno primary

🔏 Signed receipt rr_a8ad7faeff84ad5ac4209979 · 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?action ● 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?stale-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 (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
action8changes the worldno true answer exists; we check the CONTRACT (destructive/read-only/idempotent declarations, error legibility) and never fire real actions
retrieval-public6serves public factstruth-checkable against a public source — the V-ladder applies in full

Tools last seen observed

call_business capture_lead escalate_to_human find_business get_outcome get_status handle_inbound import_booking_url preview_cost schedule_appointment self_test send_message send_transactional_confirmation verify_business

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 & specific14/14
has a description14/14
description is substantive14/14
parameters are typed14/14
parameters are described2/142/14

14 of 14 tools graded · 14 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 in the Tier-2 trade lane, or not yet checked. Tier-2 re-derives a server's answers against published primary sources — see truth checks.

Protocol conformance observed

2024-11-05
protocol version
session model
0.1.0
server version smb-broker

Capabilities: logging prompts resources 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:59:24Zok_tools2001072024-11-05
2026-08-12T05:34:36Zok_tools2001802024-11-05

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

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