top_bandwidth — Netmon (demo) MCP Tool
top_bandwidth
(top bandwidth) is one of 36 tools on the
Netmon (demo)
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call top_bandwidth from your client
- Claude Code Netmon (demo) top_bandwidth run in your project directory
- Claude Desktop Netmon (demo) top_bandwidth ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Netmon (demo) top_bandwidth ~/.cursor/mcp.json
- VS Code Netmon (demo) top_bandwidth .vscode/mcp.json
- Zed Netmon (demo) top_bandwidth ~/.config/zed/settings.json
- Windsurf Netmon (demo) top_bandwidth ~/.codeium/windsurf/mcp_config.json
- Cline Netmon (demo) top_bandwidth ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Netmon (demo) top_bandwidth ~/.gemini/settings.json
- Grok Netmon (demo) top_bandwidth .mcp.json (in your project root)
- ChatGPT Netmon (demo) top_bandwidth Settings → Connectors → Advanced → Developer mode
- Claude.ai Netmon (demo) top_bandwidth Settings → Connectors → Add custom connector
- LangChain Netmon (demo) top_bandwidth pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http netmon-demo https://netmon.com/mcp-demo/mcp
Other tools on this server
- get_network_entity_info
- arp_lookup
- ping
- traceroute
- port_map
- search_ip
- syslog_search
- eventlog_search
- eve_search
- eve_get
- log_severity_summary
- syslog_facets
- netflow_search
- netflow_raw_search
- flow_summary
- device_list
- device_get
- device_find
- overwatch_summary
- snmp_test
- snmp_walk_last
- snmp_walk_run
- agent_services
- agent_processes
- alerts_list
- alerts_history
- maintenance_windows_list
- tags_list
- arp_table
- interfaces_search
- device_metric_summary
- agent_disk_usage
- capture_list
- capture_get
- speedtest_history
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.