nomue Record Verifier MCP server

by licklider-ai·io.github.licklider-ai/nomue-verifier-mcp·v0.2.0-rc.1

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

A94/100grade A

What users say

No reviews yet

Safety scan

A94/100

Adoption

Growing

0 stars157 downloads/wk

Reviews

Nobody has reviewed nomue Record Verifier yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

scanner v0.1.5 · 2026-09-19 · same rubric, same numbers if you re-run it

no findings

Code scan6 source files scanned25/25
–Live reliabilityno gateway calls yet and no remote to proben/a
–Tool poisoningtools not inspected (local package is not executed); not countedn/a
Auth qualitylocal package, no credentials required12/15
Maintenancelast push 2 days ago15/15
Maintainer identityregistry namespace matches repository owner; GitHub account older than a year9/10

Overall 94/100. Components that don't apply are left out of the denominator. Any critical finding is an F.Rubric Appeal a finding JSON

Runs npx -y @licklider/nomue-verifier-mcp on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add nomue-verifier-mcp -- npx -y @licklider/nomue-verifier-mcp

Is nomue Record Verifier MCP server safe?: Yes, by our scan: it is graded A (94/100). Read the nomue Record Verifier safety report
How do I install nomue Record Verifier?: It runs on your machine. Copy the Claude Code, Claude Desktop or Cursor config from the install section.
Does nomue Record Verifier need an API key?: Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is nomue Record Verifier maintained?: The last commit was 3 days ago (2026-09-18). The latest release is v0.2.0-rc.1.