Skip to content

byte-protocol MCP server

io.github.0rkz/byte-protocol0rkzstreamable-httpv0.13.0Scanned

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

15 tools: 2 can delete or cancel things, 6 change things and 7 only read.

Tools: 2 delete, 0 irreversible, 6 write, 7 read.
  • Reads private data · 2
  • Reads text others write · 15
  • Can send data out · 1
  • 1 finding

Tools listed without sign-in. Remote posture

With Anlyon

2 tools here can delete or cancel things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the byte-protocol MCP server can do

The byte-protocol MCP server is published by the GitHub account 0rkz. It has 15 tools. It can delete or cancel things (2 tools: byte_register_publisher and byte_publish_data) and create or change data (6 tools: byte_check_subscription, byte_unsubscribe, byte_subscribe, byte_query_fact and 2 more). 7 tools only read.

2 tools read private data (byte_get_publisher and byte_get_network_stats); 15 tools bring in text other people can write (byte_search_publishers, byte_get_publisher, byte_get_network_stats and 12 more); 1 tool can send data out of your system (byte_publish_data). On its own it has all three parts of a prompt-injection exfiltration path: private data, text others write, and a way out.

The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 15, 2026, version 0.13.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

15 tools

Deletes or cancels 2Claude Code: deny
  • byte_publish_dataPublish data to a subscriber via the PayPerByte DataStream contract.Reads text others writeCan send data outNo findings

    Why it is in this group

    • The name "byte_publish_data" says "publish": a word for a change that another call does not undo.
    • The server marks it destructive (destructiveHint: true).

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • outboundThe name "byte_publish_data" says "publish": it sends or publishes something to other people.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Publish data
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: false
    • openWorldHint: true
  • byte_register_publisherRegister as a data publisher on PayPerByte.Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it destructive (destructiveHint: true).

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Register publisher
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: false
    • openWorldHint: true
Changes things 6Claude Code: ask
  • byte_buy_dataBuy a single data packet from any PayPerByte feed via the x402 payment gateway.Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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 POST oracles (see https://x402.payperbyte.io/feeds for the live list and each feed's `method`) 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.

    Annotations the server declares

    • title: Buy data
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
  • byte_check_subscriptionCheck if an address is subscribed to a specific publisher on PayPerByte.Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Check if an address is subscribed to a specific publisher on PayPerByte.

    Annotations the server declares

    • title: Check subscription
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • byte_query_factQuery a PayPerByte fact-oracle publisher for a signed answer with citations.Reads text others write1 finding

    Why it is in this group

    • The name "byte_query_fact" says "query": a word for reading.
    • The server marks it as not read-only (readOnlyHint: false).

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.

    Findings

    • Warn

      The server marks "byte_query_fact" as not read-only (readOnlyHint: false), and its words say it reads.

      Matched text

      annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":false,"openWorldHint":true}; The name "byte_query_fact" says "query": a word for reading.

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Query fact
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
  • byte_subscribeSubscribe to a PayPerByte publisher's data feed.Reads text others writeNo findings

    Why it is in this group

    • The name "byte_subscribe" says "subscribe": a word for a change.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Subscribe
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
  • byte_unsubscribeUnsubscribe from a publisher's data feed.Reads text others writeNo findings

    Why it is in this group

    • The name "byte_unsubscribe" says "unsubscribe": a word for a change.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Unsubscribe
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
  • 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.Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Verify payload (verify-before-act)
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
Only reads 7Show 7 read-only tools
  • byte_get_network_statsGet PayPerByte network-wide statistics: total publishers, messages streamed, and total subscriber fees settled in USDC.Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "byte_get_network_stats" says "get": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "get" and "message": it reads messages.
    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • untrusted-inputThe description's first sentence says "get" and "message": it reads messages, which other people can write.
    Description, as the server wrote it
    Get PayPerByte network-wide statistics: total publishers, messages streamed, and total subscriber fees settled in USDC.

    Annotations the server declares

    • title: Get network stats
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • 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).Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "byte_get_publisher" says "get": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "get" and "message": it reads messages.
    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • untrusted-inputThe description's first sentence says "get" and "message": it reads messages, which other people can write.
    Description, as the server wrote it
    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).

    Annotations the server declares

    • title: Get publisher info
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • 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).Reads text others writeNo findings

    Why it is in this group

    • The name "byte_get_token_balances" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Get token balances
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • byte_list_feedsList all active data feeds in the PayPerByte catalog with topics, price-per-call, and frequency (pricePerKB is a deprecated alias).Reads text others writeNo findings

    Why it is in this group

    • The name "byte_list_feeds" says "list": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    List all active data feeds in the PayPerByte catalog with topics, price-per-call, and frequency (pricePerKB is a deprecated alias).

    Annotations the server declares

    • title: List feeds
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • byte_list_my_subscriptionsList every active subscription for a given wallet address.Reads text others writeNo findings

    Why it is in this group

    • The name "byte_list_my_subscriptions" says "list": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: List my subscriptions
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • byte_search_publishersSearch PayPerByte publishers by topic and sort order.Reads text others writeNo findings

    Why it is in this group

    • The name "byte_search_publishers" says "search": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Search PayPerByte publishers by topic and sort order. Returns publisher addresses, topics, subscriber counts, message counts, and price-per-KB.

    Annotations the server declares

    • title: Search publishers
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • byte_subscription_healthGet the content-drift signal for a publisher.Reads text others writeNo findings

    Why it is in this group

    • The description's first verb is "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Subscription health
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

30 paths in this server alone from private data, through text someone else wrote, to a way out. Denying 1 outbound tool breaks every one.

Reads private data2
Reads files, mail, messages, databases, secrets, calendars or repositories.
Can send data out1
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
deny to break every path
{
  "permissions": {
    "deny": [
      "mcp__byte-protocol__byte_publish_data"
    ]
  }
}

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:56 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
8
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 8 tools that change things (2 destructive, 6 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://mcp.payperbyte.io/mcp: tools/list returned 15 tools to an anonymous client, including byte_register_publisher (destructive), byte_publish_data (destructive), byte_check_subscription (write), byte_unsubscribe (write), byte_subscribe (write) and 3 more

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

1 warn
  • The server marks "byte_query_fact" as not read-only (readOnlyHint: false), and its words say it reads.

    Matched text

    annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":false,"openWorldHint":true}; The name "byte_query_fact" says "query": a word for reading.

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 0.13.0. Values in angle brackets are yours to fill in.

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

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__byte-protocol__byte_search_publishers",
      "mcp__byte-protocol__byte_get_publisher",
      "mcp__byte-protocol__byte_get_network_stats",
      "mcp__byte-protocol__byte_get_token_balances",
      "mcp__byte-protocol__byte_list_feeds",
      "mcp__byte-protocol__byte_list_my_subscriptions",
      "mcp__byte-protocol__byte_subscription_health"
    ],
    "ask": [
      "mcp__byte-protocol__byte_check_subscription",
      "mcp__byte-protocol__byte_unsubscribe",
      "mcp__byte-protocol__byte_subscribe",
      "mcp__byte-protocol__byte_query_fact",
      "mcp__byte-protocol__byte_buy_data",
      "mcp__byte-protocol__byte_verify_payload"
    ],
    "deny": [
      "mcp__byte-protocol__byte_register_publisher",
      "mcp__byte-protocol__byte_publish_data"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as byte-protocol. Review it before you use it.

Capability tags behind 15 rules
  • mcp__byte-protocol__byte_search_publishers untrusted-input
  • mcp__byte-protocol__byte_get_publisher private-data, untrusted-input
  • mcp__byte-protocol__byte_get_network_stats private-data, untrusted-input
  • mcp__byte-protocol__byte_check_subscription untrusted-input
  • mcp__byte-protocol__byte_get_token_balances untrusted-input
  • mcp__byte-protocol__byte_list_feeds untrusted-input
  • mcp__byte-protocol__byte_list_my_subscriptions untrusted-input
  • mcp__byte-protocol__byte_subscription_health untrusted-input
  • mcp__byte-protocol__byte_unsubscribe untrusted-input
  • mcp__byte-protocol__byte_subscribe untrusted-input
  • mcp__byte-protocol__byte_register_publisher untrusted-input
  • mcp__byte-protocol__byte_publish_data untrusted-input, outbound
  • mcp__byte-protocol__byte_query_fact untrusted-input
  • mcp__byte-protocol__byte_buy_data untrusted-input
  • mcp__byte-protocol__byte_verify_payload untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.github.0rkz/byte-protocol/verify?hash=8742d135c96aced4daad127185c70d9a2a8315d2f1893d1d56e371c723140599" | jq -e '.changed == false'

Pinned hash 8742d135c96a, from Nov 15, 2026, 15:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.github.0rkz/byte-protocol/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.0rkz/byte-protocol
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.0rkz/byte-protocol.svg)](https://radar.anlyon.com/servers/io.github.0rkz/byte-protocol)

Source: MCP Registry · repository. Synced Oct 21, 2026, 18:13 UTC.

byte-protocol MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the byte-protocol MCP server safe?

No scan can promise that. What its definitions show: 15 tools, 8 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the byte-protocol MCP server delete data?

Yes. 2 tools can delete, cancel or revoke something: byte_register_publisher and byte_publish_data.

Can the byte-protocol MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the byte-protocol MCP server have?

15 tools: 2 destructive, 6 write, 7 read. byte_register_publisher, byte_publish_data, byte_check_subscription, byte_unsubscribe, byte_subscribe, byte_query_fact, byte_buy_data, byte_verify_payload and 7 more.

Does the byte-protocol MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the byte-protocol MCP server send data to outside services?

1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): byte_publish_data.

Has the byte-protocol MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 15, 2026.