MCP servers observed by Lowdown
io.github.0rkz/byte-protocol MCP server: daily status and tool changes
Answered initialize and tools/list on all 4 checks recorded in the last 30 days (2026-11-09 to 2026-11-18) (Lowdown checks this server every 3 days); 15 tools listed. MCP Registry declaration recorded; observed every 3 days by Lowdown Scanner since 2026-11-09; no tool definition change in 3 compared days; no agent-reported interactions.
Lowdown observes this server daily, so this record changes from day to day. A copy older than 1 day may be outdated. Current record (JSON): GET https://lowdown-proxy.vercel.app/api/reputation/mcp:io.github.0rkz/byte-protocol
Before installing or connecting: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:io.github.0rkz/byte-protocol?menu=install-check · other questions: menu
Does it respond?
Latest daily check: 2026-11-18: the server answered initialize and tools/list.
- Observed days in the last 30: 4
- Answered initialize and tools/list: 4
- Required authentication: 0
- No response: 0
- Remotes differed: 0
Does it require authentication?
It did not return HTTP 401/403 on any of the 4 observed days. Lowdown checks without credentials.
Did its tools change recently?
No change in tool schemas, descriptions or names across 3 compared days.
What tools does it list?
15 tools on 2026-11-18:
byte_buy_databyte_check_subscriptionbyte_get_network_statsbyte_get_publisherbyte_get_token_balancesbyte_list_feedsbyte_list_my_subscriptionsbyte_publish_databyte_query_factbyte_register_publisherbyte_search_publishersbyte_subscribebyte_subscription_healthbyte_unsubscribebyte_verify_payload
MCP Registry declaration
- Registry name:
io.github.0rkz/byte-protocol - Declared version: 0.13.0
- Status: active
- Declared hosts:
mcp.payperbyte.io
Before installing: how to check
From an agent: add the remote MCP server https://lowdown-proxy.vercel.app/mcp (streamable HTTP, no authentication) and call get_lowdown with {"target": "mcp:io.github.0rkz/byte-protocol", "menu": "install-check"}. The same record without MCP: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:io.github.0rkz/byte-protocol?menu=install-check
When running its declared package, wrap it with the stdio proxy. Since lowdown-proxy 0.1.22 the proxy adds this record (install-check) to the server's initialize response; it changes no tool result and blocks nothing:
npx -y lowdown-proxy --target mcp:io.github.0rkz/byte-protocol -- npx -y byte-mcp-server
The same facts in machine-readable form are in this page's <script type="application/json" id="lowdown-evidence"> block (schema lowdown.evidence-snapshot v1).