Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Lumi Verdict: check an x402 seller before paying

NPM · LUMI-VERDICT-MCP

One signed label before paying an x402 seller, from Lumi's test-buys on XRPL, Base and Stellar

Available components

+2 this week 69 Trust /100

Last scanned (18 minutes ago)

Scores higher than 36% of npm servers

Category Finance and Payments

Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Supply Chain Security99
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 32 of 127 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability70
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 425 tokens (~212/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

Unverified: 1 category

A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 30 Oct 26 +2
    • CVE-2023-54404 no longer affects this package ▲ security
    • Known CVEs: fail → pass ▲ security
  • 27 Oct 26 +15
    • Malware scan: unverified → pass ▲ security
  • 26 Oct 26 52

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 5 Nov 2026 · Analysed npm/lumi-verdict-mcp@0.1.0

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 127 packages
Packages resolved 127
Stale 31
No linked repository 1
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 2 exposed · ~425 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
lumi_check_free ~159

Free. The same label as lumi_verdict from Lumi's record (cached, no live contact with the seller), signed by Lumi: checks_passed, check_first, checks_failed or no_data, with reason codes and an evidence link. Of the URL, only the origin and path are sent; payTo and amount are sent if you pass them. Use lumi_verdict when you want the live check at call time.

NameTypeReqDescription
amountstring–Optional: the quoted price in USD, e.g. 0.01
payTostring–Optional: the payTo address in its 402 quote
urlstringyesThe x402 resource URL (or the seller's domain) you are about to pay

No output schema declared.

No examples provided.

lumi_verdict ~266

Check an x402 seller before you pay it. Pass the resource URL (or the seller's domain) you are about to pay, and optionally the payTo and USD amount from its 402 quote. Returns one label from Lumi Trades' own test-buys and checks: checks_passed (Delivered in recent checks), check_first (Check first), checks_failed (Recent checks failed) or no_data (Not enough data), with as-of date, conclusive test-buy count, last delivered and failed dates, reason codes, evidence and appeal links. label_live is the label after Lumi contacts the seller at call time (an unpaid request) and compares its quote, price, payTo and TLS with Lumi's record. Signed by Lumi. Costs $0.01 per call, paid from your wallet within the configured caps; with no wallet it returns the price quote and pays nothing. Paying Lumi never changes a result. Observations, not a guarantee.

NameTypeReqDescription
amountstring–Optional: the quoted price in USD, e.g. 0.01
payTostring–Optional: the payTo address in its 402 quote
urlstringyesThe x402 resource URL (or the seller's domain) you are about to pay

No output schema declared.

No examples provided.

Install

How do I install the Lumi Verdict: check an x402 seller before paying MCP server?

Lumi Verdict: check an x402 seller before paying runs locally as an npm package, launched with npx -y lumi-verdict-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · lumi-verdict-mcp

# add to Claude Code
claude mcp add cypher-osiris-lumi-verdict-mcp -- npx -y lumi-verdict-mcp
Common questions

What is the Lumi Verdict: check an x402 seller before paying MCP server?

Lumi Verdict: check an x402 seller before paying is an MCP server listed in the public MCP registry as io.github.cypher-osiris/lumi-verdict-mcp. One signed label before paying an x402 seller, from Lumi's test-buys on XRPL, Base and Stellar. This page covers its npm package (lumi-verdict-mcp).

Is the Lumi Verdict: check an x402 seller before paying MCP server safe to use?

Lumi Verdict: check an x402 seller before paying scores 69 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. 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 Lumi Verdict: check an x402 seller before paying MCP server expose?

Lumi Verdict: check an x402 seller before paying exposes 2 tools: lumi_verdict, lumi_check_free. Their descriptions and schemas cost roughly 425 tokens of context every time the server is loaded.

Is the Lumi Verdict: check an x402 seller before paying MCP server still maintained?

Lumi Verdict: check an x402 seller before paying is still listed as active in the MCP registry. We last reached this channel on 5 November 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 Lumi Verdict: check an x402 seller before paying MCP server under?

Lumi Verdict: check an x402 seller before paying declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.