byte_get_network_stats — byte protocol MCP Tool
byte_get_network_stats
(byte get network stats) is one of 15 tools on the
byte protocol
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call byte_get_network_stats from your client
- Claude Code byte protocol byte_get_network_stats run in your project directory
- Claude Desktop byte protocol byte_get_network_stats ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor byte protocol byte_get_network_stats ~/.cursor/mcp.json
- VS Code byte protocol byte_get_network_stats .vscode/mcp.json
- Zed byte protocol byte_get_network_stats ~/.config/zed/settings.json
- Windsurf byte protocol byte_get_network_stats ~/.codeium/windsurf/mcp_config.json
- Cline byte protocol byte_get_network_stats ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI byte protocol byte_get_network_stats ~/.gemini/settings.json
- Grok byte protocol byte_get_network_stats .mcp.json (in your project root)
- ChatGPT byte protocol byte_get_network_stats Settings → Connectors → Advanced → Developer mode
- Claude.ai byte protocol byte_get_network_stats Settings → Connectors → Add custom connector
- LangChain byte protocol byte_get_network_stats pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http byte-protocol https://mcp.payperbyte.io/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.