Robin Saige we check the tools AI agents call

biii

io.github.philpof102-svg/biii

Fail-closed safe-to-pay verdicts on Base: known-bad wallets, look-alike tokens, repeat rug funders.

— the operator's own registry description reported

Publisher io.github.philpof102-svg · first seen 2026-08-12 · endpoint https://biii-production.up.railway.app/mcp

allow
verdict
stale-mid-fast-solo
cluster
ok_tools
answers
29
tools served

Dependency rating derived

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

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

Does it answer? Q1 · observed
answersalive_tools
latency14 ms
vs populationfast
protocolstale
authopen
Can it be used? Q4 · observed
tools29
vs populationmid
capabilities1
harnessA
Did it hold when checked? Q3–Q4 · derived
identitysolo
servers on its host1
verifiabilityunassessed
duplicate inventoryno
drift events0
answers trueno primary

🔏 Signed receipt rr_9ad5b23861038a5c8a8472f7 · 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 A · truth not yet run · no drift ●evidence ↓
Q5What company does it keep?stale-mid-fast-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
action23changes the worldno true answer exists; we check the CONTRACT (destructive/read-only/idempotent declarations, error legibility) and never fire real actions
unclassified4not classifiable from its textTier-1 only until its tools describe themselves
generative1creates contentno answer key exists; disclosure + stability checks, never truth verdicts
retrieval-public1serves public factstruth-checkable against a public source — the V-ladder applies in full

Tools last seen observed

till_authorize till_b20_authentic till_check_invoice till_check_payment till_create_charge till_create_invoice till_export till_floor till_funder_history till_key_exposure till_kya till_launch_funder till_meter till_open_approvals till_receipt till_recovery_offer till_resolve till_roll till_rug_powers till_seed_exposure till_trace_theft till_trust till_verify_delivery till_vet_agent till_vet_approach till_vet_asset till_vet_meme till_vet_merchant till_watch_wallet

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 & specific29/29
has a description29/29
description is substantive29/29
parameters are typed26/2926/29
parameters are described20/2920/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 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 biii

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:59:56Zok_tools200142024-11-05
2026-08-12T05:35:12Zok_tools200162024-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.philpof102-svg/biii.svg)](https://robinsaige.com/s/io.github.philpof102-svg/biii)

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