Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

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.

−6 this week 45 Trust /100

Last scanned (2 hours ago)

Scores higher than 64% of OCI servers

Category Security

Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Supply Chain Security0
  • No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
  • Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
  • Install-script risk not yet assessed.Unverified
  • Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
Provenance & Transparency19
Schema Quality & AI Usability66
  • AI-judged instruction clarity (good).Pass
  • 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. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage71
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 12 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 13 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass

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.

What we tested

Checks we ran (12)

  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (4)

These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Malware scan in Supply Chain Security (scores 0 for this)No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.
  • Known CVEs in Supply Chain Security (scores 0 for this)Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.
  • Install scripts in Supply Chain Security (scores 0 for this)Install-script risk not yet assessed.
  • Dependency health in Supply Chain Security (scores 0 for this)Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 6 Nov 26 −6
    • Source repository: pass → fail ▼ security
  • 1 Nov 26 +1
    • Stability: 0.97 → pass security
  • 31 Oct 26 −1
    • Stability: pass → 0.97 functional
  • 20 Oct 26 +1
    • Stability: 0.97 → pass security
  • 19 Oct 26 −1
    • Stability: pass → 0.97 functional
  • 17 Oct 26 +2
    • Stability: 0.87 → pass security
  • 16 Oct 26 +1

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

  • 14 Oct 26 −3
    • Stability: pass → 0.80 functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 6 Nov 2026 · Analysed oci/ghcr.io/labaccessnow/netops-field-notes-mcp:0.1.0

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem oci
Reason No attestation published

Background: How many MCP packages publish verified provenance →

MCP tools · 12 exposed · ~1,297 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
check_config_compliance ~99

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.

NameTypeReqDescription
configstringyes–
vendorstring––
NameTypeReqDescription
resultstringyes–

No examples provided.

check_tls_endpoint ~94

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.

NameTypeReqDescription
hoststringyes–
portinteger––
rolestring––
NameTypeReqDescription
resultstringyes–

No examples provided.

diagnose_dot1x ~134

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.

NameTypeReqDescription
radius_logstring––
supplicant_logstring––
switchport_configstring––
NameTypeReqDescription
resultstringyes–

No examples provided.

explain_config_diff ~117

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.

NameTypeReqDescription
afterstringyes–
beforestringyes–
devicestring––
vendorstring––
NameTypeReqDescription
resultstringyes–

No examples provided.

explain_firewall_change ~133

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.

NameTypeReqDescription
afterstringyes–
beforestringyes–
devicestring––
NameTypeReqDescription
resultstringyes–

No examples provided.

extract_device_facts ~92

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.

NameTypeReqDescription
configstringyes–
devicestring––
vendorstring––
NameTypeReqDescription
resultstringyes–

No examples provided.

find_certs_in_config ~122

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.

NameTypeReqDescription
configstringyes–
rolestring––
vendorstring––
NameTypeReqDescription
resultstringyes–

No examples provided.

infer_topology ~89

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.

NameTypeReqDescription
devicesarrayyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

latest_field_note ~63

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.

NameTypeReqDescription
countinteger––
NameTypeReqDescription
resultstringyes–

No examples provided.

lookup_ise_failure_code ~86

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.

NameTypeReqDescription
codestringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

preflight_change ~125

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.

NameTypeReqDescription
currentstringyes–
devicestring––
fleet–––
proposedstringyes–
vendorstring––
NameTypeReqDescription
resultstringyes–

No examples provided.

sanitize_config ~143

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.

NameTypeReqDescription
configstringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

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.

oci · ghcr.io/labaccessnow/netops-field-notes-mcp:0.1.0

# add to Claude Code
claude mcp add labaccessnow-netops-field-notes-mcp -- docker run --rm -i ghcr.io/labaccessnow/netops-field-notes-mcp:0.1.0
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 45 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 6 November 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.

What did VerifyMCP test on the NetOps Field Notes MCP server?

VerifyMCP ran 12 checks on NetOps Field Notes, covering Source repository, Provenance, License, Maintenance and 8 more. 4 items could not be completed, a gap on our side rather than a finding about NetOps Field Notes: Malware scan, Known CVEs, Install scripts and Dependency health. One category scores 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to a container image, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.