Payperbyte

Name: Payperbyte
Author: 0rkz

@0rkz

About Payperbyte

MCP server for PayPerByte — a verify-before-act trust layer for AI agent data. 15 tools to discover, subscribe to, or pay-per-call for first-party feeds (markets, security/threat-intel, legal oracles). Every payload carries an on-chain EIP-712 PayloadAttestation the agent recompu

#finance #data #crypto

Basic information

Config

Add this server to your MCP-compatible client using the configuration below.

{
  "mcpServers": {
    "byte-library": {
      "command": "npx",
      "args": [
        "-y",
        "byte-mcp-server"
      ]
    }
  }
}

Tools

No tools detected

We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.

Overview

What is Payperbyte?

Payperbyte is an MCP (Model Context Protocol) server for a per-byte USDC data marketplace on Arbitrum. It enables AI agents to discover first-party publishers, subscribe to live feeds or pay-per-call via x402, and verify-before-act by recomputing keccak256 of received data and checking it against the publisher's on-chain EIP-712 PayloadAttestation before trusting it.

How to use Payperbyte?

Install with npx -y byte-mcp-server. The server is also available on the Official MCP Registry as io.github.0rkz/byte-protocol. It exposes 15 tools: 10 are read‑only (e.g., discover publishers & feeds, network stats, subscription health, token balances, byte_query_fact, and the verify gate byte_verify_payload) and 5 require a PRIVATE_KEY (byte_subscribe, byte_unsubscribe, byte_register_publisher, byte_publish_data, byte_buy_data).

Key features of Payperbyte

Per‑byte USDC settlement on Arbitrum Sepolia testnet
Verify‑before‑act: cryptographic data integrity check before trust
15 tools; 10 read‑only, 5 require a private key
No API keys or tokens needed
Every settlement emits an EIP‑712 PayloadAttestation as a cryptographic receipt

Use cases of Payperbyte

AI agents subscribing to live data feeds from verifiable publishers
Pay‑per‑call data acquisition via x402 with on‑chain attestation
Discovering first‑party data feeds and publishers on Arbitrum
Verifying received data integrity before acting on it (verify‑before‑act)

FAQ from Payperbyte

What runtime or dependencies does Payperbyte require?

The server is distributed as an npm package and can be run via npx. A PRIVATE_KEY is required for write operations (subscribe, publish, buy data). No API keys or tokens are needed.

On which network does Payperbyte operate?

It runs on Arbitrum Sepolia testnet. Settlement is done in USDC.

How does the verify‑before‑act mechanism work?

The server recomputes keccak256 of received data and checks it against the publisher’s on‑chain EIP‑712 PayloadAttestation. Payment can clear even if the data is garbage; the verify gate catches mismatches.

What tools are available without a private key?

Ten read‑only tools: discover publishers & feeds, network stats, subscription health, token balances, fact‑oracle queries (byte_query_fact), and the verify‑before‑act gate (byte_verify_payload).

Are there any known limitations?

The server currently targets Arbitrum Sepolia (testnet). All write tools require a private key environment variable. No production mainnet support is mentioned.