# NetOps Field Notes (oci · ghcr.io/labaccessnow/netops-field-notes-mcp:0.1.0)

Config drift, CIS/PCI checks, 802.1X diagnosis, certs inside configs, topology, change pre-flight.

- Trust score: 44/100 (low)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-21

## Components

- oci · `ghcr.io/labaccessnow/netops-field-notes-mcp:0.1.0`: 44/100 (this document), [markdown](https://verifymcp.io/servers/labaccessnow-netops-field-notes-mcp/ghcr-io-labaccessnow-netops-field-notes-mcp-0-1-0.md), [page](https://verifymcp.io/servers/labaccessnow-netops-field-notes-mcp/ghcr-io-labaccessnow-netops-field-notes-mcp-0-1-0)

## Channel facts

- Registry: `oci`
- Package: `ghcr.io/labaccessnow/netops-field-notes-mcp:0.1.0`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-21.

- **Supply Chain Security**: 0/100
  - Malware scan not yet available for this package.
  - Known CVEs could not be checked: this artifact ships no SBOM, so there is no dependency list to read. Publishing one would let us assess it.
  - Install-script risk not yet assessed.
  - Dependency health could not be checked: this artifact ships no SBOM, so there is no dependency list to read. Publishing one would let us assess it.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 14 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 66/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1348 tokens (~112/item across 12 items; 12 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 50/100
  - Stability observed for 15 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 71/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 12 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 13 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

**Unverified: 1 category.** A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

## Install

### How do I install the NetOps Field Notes MCP server?

NetOps Field Notes runs locally as a container image, launched with docker run --rm -i ghcr.io/labaccessnow/netops-field-notes-mcp:0.1.0. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add labaccessnow-netops-field-notes-mcp -- docker run --rm -i ghcr.io/labaccessnow/netops-field-notes-mcp:0.1.0
```

### Cursor

```json
{
  "mcpServers": {
    "labaccessnow-netops-field-notes-mcp": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/labaccessnow/netops-field-notes-mcp:0.1.0"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "labaccessnow-netops-field-notes-mcp": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/labaccessnow/netops-field-notes-mcp:0.1.0"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add labaccessnow-netops-field-notes-mcp -- docker run --rm -i ghcr.io/labaccessnow/netops-field-notes-mcp:0.1.0
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "labaccessnow-netops-field-notes-mcp": {
      "type": "local",
      "command": [
        "docker",
        "run",
        "--rm",
        "-i",
        "ghcr.io/labaccessnow/netops-field-notes-mcp:0.1.0"
      ],
      "enabled": true
    }
  }
}
```

### Hermes

```yaml
mcp_servers:
  labaccessnow-netops-field-notes-mcp:
    command: "docker"
    args: ["run", "--rm", "-i", "ghcr.io/labaccessnow/netops-field-notes-mcp:0.1.0"]
```

### Netclaw

```json
{
  "McpServers": {
    "labaccessnow-netops-field-notes-mcp": {
      "Transport": "stdio",
      "Command": "docker",
      "Arguments": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/labaccessnow/netops-field-notes-mcp:0.1.0"
      ]
    }
  }
}
```

### Other

```json
{
  "mcpServers": {
    "labaccessnow-netops-field-notes-mcp": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/labaccessnow/netops-field-notes-mcp:0.1.0"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-21 (score 44, +1)

No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-19 (score 43, +1)

No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-17 (score 42, +1)

No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-15 (score 41, +1)

No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-14 (score 40, +3)

- [functional improvement] Stability: unverified → 0.27

### 2026-09-06 (score 37)

First indexed and scored.

## MCP tools (12)

### `explain_config_diff` (~117 tokens)

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.

Input parameters:

- `after` (string, required)
- `before` (string, required)
- `device` (string)
- `vendor` (string)

Output parameters:

- `result` (string)

### `check_config_compliance` (~99 tokens)

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.

Input parameters:

- `config` (string, required)
- `vendor` (string)

Output parameters:

- `result` (string)

### `diagnose_dot1x` (~134 tokens)

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.

Input parameters:

- `radius_log` (string)
- `supplicant_log` (string)
- `switchport_config` (string)

Output parameters:

- `result` (string)

### `lookup_ise_failure_code` (~86 tokens)

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.

Input parameters:

- `code` (string, required)

Output parameters:

- `result` (string)

### `find_certs_in_config` (~122 tokens)

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 config.xml <crt> blobs — the certificates web monitors never see because they are inside the config, not on a port.

Input parameters:

- `config` (string, required)
- `role` (string)
- `vendor` (string)

Output parameters:

- `result` (string)

### `check_tls_endpoint` (~94 tokens)

Connect to a public host:port, read the certificate it actually serves, and run the same findings as find_certs_in_config on it (expiry, weak key, weak signature, self-signed, hostname not in SANs, CA expiry). Any port. Refuses hosts that resolve to private or reserved addresses.

Input parameters:

- `host` (string, required)
- `port` (integer)
- `role` (string)

Output parameters:

- `result` (string)

### `extract_device_facts` (~92 tokens)

Pull the facts out of a device config: hostname, inferred role, every IPv4 address with its subnet, the subnets it sits on, and its VLANs. EdgeOS config.boot, MikroTik export, OPNsense config.xml, EdgeSwitch/FastPath, and Cisco IOS-style text.

Input parameters:

- `config` (string, required)
- `device` (string)
- `vendor` (string)

Output parameters:

- `result` (string)

### `infer_topology` (~89 tokens)

Given several device configs, work out which devices share subnets or VLANs and draw the segments as a Mermaid diagram (graph LR). Shared-subnet inference: two devices with an interface on the same network are adjacent. A subnet contained in a broader declared one is merged into it. Prefixes shorter than /16 are ignored as too broad to mean a segment.

Input parameters:

- `devices` (array, required)

Output parameters:

- `result` (string)

### `explain_firewall_change` (~133 tokens)

Explain a change between two OPNsense config.xml captures rule by rule: which rules were added, removed, edited or moved (keyed by uuid, so an edit is not mistaken for delete-plus-add), what each rule does in plain English, a risk rating with its stated grounds (any-source to a management port, any-source to the firewall itself, any/any/any pass), shadowed-rule notes, and which API call made the change. Save-stamp noise is recognised and set aside.

Input parameters:

- `after` (string, required)
- `before` (string, required)
- `device` (string)

Output parameters:

- `result` (string)

### `preflight_change` (~125 tokens)

Before you push a change: diff the proposed config against the current one, risk-tag every change, list compliance checks that would regress, and — if you pass the configs of the other devices you manage — compute the blast radius (who shares the affected subnets and VLANs). Returns a gate verdict: BLOCK, REVIEW REQUIRED, PROCEED WITH CARE, or NO CHANGE. Read-only; nothing is applied.

Input parameters:

- `current` (string, required)
- `device` (string)
- `fleet`
- `proposed` (string, required)
- `vendor` (string)

Output parameters:

- `result` (string)

### `sanitize_config` (~143 tokens)

Scrub a config before it goes anywhere: passwords, secrets, RADIUS/TACACS keys, IPsec PSKs, SNMP communities, MD5 digests, Wi-Fi PSKs, key/certificate blocks and hashes are redacted; IPv4 addresses are mapped consistently to RFC 5737 documentation ranges (same address, same placeholder, so the logic still reads), IPv6 to 2001:db8::, MACs to the RFC 7042 range, hostnames to ROUTER-n, domains and emails to example.com. Subnet and wildcard masks are preserved. Returns the clean text and a count per category.

Input parameters:

- `config` (string, required)

Output parameters:

- `result` (string)

### `latest_field_note` (~63 tokens)

The most recent This Week in NetOps episodes — what changed in networking, cloud and automation this week and what to do about it. The only tool here that touches the network besides check_tls_endpoint; it reads a public RSS feed.

Input parameters:

- `count` (integer)

Output parameters:

- `result` (string)

## Diagnostics

Captured diagnostic sections: Provenance. The full working is on the page: https://verifymcp.io/servers/labaccessnow-netops-field-notes-mcp/ghcr-io-labaccessnow-netops-field-notes-mcp-0-1-0#diagnostics

## Score history

- 2026-09-21: 44
- 2026-09-20: 43
- 2026-09-19: 43
- 2026-09-18: 42
- 2026-09-17: 42
- 2026-09-16: 41
- 2026-09-15: 41
- 2026-09-14: 40
- 2026-09-13: 37
- 2026-09-12: 37
- 2026-09-11: 37
- 2026-09-10: 37
- 2026-09-09: 37
- 2026-09-08: 37
- 2026-09-07: 37
- 2026-09-06: 37

## Common questions

### What is the NetOps Field Notes MCP server?

NetOps Field Notes is an MCP server listed in the public MCP registry as io.github.labaccessnow/netops-field-notes-mcp. Config drift, CIS/PCI checks, 802.1X diagnosis, certs inside configs, topology, change pre-flight. This page covers its container image (ghcr.io/labaccessnow/netops-field-notes-mcp:0.1.0).

### Is the NetOps Field Notes MCP server safe to use?

NetOps Field Notes scores 44 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the NetOps Field Notes MCP server expose?

NetOps Field Notes exposes 12 tools: explain_config_diff, check_config_compliance, diagnose_dot1x, lookup_ise_failure_code, find_certs_in_config, and 7 more. Their descriptions and schemas cost roughly 1,297 tokens of context every time the server is loaded.

### Is the NetOps Field Notes MCP server still maintained?

NetOps Field Notes is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the NetOps Field Notes MCP server under?

NetOps Field Notes declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- Repository: https://github.com/labaccessnow/netops-field-notes-mcp
- Website: https://netopsfieldnotes.com/
- Changelog RSS feed: https://verifymcp.io/servers/labaccessnow-netops-field-notes-mcp/ghcr-io-labaccessnow-netops-field-notes-mcp-0-1-0.xml
- Changelog JSON feed: https://verifymcp.io/servers/labaccessnow-netops-field-notes-mcp/ghcr-io-labaccessnow-netops-field-notes-mcp-0-1-0.json
- HTML version of this page: https://verifymcp.io/servers/labaccessnow-netops-field-notes-mcp/ghcr-io-labaccessnow-netops-field-notes-mcp-0-1-0