Robin Saige we check the tools AI agents call

Bitview

io.github.bitcoinresearchkit/bitview

Read-only Bitcoin blockchain, mempool, mining, market, and on-chain analytics; no API key.

— the operator's own registry description reported

Publisher io.github.bitcoinresearchkit · first seen 2026-08-31 · endpoint https://mcp.bitview.space/

warn
verdict
alive-toolless
cluster
ok
answers
tools served

Dependency rating derived

warn
warn — alive, no tools · retrieval-public ○ · V n/a
warn — because answers ●, no confirmed drift in 1 probes ●; not yet checked: harness, truth (0 runs)

Cluster alive-toolless · distinctiveness 0.253 (typical). Every figure is a percentile or class within the 15,472-server censussee the whole spectrum.

Does it answer? Q1 · observed
answersalive_no_tools
latency290 ms
vs populationtypical
protocolleading
authopen
Can it be used? Q4 · observed
capabilities1
Did it hold when checked? Q3–Q4 · derived
identitysolo
servers on its host1
verifiabilityunassessed
duplicate inventoryno
drift events0
answers trueno primary

🔏 Signed receipt rr_52a6ae1e6e152b1545e1b3dd · 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, no tools — 1 probes ●evidence ↓
Q2What is it?retrieval-public ○ evidence ↓
Q3Can it be checked?V n/a for this kind ◐evidence ↓
Q4Did it hold?truth not yet run · no drift ●evidence ↓
Q5What company does it keep?alive-toolless · 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 (1 shown, 2026-09-06 → 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-09-06outcomefirst probe: ok

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 the operator's own registry description — REPORTED, not observed (tools were not visible to the probe). What checking applies to each kind (the full methodology →):

naturetoolsmeaning what checking applies
retrieval-public1serves public factstruth-checkable against a public source — the V-ladder applies in full

Tools last seen observed

no tool inventory served

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

2026-07-28
protocol version
session model
0.12.2
server version bitview_mcp

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-06T06:15:47Zok2002902026-07-28

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

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 →