Robin Saige we check the tools AI agents call

WhiteIntel — Ownership Intelligence

dev.whiteintel/whiteintel

UBO, sanctions & ownership graph. 23 tools, 130.7M entities, 31 registries.

— the operator's own registry description reported

Publisher dev.whiteintel · first seen 2026-08-20 · endpoint https://whiteintel.dev/api/mcp

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

Dependency rating derived

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

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

Does it answer? Q1 · observed
answersalive_tools
latency353 ms
vs populationslow
protocolcurrent
authopen
Can it be used? Q4 · observed
tools24
vs populationhigh
capabilities2
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_5c19ecf6b80e17c9094989cf · 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 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 (3 shown, 2026-08-23 → 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 (2 events)
datetypewhat changed
2026-08-30inventorytools 23 → 24
2026-08-23outcomefirst 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-public22serves 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

Tools last seen observed

buy_dossier check_offshore_exposure claim_dossier find_similar get_company_details get_dossier get_entity get_financials get_payment_link get_pricing get_pulse get_sanctions graph_neighbourhood graph_path list_asset_coverage list_jurisdictions lookup_by_identifier lookup_company purchase_dossier resolve search_companies search_entities semantic_search trace_ownership_path

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 & specific24/24
has a description24/24
description is substantive24/24
parameters are typed24/24
parameters are described8/248/24

24 of 24 tools graded · 24 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
OFAC SDN screening (vs the official list)ISLAMIC REVOLUTIONARY GUARD CORPSunverifiableofac-sdn
OFAC SDN screening (vs the official list)MAERSK LINEunverifiableofac-sdn

Protocol conformance observed

2025-06-18
protocol version
session model
0.7.11
server version whiteintel-mcp-server

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:13:24Zok_tools2003532025-06-18
2026-08-30T06:13:04Zok_tools2003412025-06-18
2026-08-23T06:12:31Zok_tools2003632025-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/dev.whiteintel/whiteintel.svg)](https://robinsaige.com/s/dev.whiteintel/whiteintel)

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 →