Robin Saige we check the tools AI agents call

cryptotaxedge

io.github.sturs49/cryptotaxedge

US tax classification for on-chain transactions: category, treatment, confidence, review flags.

— the operator's own registry description reported

Publisher io.github.sturs49 · first seen 2026-08-12 · endpoint https://mcp.cryptotaxedge.com/

allow
verdict
thin-fast-solo
cluster
ok_tools
answers
4
tools served

Dependency rating derived

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

Cluster thin-fast-solo · distinctiveness 0.639 (unusual). Every figure is a percentile or class within the 15,472-server censussee the whole spectrum.

Does it answer? Q1 · observed
answersalive_tools
latency44 ms
vs populationfast
protocolcurrent
authopen
Can it be used? Q4 · observed
tools4
vs populationmid
capabilities3
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_b565817b91ae3b74448a37b5 · 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 — 6 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?thin-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 (6 shown, 2026-08-12 → 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-09-06outcomeok_tools (was auth_required)
2026-08-12outcomefirst probe: auth_required

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-public2serves public factstruth-checkable against a public source — the V-ladder applies in full
computational1deterministic transformsself-checkable by re-computation and known-answer tests
retrieval-private1serves the caller's own dataoutside truth-checking is impossible BY NATURE, not by failure — the operator-invited pathway applies

Tools last seen observed

classify_batch classify_transaction lookup_contract map_to_chart_of_accounts

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 & specific4/4
has a description4/4
description is substantive4/4
parameters are typed4/4
parameters are described4/4

4 of 4 tools graded · 4 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
0.2.2
server version cte-mcp-server

Capabilities: prompts 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:17:10Zok_tools200442025-06-18
2026-08-30T06:16:58Zauth_required40167
2026-08-23T06:14:19Zauth_required401115
2026-08-16T06:13:48Zauth_required40171
2026-08-14T20:00:14Zauth_required40184
2026-08-12T05:35:26Zauth_required40151

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

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 →