Use nomue Record verification over MCP

Current public MCP surface

The exact @licklider/nomue-verifier-mcp@0.2.0-rc.1 release candidate is public on npm and in the official MCP Registry as nomue Record Verifier. It exposes the method-neutral verify_nomue_record tool over local stdio; the current supported scientific scope remains Release 1 Welch Record verification. It delegates to @licklider/nomue-verifier@0.2.1-rc.1 and has passing package-path CI across Linux, macOS, and Windows. It requires no account, API key, environment variable, or Licklider-hosted service. The first npx launch may download npm dependencies; after installation, verification runs locally. This release candidate supports stdio only: it is not a hosted HTTP endpoint and does not add paired-t, Wilcoxon, Mann–Whitney, method selection, raw-sample calculation, or an overall scientific verdict.

• Display name: nomue Record Verifier.
• Client configuration name: nomue-verify.
• Package: @licklider/nomue-verifier-mcp@0.2.0-rc.1, published under the rc dist-tag.
• Official MCP Registry name: io.github.licklider-ai/nomue-verifier-mcp.
• Transport: local stdio; no remote URL or environment variables.
• Method-neutral tool: verify_nomue_record; current support remains the Release 1 Welch bundle.
• Verifier dependency: exact @licklider/nomue-verifier@0.2.1-rc.1.
• Tested package path: Linux, macOS, Windows with Node.js 20 and 22.
• The mutable npm rc tag is not a stable-release claim. Client configurations pin 0.2.0-rc.1 exactly.

Add the server to an MCP client

Claude Code can register the server with the first command below. Other clients can use the same exact prerelease version in their MCP configuration so later npm tag changes cannot silently change the installed server.

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

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

Windows command-shim fallback

Use this equivalent configuration only when the MCP client does not resolve the npm command shim directly:

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

When to use the MCP 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.

• You already have the complete Record as JSON text.
• The Record declares the exact public Release 1 interpretation bundle.
• You need the same scoped report and refusal semantics as the independently runnable npm verifier.
• You will preserve the exact exit code and inspect the machine-readable artifact rather than infer a verdict from transport success.

When not to use the MCP tool

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.

• Do not pass only sample arrays, a spreadsheet, or prose and expect the tool to create a Record.
• Do not silently substitute Welch for paired or rank-based procedures.
• Do not treat a transport-successful tool call as evidence that every scoped check passed.
• Do not treat every passing scoped check as overall scientific validity.

Pass complete Record JSON text

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

Result and non-claim contract

• The first MCP text content block is the exact stdout emitted by the pinned verifier in that same invocation, including its final newline.
• structuredContent contains the same parsed verifier artifact; the adapter does not add a success verdict.
• MCP metadata carries the verifier exit code, exact input and stdout SHA-256 digests, verifier package identity, and the verifier-generated generated_at field.
• Codes 2 through 5 remain normal machine-readable verifier artifacts; only an adapter failure is an MCP tool error.
• There is no blanket VERIFIED field. Read every scoped result, its version and reason codes, next actions, and guarantee_boundary.

Preserved verifier exit codes

Replay independently with the verifier

Save the same record_json text as record.json and run the exact verifier dependency:

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

Package, registry, and source authority

• nomue MCP on npm
• Official MCP Registry entry
• Public nomue MCP source
• Cross-platform release CI
• Official Registry publication evidence
• Independent verifier guide

Flat summary for LLMs

This llms.txt-style summary is intentionally repetitive. Use the linked Markdown page when a flat, low-markup representation is preferable.

• Start the exact release candidate with npx --yes @licklider/nomue-verifier-mcp@0.2.0-rc.1.
• The sole method-neutral tool is verify_nomue_record; its input field record_json contains complete Record JSON text, not a parsed object. The current supported scientific scope remains the Release 1 Welch bundle.
• 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.
• The adapter delegates verification semantics to the exact @licklider/nomue-verifier@0.2.1-rc.1 package.
• The first MCP text block preserves the pinned verifier stdout from the same invocation, while structuredContent carries the same parsed artifact without a new verdict.
• Read scoped results, check versions, reason codes, guarantee_boundary, and next actions; never emit a blanket VERIFIED claim.
• This release candidate is local stdio only. It has no account, API key, hosted HTTP endpoint, or runtime call to a Licklider service.

Markdown version of this page