# io.github.0rkz/byte-protocol (remote · mcp.payperbyte.io)

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

- Trust score: 59/100 (low)
- Change this week: +1
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

> **Recent critical change**: Authorization (2026-08-02). See the changelog below before you install this server.

## Components

- remote · `mcp.payperbyte.io`: 59/100 (this document), [markdown](https://verifymcp.io/servers/0rkz-byte-protocol/mcp.md), [page](https://verifymcp.io/servers/0rkz-byte-protocol/mcp)
- npm · `byte-mcp-server`: 35/100, [markdown](https://verifymcp.io/servers/0rkz-byte-protocol/byte-mcp-server.md), [page](https://verifymcp.io/servers/0rkz-byte-protocol/byte-mcp-server)

## Channel facts

- Endpoint: `https://mcp.payperbyte.io/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.11.10`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (byte_register_publisher).
  - HTTPS not yet verified: we couldn't determine whether a plaintext access path exists.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 60/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 2370 tokens (~158/item across 15 items; 15 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http 0rkz-byte-protocol https://mcp.payperbyte.io/mcp
```

### Codex

```toml
[mcp_servers.0rkz-byte-protocol]
url = "https://mcp.payperbyte.io/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "0rkz-byte-protocol": {
      "type": "remote",
      "url": "https://mcp.payperbyte.io/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add 0rkz-byte-protocol --url https://mcp.payperbyte.io/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  0rkz-byte-protocol:
    url: "https://mcp.payperbyte.io/mcp"
```

### Other

```json
{
  "mcpServers": {
    "0rkz-byte-protocol": {
      "type": "http",
      "url": "https://mcp.payperbyte.io/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-03 (score 59, 0)

- [functional] Server version: 0.11.11 → 0.12.0

### 2026-08-02 (score 59, +41)

- [critical regression] Authorization: unverified → fail
- [security improvement] Transport: fail → pass
- [functional improvement] Endpoint reachability: not serving MCP → reachable
- [functional improvement] Stability: unverified → 0.23
- [functional improvement] Tool coverage: unverified → 100
- [functional improvement] MCP protocol: unverified → pass

### 2026-08-01 (score 18, −40)

- [security regression] Endpoint reachability: reachable → not serving MCP
- [security regression] Stability: 0.17 → unverified
- [security regression] Authorization: fail → unverified
- [security regression] Transport: pass → fail
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional] First check of Schema quality: unverified

### 2026-07-31 (score 58, −1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-29 (score 59, +1)

- [cosmetic] “byte_buy_data” reworded the description of “feed”

### 2026-07-27 (score 58, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 57)

First indexed and scored.

## MCP tools (15)

### `byte_search_publishers` (~99 tokens)

Search PayPerByte publishers by topic and sort order. Returns publisher addresses, topics, subscriber counts, message counts, and price-per-KB.

Input parameters:

- `limit` (number): Max results to return (default 20)
- `query` (string): Topic keyword to search (e.g. 'weather', 'crypto', 'cve')
- `sortBy` (string): Sort field: 'subscribers', 'revenue', 'messages'

Output parameters:

- `publishers` (array): Matching publishers, sorted by the requested field

### `byte_get_publisher` (~61 tokens)

Get on-chain info for a specific PayPerByte publisher: status, subscriber and message counts, USDC revenue, and the registered schema (size bounds, cadence, price-per-KB).

Input parameters:

- `address` (string, required): Publisher Ethereum address (0x...)

Output parameters:

- `address` (string): Publisher Ethereum address
- `lastActive` (number): Unix timestamp of last on-chain activity
- `messages` (number): Total messages published
- `registeredAt` (number): Unix timestamp of publisher registration
- `revenueUsdc` (string): Total USDC revenue (decimal string)
- `schema`: Registered schema (topic, sizes, cadence, price)
- `status` (string): On-chain publisher status
- `subscribers` (number): Active subscriber count

### `byte_get_network_stats` (~33 tokens)

Get PayPerByte network-wide statistics: total publishers, messages streamed, and total subscriber fees settled in USDC.

Output parameters:

- `messages` (number): Total messages streamed all-time
- `publishers` (number): Active publisher count network-wide
- `totalSubscriberFeesUsdc` (string): Total subscriber fees settled (USDC, decimal string)

### `byte_check_subscription` (~50 tokens)

Check if an address is subscribed to a specific publisher on PayPerByte.

Input parameters:

- `publisher` (string, required): Publisher Ethereum address (0x...)
- `subscriber` (string, required): Subscriber Ethereum address (0x...)

Output parameters:

- `subscribed` (boolean): True if the subscriber has an active subscription to the publisher

### `byte_get_token_balances` (~74 tokens)

Get USDC and ETH balances for an address on Arbitrum Sepolia (the on-chain testnet layer — MockUSDC settles subscriptions and fact-oracle queries there). Does NOT show the Base-mainnet USDC balance that byte_buy_data spends.

Input parameters:

- `address` (string, required): Ethereum address (0x...)

Output parameters:

- `address` (string): Echoed address
- `eth` (string): ETH balance (wei)
- `usdc` (string): USDC balance (atomic, 6 decimals)

### `byte_list_feeds` (~32 tokens)

List all active data feeds in the PayPerByte catalog with topics, price-per-KB, and frequency.

Output parameters:

- `feeds` (array): Catalog of active feeds

### `byte_list_my_subscriptions` (~126 tokens)

List every active subscription for a given wallet address. Each entry has the publisher address, topic, status, when you subscribed, messages received in 7/30 days, USDC spent in 7/30 days, and the timestamp of the last message received. Use this to see what you're currently paying for and decide whether to unsubscribe.

Input parameters:

- `indexerUrl` (string): Optional indexer URL override (default: INDEXER_URL/BYTE_INDEXER_URL env or https://feeds.payperbyte.io)
- `subscriber` (string, required): Wallet address to list subscriptions for

Output parameters:

- `subscriptions` (array): Active subscriptions for the given wallet

### `byte_subscription_health` (~144 tokens)

Get the content-drift signal for a publisher. Compares their last 7 days of publishing activity (cadence, message count) against their 23-day baseline (days 8-30). Returns 'stable' (steady publishing), 'moderate' (20-50% cadence shift or 24-48h silence), 'significant' (>50% shift or >48h silence), or 'unknown' (new publisher, insufficient baseline). Use this to detect when a publisher you subscribe to has pivoted content or gone dormant.

Input parameters:

- `indexerUrl` (string): Optional indexer URL override
- `publisher` (string, required): Publisher address to check

Output parameters:

- `cadence_drift_bps`: Cadence drift vs 23-day baseline (bps)
- `messages30d`: Messages in the last 30 days
- `messages7d`: Messages in the last 7 days
- `messages_30d`: Messages in the last 30 days (indexer key)
- `messages_7d`: Messages in the last 7 days (indexer key)
- `publisher` (string): Publisher address checked
- `signal` (string): Content-drift bucket for the publisher
- `silence_hours`: Hours since the last message (null if never)
- `volume_ratio_bps`: 7d/baseline volume ratio (bps)

### `byte_unsubscribe` (~93 tokens)

Unsubscribe from a publisher's data feed. Takes effect next block: no more billing, no more data flow. Reversible — you can resubscribe later via byte_subscribe. Use this when a publisher has pivoted content (check with byte_subscription_health first) or when you simply don't want the feed anymore. Requires PRIVATE_KEY for the connected wallet.

Input parameters:

- `publisher` (string, required): Publisher address to unsubscribe from

Output parameters:

- `blockNumber` (string): Block number the tx landed in
- `publisher` (string): Publisher unsubscribed from
- `status` (string): Receipt status ('success' | 'reverted')
- `subscriber` (string): Subscriber address (the signer)
- `txHash` (string): Unsubscribe transaction hash

### `byte_subscribe` (~156 tokens)

Subscribe to a PayPerByte publisher's data feed. By default also sets USDC allowance to DataStreamLib to type(uint256).max so the subscription doesn't silently lose payments when allowance depletes (the contract's allowance-skip path emits DataStreamed with amount=0 on transferFrom failure rather than reverting). Pass skipAllowance: true to opt out and set a finite cap manually. Requires PRIVATE_KEY.

Input parameters:

- `publisher` (string, required): Publisher Ethereum address (0x...) to subscribe to
- `skipAllowance` (boolean): If true, don't bundle the USDC approve(max) call. Default false. Auto-approve is also skipped when the wallet already has ≥ $1000 USDC of allowance to DataStreamLib.

Output parameters:

- `allowanceTxHash` (string): USDC approve(max) transaction hash, if bundled
- `publisher` (string): Publisher subscribed to
- `success` (boolean): True if subscribe landed on-chain
- `txHash` (string): Subscribe transaction hash

### `byte_register_publisher` (~199 tokens)

Register as a data publisher on PayPerByte. Registers a schema and the publisher on-chain. Requires PRIVATE_KEY. PayPerByte v1 publishers are first-party and unstaked — leave stake at '0'; a non-zero USDC stake is approved to DataRegistry first if you choose to post one.

Input parameters:

- `expectedSize` (number, required): Expected payload size in bytes per message
- `frequency` (number, required): Expected publishing frequency in seconds
- `maxSize` (number, required): Maximum payload size in bytes per message
- `pricePerKB` (number, required): Price per kilobyte in USDC (e.g. 0.003)
- `stake` (string, required): USDC reputation stake to post, as a decimal string. Default '0' — PayPerByte v1 publishers are unstaked.
- `topic` (string, required): Data feed topic (e.g. 'eth-price', 'weather-nyc', 'gas-tracker')

Output parameters:

- `approveTxHash` (string): USDC stake approval tx hash, if a non-zero stake was posted
- `publisher` (string): Registered publisher address (the signer)
- `schemaTxHash` (string): Schema-registration transaction hash
- `stakeUsdc` (string): USDC stake posted (decimal string; '0' for v1 first-party)
- `success` (boolean): True if registration landed on-chain
- `topic` (string): Registered feed topic
- `txHash` (string): Publisher-registration transaction hash

### `byte_publish_data` (~102 tokens)

Publish data to a subscriber via the PayPerByte DataStream contract. Hashes the payload, records size on-chain, and settles the fee in USDC. Requires PRIVATE_KEY.

Input parameters:

- `data` (string, required): Data payload to publish (will be hashed on-chain)
- `maxFee` (number, required): Maximum fee in USDC willing to pay for this publish (e.g. 0.05)
- `subscriber` (string, required): Subscriber Ethereum address (0x...)

Output parameters:

- `payloadHash` (string): keccak256 of the payload as recorded on-chain
- `payloadSize` (number): Payload size recorded on-chain (bytes)
- `success` (boolean): True if publish landed on-chain
- `txHash` (string): Publish transaction hash

### `byte_query_fact` (~385 tokens)

Query a PayPerByte fact-oracle publisher for a signed answer with citations. Posts the question to a registered fact-oracle publisher (topic='fact-oracle'), waits for the on-chain BroadcastStreamed response, and returns the answer plus structured citation URLs. The signed receipt proves which publisher produced the answer (provenance + tamper-evidence), NOT that the answer is correct — ground your output in the cited sources, not in a truth guarantee. Availability: this requires a registered fact-oracle publisher actively broadcasting; if none is live the call returns a timeout rather than an answer.

Input parameters:

- `max_byte_cost` (number): Max response payload bytes you're willing to pay for (defaults to 2000, ≈$1 at $0.0005/byte). Publisher refuses if can't fit answer.
- `max_response_latency_ms` (number): Max time to wait for the publisher's broadcast (default 30000 ms). Local-LLM publishers (Ollama + Searxng + 3-sample NLI gate) take ~30-60s; Anthropic + passthrough takes ~10-20s. Hard ceiling 180s.
- `min_publisher_pqs` (number): Minimum PQS to consider (BPS scale, 0-10000). 9000 = Elite-only, 7500 = Premium+.
- `question` (string, required): The factual question to ask (e.g. 'What was last night's Lakers vs Warriors score?'). Should be specific and verifiable.
- `subscriber_address` (string, required): Your wallet address. You MUST be subscribed to the chosen publisher (with sufficient USDC escrow) or the publisher's on-chain broadcast will be skipped.
- `topic_filter` (string): Optional topic filter (e.g. 'fact-oracle' default; future: 'sports', 'finance').

Output parameters:

- `answer` (string): Publisher's grounded answer to the question
- `citations` (array): URLs/sources cited by the publisher in support of the answer
- `confidence` (number): Publisher-reported confidence (0-1)
- `elapsed_ms` (number): End-to-end time to obtain the answer (ms)
- `error` (string): Error message if the query failed (no eligible publisher, broadcast timeout, etc.)
- `payload_hash` (string): keccak256 of the response payload
- `publisher_address` (string): Publisher address that fulfilled the query
- `publisher_pqs` (number): Publisher quality score (PQS) at fulfillment
- `publisher_tx_or_status` (string): Delivery status or settlement reference
- `request_id` (string): Request id binding the query to this answer
- `response_size_bytes` (number): Size of the response payload (bytes)

### `byte_buy_data` (~493 tokens)

Buy a single data packet from any PayPerByte feed via the x402 payment gateway. No subscription, no allowance, no prior on-chain setup — pay-per-call USDC settlement. The MCP server signs an EIP-3009 transferWithAuthorization on behalf of the wallet whose PRIVATE_KEY is configured, the x402 facilitator submits the tx, and the data comes back inline with the on-chain settlement tx hash. Use byte_subscribe instead if you want a continuous stream of broadcasts from a publisher. The catalog of available feed slugs lives at https://x402.payperbyte.io/feeds (free GET). GET data feeds (weather, earthquakes, …) need only `feed`; the 9 POST oracles — address-reputation, sanctions-screen, pkg-verdict, reasoning-verdict, evidence-pack, liquidation-stream, positioning-snapshot, runtime-eol, threat-intel — additionally require a JSON `body` (the query) — supplying `body` switches this call to POST. Requires PRIVATE_KEY env var on the MCP server and USDC on the configured wallet. NOTE: paid feeds settle REAL USDC on Base mainnet (eip155:8453) — the exact price is quoted in the 402 challenge (flagship address-reputation: $0.10/verdict). Use a dedicated wallet holding only what you intend to spend.

Input parameters:

- `body` (object): Optional JSON query body for POST oracles. Supplying it switches the call from GET to POST. Required by the verdict oracles, e.g. address-reputation {domain,address[,amount,chain]}, sanctions-screen…
- `feed` (string, required): Feed slug — one of: weather ($0.0050), earthquakes ($0.0030), runtime-eol ($0.020), threat-intel ($0.050), address-reputation ($0.100), pkg-verdict ($0.100), sanctions-screen ($0.100), reasoning-verd…

Output parameters:

- `data`: Decoded feed payload returned by the publisher
- `detail` (string): Additional error detail, if any
- `error` (string): Error message if the buy failed
- `feed` (string): Echoed feed slug
- `paid` (boolean): True if an x402 payment was made (false on free/cached feeds)
- `payer` (string): Wallet that signed the EIP-3009 authorization
- `price` (string): USDC paid for this packet (e.g. '$0.003000'); omitted on free feeds
- `status` (number): HTTP status of the (post-payment) gateway response
- `txHash` (string): x402 settlement transaction hash
- `verification` (object): Two-leg verify-before-act result: {gatewayVerified, hashMatch, signerMatch, recovered, attester, expired, deadline, checkedAt, embeddedAttestation, reason, note}. gatewayVerified=true means the GATEW…

### `byte_verify_payload` (~323 tokens)

Verify-before-act: confirm a data payload an agent is about to act on actually matches what the publisher cryptographically attested to on-chain. Recomputes keccak256 of the received bytes and compares it to the on-chain EIP-712 PayloadAttestation hash. ALWAYS call this on BYTE-sourced data before acting on it; if verified=false the bytes were tampered/corrupted in transit and MUST NOT be used. Anchor the check with EITHER expectedHash (an on-chain payloadHash you already hold, e.g. from byte_query_fact / byte_buy_data) OR txHash (the settlement tx — also recovers the attestation signer and confirms it is the named publisher). Read-only; no wallet or payment required.

Input parameters:

- `data` (string, required): The exact payload bytes the agent received and is about to act on — the raw delivered string, or a 0x-prefixed hex byte string.
- `expectedHash` (string): On-chain payloadHash to verify against (0x + 64 hex), e.g. the payloadHash returned by byte_query_fact or byte_buy_data.
- `hashMode` (string): How to hash structured payloads: 'raw' (keccak of the utf8 string, default — matches byte_publish_data) or 'canonical' (keccak of key-sorted, whitespace-free JSON).
- `txHash` (string): Settlement tx hash whose on-chain BroadcastStreamed attestation to verify against. When provided, also recovers the EIP-712 signer and confirms it is the attesting publisher.

Output parameters:

- `attestingPublisher` (string): Publisher named in the on-chain event (txHash mode)
- `blockNumber` (string): Block number of the settlement tx (txHash mode)
- `checkedAt` (string): Wall-clock time the expiry comparison was made, UNIX seconds (decimal string)
- `deadline` (string): Attestation deadline as UNIX seconds (decimal string) — txHash mode only
- `expired` (boolean): Whether the attestation's EIP-712 deadline has passed at check time — the same rule the contract enforces (block.timestamp > deadline). txHash mode only; absent in expectedHash mode, which carries no…
- `hashMatch` (boolean): Whether the recomputed hash equals the on-chain hash
- `onChainHash` (string): The on-chain attested payloadHash compared against
- `reason` (string): Human-readable verdict an agent can surface when it acts or refuses
- `recomputedHash` (string): keccak256 of the received bytes
- `signer` (string): Recovered EIP-712 attestation signer (txHash mode)
- `signerMatch` (boolean): Whether the recovered signer is the attesting publisher
- `source` (string): Which anchor was used: 'txHash' or 'expectedHash'
- `txHash` (string): Settlement tx hash verified against (txHash mode)
- `verified` (boolean): True only if the recomputed hash matches the on-chain attested hash AND (when a signer was recovered) the signer is the publisher. If false: do NOT act on the data.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/0rkz-byte-protocol/mcp#diagnostics

## Score history

- 2026-08-03: 59
- 2026-08-02: 59
- 2026-08-01: 18
- 2026-07-31: 58
- 2026-07-30: 59
- 2026-07-29: 59
- 2026-07-28: 58
- 2026-07-27: 58
- 2026-07-26: 57

## Links

- Remote endpoint: https://mcp.payperbyte.io/mcp
- Repository: https://github.com/0rkz/byte-mcp-server
- Changelog RSS feed: https://verifymcp.io/servers/0rkz-byte-protocol/mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/0rkz-byte-protocol/mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/0rkz-byte-protocol/mcp