Byte Protocol MCP Server

by 0rkz Your server? Claim it

answering

Byte Protocol is answering right now. Last checked 3 min ago. 695 installs a week from npm. It exposes 15 tools. Last commit 13 Sep 2026.

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

Installs per day peak 170 · avg 41 · +96% w/w

a month agotoday

Uptime history 47 days of history · worst day 56%

47 days agonow

100.0%

Uptime 24h

92 of 92 checks

Tools

read from the server

576 ms

Response time

average over 24h

695

Installs / week

npm and PyPI

What changed 17

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 9 August 2026. No other catalogue keeps this.

13 Sep a tool changed the parameters it asks for2 times that day byte_buy_data

13 Sep a tool description was rewritten byte_buy_data

13 Sep a tool changed version

7 Sep a tool changed the parameters it asks for byte_query_fact

6 Sep a tool description was rewritten byte_buy_data

4 Sep 2 tool descriptions were rewritten byte_buy_data, byte_list_feeds

4 Sep a tool changed the parameters it asks for byte_buy_data

1 Sep a tool description was rewritten byte_buy_data

1 Sep a tool changed the parameters it asks for byte_buy_data

25 Aug a tool description was rewritten byte_buy_data

and 6 more, back to 9 August 2026

Nothing serious here today

Today is the operative word: we check Byte Protocol every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 3 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

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

~/Library/Application Support/Claude/claude_desktop_config.json

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

~/.codex/config.toml

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

.cursor/mcp.json

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

.vscode/mcp.json

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

This one needs environment variables set before it will start: PRIVATE_KEY (Ethereum private key for write/buy tools (subscribe, unsubscribe, publish, buy_data). buy_data spends real Base-mainnet USDC — use a dedicated wallet. Not required for read-only tools.), RPC_URL (RPC for the on-chain library + EIP-712 attestation layer (Arbitrum Sepolia, eip155:421614). The x402 buy rail settles USDC on Base mainnet and needs no RPC here. Defaults to Arbitrum Sepolia public RPC.), BYTE_GATEWAY_ATTESTER (Gateway attester address byte_buy_data pins receipts against. Defaults to the current PayPerByte gateway attester (rotated 2026-08-19; previous default 0x77c86a...C472 is retired). Override only if the gateway discloses a rotation you need ahead of a package update - see /.well-known/agent.json receipt.attester and receipt.retiredAttesters.). The author declared them in the registry entry; get the values from the project itself.

Available tools 15

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

byte

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 10 POST oracles — runtime-eol, threat-intel, address-reputation, pkg-verdict, sanctions-screen, reasoning-verdict, merchant-screen, positioning-snapshot, cctp-attestation-latency, regime-signal — 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 and listed per feed at https://x402.payperbyte.io/feeds — the signed EIP-712 attestation over the exact response bytes proves delivery, not that a verdict itself is correct. Use a dedicated wallet holding only what you intend to spend.

byte_check_subscription

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

byte_get_network_stats

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

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_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 whether to unsubscribe.

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.

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.

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.

byte_search_publishers

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

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.

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.

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.

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.

Endpoints

URL	Transport	State	Latency	Checked
https://mcp.payperbyte.io/mcp	streamable-http	answering	624 ms	3 min ago

Alternatives to Byte Protocol

same job, measured the same way

Boo X402 MCP

by lucle87

Pay-per-call crypto data for AI agents. USDC on Base via x402. No API key.

30 installs/wk local only

X402 API

by fernsugi

DeFi data API for AI agents — pay-per-call via x402/USDC on Base

41 installs/wk local only

Polyform

by polyform

Pay-per-call data APIs for AI agents. USDC on Base via x402. 33 tools, no signup.

67 tools answering

Oromi Agent Services

by oromi-uk

25 pay-per-call UK data & verification tools for AI agents. x402 USDC on Base; free quote mode.

39 installs/wk local only

X402 Tools MCP

by mizukaizen

melis x402 Tools — 22 pay-per-call APIs for AI agents. No accounts, no API keys. USDC on Base.

61 installs/wk local only

Kristo Intelligence

by hristovdimitri2-hub

Pay-per-call DeFi intelligence for AI agents on Base — x402, USDC, no keys.

3 tools answering

Agent Web Reader

by charliemorrison

Pay-per-call data tools for AI agents: crypto signal, web reader, SEO audit. x402 USDC on Base.

3 tools answering

Agishub

by agishub

AgisHub — 34 pay-per-call tools for AI agents over x402 (USDC on Base). No API key, no signup.

232 installs/wk 34 tools answering

Byte Protocol — questions

Answers built from our own checks of this server.

What can Byte Protocol do?

It exposes 15 tools, read directly from the server on our last check. Among them: byte_buy_data, byte_check_subscription, byte_get_network_stats, byte_get_publisher, byte_get_token_balances, byte_list_feeds and 9 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is Byte Protocol working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 576 ms. The bar chart above shows every period we have measured.

How do I connect Byte Protocol?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does Byte Protocol need an API key?

No. Byte Protocol completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 15 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is Byte Protocol?

It answers our handshake in 576 ms on average, which is faster than 23% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.

How many people use Byte Protocol?

The npm package byte-mcp-server was installed 695 times in the last week. Week over week that is +96%. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.

Is Byte Protocol open source?

Yes — it is published under the MIT licence, written in TypeScript and 1 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.