Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/0rkz/byte-mcp-serverWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/0rkz/byte-mcp-server/byte-protocol)<a href="https://agentmods.dev/mcp/0rkz/byte-mcp-server/byte-protocol"><img src="https://agentmods.dev/badge/mcp/0rkz/byte-mcp-server/byte-protocol/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/mcp/0rkz/byte-mcp-server/byte-protocol"><img src="https://agentmods.dev/badge/mcp/0rkz/byte-mcp-server/byte-protocol.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
byte-protocol scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{
"byte-protocol": {
"command": "npx",
"args": [
"-y",
"byte-mcp-server"
],
"env": {
"PRIVATE_KEY": "",
"RPC_URL": ""
}
}
}What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 1mo ago First seen · 13 lines scan A 4343f14c9c75
byte-protocol is an MCP server published in the GitHub repository 0rkz/byte-mcp-server (1 stars, last pushed 3d ago), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other mcp servers, from other repositories
coinopai-mcp
Kronos crypto signals + trade decisions + 819 automation prompts. x402 micropayments, USDC/Base. Runs locally from the coinopai-mcp npm package. Needs 1 environment variable to run.
ddg-agent-services-mcp
Payment-aware MCP server + multi-framework SDK for DDG Agent-Payable Services (248 x402/direct-crypto services, OpenAI-compatible gateway). Runs locally from the ddg-agent-services-mcp Python package. Needs 2 environment variables to run.
hive-mcp-depin
MCP server: DePIN reward routing, capacity verification, settlement reports · Hive Civilization. Remote server at hive-mcp-gateway.onrender.com.
hive-mcp-evaluator
MCP server: NEED + YIELD + CLEAN-MONEY gates with EIP-3009 attestations · Hive Civilization. Remote server at hive-mcp-gateway.onrender.com.
vaultpilot-mcp
Safety first. Hardware-verified DeFi for AI agents — designed for when the AI can be compromised. Runs locally from the vaultpilot-mcp npm package. Needs 10 environment variables to run.
hive-mcp-mining
Tether MOS telemetry + Boltz BTC↔USDC atomic swap broker MCP. Remote server at hive-mcp-gateway.onrender.com.