nomue Record Verifier
NPM · @LICKLIDER/NOMUE-VERIFIER-MCP · SCANNED SEP 21
Local verification of nomue Protocol Records; current release supports the Release 1 Welch bundle.
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 Security99
- No malware found by supply-chain analysis.Pass
- Known CVEs were checked across the 272 of 274 dependencies we could resolve, so this covers what we could see, not the whole tree.Partial
- 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 3 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 Management57
- Stability observed for 17 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
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
{
"mcpServers": {
"licklider-ai-nomue-verifier-mcp": {
"command": "npx",
"args": [
"-y",
"@licklider/nomue-verifier-mcp"
]
}
}
} {
"servers": {
"licklider-ai-nomue-verifier-mcp": {
"command": "npx",
"args": [
"-y",
"@licklider/nomue-verifier-mcp"
]
}
}
} codex mcp add licklider-ai-nomue-verifier-mcp -- npx -y @licklider/nomue-verifier-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"licklider-ai-nomue-verifier-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"@licklider/nomue-verifier-mcp"
],
"enabled": true
}
}
} openclaw mcp add licklider-ai-nomue-verifier-mcp --command npx --arg -y --arg @licklider/nomue-verifier-mcp
mcp_servers:
licklider-ai-nomue-verifier-mcp:
command: "npx"
args: ["-y", "@licklider/nomue-verifier-mcp"] {
"McpServers": {
"licklider-ai-nomue-verifier-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@licklider/nomue-verifier-mcp"
]
}
}
} assistant mcp add licklider-ai-nomue-verifier-mcp -t stdio -c npx -a -y @licklider/nomue-verifier-mcp
{
"mcpServers": {
"licklider-ai-nomue-verifier-mcp": {
"command": "npx",
"args": [
"-y",
"@licklider/nomue-verifier-mcp"
]
}
}
} 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.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +11
- Provenance: fail → pass ▲ security
- The attested source repository moved: licklider-ai/nomue-verifier-mcp security
- Package version: 0.2.0-rc.0 → 0.2.0-rc.1 functional
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 +4
- Stability: unverified → 0.27 ▲ functional
- 5 Sept 26 +15
- Malware scan: unverified → pass ▲ security
- 4 Sept 26 55
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 21 Sept 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 | https://slsa.dev/provenance/v1 |
| Subject digest | sha512:034acaa5d893e28e3570737f5168b7614574ad97a3b15b52ec645bcd64710dc2b53f63fd1516378afe3777a5e5678070063fcf7142956f5853beb1960 |
Background: How many MCP packages publish verified provenance →
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.
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 88 out of 100 on VerifyMCP. 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 21 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 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.