Base Transaction Decoder
io.github.0200project/base-transaction-decoder
Decode any Base tx: plain English, strict JSON, risk flags, no LLM. 50 free/day per IP, then $0.02.
— the operator's own registry description reported
Publisher io.github.0200project · first seen 2026-08-27 · endpoint https://api.0200project.com/mcp?ref=mcp-registry
Dependency rating derived
warn — alive, no tools · computational ○ · V n/a
Cluster alive-toolless · distinctiveness 0.529 (moderate). Every figure is a percentile or class within the 15,472-server census — see the whole spectrum.
🔏 Signed receipt rr_0e837b931e7c6901977521c0 · 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.
● 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 (2 events)
| date | type | what changed |
|---|---|---|
| 2026-09-06 | outcome | ok (was not_mcp) |
| 2026-08-30 | outcome | first probe: not_mcp |
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 →):
| nature | tools | meaning | what checking applies |
|---|---|---|---|
| computational | 1 | deterministic transforms | self-checkable by re-computation and known-answer tests |
Tools last seen observed
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
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) | outcome | http | ms | protocol |
|---|---|---|---|---|
| 2026-09-06T06:13:37Z | ok | 200 | 1088 | 2025-06-18 |
| 2026-08-30T06:13:14Z | not_mcp | 200 | 12043 |
Watch or embed this verdict
Operators: put the live verdict in your README — it updates with every census, links back here, and is a dated observation, never a warranty:
[](https://robinsaige.com/s/io.github.0200project/base-transaction-decoder)
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.
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 →