netops-mcp
Related Servers
Alternatives to netops-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to perform real network diagnostics on the local machine, including ping, traceroute, DNS lookups, TLS checks, and more.MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to debug local networks in plain language by pinging, sweeping subnets, tracing routes, resolving DNS, scanning ports, inspecting ARP tables and active connections, and checking URL reachability.MIT
- AlicenseAqualityBmaintenanceEnables AI agents to check the health of internet infrastructure and specific services, helping diagnose whether issues are local or external.36ISC
- FlicenseAqualityBmaintenanceProvides AI coding agents with real-time visibility into local development runtime state, enabling them to tail application logs, inspect ports, monitor process metrics, and diagnose network errors.1-
- AlicenseNot gradedqualityDmaintenanceQuery devices, check connectivity, and get network status from your Tailscale tailnet directly via an AI assistant.MIT
- AlicenseNot gradedqualityCmaintenanceDiagnoses proxy misconfigurations that break AI coding tools like Cursor, VS Code, and Windsurf.1MIT
TDQS
Scored across 19 tools
Most tools have clearly distinct purposes, especially the WireGuard and diagnostic tools. However, there is some overlap among net_diagnose, diagnosis_bundle, and net_triangulate that could cause confusion, though descriptions help differentiate.
Naming patterns are inconsistent: some tools use verb_noun (e.g., dns_lookup, http_probe), others noun_verb (e.g., tcp_port_check, tls_inspect), and some use prefixes like 'net_' or 'wg_'. While still readable, the mix reduces predictability.
With 19 tools, the server covers network diagnostics, DNS, TLS, MTU, traceroute, and WireGuard management comprehensively. Each tool addresses a specific need without being excessive.
The tool surface is largely complete for network operations, covering diagnosis, DNS, TLS, connectivity, and WireGuard configuration. Minor gaps exist, such as missing routing table inspection or interface configuration, but core workflows are well-supported.