# SecOps Field Notes (oci · ghcr.io/labaccessnow/secops-field-notes-mcp:0.1.0) CVSS scoring, IOC extraction, email header triage, hash/JWT/timestamp decoding, CISA KEV lookup. - Trust score: 47/100 (low) - Change this week: +6 - Registry status: active - Liveness: live - Owner verified: no - Last scored: 2026-09-20 ## Components - oci · `ghcr.io/labaccessnow/secops-field-notes-mcp:0.1.0`: 47/100 (this document), [markdown](https://verifymcp.io/servers/labaccessnow-secops-field-notes-mcp/ghcr-io-labaccessnow-secops-field-notes-mcp-0-1-0.md), [page](https://verifymcp.io/servers/labaccessnow-secops-field-notes-mcp/ghcr-io-labaccessnow-secops-field-notes-mcp-0-1-0) ## Channel facts - Registry: `oci` - Package: `ghcr.io/labaccessnow/secops-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-20. - **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 13 days ago). - Disclosure check failed: no security disclosure policy was found in the source repository. - **Schema Quality & AI Usability**: 81/100 - AI-judged instruction clarity (excellent). - Tool/resource definitions use about 920 tokens (~92/item across 10 items; 10 tools + 0 resources), lean. - Usage-examples check failed: none of the tools include examples. - **Stability & Change Management**: 47/100 - Stability observed for 14 of 30 days with no destabilising changes; credit accrues until the full window elapses. - **Tool Coverage**: 88/100 - 100% of tools have a non-trivial description (not blank, and not just the tool's name). - 64% of tool parameters carry a description. - **Tool Safety**: 100/100 - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured. - We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation. - An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it. - **Capabilities**: 100/100 - Implements a supported MCP spec version (2025-11-25); the latest is 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 SecOps Field Notes MCP server? SecOps Field Notes runs locally as a container image, launched with docker run --rm -i ghcr.io/labaccessnow/secops-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-secops-field-notes-mcp -- docker run --rm -i ghcr.io/labaccessnow/secops-field-notes-mcp:0.1.0 ``` ### Cursor ```json { "mcpServers": { "labaccessnow-secops-field-notes-mcp": { "command": "docker", "args": [ "run", "--rm", "-i", "ghcr.io/labaccessnow/secops-field-notes-mcp:0.1.0" ] } } } ``` ### VS Code ```json { "servers": { "labaccessnow-secops-field-notes-mcp": { "command": "docker", "args": [ "run", "--rm", "-i", "ghcr.io/labaccessnow/secops-field-notes-mcp:0.1.0" ] } } } ``` ### Codex ```bash codex mcp add labaccessnow-secops-field-notes-mcp -- docker run --rm -i ghcr.io/labaccessnow/secops-field-notes-mcp:0.1.0 ``` ### opencode ```json { "$schema": "https://opencode.ai/config.json", "mcp": { "labaccessnow-secops-field-notes-mcp": { "type": "local", "command": [ "docker", "run", "--rm", "-i", "ghcr.io/labaccessnow/secops-field-notes-mcp:0.1.0" ], "enabled": true } } } ``` ### Hermes ```yaml mcp_servers: labaccessnow-secops-field-notes-mcp: command: "docker" args: ["run", "--rm", "-i", "ghcr.io/labaccessnow/secops-field-notes-mcp:0.1.0"] ``` ### Netclaw ```json { "McpServers": { "labaccessnow-secops-field-notes-mcp": { "Transport": "stdio", "Command": "docker", "Arguments": [ "run", "--rm", "-i", "ghcr.io/labaccessnow/secops-field-notes-mcp:0.1.0" ] } } } ``` ### Other ```json { "mcpServers": { "labaccessnow-secops-field-notes-mcp": { "command": "docker", "args": [ "run", "--rm", "-i", "ghcr.io/labaccessnow/secops-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-19 (score 47, +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 46, +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 45, +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 44, +3) - [functional improvement] Stability: unverified → 0.27 ### 2026-09-06 (score 41) First indexed and scored. ## MCP tools (10) ### `cvss_score` (~143 tokens) Score a vulnerability with CVSS v3.1, exactly as the FIRST specification computes it. Give a vector string (CVSS:3.1/AV:N/AC:L/...) or the eight base metrics; returns the base score, severity band, normalised vector, and the impact/exploitability sub-scores. Input parameters: - `metrics` (object): Alternative to vector: {AV, AC, PR, UI, S, C, I, A} with single-letter values. - `vector` (string): e.g. CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H ### `extract_iocs` (~125 tokens) Pull every indicator out of a blob of text — a report, an alert, a mail — and return them sectioned and defanged, ready for a ticket: IPv4, IPv6, domains, URLs, emails, CVE ids, MD5/SHA-1/SHA-256. Defanged input (hxxp, [.], [at]) is refanged first, so pasting from another report works. Filenames are not mistaken for domains. Input parameters: - `defanged` (boolean): Defang the output (default true). - `text` (string, required) ### `defang_text` (~76 tokens) Defang or refang indicators in text: http→hxxp[://], dots→[.], @→[at], and back. Use before pasting live URLs into anything that auto-links. Input parameters: - `mode` (string): 'defang' (default) or 'refang'. - `text` (string, required) ### `analyze_email_headers` (~94 tokens) Phishing triage on raw email headers: the Received chain in chronological order with per-hop delay, the originating public IP, SPF/DKIM/DMARC verdicts, and the mismatches that matter — From vs Return-Path domain, Reply-To pointing elsewhere (BEC), authentication failures, hops timestamped before the previous one. Input parameters: - `headers` (string, required): The raw message source, or at least the header block. ### `identify_hash` (~73 tokens) Identify a hash by shape: bcrypt, Argon2, yescrypt, the Unix crypt family, LM:NT pairs, and hex-length MD5/NTLM, SHA-1, SHA-224/256/384/512 — with what that shape implies for cracking or reuse. Input parameters: - `hash` (string, required) ### `decode_jwt` (~73 tokens) Decode a JWT's header and payload (no verification — it says so), show iat/nbf/exp as dates, and flag alg:none, missing alg, expiry, tokens that never expire, and long-lived tokens. Input parameters: - `token` (string, required): The token, with or without a 'Bearer ' prefix. ### `convert_timestamp` (~68 tokens) Turn any timestamp into every form an investigation needs: Unix epoch in s/ms/µs (detected by digit count), Windows FILETIME, ISO 8601, RFC 2822 dates, or 'now' — with UTC, weekday and relative time. Input parameters: - `value` (string, required) ### `decode_layers` (~116 tokens) Peel a layered payload: run a chain of operations (base64_decode, base64_encode, hex_decode, hex_encode, url_decode, url_encode, html_decode, rot13) and see every intermediate result. Default chain is a single base64_decode. Stops at the first step that fails and says which. Input parameters: - `input` (string, required) - `ops` (array): Ops in order, from: base64_decode, base64_encode, hex_decode, hex_encode, url_decode, url_encode, html_decode, rot13 ### `lookup_kev` (~96 tokens) Is this CVE exploited in the wild? Checks CISA's Known Exploited Vulnerabilities catalog: date added, the federal due date, whether it is used in ransomware campaigns, and the required action. Accepts any text containing CVE ids. The only tool here that touches the network; the catalog is cached for an hour. Input parameters: - `cves` (string, required): One or more CVE ids, or text containing them. ### `latest_field_note` (~56 tokens) The most recent This Week in Security episodes — what got exploited, what to patch, what it means for the systems you defend. Reads a public RSS feed. Input parameters: - `count` (number): How many recent episodes (default 3). ## Diagnostics Captured diagnostic sections: Provenance. The full working is on the page: https://verifymcp.io/servers/labaccessnow-secops-field-notes-mcp/ghcr-io-labaccessnow-secops-field-notes-mcp-0-1-0#diagnostics ## Score history - 2026-09-20: 47 - 2026-09-19: 47 - 2026-09-18: 46 - 2026-09-17: 46 - 2026-09-16: 45 - 2026-09-15: 45 - 2026-09-14: 44 - 2026-09-13: 41 - 2026-09-12: 41 - 2026-09-11: 41 - 2026-09-10: 41 - 2026-09-09: 41 - 2026-09-08: 41 - 2026-09-07: 41 - 2026-09-06: 41 ## Common questions ### What is the SecOps Field Notes MCP server? SecOps Field Notes is an MCP server listed in the public MCP registry as io.github.labaccessnow/secops-field-notes-mcp. CVSS scoring, IOC extraction, email header triage, hash/JWT/timestamp decoding, CISA KEV lookup. This page covers its container image (ghcr.io/labaccessnow/secops-field-notes-mcp:0.1.0). ### Is the SecOps Field Notes MCP server safe to use? SecOps Field Notes scores 47 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 SecOps Field Notes MCP server expose? SecOps Field Notes exposes 10 tools: cvss_score, extract_iocs, defang_text, analyze_email_headers, identify_hash, and 5 more. Their descriptions and schemas cost roughly 920 tokens of context every time the server is loaded. ### Is the SecOps Field Notes MCP server still maintained? SecOps Field Notes is still listed as active in the MCP registry. We last reached this channel on 20 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 SecOps Field Notes MCP server under? SecOps 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/secops-field-notes-mcp - Website: https://secopsfieldnotes.com/ - Changelog RSS feed: https://verifymcp.io/servers/labaccessnow-secops-field-notes-mcp/ghcr-io-labaccessnow-secops-field-notes-mcp-0-1-0.xml - Changelog JSON feed: https://verifymcp.io/servers/labaccessnow-secops-field-notes-mcp/ghcr-io-labaccessnow-secops-field-notes-mcp-0-1-0.json - HTML version of this page: https://verifymcp.io/servers/labaccessnow-secops-field-notes-mcp/ghcr-io-labaccessnow-secops-field-notes-mcp-0-1-0