Robin Saige we check the tools AI agents call

customswise

io.github.giachi85it-ux/customswise

Practitioner-verified EU customs facts: classification, duty, origin, procedures. x402.

— the operator's own registry description reported

Publisher io.github.giachi85it-ux · first seen 2026-08-12 · endpoint https://customswise-api.onrender.com/mcp

allow
verdict
mid-solo
cluster
ok_tools
answers
7
tools served

Dependency rating derived

allow
allow — alive & usable · action ● · V n/a
allow — because answers ●, 7 tools legible (band A) ●, no confirmed drift in 37 probes ●; not yet checked: truth (4 attempts unverifiable, 0 disagreements)

Cluster mid-solo · distinctiveness 0.132 (typical). Every figure is a percentile or class within the 15,472-server census — see the whole spectrum.

Does it answer? Q1 · observed
answersalive_tools
latency125 ms
vs populationtypical
protocolcurrent
authopen
Can it be used? Q4 · observed
tools7
vs populationmid
capabilities1
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_fa00b250bd0a46a6b4f95249 · 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 — 37 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?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 (37 shown, 2026-08-12 → 2026-09-10). 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-09-01outcomeok_tools (was http_error)
2026-08-12outcomefirst probe: http_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
action4changes the worldno true answer exists; we check the CONTRACT (destructive/read-only/idempotent declarations, error legibility) and never fire real actions
retrieval-public3serves public factstruth-checkable against a public source — the V-ladder applies in full

Tools last seen observed

ask_customs check_restrictions classify_product get_origin_rule get_procedure get_tariff list_catalog

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 & specific7/7✓
has a description7/7✓
description is substantive7/7✓
parameters are typed7/7✓
parameters are described7/7✓

7 of 7 tools graded · 7 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 — 4 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
tariff-duty0901.21.00unverifiableus-hts
tariff-duty6109.10.00unverifiableus-hts

Protocol conformance observed

2025-06-18
protocol version
—
session model
0.1.0
server version CustomsWise

Capabilities: 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-10T05:10:48Zok_tools2001502025-06-18
2026-09-09T05:10:48Zok_tools2001292025-06-18
2026-09-08T05:10:36Zok_tools2001262025-06-18
2026-09-07T05:10:46Zok_tools2003042025-06-18
2026-09-06T06:16:02Zok_tools2001252025-06-18
2026-09-06T05:10:09Zok_tools2001462025-06-18
2026-09-05T05:10:48Zok_tools2001312025-06-18
2026-09-04T05:10:02Zok_tools2001472025-06-18
2026-09-03T05:10:09Zok_tools2001482025-06-18
2026-09-02T05:10:04Zok_tools2001862025-06-18
2026-09-01T05:10:09Zok_tools2001572025-06-18
2026-08-31T05:10:09Zhttp_error503158
2026-08-30T06:15:37Zhttp_error503115
2026-08-30T05:10:09Zhttp_error503135
2026-08-29T05:10:02Zhttp_error503131
2026-08-28T05:10:09Zhttp_error503304
2026-08-27T05:10:09Zhttp_error503140
2026-08-26T05:10:07Zhttp_error503304
2026-08-25T05:10:09Zhttp_error503137
2026-08-24T05:10:09Zhttp_error503123
2026-08-23T06:13:21Zhttp_error503180
2026-08-23T05:10:09Zhttp_error503130
2026-08-22T05:10:08Zhttp_error503166
2026-08-21T05:10:09Zhttp_error503305
2026-08-20T05:10:08Zhttp_error503136
2026-08-19T05:10:09Zhttp_error503132
2026-08-18T05:10:09Zhttp_error503137
2026-08-17T05:10:09Zhttp_error503135
2026-08-16T06:13:07Zhttp_error503134
2026-08-16T05:10:09Zhttp_error503132

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

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 →