nomue Record Verifier
NPM · @LICKLIDER/NOMUE-VERIFIER-MCP
Local verification of nomue Protocol Records; current release supports the Release 1 Welch bundle.
Available components
Last scanned (13 hours ago)
Scores higher than 91% of npm servers
Category Testing and QA
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 Security82
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects @modelcontextprotocol/server 2.0.0, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- Dependency health was assessed across the 272 of 274 dependencies we could resolve, so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to licklider-ai/nomue-verifier-mcp). View diagnostics → Pass
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 49 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability71
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 316 tokens (~316/item across 1 items; 1 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 Management80
- Stability observed for 24 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 2 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
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
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 →
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 −2
- Stability: pass → 0.80 functional
- 28 Oct 26 0
- GHSA-f897-62hf-6gxq affects this package: high ▼ security
- 25 Oct 26 0
- Stability: 0.97 → pass security
- 24 Oct 26 0
- CVE-2023-54404 affects this package: high ▼ security
- Stability: pass → 0.97 functional
- 21 Oct 26 −5
- CVE-2026-111771 affects this package: high ▼ security
- CVE-2026-111770 affects this package: high ▼ security
- CVE-2026-111768 affects this package: high ▼ security
- Known CVEs: partial → fail ▼ security
- 18 Oct 26 0
- Stability: 0.97 → pass security
- 17 Oct 26 +2
No change was recorded against any check on this day. Supply Chain Security went from 95 to 99. Other categories moved too: Stability & Change Management rose 4.
- 16 Oct 26 −1
No change was recorded against any check on this day. Supply Chain Security went from 99 to 95. Other categories moved too: Stability & Change Management rose 3.
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 npm/@licklider/nomue-verifier-mcp@0.2.0-rc.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | licklider-ai/nomue-verifier-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/licklider-ai/nomue-verifier-mcp/.github/workflows/publish-npm.yml@refs/heads/main |
| Rekor log index | 2882602902 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:034acaa5d893e28e3570737f5168b7614574ad97a3b15b52ec645bcd64710dc2b53f63fd1516378afe3777a5e5678070063fcf7142956f5853beb1960 |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 5 findings
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-46jr-4wx8-v453 | CVE-2026-111768 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
| GHSA-f897-62hf-6gxq | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes | |
| GHSA-jm63-cq47-j5jp | CVE-2026-111770 | high | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:H | yes |
| GHSA-rvq5-wwqv-78pq | CVE-2026-111771 | medium | CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N | yes |
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 272 packages
| Packages resolved | 272 |
|---|---|
| Stale | 11 |
| Tree resolution | Partial |
The dependency tree was only partially resolved, so these counts may be incomplete.
Background: SBOMs and build attestations, explained →
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 →
verify_nomue_record Verify nomue Record ~264
Experimental release-candidate tool for issuer-independent local verification of a complete nomue Protocol Record under an explicitly supported interpretation bundle. Use when a Record declares a supported bundle. The current release supports urn:nomue:bundle:itgc-guarantee:0.2.1-draft.1 for independent two-group continuous outcomes using the two-sided Welch two-sample t procedure and performs scoped structural, digest, admissibility, computability, or recomputation checks. Do not use to calculate a statistical method from raw samples, select a method, judge scientific truth or causality, or interpret an unsupported bundle. The current release does not support paired-t, Wilcoxon, Mann-Whitney, or other unregistered methods. The returned artifact is the unmodified verifier report or refusal; it contains no blanket VERIFIED result. Inspect each scoped check, version, reason code, and guarantee boundary. After a failure or refusal, use the exact reason codes to request a corrected or supported Record; do not silently select another statistical method.
| Name | Type | Req | Description |
|---|---|---|---|
| record_json | string | yes | The complete nomue Record as JSON text. Pass the original text, including an empty or malformed candidate, so strict parsing, duplicate-member rejection, digest verification, and resource limits rema… |
No output schema declared.
No examples provided.
How do I install the nomue Record Verifier MCP server?
nomue Record Verifier runs locally as an npm package, launched with npx -y @licklider/nomue-verifier-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @licklider/nomue-verifier-mcp
claude mcp add licklider-ai-nomue-verifier-mcp -- npx -y @licklider/nomue-verifier-mcp
What is the nomue Record Verifier MCP server?
nomue Record Verifier is an MCP server listed in the public MCP registry as io.github.licklider-ai/nomue-verifier-mcp. Local verification of nomue Protocol Records; current release supports the Release 1 Welch bundle. This page covers its npm package (@licklider/nomue-verifier-mcp).
Is the nomue Record Verifier MCP server safe to use?
nomue Record Verifier scores 87 out of 100 on VerifyMCP. We recorded 5 known advisories against it as of 6 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 nomue Record Verifier MCP server expose?
nomue Record Verifier exposes 1 tool: verify_nomue_record. Their descriptions and schemas cost roughly 264 tokens of context every time the server is loaded.
Is the nomue Record Verifier MCP server still maintained?
nomue Record Verifier 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 nomue Record Verifier MCP server under?
nomue Record Verifier declares the Apache-2.0 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 nomue Record Verifier MCP server?
VerifyMCP ran 16 checks on nomue Record Verifier, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.