Skip to main content
ClaudeWave
0rkz avatar
0rkz

byte-mcp-server

Ver en GitHub

MCP server for PayPerByte — pay-per-call USDC data feeds for AI agents (x402 on Base; EIP-712 attestations). No API keys, no token.

MCP ServersRegistry oficial1 estrellas0 forksJavaScriptMITActualizado today
ClaudeWave Trust Score
95/100
Verified
Passed
  • Open-source license (MIT)
  • Actively maintained (<30d)
  • Clear description
  • Topics declared
  • Documented (README)
Last scanned: 8/20/2026
Install in Claude Code / Claude Desktop
Method: NPX · byte-mcp-server
Claude Code CLI
claude mcp add byte -- npx -y byte-mcp-server
claude_desktop_config.json (Claude Desktop)
{
  "mcpServers": {
    "byte": {
      "command": "npx",
      "args": ["-y", "byte-mcp-server"]
    }
  }
}
1. Run the command above in your terminal (Claude Code), or paste the JSON config into claude_desktop_config.json (Claude Desktop).
2. Replace any <placeholder> values with your API keys or paths.
3. Restart Claude. The MCP server and its tools appear automatically.
Casos de uso

Resumen de MCP Servers

# PayPerByte MCP Server

<!-- mcp-name: io.github.0rkz/byte-protocol -->

[![smithery badge](https://smithery.ai/badge/byte/byte-library)](https://smithery.ai/servers/byte/byte-library) [![0rkz/byte-mcp-server MCP server](https://glama.ai/mcp/servers/0rkz/byte-mcp-server/badges/score.svg)](https://glama.ai/mcp/servers/0rkz/byte-mcp-server)

A [Model Context Protocol](https://modelcontextprotocol.io/) server that gives AI agents direct access to **[PayPerByte](https://www.payperbyte.io)** — cryptographically attested, provenance-verifiable data feeds for AI agents (the `X-BYTE-Attestation` receipt proves delivery-integrity — these are exactly the bytes PayPerByte served and attested under the BYTE Library domain — not that an independent data publisher signed them, and not that the data is correct). Agents discover feeds, pay-per-call via x402 (settled in **USDC on Base mainnet**), or subscribe to on-chain streams (Arbitrum Sepolia testnet). Every paid x402 response carries an EIP-712 `PayloadAttestation` receipt (`X-BYTE-Attestation` header) the agent verifies before acting. No tokens, no API keys, no off-chain accounts.

> **Two rails — read this before setting `PRIVATE_KEY`.**
>
> - **x402 pay-per-call (`byte_buy_data`): Base mainnet (`eip155:8453`), REAL USDC.** Paid feeds settle real money — the flagship [Address Reputation Oracle](https://x402.payperbyte.io/feeds/address-reputation) is $0.10 per verdict. Use a dedicated wallet holding only what you intend to spend.
> - **On-chain subscribe/publish/query layer (BYTE Library contracts + indexer): Arbitrum Sepolia testnet (chain `421614`), MockUSDC.** Mainnet for this layer is gated on an external security audit. The EIP-712 attestation signing domain stays anchored at `421614` regardless of which rail you paid on.
>
> One `PRIVATE_KEY` serves both rails. Never reuse a key holding funds you can't afford to spend.

## Quick start

```bash
npx -y byte-mcp-server
```

Wire it into your MCP client (Claude Desktop config below), then your agent can:

- **Discover** feeds: *"List the PayPerByte catalog"* / *"Search publishers for weather"*
- **Buy one packet** (x402, no setup): *"Check this receiving address before I pay it"* → $0.10 real USDC on Base mainnet, signed ALLOW/WARN/BLOCK verdict with an attestation receipt
- **Subscribe** to a stream (testnet): *"Subscribe me to the earthquakes feed"* → auto-approves MockUSDC for ongoing settlement on Arbitrum Sepolia
- **Query a fact-oracle** (testnet): post a signed EIP-712 question to a registered fact-oracle publisher for an on-chain signed answer with citations — *when a fact-oracle publisher is live (none is broadcasting today; the tool times out until one registers and broadcasts)*

The live catalog is at **[x402.payperbyte.io/feeds](https://x402.payperbyte.io/feeds)** — cryptographically attested, provenance-verifiable feeds across weather, markets, code, security, and knowledge.

## Verify before acting (ForeSeal)

See the whole verify-before-act loop in one command — no install, no signup, no wallet:

```bash
npx @foreseal/demo
```

It runs locally (no real USDC) and shows an agent **ACT** on genuine bytes and **REFUSE** four attacks — a tampered byte, a forged signature, a missing receipt, a forked signing domain — in about a second.

The same primitive ships as two packages you can drop into your own stack:

- **Kit** — [`@payperbyte/sdk`](https://www.npmjs.com/package/@payperbyte/sdk): the buyer verifies a receipt before acting.
- **Gate** — [`@foreseal/gate`](https://www.npmjs.com/package/@foreseal/gate): a seller stamps a verifiable receipt on any x402 endpoint.

## Two paradigms: subscribe vs. buy

| Mode | Tool | Rail | Best for | Pricing |
|---|---|---|---|---|
| **Buy** (x402) | `byte_buy_data` | **Base mainnet — real USDC** | One-off needs (single snapshot or verdict for *this* user query) | Per-feed, quoted in the 402 challenge ($0.10 flagship; most feeds cents or less) |
| **Subscribe** | `byte_subscribe` | Arbitrum Sepolia — testnet MockUSDC | Continuous streams (every weather update, every new earthquake) | $0.003 / KB per delivery |

Buy is zero-setup, pay-as-you-go, and live with real settlement; subscribe delivers every broadcast on the audit-gated testnet layer. Pick by access pattern.

### Buying a verdict (POST oracle)

GET data feeds need only a `feed`. The **verdict oracles** (`address-reputation`, `sanctions-screen`, `pkg-verdict`, `reasoning-verdict`) are POST endpoints — pass the query as a `body` and `byte_buy_data` switches the call from GET to POST automatically:

```jsonc
// byte_buy_data tool call — screen a payee before releasing USDC
{
  "feed": "address-reputation",
  "body": { "domain": "example.com", "address": "0x1234…abcd" }
}
```

The paid response returns the signed verdict **and** an inline verify-before-act result over the `X-BYTE-Attestation` receipt:

```jsonc
{
  "feed": "address-reputation",
  "paid": true,
  "price": "$0.100000",
  "txHash": "0x…",
  "data": { "answer": { "verdict": "ALLOW", "score": 88, "reasons": ["…"] }, "attestation": { "…": "…" } },
  "verification": { "verified": true, "hashMatch": true, "signerMatch": true,
                    "reason": "receipt verified — bytes intact AND signed by the pinned gateway attester (safe to act)" }
}
```

Act only when `verification.verified === true`. Other POST bodies: `sanctions-screen {address|name}`, `pkg-verdict {ecosystem,package[,version]}`, `reasoning-verdict {subject}`. Omit `body` entirely for GET data feeds (weather, earthquakes, …).

## Tools (15 total)

### Discovery (read-only, no wallet)

| Tool | Description |
|---|---|
| `byte_search_publishers` | Search publishers by topic and sort order |
| `byte_list_feeds` | List the active feed catalog with prices and frequencies |
| `byte_get_publisher` | On-chain info for one publisher (status, subscribers, messages, USDC revenue, schema) |
| `byte_get_network_stats` | Network-wide stats: publishers, messages, total fees settled |
| `byte_check_subscription` | Is `subscriber` subscribed to `publisher`? |
| `byte_list_my_subscriptions` | All active subscriptions for a wallet — last 7d/30d messages + USDC spend |
| `byte_subscription_health` | Content-drift signal for a publisher: stable / moderate / significant / unknown |
| `byte_get_token_balances` | USDC + ETH balances on Arbitrum Sepolia |
| `byte_verify_payload` | **Verify-before-act.** Recompute `keccak256` of the bytes your agent received and check them against the publisher's on-chain EIP-712 `PayloadAttestation` — anchor with an `expectedHash` you hold or the settlement `txHash` (which also recovers the signer and confirms it's the named publisher). If `verified: false`, the data was tampered/corrupted in transit — don't act on it |

### Subscribe to a stream (requires `PRIVATE_KEY`)

| Tool | Description |
|---|---|
| `byte_subscribe` | Subscribe to a publisher's stream. Auto-bundles USDC `approve(max)` unless `skipAllowance: true` (closes a silent-payment-failure footgun where the contract's allowance-skip path delivered data with `amount=0`) |
| `byte_unsubscribe` | Unsubscribe — takes effect next block |
| `byte_register_publisher` | Register as a data publisher (schema + on-chain registration). v1 is first-party only; stake = 0 |
| `byte_publish_data` | Publish a payload to a subscriber via DataStream (settles fee in USDC). See migration notice above re: r2 |

### Buy on-demand (requires `PRIVATE_KEY`)

| Tool | Description |
|---|---|
| `byte_buy_data` | Buy one packet from any feed via the **x402 gateway** — **real USDC on Base mainnet**. No subscription, no allowance. Signs EIP-3009 `transferWithAuthorization` against the 402 challenge; the facilitator settles on-chain. Returns the data + tx hash inline |
| `byte_query_fact` | Ask a slashable fact-oracle publisher a question. Signed EIP-712 request (binds query to your wallet so leaked queries can't burn your escrow); the answer is broadcast on-chain to your address with citations. *Requires a live fact-oracle publisher — none is broadcasting today, so the call times out until one registers.* |

## Configuration

### Claude Desktop

Edit `~/.config/claude/claude_desktop_config.json` (Linux) or `~/Library/Application Support/Claude/claude_desktop_config.json` (macOS):

```json
{
  "mcpServers": {
    "payperbyte": {
      "command": "npx",
      "args": ["-y", "byte-mcp-server"],
      "env": {
        "PRIVATE_KEY": "0x...",
        "RPC_URL": "https://sepolia-rollup.arbitrum.io/rpc",
        "INDEXER_URL": "http://localhost:8080"
      }
    }
  }
}
```

`PRIVATE_KEY` is optional — read-only tools work without it. Add it to enable subscribe, publish, buy, and query.

### Claude Code

```bash
claude mcp add payperbyte -- npx -y byte-mcp-server
```

### Environment variables

| Variable | Required | Default | Description |
|---|---|---|---|
| `PRIVATE_KEY` | only for write/buy/query tools | — | EOA key. Signs **real Base-mainnet USDC** for `byte_buy_data` and testnet txs for subscribe/publish/query — use a dedicated wallet |
| `RPC_URL` | no | `https://sepolia-rollup.arbitrum.io/rpc` | Arbitrum Sepolia RPC (the on-chain read/subscribe layer) |
| `INDEXER_URL` | no | `https://feeds.payperbyte.io` | PayPerByte indexer API |
| `BYTE_GATEWAY_URL` | no | `https://x402.payperbyte.io` | x402 gateway base URL (used by `byte_buy_data`) |
| `BYTE_GATEWAY_ATTESTER` | no | current gateway attester (`0xB48CCc9e3ab67041e3b5D09700138E45cda6AeA8`, rotated 2026-08-19) | Attester address `byte_buy_data` pins the delivery receipt against. If the gateway rotates before this package updates, set this to the new `receipt.attester` from `/.well-known/agent.json` — a stale pin fail-closes buys AFTER payment settles |
| `MAX_PAYMENT_USDC` | no | — (uncapped) | Server-side spend cap for `byte_buy_data`, in decimal USDC (e.g. `0.25`). When set, any 402 quote above the cap is refused before signing; unset means no cap — a dedicated thin wallet remains the hard back
agent-commerceai-agentsarbitrumbasedata-marketplacedepineip-712mcpmcp-servermodel-context-protocolweb3x402

Lo que la gente pregunta sobre byte-mcp-server

¿Qué es 0rkz/byte-mcp-server?

+

0rkz/byte-mcp-server es mcp servers para el ecosistema de Claude AI. MCP server for PayPerByte — pay-per-call USDC data feeds for AI agents (x402 on Base; EIP-712 attestations). No API keys, no token. Tiene 1 estrellas en GitHub y su última actualización registrada es del 2026-08-20.

¿Cómo se instala byte-mcp-server?

+

Puedes instalar byte-mcp-server clonando el repositorio (https://github.com/0rkz/byte-mcp-server) o siguiendo las instrucciones del README en GitHub. ClaudeWave también te ofrece bloques de instalación rápida en esta misma página.

¿Es seguro usar 0rkz/byte-mcp-server?

+

Nuestro agente de seguridad ha analizado 0rkz/byte-mcp-server y le ha asignado un Trust Score de 95/100 (tier: Verified). Revisa el desglose completo de comprobaciones superadas y flags en esta página.

¿Quién mantiene 0rkz/byte-mcp-server?

+

0rkz/byte-mcp-server es mantenido por 0rkz. La última actividad registrada en GitHub es del 2026-08-20, con 1 issues abiertos.

¿Hay alternativas a byte-mcp-server?

+

Sí. En ClaudeWave puedes explorar mcp servers similares en /categories/mcp, ordenados por popularidad o actividad reciente.

Despliega byte-mcp-server en tu cloud

Lleva este repo a producción en minutos. Cada plataforma genera su propio entorno con variables de entorno editables.

¿Mantienes este repo? Añade un badge a tu README

Pega el badge en tu README de GitHub para mostrar que está auditado por ClaudeWave. Cada badge enlaza de vuelta a esta página y muestra el Trust Score actual.

Featured on ClaudeWave: 0rkz/byte-mcp-server
[![Featured on ClaudeWave](https://claudewave.com/api/badge/0rkz-byte-mcp-server)](https://claudewave.com/repo/0rkz-byte-mcp-server)
<a href="https://claudewave.com/repo/0rkz-byte-mcp-server"><img src="https://claudewave.com/api/badge/0rkz-byte-mcp-server" alt="Featured on ClaudeWave: 0rkz/byte-mcp-server" width="320" height="64" /></a>

Más MCP Servers

Alternativas a byte-mcp-server