All servers · Agent payments (x402)

io.github.0rkz/byte-protocol

io.github.0rkz/byte-protocol · v0.13.0

Measured by MCP Station

Description written by the publisher, not verified

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

Connect

claude mcp add --transport http byte-protocol https://mcp.payperbyte.io/mcp

{
  "mcpServers": {
    "byte-protocol": {
      "url": "https://mcp.payperbyte.io/mcp"
    }
  }
}

Tools as reported by the server

• byte_search_publishers
  Search PayPerByte publishers by topic and sort order. Returns publisher addresses, topics, subscriber counts, message counts, and price-per-KB.
• 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).
• byte_get_network_stats
  Get PayPerByte network-wide statistics: total publishers, messages streamed, and total subscriber fees settled in USDC.
• byte_check_subscription
  Check if an address is subscribed to a specific publisher on PayPerByte.
• 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.
• byte_list_feeds
  List all active data feeds in the PayPerByte catalog with topics, price-per-call, and frequency (pricePerKB is a deprecated alias).
• 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 wh
• 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), o
• 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.
• 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 th
• byte_register_publisher write/delete
  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.
• byte_publish_data write/delete
  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.
• 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 publis
• 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 facilita
• 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 a

Repository · JSON · Text for agents · Registry updated 2026-09-13