Index / MCP servers / Byte Protocol

Byte Protocol MCP server

Byte Protocol is a remote MCP server that gives an AI agent 15 tools, among them byte_buy_data, byte_check_subscription, byte_get_network_stats. It answers at https://mcp.payperbyte.io/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 6 of 6 times since 10 September 2026; the last check, on 19 October 2026, succeeded.

Status
Answering
Tools
15
Reliability
6 of 6 checks
Response time
470 ms
Transport
streamable HTTP
Last checked
19 October 2026

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

Description as the publisher wrote it.

The 15 tools Byte Protocol offers

ToolWhat it does
byte_buy_dataBuy 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 t
Inputs: feed, body
byte_check_subscriptionCheck if an address is subscribed to a specific publisher on PayPerByte.
Inputs: subscriber, publisher
byte_get_network_statsGet PayPerByte network-wide statistics: total publishers, messages streamed, and total subscriber fees settled in USDC.
byte_get_publisherGet 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).
Inputs: address
byte_get_token_balancesGet 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.
Inputs: address
byte_list_feedsList all active data feeds in the PayPerByte catalog with topics, price-per-call, and frequency (pricePerKB is a deprecated alias).
byte_list_my_subscriptionsList 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. Us
Inputs: subscriber, indexerUrl
byte_publish_dataPublish 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.
Inputs: subscriber, data, maxFee
byte_query_factQuery 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 stru
Inputs: question, subscriber_address, max_byte_cost, topic_filter, min_publisher_pqs, max_response_latency_ms
byte_register_publisherRegister 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 f
Inputs: stake, topic, expectedSize, maxSize, frequency, pricePerKB
byte_search_publishersSearch PayPerByte publishers by topic and sort order. Returns publisher addresses, topics, subscriber counts, message counts, and price-per-KB.
Inputs: query, sortBy, limit
byte_subscribeSubscribe 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
Inputs: publisher, skipAllowance
byte_subscription_healthGet 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
Inputs: publisher, indexerUrl
byte_unsubscribeUnsubscribe 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_he
Inputs: publisher
byte_verify_payloadVerify-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 PayloadAtte
Inputs: data, expectedHash, txHash, hashMode

Add Byte Protocol to your AI client

Every block below points at https://mcp.payperbyte.io/mcp. Pick your client and copy.

Claude Code: one command in your terminal
claude mcp add --transport http byte-protocol https://mcp.payperbyte.io/mcp
Claude Desktop: claude_desktop_config.json
{
  "mcpServers": {
    "byte-protocol": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://mcp.payperbyte.io/mcp"]
    }
  }
}
Cursor: ~/.cursor/mcp.json, or .cursor/mcp.json in a project
{
  "mcpServers": {
    "byte-protocol": {
      "url": "https://mcp.payperbyte.io/mcp"
    }
  }
}
VS Code and GitHub Copilot: .vscode/mcp.json
{
  "servers": {
    "byte-protocol": {
      "type": "http",
      "url": "https://mcp.payperbyte.io/mcp"
    }
  }
}
Zed: Zed settings.json
{
  "context_servers": {
    "byte-protocol": {
      "url": "https://mcp.payperbyte.io/mcp"
    }
  }
}
Windsurf: ~/.codeium/mcp_config.json
{
  "mcpServers": {
    "byte-protocol": {
      "serverUrl": "https://mcp.payperbyte.io/mcp"
    }
  }
}
JetBrains AI Assistant: Settings, Tools, AI Assistant, MCP, New MCP Server, as JSON
{
  "mcpServers": {
    "byte-protocol": {
      "url": "https://mcp.payperbyte.io/mcp"
    }
  }
}
Continue: .continue/mcpServers/neuronto.yaml
name: Byte Protocol
version: 0.0.1
schema: v1
mcpServers:
  - name: Byte Protocol
    type: streamable-http
    url: https://mcp.payperbyte.io/mcp
Gemini CLI: ~/.gemini/settings.json
{
  "mcpServers": {
    "byte-protocol": {
      "httpUrl": "https://mcp.payperbyte.io/mcp"
    }
  }
}
Codex CLI: MCP server config
{
  "mcpServers": {
    "byte-protocol": {
      "type": "http",
      "url": "https://mcp.payperbyte.io/mcp"
    }
  }
}
Warp: MCP servers, + Add, paste JSON
{
  "mcpServers": {
    "byte-protocol": {
      "url": "https://mcp.payperbyte.io/mcp"
    }
  }
}
Goose: a one-click extension link
goose://extension?url=https%3A%2F%2Fmcp.payperbyte.io%2Fmcp&type=streamable_http&id=byte-protocol&name=Byte%20Protocol

Is Byte Protocol up right now?

It answered our last check on 19 October 2026 in 470 ms. Over 6 checks since 10 September 2026 it answered 6. Status here comes from Neuronto's own probes, not from the publisher.

MCP servers similar to Byte Protocol

Questions about Byte Protocol

How many tools does Byte Protocol have?

15, as returned by the server's own tools/list on 12 September 2026: byte_buy_data, byte_check_subscription, byte_get_network_stats, byte_get_publisher, byte_get_token_balances, byte_list_feeds, byte_list_my_subscriptions, byte_publish_data, and 7 more.

Is Byte Protocol down?

It answered our last check on 19 October 2026 in 470 ms. Over 6 checks since 10 September 2026 it answered 6.

How do I add Byte Protocol to Cursor?

Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://mcp.payperbyte.io/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.

Does Byte Protocol need an API key?

It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.

Where this comes from

Publisher: io.github.0rkz. Endpoint host: mcp.payperbyte.io. ARD identifier: urn:air:io.github.0rkz:mcp:byte-protocol. First indexed 10 September 2026. The tools are exactly what the server returned; nothing on this page is inferred from its name. Ranking in Neuronto search is never for sale.

Is this your server? Get a message the day it stops answering or its tools change: monitoring, 14 days free. Or claim the domain to manage how it is listed.