# nomue Record Verifier (npm · @licklider/nomue-verifier-mcp)

Local verification of nomue Protocol Records; current release supports the Release 1 Welch bundle.

- Trust score: 88/100 (high trust)
- Change this week: +13
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-21

## Components

- npm · `@licklider/nomue-verifier-mcp`: 88/100 (this document), [markdown](https://verifymcp.io/servers/licklider-ai-nomue-verifier-mcp/licklider-nomue-verifier-mcp.md), [page](https://verifymcp.io/servers/licklider-ai-nomue-verifier-mcp/licklider-nomue-verifier-mcp)

## Channel facts

- Registry: `npm`
- Package: `@licklider/nomue-verifier-mcp`
- Version: `0.2.0-rc.1`
- 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-21.

- **Supply Chain Security**: 99/100
  - No malware found by supply-chain analysis.
  - Known CVEs were checked across the 272 of 274 dependencies we could resolve, so this covers what we could see, not the whole tree.
  - No install/post-install scripts declared.
  - Dependency health was assessed across the 272 of 274 dependencies we could resolve, so this covers what we could see, not the whole tree.
- **Provenance & Transparency**: 100/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to licklider-ai/nomue-verifier-mcp).
  - Clear OSI-approved license (Apache-2.0).
  - Actively maintained (last published 3 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 71/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 57/100
  - Stability observed for 17 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% 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 1 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 2 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.

## Install

### 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.

### Claude

```bash
claude mcp add licklider-ai-nomue-verifier-mcp -- npx -y @licklider/nomue-verifier-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "licklider-ai-nomue-verifier-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@licklider/nomue-verifier-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "licklider-ai-nomue-verifier-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@licklider/nomue-verifier-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add licklider-ai-nomue-verifier-mcp -- npx -y @licklider/nomue-verifier-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "licklider-ai-nomue-verifier-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@licklider/nomue-verifier-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add licklider-ai-nomue-verifier-mcp --command npx --arg -y --arg @licklider/nomue-verifier-mcp
```

### Hermes

```yaml
mcp_servers:
  licklider-ai-nomue-verifier-mcp:
    command: "npx"
    args: ["-y", "@licklider/nomue-verifier-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "licklider-ai-nomue-verifier-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@licklider/nomue-verifier-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add licklider-ai-nomue-verifier-mcp -t stdio -c npx -a -y @licklider/nomue-verifier-mcp
```

### Other

```json
{
  "mcpServers": {
    "licklider-ai-nomue-verifier-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@licklider/nomue-verifier-mcp"
      ]
    }
  }
}
```

## 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-20 (score 88, +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.

### 2026-09-18 (score 87, +11)

- [security improvement] Provenance: fail → pass
- [security] The attested source repository moved: licklider-ai/nomue-verifier-mcp
- [functional] Package version: 0.2.0-rc.0 → 0.2.0-rc.1

### 2026-09-16 (score 76, +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.

### 2026-09-14 (score 75, +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.

### 2026-09-12 (score 74, +4)

- [functional improvement] Stability: unverified → 0.27

### 2026-09-05 (score 70, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-09-04 (score 55)

First indexed and scored.

## MCP tools (1)

### `verify_nomue_record` (~264 tokens)

Verify nomue Record

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.

Input parameters:

- `record_json` (string, required): 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…

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/licklider-ai-nomue-verifier-mcp/licklider-nomue-verifier-mcp#diagnostics

## Score history

- 2026-09-21: 88
- 2026-09-20: 88
- 2026-09-19: 87
- 2026-09-18: 87
- 2026-09-17: 76
- 2026-09-16: 76
- 2026-09-15: 75
- 2026-09-14: 75
- 2026-09-13: 74
- 2026-09-12: 74
- 2026-09-11: 70
- 2026-09-10: 70
- 2026-09-09: 70
- 2026-09-08: 70
- 2026-09-07: 70
- 2026-09-06: 70
- 2026-09-05: 70
- 2026-09-04: 55

## Common questions

### 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.

## Links

- npm package: https://www.npmjs.com/package/@licklider/nomue-verifier-mcp
- Socket report: https://socket.dev/npm/package/@licklider/nomue-verifier-mcp
- Repository: https://github.com/licklider-ai/nomue-verifier-mcp
- Changelog RSS feed: https://verifymcp.io/servers/licklider-ai-nomue-verifier-mcp/licklider-nomue-verifier-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/licklider-ai-nomue-verifier-mcp/licklider-nomue-verifier-mcp.json
- HTML version of this page: https://verifymcp.io/servers/licklider-ai-nomue-verifier-mcp/licklider-nomue-verifier-mcp