Robin Saige we check the tools AI agents call

Blackbook Protocol Advisor

io.github.koynlabs/blackbook-advisor

Purchaser-gated MCP for Vault, HMRC TRS, 95/5 equity, and Companies House PSC.

— the operator's own registry description reported

Publisher io.github.koynlabs · first seen 2026-08-30 · endpoint https://theblackbook.pro

allow
verdict
mid-solo
cluster
ok_tools
answers
25
tools served

Dependency rating derived

allow
allow — alive & usable · retrieval-public ● · V1 shows its work ◐
allow — because answers ●, 25 tools legible (band A) ●, no confirmed drift in 2 probes ●; not yet checked: truth (0 runs)

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

Does it answer? Q1 · observed
answersalive_tools
latency114 ms
vs populationtypical
protocolcurrent
authopen
Can it be used? Q4 · observed
tools25
vs populationhigh
capabilities2
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_0de4c8218f12eaab5bf055a6 · 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?V1 shows its work ◐evidence ↓
Q4Did it hold?harness A · 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 (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-public14serves public factstruth-checkable against a public source — the V-ladder applies in full
action4changes 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
generative3creates contentno answer key exists; disclosure + stability checks, never truth verdicts

Tools last seen observed

confirm_and_submit draft_form_answers end_browser_session explain_current_screen fill_fields generate_review_bundle get_companies_house_guidance get_hmrc_guidance get_legal_boundary get_module_playbook get_self_serve_portal get_skill list_fillable_fields list_implementation_modes list_modules list_risk_flags list_skills open_portal prepare_portal_fill prepare_submit_confirmation request_user_action run_trust_intake search_book start_browser_session wait_for_user_ready

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 & specific25/25
has a description25/25
description is substantive25/25
parameters are typed25/25
parameters are described25/25

25 of 25 tools graded · 25 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

2025-06-18
protocol version
session model
1.0.0
server version blackbook-advisor

Capabilities: resources 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:16:15Zok_tools2001142025-06-18
2026-08-30T06:15:48Zok_tools2001172025-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.github.koynlabs/blackbook-advisor.svg)](https://robinsaige.com/s/io.github.koynlabs/blackbook-advisor)

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 →