Remote MCP · Endpoint

io.github.0rkz/byte-protocol MCP server

No. io.github.0rkz/byte-protocol answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://mcp.payperbyte.io/mcp

The last check completed an MCP handshake.

Registry name
io.github.0rkz/byte-protocol
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
147 ms
Tools exposed
15 tools
Uptime, last 30 days
100% from 18 checks
Described by its publisher as
PayPerByte — per-byte data for AI agents: x402 USDC on Base, EIP-712-attested. No token.
Listing
From the official MCP registry (active).
Recent checks of io.github.0rkz/byte-protocol
CheckedResultHandshake
1 hour agoHandshake completed147 ms
1 day agoHandshake completed765 ms
2 days agoHandshake completed203 ms
3 days agoHandshake completed180 ms
4 days agoHandshake completed158 ms
5 days agoHandshake completed437 ms
6 days agoHandshake completed213 ms
9 days agoHandshake completed188 ms
11 days agoHandshake completed155 ms
14 days agoHandshake completed194 ms
16 days agoHandshake completed184 ms
18 days agoHandshake completed158 ms
20 days agoHandshake completed241 ms
22 days agoHandshake completed205 ms
24 days agoHandshake completed148 ms
26 days agoHandshake completed152 ms
27 days agoHandshake completed147 ms
28 days agoHandshake completed764 ms

The last 18 checks. Full history is kept for 30 days; the all-time counter stands at 29 responding of 29.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with io.github.0rkz/byte-protocol and makes no claim about it beyond what these checks measured.