SecOps Field Notes
OCI · GHCR.IO/LABACCESSNOW/SECOPS-FIELD-NOTES-MCP:0.1.0 · SCANNED SEP 20
CVSS scoring, IOC extraction, email header triage, hash/JWT/timestamp decoding, CISA KEV lookup.
Available components
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
- Malware scan not yet available for this package.Unverified
- 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.Unverified
- Install-script risk not yet assessed.Unverified
- 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.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 13 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability81
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 920 tokens (~92/item across 10 items; 10 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management47
- Stability observed for 14 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage88
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 64% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 10 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.
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.
oci · ghcr.io/labaccessnow/secops-field-notes-mcp:0.1.0
claude mcp add labaccessnow-secops-field-notes-mcp -- docker run --rm -i ghcr.io/labaccessnow/secops-field-notes-mcp:0.1.0
{
"mcpServers": {
"labaccessnow-secops-field-notes-mcp": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"ghcr.io/labaccessnow/secops-field-notes-mcp:0.1.0"
]
}
}
} {
"servers": {
"labaccessnow-secops-field-notes-mcp": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"ghcr.io/labaccessnow/secops-field-notes-mcp:0.1.0"
]
}
}
} codex mcp add labaccessnow-secops-field-notes-mcp -- docker run --rm -i ghcr.io/labaccessnow/secops-field-notes-mcp:0.1.0
{
"$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
}
}
} mcp_servers:
labaccessnow-secops-field-notes-mcp:
command: "docker"
args: ["run", "--rm", "-i", "ghcr.io/labaccessnow/secops-field-notes-mcp:0.1.0"] {
"McpServers": {
"labaccessnow-secops-field-notes-mcp": {
"Transport": "stdio",
"Command": "docker",
"Arguments": [
"run",
"--rm",
"-i",
"ghcr.io/labaccessnow/secops-field-notes-mcp:0.1.0"
]
}
}
} {
"mcpServers": {
"labaccessnow-secops-field-notes-mcp": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"ghcr.io/labaccessnow/secops-field-notes-mcp:0.1.0"
]
}
}
} 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 Sept 26 +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.
- 17 Sept 26 +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.
- 15 Sept 26 +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.
- 14 Sept 26 +3
- Stability: unverified → 0.27 ▲ functional
- 6 Sept 26 41
First indexed and scored.
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 20 Sept 2026 · Analysed oci/ghcr.io/labaccessnow/secops-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 →
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 →
analyze_email_headers ~94
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.
| Name | Type | Req | Description |
|---|---|---|---|
| headers | string | yes | The raw message source, or at least the header block. |
No output schema declared.
No examples provided.
convert_timestamp ~68
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.
| Name | Type | Req | Description |
|---|---|---|---|
| value | string | yes | – |
No output schema declared.
No examples provided.
cvss_score ~143
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 |
No output schema declared.
No examples provided.
decode_jwt ~73
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.
| Name | Type | Req | Description |
|---|---|---|---|
| token | string | yes | The token, with or without a 'Bearer ' prefix. |
No output schema declared.
No examples provided.
decode_layers ~116
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.
| Name | Type | Req | Description |
|---|---|---|---|
| input | string | yes | – |
| ops | array | – | Ops in order, from: base64_decode, base64_encode, hex_decode, hex_encode, url_decode, url_encode, html_decode, rot13 |
No output schema declared.
No examples provided.
defang_text ~76
Defang or refang indicators in text: http→hxxp[://], dots→[.], @→[at], and back. Use before pasting live URLs into anything that auto-links.
| Name | Type | Req | Description |
|---|---|---|---|
| mode | string | – | 'defang' (default) or 'refang'. |
| text | string | yes | – |
No output schema declared.
No examples provided.
extract_iocs ~125
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.
| Name | Type | Req | Description |
|---|---|---|---|
| defanged | boolean | – | Defang the output (default true). |
| text | string | yes | – |
No output schema declared.
No examples provided.
identify_hash ~73
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.
| Name | Type | Req | Description |
|---|---|---|---|
| hash | string | yes | – |
No output schema declared.
No examples provided.
latest_field_note ~56
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.
| Name | Type | Req | Description |
|---|---|---|---|
| count | number | – | How many recent episodes (default 3). |
No output schema declared.
No examples provided.
lookup_kev ~96
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.
| Name | Type | Req | Description |
|---|---|---|---|
| cves | string | yes | One or more CVE ids, or text containing them. |
No output schema declared.
No examples provided.
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.