byte protocol
io.github.0rkz/byte-protocol
PayPerByte — per-byte data for AI agents: x402 USDC on Base, EIP-712-attested. No token.
— the operator's own registry description reported
Publisher io.github.0rkz · first seen 2026-08-12 · endpoint https://mcp.payperbyte.io/mcp
Dependency rating derived
allow — alive & usable · retrieval-public ● · V3 has answer key ◐
Cluster mid-solo · distinctiveness 0.101 (typical). Every figure is a percentile or class within the 11,363-server census — see the whole spectrum.
🔏 Signed receipt rr_d5eaf9443c5b499fb42d7dcc · 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 (3 shown, 2026-08-12 → 2026-08-16). 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)
| date | type | what changed |
|---|---|---|
| 2026-08-12 | outcome | first 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 →):
| nature | tools | meaning | what checking applies |
|---|---|---|---|
| retrieval-public | 9 | serves public facts | truth-checkable against a public source — the V-ladder applies in full |
| action | 4 | changes the world | no true answer exists; we check the CONTRACT (destructive/read-only/idempotent declarations, error legibility) and never fire real actions |
| computational | 1 | deterministic transforms | self-checkable by re-computation and known-answer tests |
| unclassified | 1 | not classifiable from its text | Tier-1 only until its tools describe themselves |
Tools last seen observed
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 check | tools passing | ok |
|---|---|---|
| name is clear & specific | 15/15 | ✓ |
| has a description | 15/15 | ✓ |
| description is substantive | 15/15 | ✓ |
| parameters are typed | 15/15 | ✓ |
| parameters are described | 15/15 | ✓ |
15 of 15 tools graded · 15 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 — 1 attempt(s) currently unverifiable (rate limits, walls, or unmappable schemas — never counted against the server) · 0 disagreements.
| claim class | key | verdict | primary source |
|---|---|---|---|
| OFAC SDN screening (vs the official list) | unmapped | unverifiable | ofac-sdn |
Protocol conformance observed
Capabilities: tools
Drift observed
No confirmed drift on record. Baseline set 2026-08-16; changes appear here after human review.
raw probe records
| probed (UTC) | outcome | http | ms | protocol |
|---|---|---|---|---|
| 2026-08-16T06:12:25Z | ok_tools | 200 | 178 | 2025-06-18 |
| 2026-08-14T19:58:52Z | ok_tools | 200 | 240 | 2025-06-18 |
| 2026-08-12T05:34:06Z | ok_tools | 200 | 164 | 2025-06-18 |
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.0rkz/byte-protocol)
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 →