nomue Record Verifier MCP release candidate is available

What is available

@licklider/nomue-verifier-mcp@0.2.0-rc.1 is publicly available on npm and registered as io.github.licklider-ai/nomue-verifier-mcp in the official MCP Registry under the display name nomue Record Verifier. It is a local stdio server with the method-neutral tool verify_nomue_record.

The server is a thin adapter around the exact @licklider/nomue-verifier@0.2.1-rc.1 npm package. It does not reimplement statistical or Protocol semantics and does not add a blanket verification verdict.

Add it to an MCP client

Claude Code can add the exact release candidate with one command:

claude mcp add nomue-verify -- npx --yes @licklider/nomue-verifier-mcp@0.2.0-rc.1

Other clients can use the same version-pinned server configuration:

{"mcpServers":{"nomue-verify":{"command":"npx","args":["--yes","@licklider/nomue-verifier-mcp@0.2.0-rc.1"]}}}

Or start the same exact package directly:

npx --yes @licklider/nomue-verifier-mcp@0.2.0-rc.1

The first npx launch may download npm dependencies. No account, API key, environment variable, or Licklider-hosted URL is required. Client configurations pin the exact release-candidate version rather than relying on a mutable npm tag.

One bounded Record verification tool

Use when a Record declares urn:nomue:bundle:itgc-guarantee:0.2.1-draft.1, represents independent two-group continuous outcomes using the two-sided Welch two-sample t procedure, and needs scoped structural, digest, admissibility, computability, or recomputation checks.

Do not use to calculate a Welch test from raw samples, select a method, judge scientific truth or causality, verify paired-t, Wilcoxon, Mann–Whitney, or interpret an unsupported bundle.

{"record_json":"{...complete nomue Record JSON text...}"}

record_json contains the complete Record as JSON text, not a parsed object. Preserving the original text keeps strict parsing, duplicate-member rejection, digest checks, and resource limits inside the verifier.

The first MCP text block preserves the verifier stdout from that invocation. Structured content carries the same parsed verifier artifact, while metadata preserves the verifier exit code and input/output digests. Transport success does not mean that every scoped check passed, and passing scoped checks do not establish overall scientific validity.

Replay independently with the npm verifier

Save the same Record JSON text as record.json, then run:

npx --yes @licklider/nomue-verifier@0.2.1-rc.1 verify ./record.json --format json-compact

Every substantive artifact field is independently reproducible. Separate verifier invocations intentionally create different top-level generated_attimestamps, so cross-invocation byte identity is not claimed. Byte preservation is exact within the MCP invocation.

Local-only Phase 1 boundary

After npm installs the package and its dependencies, verification runs locally and does not call a Licklider service. Release CI tests the stdio package path on Linux, macOS, and Windows with Node.js 20 and 22. It does not expose HTTP, authentication, logging, rate limiting, an SLA, or a management interface.

Release status and exact scope

The release candidate does not expand the Protocol support target. It verifies existing nomue Release 1 Welch Records only. Paired-t, Wilcoxon, Mann–Whitney, raw-data calculation, method selection, source-data truth, causality, and overall scientific correctness remain outside this tool's result.

See the MCP installation and result contract for the complete machine-readable boundary and replay instructions.