Netdryrun
OfficialRelated Servers
Alternatives to Netdryrun
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables read-only verification of SR Linux and FRR network-device command output without device credentials, turning raw text into structured verdicts about interfaces, routes, BGP peers, and overall health. It also sanitizes that untrusted output by masking secrets and neutralizing prompt injection before a model reads it.MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI-assisted management of multi-vendor network devices (Cisco, Juniper, Nokia, Arista, Linux) through natural language, supporting health checks, configuration changes, routing analysis, and automation workflows.MIT
- AlicenseNot gradedqualityBmaintenanceEnables LLMs to turn natural-language prompts into validated, deployed Cisco network topologies, including routing, switching, DHCP, VLANs, security auditing, and live device inspection.MIT
- AlicenseAqualityCmaintenanceWraps ipspace/netlab as an engine to give LLMs access to validated, lab-tested network device configurations instead of hallucinated ones.88Apache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to design and validate Cisco network topologies, generate IOS CLI configurations, deploy and configure devices live in Cisco Packet Tracer, and verify connectivity through pings and packet captures. It also supports building auto-graded Packet Tracer activities (.pka) for CCNA labs.MIT
- AlicenseBqualityBmaintenanceEnables AI assistants to plan and build Cisco Packet Tracer network labs, generate and validate Cisco IOS configurations, run live connectivity tests, grade activities, and diagnose broken labs non-destructively.261MIT
TDQS
Scored across 8 tools
The core verbs are distinct: record_baseline writes checks, validate/check_types are lab-free inspection, dry_run is the synchronous verdict, start_run+get_result are its async split, run_checks targets an already-running lab, and verify_change diffs against a declared intent. The one weak spot is dry_run vs start_run vs run_checks, which all produce 'the same result and verdict' and could be misselected if the agent skips the caveats about kept labs and async clients.
Consistent snake_case with a verb_noun shape for nearly everything (record_baseline, dry_run, get_result, run_checks, start_run, verify_change). Only 'validate' (bare verb, no object) and 'check_types' (reads as noun phrase) break the pattern, a minor deviation that stays readable.
Eight tools is well-scoped for a dry-run verification server: baseline capture, config validation, check-type discovery, synchronous and asynchronous run paths, re-check against a live lab, and intent diffing. Each entry maps to a distinct step in the workflow rather than duplicating surface.
The happy path is covered end to end (baseline -> validate -> dry_run -> verdict -> verify_change), but there is no tool to destroy or list a lab kept with keep_lab=true, even though dry_run's failure guidance tells the agent to keep the lab up and 'then destroy the lab' — an agent dead end. There is also no way to read or amend netdryrun.yml through the server, so check authoring depends on external file editing plus check_types as a reference.