AIOps Field Notes
OCI · GHCR.IO/LABACCESSNOW/AIOPS-FIELD-NOTES-MCP:0.1.1
Audit an MCP config, price a model, size a GPU, explain network config drift. Key-free.
Available components
Last scanned (23 hours ago)
Scores higher than 93% of OCI servers
Category Security
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 & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 59 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability80
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 821 tokens (~117/item across 7 items; 7 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 Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 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.
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.
- 19 Oct 26 0
- Stability: 0.97 → pass security
- 18 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 15 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.
- 13 Oct 26 −2
- Stability: pass → 0.80 functional
- 12 Oct 26 +1
- Stability: 0.93 → pass security
- 9 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 90. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 7 Oct 26 −2
No change was recorded against any check on this day. Stability & Change Management went from 97 to 83.
- 4 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
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 4 Nov 2026 · Analysed oci/ghcr.io/labaccessnow/aiops-field-notes-mcp:0.1.1
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 →
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 →
audit_mcp_config ~127
Review an MCP client config before you trust it. Paste the JSON from .mcp.json, claude_desktop_config.json or any equivalent and it flags unpinned packages that auto-update, secrets written in plaintext, filesystem roots scoped to the whole home directory, shell entrypoints, privileged containers, credentials on the command line, unauthenticated or plain-HTTP remote servers, and database access that is not read-only — each with the fix. Nothing is read from disk; pass the text.
| Name | Type | Req | Description |
|---|---|---|---|
| config | string | yes | Contents of the MCP config file, as JSON text. |
No output schema declared.
No examples provided.
check_config_compliance ~102
Run a CIS/PCI starter pack over one network device config: telnet disabled, SSH enabled, no default SNMP community, remote logging, time sync, login banner, hashed credentials, a firewall or ACL, and idle timeout. Deterministic regex checks with framework references, so two reviewers get the same result.
| Name | Type | Req | Description |
|---|---|---|---|
| config | string | yes | The device config text. |
| vendor | string | – | Optional vendor hint; detected from the config when omitted. |
No output schema declared.
No examples provided.
check_vram_fit ~137
Work out whether an open-weights model fits on a given GPU. Takes parameter count in billions, quantisation bit width and context length; returns weights + KV cache + overhead in GB and which common cards (and Macs) have room.
| Name | Type | Req | Description |
|---|---|---|---|
| context_tokens | number | – | Context window you intend to use, in tokens. |
| params_b | number | yes | Parameter count in billions, e.g. 70 for a 70B model. |
| quant_bits | number | – | Bits per weight: 16 (fp16), 8 (int8/fp8), 5, 4 (Q4) are typical. |
No output schema declared.
No examples provided.
estimate_llm_cost ~146
Price a workload across current frontier and open-weights models. Give tokens per request and monthly request volume; returns cost per request and per month for every model, cheapest first, with the caveats that move the number (batch discounts, prompt caching, intro pricing that expires).
| Name | Type | Req | Description |
|---|---|---|---|
| filter | string | – | Optional substring to limit the table, e.g. 'claude' or 'gemini'. |
| input_tokens | number | yes | Input tokens per request (a typical chat turn is 1000-3000 with context). |
| output_tokens | number | yes | Output tokens per request (typically 200-800). |
| requests_per_month | number | yes | Requests per month. |
No output schema declared.
No examples provided.
explain_config_diff ~142
Explain what changed between two network device config snapshots, in plain English. Works on EdgeOS, MikroTik RouterOS, OPNsense, Cisco IOS-style and EdgeSwitch configs: strips volatile lines, groups changes by config section, and tags each with a risk level and why it matters (security, routing, access, connectivity). Deterministic — no model call, nothing leaves the machine.
| Name | Type | Req | Description |
|---|---|---|---|
| after | string | yes | The later config snapshot. |
| before | string | yes | The earlier config snapshot. |
| device | string | – | Optional device name, for the summary line. |
| vendor | string | – | Optional vendor hint; detected from the config when omitted. |
No output schema declared.
No examples provided.
latest_field_note ~72
The most recent This Week in AIOps episodes — what shipped in models, agents and MCP, and what it means for the systems you run. The only tool here that touches the network; it reads a public RSS feed.
| Name | Type | Req | Description |
|---|---|---|---|
| count | number | – | How many recent episodes to return (default 3). |
No output schema declared.
No examples provided.
lookup_mcp_server ~95
Look up an MCP server in the curated AIOps Field Notes directory: what it connects to, who maintains it, and whether it is a reference, vendor or community server. Search by name, capability or category. An unlisted server is not condemned — the answer says how to vet it yourself.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | – | Name, capability or category, e.g. 'postgres', 'browser', 'vendor'. |
No output schema declared.
No examples provided.
How do I install the AIOps Field Notes MCP server?
AIOps Field Notes runs locally as a container image, launched with docker run --rm -i ghcr.io/labaccessnow/aiops-field-notes-mcp:0.1.1. 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/aiops-field-notes-mcp:0.1.1
claude mcp add labaccessnow-aiops-field-notes-mcp -- docker run --rm -i ghcr.io/labaccessnow/aiops-field-notes-mcp:0.1.1
What is the AIOps Field Notes MCP server?
AIOps Field Notes is an MCP server listed in the public MCP registry as io.github.labaccessnow/aiops-field-notes-mcp. Audit an MCP config, price a model, size a GPU, explain network config drift. Key-free. This page covers its container image (ghcr.io/labaccessnow/aiops-field-notes-mcp:0.1.1).
Is the AIOps Field Notes MCP server safe to use?
AIOps Field Notes scores 55 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 AIOps Field Notes MCP server expose?
AIOps Field Notes exposes 7 tools: estimate_llm_cost, check_vram_fit, audit_mcp_config, lookup_mcp_server, explain_config_diff, and 2 more. Their descriptions and schemas cost roughly 821 tokens of context every time the server is loaded.
Is the AIOps Field Notes MCP server still maintained?
AIOps Field Notes is still listed as active in the MCP registry. We last reached this channel on 4 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 AIOps Field Notes MCP server under?
AIOps 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.