Docs

Use nomue Record verification over MCP (earlier version)

Archived nomue guide: the public local stdio server, when its method-neutral Record tool applied, and how a Release 1 Welch result was replayed with the independent verifier.

This is a nomue reference for the named artifact and version. Go to SciGround documentation.

The public MCP surface (0.2.0-rc.1)

The exact @licklider/nomue-verifier-mcp@0.2.0-rc.1 release candidate was published on npm and in the official MCP Registry as nomue Record Verifier. It exposed the method-neutral verify_nomue_record tool over local stdio, limited to Release 1 Welch Record verification, delegated to @licklider/nomue-verifier@0.2.1-rc.1, and passed package-path CI across Linux, macOS, and Windows. It required no account, API key, environment variable, or Licklider-hosted service; the first npx launch could download npm dependencies, after which verification ran locally. It supported stdio only: it was not a hosted HTTP endpoint and did 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; support was limited to 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.

nomue was the earlier version of SciGround. This archived guide describes the named nomue releases and packages only; for current verification, see https://www.licklider.ai/docs/.

Adding the server to an MCP client

Claude Code registered the server with the first command below. Other clients used the same exact prerelease version in their MCP configuration so later npm tag changes could not 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"]}}}

The first npx launch may download the package and its dependencies. No account, API key, URL, or environment variable is required. After installation, verification itself is local.

Windows command-shim fallback

This equivalent configuration applied only when the MCP client did 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 the MCP tool applied

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 the MCP tool did not apply

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...}"}

record_json is JSON text, not a parsed object. Preserve the original text so strict parsing, duplicate-member rejection, digest checks, and resource limits remain inside the verifier.

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

CodeMeaning
0A report exists and every applicable scoped check outcome is pass.
2A scoped check failed, or parsing or canonicalization was refused.
3Routing failed or the declared bundle is unsupported; no report exists.
4The verifier refused safely because a resource limit was reached.
5Internal verifier refusal.

Exit codes are routing and process signals, not overall scientific verdicts.

Replay independently with the verifier

The same record_json text, saved as record.json, could be replayed with the exact verifier dependency:

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

The substantive artifact is reproducible field-for-field. Each separate verifier invocation intentionally creates a new top-level generated_at timestamp, so two independent invocations are not honestly byte-identical; byte preservation is exact within the MCP invocation.

Package, registry, and source authority

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.

  • This is an archived nomue (earlier version) guide. nomue’s verification capabilities are now part of SciGround.
  • The exact release candidate was started with npx --yes @licklider/nomue-verifier-mcp@0.2.0-rc.1.
  • The sole method-neutral tool was verify_nomue_record; its input field record_json contains complete Record JSON text, not a parsed object. Its supported scientific scope was 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 delegated 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 was local stdio only. It had no account, API key, hosted HTTP endpoint, or runtime call to a Licklider service.

Markdown version of this page