# io.github.0rkz/byte-protocol (io.github.0rkz/byte-protocol@0.12.3)

> Source: <https://mcpindex.ai/server/io-github-0rkz-byte-protocol>
> Published: 2026-09-03 00:04:38+00:00

[← Index](/leaderboard)

# io.github.0rkz/byte-protocol

PayPerByte — per-byte data for AI agents: x402 USDC on Base, EIP-712-attested. No token.

The current version, v0.12.3, was published to the official MCP registry on 2026-09-03. It is distributed as byte-mcp-server on npm and as a hosted remote over streamable-http, filed under Other by this index, and declares 3 environment variables. Removals and unreachable sources are measured across every server this index tracks, contract drift across the servers that answer in consecutive snapshots; [the index's current counts](/stats) put this record in context.

## Using io.github.0rkz/byte-protocol in Claude, Cursor, Gemini CLI, Cline, or Zed?

MCP tool contracts can change remotely with no version bump. The mcpindex gate pins each contract and **HOLDs the call** when it drifts-before your agent acts. Zero credentials. This is not the package install for this server itself (use **Install this server** for that).

Rewrites your MCP host config so each server launches behind the gate. Inspect first: curl -fsSL https://mcpindex.ai/install.sh | less

```
uv tool install mcpindex-gate && mcpindex-config-wire
```

[method](/methodology)

Semantic screen found no manipulation pattern in the description. Conformance probe not yet run.

`mcpindex.integrity.description`

passINFOevidence“No hidden instructions”via static_description

- - Semantic screen only - the deterministic conformance probe has not run on this server
- - Confidence is reported but not yet calibrated (v1)
- - Screen reads the tool description, not the live behavior
- - advisory
- - registry description only no input schema
- - Still current: the description we screened is unchanged, re-checked against the registry
- - The registry listing (version, packages, links) changed after this screen ran - the description we assessed did not

Semantic screen: an LLM judge reads the tool description for hidden instructions (status PARTIAL). A pass means the description is not lying, not that the tool is safe: a high-capability tool with an honest description still warrants caution. The deterministic conformance probe has not been run on this server yet, so the screen here is semantic-only. Posture: advisory. Confidences are reported but not yet calibrated (calibrated=false at v1). Full verdict history is not shown on this page.

Own this server? [Screen its description →](/screen)

## That verdict was true at screening time (snapshot 2026-09-03).

Contracts can change after screening, with no version bump. The gate pins io.github.0rkz/byte-protocol’s tool contracts on first sight and holds any silent change before your agent acts - the check that keeps being true on Tuesday.

[See your first HOLD in 2 minutes →](/guides/install-the-gate-first-hold)

Related: [how to trust an MCP server](/guides/how-to-trust-an-mcp-server) · [screen before install](/guides/screen-mcp-server-before-install) · [silent contract drift](/guides/mcp-silent-contract-drift)

People vet a server before wiring it in. One line on your project site or docs answers that with an independent record: screening verdict, registry provenance, contract drift history. It stays current as new screens and drift events land.

```
[Independent trust record for io.github.0rkz/byte-protocol](https://mcpindex.ai/server/io-github-0rkz-byte-protocol) - screening verdict, registry provenance, and contract drift monitoring.
<a href="https://mcpindex.ai/server/io-github-0rkz-byte-protocol">Independent trust record for io.github.0rkz/byte-protocol</a> - screening verdict, registry provenance, and contract drift monitoring.
```

A live verdict badge for your README or listing. It reflects the current screen, links back here, and updates when the verdict does.

```
[![mcpindex](https://mcpindex.ai/api/v1/badge/io-github-0rkz-byte-protocol)](https://mcpindex.ai/server/io-github-0rkz-byte-protocol)
<a href="https://mcpindex.ai/server/io-github-0rkz-byte-protocol"><img src="https://mcpindex.ai/api/v1/badge/io-github-0rkz-byte-protocol" alt="mcpindex verdict" height="20" /></a>
```

`PRIVATE_KEY`

Ethereum private key for write/buy tools (subscribe, unsubscribe, publish, buy_data). buy_data spends real Base-mainnet USDC — use a dedicated wallet. Not required for read-only tools.

`RPC_URL`

RPC for the on-chain library + EIP-712 attestation layer (Arbitrum Sepolia, eip155:421614). The x402 buy rail settles USDC on Base mainnet and needs no RPC here. Defaults to Arbitrum Sepolia public RPC.

`BYTE_GATEWAY_ATTESTER`

Gateway attester address byte_buy_data pins receipts against. Defaults to the current PayPerByte gateway attester (rotated 2026-08-19; previous default 0x77c86a...C472 is retired). Override only if the gateway discloses a rotation you need ahead of a package update - see /.well-known/agent.json receipt.attester and receipt.retiredAttesters.

[methodology](/methodology)

[AgentRoamai.agentroam/agentroam](/server/ai-agentroam-agentroam)

Buy travel eSIMs, gift cards and mobile top-ups with crypto — user confirms before any order.

[Authoryzeai.authoryze/authoryze](/server/ai-authoryze-authoryze)

Give your AI agent a spending limit: approval controls and single-use virtual cards.

[io.github.0x-devc/novai-mcp-serverio.github.0x-devc/novai-mcp-server](/server/io-github-0x-devc-novai-mcp-server)

Read-only MCP server for querying the live NOVAI blockchain over its public JSON-RPC endpoint.
