Read-only MCP server for network engineers: config drift, CIS/PCI checks, 802.1X diagnosis, certificates inside configs, device facts and topology, OPNsense rule changes, change pre-flight, config sanitising.
Server has 11 well-intentioned tools with detailed descriptions (avg 180 chars, within baseline 194). All tools are READ_ONLY and deterministic, which is good for safety. However, input schemas are inferred from function signatures rather than explicitly visible in JSON Schema format. Parameter descriptions exist in docstrings but are not formally declared in schema objects. Output schemas are completely undocumented, responses are rendered as plain text strings rather than structured objects. Error handling is minimal (basic validation, no recovery guidance). Tool naming is clear and verb-forward (explain_, check_, diagnose_, lookup_, find_, extract_, sanitize_), but composition could be tighter, some tools overlap (explain_config_diff vs explain_opnsense_change).
Run a CIS/PCI starter pack over one device config: cleartext management, SSH, default SNMP communities, centralised AAA, remote logging, NTP, hashed credentials, default credentials, management exposed to any source, login banner. Ten deterministic checks, each with a framework reference and a one-line remediation. Cisco, MikroTik, EdgeOS, OPNsense.
Connect to a TLS endpoint (hostname:port), retrieve its certificate chain, and check each cert: expiry, weak keys, self-signed, SAN mismatch, CA chain completeness. The one tool that connects to a host you name (everything else is local/deterministic).
Diagnose a port that will not authenticate. Paste any of: the RADIUS/ISE authentication log, the switchport interface config, the supplicant (Windows wired AutoConfig) log. Names the root cause — EAP method mismatch, unknown CA, shared-secret/NAD mismatch, missing dynamic VLAN, CoA NAK on the wrong port, invalid dACL — decodes ISE failure codes, and gives the fix on the switch AND in ISE. Read-only, rule-based.
Explain what changed between two network device config snapshots, in plain English. EdgeOS, MikroTik RouterOS, OPNsense config.xml (per-rule stories, save-stamp noise filtered), EdgeSwitch and Cisco IOS-style configs: volatile lines stripped, changes grouped by config section, each tagged with a risk level and why it matters. Deterministic — no model call, nothing leaves the machine.
Output schemas completely undocumented. All tools return plain text strings (str) with no structured field definitions. LLMs cannot parse results or chain downstream tool calls. E.g., explain_config_diff returns a formatted string; extract_device_facts should return {hostname, role, ips, vlans} but returns text.
Input schemas are inferred from Python function signatures, not explicitly declared as JSON Schema objects. Parameters lack formal type constraints, enums, and min/max bounds. E.g., 'vendor' is a free-form string with no enum constraint; 'role' in find_certs_in_config has no validation.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 55 | 2026-07-28+ | v2 |
Explain OPNsense config.xml changes in plain English: per-rule stories, save-stamp noise filtered, lifecycle tracking (added/modified/removed), blast radius, and rollback guidance. Deterministic XML parsing, not a diff template.
Extract device facts from a config: hostname, role (firewall/router/switch/etc), IP addresses, VLANs, and network segments. Multi-vendor: OPNsense XML, EdgeOS, MikroTik RouterOS, EdgeSwitch, Cisco IOS.
Find every certificate embedded in a device config and check it: expiry (with severity buckets), weak RSA keys, MD5/SHA-1 signatures, self-signed leaves, CA certificates about to expire. Reads inline PEM blocks (Cisco crypto pki chains, EdgeOS, RouterOS exports, anything) and OPNsense base64-encoded certs in XML.
Fetch the latest NetOps Field Notes from the public RSS feed (netopsfieldnotes.com). Returns the most recent post title, link, and summary.
Decode a Cisco ISE / RADIUS failure or step code (5400, 5411, 5440, 11007, 11036, 11514, 12321, 12508, 12514, 15039, 22056): what it means, the usual cause, and the fix.
Read-only pre-flight for a proposed config change: what changes, how risky, which compliance checks regress, and who else shares the affected segments. Nothing here touches a device — the write path stays with the product.
Redact sensitive data from a device config: credentials, API keys, pre-shared keys, private keys, SNMP communities, RADIUS secrets. Returns the sanitized config safe to share.
Error handling is minimal. No recovery guidance, no actionable error messages. E.g., 'Both before and after snapshots are needed' is generic; should suggest 'Paste the previous config snapshot in 'before' and current snapshot in 'after'.' No categorization of retryable vs fatal errors.
Tool overlap and composition gaps. explain_config_diff and explain_opnsense_change both explain config changes; LLM must reason about which to call. extract_device_facts returns text instead of structured {hostname, role, ips, vlans} that downstream tools could consume.
latest_field_note has empty input schema (no parameters), but description is vague ('Fetch the latest NetOps Field Notes from the public RSS feed'). Should clarify: returns single most recent post, or paginated list? What fields in response?