# byte-protocol MCP server

PayPerByte — per-byte USDC data feeds for AI agents on Arbitrum. EIP-712-attested, no token.

## Links
- Registry page: https://www.getdrio.com/mcp/io-github-0rkz-byte-protocol
- Repository: https://github.com/0rkz/byte-mcp-server

## Install
- Command: `npx -y byte-mcp-server`
- Endpoint: https://mcp.payperbyte.io/mcp
- Auth: Not captured

## Setup notes
- Package: Npm byte-mcp-server v0.11.1
- Environment variable: PRIVATE_KEY (secret)
- Environment variable: RPC_URL
- Remote endpoint: https://mcp.payperbyte.io/mcp

## Tools
- byte_search_publishers - Search PayPerByte publishers by topic and sort order. Returns publisher addresses, topics, subscriber counts, message counts, and price-per-KB. Endpoint: https://mcp.payperbyte.io/mcp
- byte_get_publisher - 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). Endpoint: https://mcp.payperbyte.io/mcp
- byte_get_network_stats - Get PayPerByte network-wide statistics: total publishers, messages streamed, and total subscriber fees settled in USDC. Endpoint: https://mcp.payperbyte.io/mcp
- byte_check_subscription - Check if an address is subscribed to a specific publisher on PayPerByte. Endpoint: https://mcp.payperbyte.io/mcp
- byte_get_token_balances - 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. Endpoint: https://mcp.payperbyte.io/mcp
- byte_list_feeds - List all active data feeds in the PayPerByte catalog with topics, price-per-KB, and frequency. Endpoint: https://mcp.payperbyte.io/mcp
- byte_list_my_subscriptions - 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. Endpoint: https://mcp.payperbyte.io/mcp
- byte_subscription_health - 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. Endpoint: https://mcp.payperbyte.io/mcp
- byte_unsubscribe - 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. Endpoint: https://mcp.payperbyte.io/mcp
- byte_subscribe - 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. Endpoint: https://mcp.payperbyte.io/mcp
- byte_register_publisher - 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. Endpoint: https://mcp.payperbyte.io/mcp
- byte_publish_data - 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. Endpoint: https://mcp.payperbyte.io/mcp
- byte_query_fact - 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. Endpoint: https://mcp.payperbyte.io/mcp
- byte_buy_data - 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. Endpoint: https://mcp.payperbyte.io/mcp
- byte_verify_payload - 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. Endpoint: https://mcp.payperbyte.io/mcp

## Resources
Not captured

## Prompts
Not captured

## Metadata
- Owner: io.github.0rkz
- Version: 0.11.1
- Runtime: Npm
- Transports: STDIO, HTTP
- License: Not captured
- Language: Not captured
- Stars: Not captured
- Updated: Jun 4, 2026
- Source: https://registry.modelcontextprotocol.io