MCP.Market

Lumière PayCheck MCP server

online · 100% uptime
by Book0fEli·io.github.Book0fEli/paycheck·v1.8.1

Check any x402 endpoint before your AI agent pays it: trust grade, verdict, and hijack checks.

A91/100grade A
What users say
No reviews yet
Be the first
Safety scan
A91/100

not scanned yet

Adoption
Growing

0 stars

Reviews

Write one

Nobody has reviewed Lumière PayCheck yet.

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

Lumière PayCheck tools

Tool list not cached yet. `describe` through the gateway fetches it live.

Not scanned yet. New listings are scanned within a day or two of arriving.

How Lumière PayCheck compares

Against every graded AI and agents MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
91/100
higher than 88% of 4,460 AI and agents servers
Uptime
100%
of our recent checks; the typical remote AI and agents server answers 100%
Response time
386 ms
faster than 36% of 2,331 AI and agents servers

Release history: 3 versions in the registry since 2026-09-30, latest 2026-10-18, typically one every 13 days.

Install Lumière PayCheck in Claude Code, Cursor or VS Code

claude mcp add --transport http paycheck https://lumierepaycheck.org/mcp?plans=1
Add to Cursor

What the publisher says

From the Lumière PayCheck repository's README, as published. We do not edit it. Read it on GitHub

Lumière PayCheck

Check an x402 endpoint before your agent pays it.

AI agents now pay for APIs on their own with x402: an endpoint answers 402 Payment Required with a price, the agent pays in USDC, and gets the data. Nothing in that flow tells the agent whether the endpoint works, whether the price is right, or whether the payout wallet is the real one.

Lumière PayCheck answers those questions. It monitors every endpoint listed in the x402 Bazaar, grades each one, and gives your agent a plain verdict: proceed, caution, or avoid.

🌐 Live: https://lumierepaycheck.org · 🔌 MCP: https://lumierepaycheck.org/mcp · 📜 Terms

This repository is the public home for docs, examples, and feedback. The monitoring service itself is hosted and closed-source; the scoring formula is public (below).

What it does

  • Monitors every endpoint in the x402 Bazaar (the badge above shows the live count, which grows as new endpoints are listed) every 30 minutes: price quote, payout wallet, uptime, response time.
  • Flags hijack risk, without punishing normal rotations. Every payout-wallet change is checked against the seller's own wallet declaration, the seller's earlier wallets, and direct transfers between the old and new wallet. Confirmed rotations don't affect the grade; unexplained changes are avoid, then caution with human review. Sellers that use a new address per request are recognized automatically. How it works.
  • Spending rules for agents. Before paying, an agent asks "may I pay this endpoint this amount to this wallet?" and gets allow or deny with reasons.
  • Plans for teams (new). Scoped agent keys, daily/monthly spend limits, signed receipts your wallet verifies before paying, a replayable audit trail, and human review for anomalies. Details.
  • Alerts. Watch an endpoint and get signed webhook alerts when it breaks, changes wallet, or raises its price.
  • Paid delivery checks: small real payments that confirm an endpoint returns what it advertises. A failure only counts if a re-test about two hours later fails too, and requests an endpoint rejects for missing input never count.
  • Known-answer tests: values, not just shape. Uptime and schema checks can pass while an API returns the wrong number. For endpoints with a knowable answer, the verifier pays for a call with a known correct result, or compares against an independent live source, and checks the value itself. Sellers can add their own tests. How it works.
  • Real usage from on-chain data: actual x402 payments (USDC on Base and Solana) into each endpoint's payout wallet over 30 days: volume, distinct buyers, typical and largest payment, trend, and how concentrated the buyers are, counting only payments submitted by recognized facilitators.
  • Community outcome reports: agents that pay through us report whether calls worked. Reports only point our re-tests at problems; grades change only when our own paid test confirms. On by default, easy to opt out.

No accounts, no API keys. Free checks are free; paid features are paid per call with x402, the same way agents pay everything else.

Quick start

1. From Claude, Cursor, or any MCP client

Add the remote MCP server:

https://lumierepaycheck.org/mcp

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Lumière PayCheck: common questions

Is Lumière PayCheck MCP server safe?
Yes, by our scan: it is graded A (91/100). Read the Lumière PayCheck safety report
How do I install Lumière PayCheck?
It runs remotely at lumierepaycheck.org. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does Lumière PayCheck need an API key?
No secret keys are declared. It reads 1 setting from the environment.
Is Lumière PayCheck maintained?
The last commit was 35 days ago (2026-09-30). The latest release is v1.8.1.
Is Lumière PayCheck up?
100% of our last 28 checks got an answer. We check remote servers about four times a day.
What can I use instead of Lumière PayCheck?
Servers from other publishers that do the same job: Decionis MCP server, DCC-MCP Core MCP server and Kiln MCP server.
How does Lumière PayCheck compare with other AI and agents MCP servers?
safety score 91/100 (higher than 88% of 4,460 AI and agents servers); uptime 100% (of our recent checks; the typical remote AI and agents server answers 100%); response time 386 ms (faster than 36% of 2,331 AI and agents servers). Full comparison.

Alternatives to Lumière PayCheck

Same job from other publishers: the closest match first, then the best rated.

  • Decionis
    Authorize consequential AI agent actions before execution
    A
  • DCC-MCP Core
    Agent control plane for DCC and engine hosts: one MCP endpoint, one tool contract.
    A
  • Kiln
    Spawn an object into existence: describe it, and your agent designs it, checks it, and 3D prints it.
    B
  • Lm
    Connect Claude to any OpenAI-compatible LLM endpoint and offload routine work to a local model.
    A
  • Vibe Check
    Metacognitive AI agent oversight: adaptive CPI interrupts for alignment, reflection and safety
    B