net-mcp
Related Servers
Alternatives to net-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceAn MCP server that enables LLMs to retrieve structured network information, including routing, interfaces, MPLS, and topology, from devices using gNMI and OpenConfig models. It facilitates real-time network analysis, log filtering, and status monitoring through a standardized interface.1014BSD 3-Clause
- AlicenseNot gradedqualityAmaintenanceAn MCP server that allows LLMs to create, configure, validate, and explain Cisco Packet Tracer network topologies. It provides a comprehensive suite of tools for generating deployment scripts, CLI configurations, and automated network troubleshooting.349 PyPI217MIT
- AlicenseAqualityAmaintenanceMCP server for on-demand network diagnostics, providing DNS lookups with DNSSEC checks, ping, traceroute, TCP port checks, HTTP checks, TLS certificate inspection, WHOIS, and ASN lookups.1241 PyPIMIT
- FlicenseNot gradedqualityDmaintenanceA secure MCP server for network diagnostics, providing tools like ping, traceroute, whois, nslookup, dig, nmap, curl, and netstat through natural language interfaces.-
- AlicenseAqualityDmaintenanceAn MCP server that exposes live network monitoring data as Resources and diagnostic capabilities as Tools, letting AI assistants query network health conversationally.6MIT
- AlicenseNot gradedqualityDmaintenanceA comprehensive MCP server that provides AI assistants with professional-grade network analysis capabilities, combining Wireshark packet analysis, nmap scanning, and threat intelligence for enhanced network troubleshooting and security analysis.MIT
TDQS
Scored across 39 tools
Most tools have a clear, distinct target and data source, and descriptions explicitly call out differences (e.g., dns_lookup vs local_dig). A few pairs overlap in concept (bgp_prefix_origin vs bgp_route_lookup, local_mtr vs local_ping/local_traceroute), but the descriptions are enough to disambiguate.
Names are all lowercase snake_case and consistently use a domain-prefix pattern (rpki_*, bgp_*, irr_*, peeringdb_*, local_*). The tails mix verbs and plain nouns (lookup, validate, info, hijacks, public_ip), so it is not a uniform verb_noun scheme, but it is predictable.
39 tools is beyond the 25+ threshold and presents a heavy selection surface, even though the tools are organized into distinct clusters. The broad network scope justifies more than a typical server, but the count strains agent decision-making.
The server covers core workflows across IP planning, DNS, BGP, RPKI, IRR, PeeringDB, and local diagnostics with no serious dead ends. Minor gaps exist (e.g., no RDAP abstraction or multi-vantage-point probing), but the covered domains feel substantially complete.