mcpbeat Sign in

Lumière PayCheck MCP Server

by book0feli Your server? Claim it
answering

Lumière PayCheck is answering right now. Last checked 7 min ago. It exposes 6 tools. Last commit 11 Oct 2026.

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

Uptime history 12 days of history · worst day 97%
12 days agonow
100.0%
Uptime 24h
184 of 184 checks
6
Tools
read from the server
533 ms
Response time
average over 24h
0
Stars
last commit 11 Oct 2026

What changed 19

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 1 October 2026. No other catalogue keeps this.

11 Oct a tool changed the parameters it asks for check_payment
6 Oct a tool description was rewritten get_full_report
5 Oct a tool changed version5 times that day
5 Oct 2 tools changed the parameters they ask for3 times that day check_payment, report_outcome
5 Oct 3 tool descriptions were rewritten check_endpoint, check_payment, report_outcome
4 Oct a tool changed version
1 Oct 4 tool descriptions were rewritten5 times that day check_endpoint, check_payment, get_full_report and 1 more
and 6 more, back to 1 October 2026

Lumière PayCheck does not always answer

Over the last week it answered 99.1% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 7 min ago.

run in your terminal
claude mcp add paycheck --transport http https://lumierepaycheck.org/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "paycheck": {
      "url": "https://lumierepaycheck.org/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.paycheck]
url = "https://lumierepaycheck.org/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "paycheck": {
      "url": "https://lumierepaycheck.org/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "paycheck": {
      "url": "https://lumierepaycheck.org/mcp"
    }
  }
}

This server publishes 1 more address. The block above uses the one we reach during checks; the full list is under Endpoints below, and the author may intend a particular one for your client.

Available tools 6

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

catalog
catalog_stats
Get an overview of the whole monitored x402 catalog: how many endpoints are monitored, how many fall into each verdict (proceed, caution, avoid, free, insufficient_data), and when scores were last computed. Use it for context or reporting, for example to tell a user how much of the x402 ecosystem passes checks. It says nothing about any single endpoint: use check_endpoint for one endpoint, top_endpoints for a ranked list, or check_payment before paying. Read-only, free, no parameters.
endpoint
check_endpoint
Get the trust verdict for one x402 endpoint: score (0-100), grade (A-F), and verdict (proceed, caution, avoid, free, or insufficient_data), plus uptime, delivery-test status, payout-wallet incidents, and how many independent buyers stand behind the seller's buyer wallets (we count customers, not wallets). Use it when you're deciding whether an endpoint is trustworthy at all, before you have a price quote. When you already have the 402 quote (amount and payTo) and are about to pay, use check_payment instead: it runs this same check and also verifies the price and wallet. To discover good endpoints rather than check a known one, use top_endpoints. Read-only and free; reflects monitoring every 30 minutes and real test payments, so a brand-new endpoint may return insufficient_data. Endpoints not in the catalog return monitored: false. API docs: https://github.com/Book0fEli/lumiere-paycheck/blob/main/docs/api.md
full
get_full_report
Get instructions for buying the detailed paid report on one x402 endpoint (score breakdown, current price quote, wallet and price history, test-payment results). Returns the report URL, price, and network; it doesn't buy the report itself. The report is an x402 endpoint that your agent pays with any x402 client. Use it only when the free check_endpoint result isn't enough and the user wants the full history. The response also lists the other paid x402 checks (wallet risk, batch grades, watch alerts), paid the same way. Endpoints we don't monitor return 404 on the report URL and are never charged. API docs: https://github.com/Book0fEli/lumiere-paycheck/blob/main/docs/api.md
payment
check_payment
Decide whether a specific x402 payment should go through: returns allow true/false with reasons. Checks the endpoint's trust verdict, that the amount is within your cap and not above the monitored price, and that the payTo wallet matches the one we've observed (catches swapped or hijacked wallets). Optionally (minOrganicShare) it also requires that enough of the seller's volume comes from independent buyers. Intended for right before a payment, with the amount, payTo, and network from the endpoint's 402 quote; allow is true only when every rule passes. Use check_endpoint instead if you only want an endpoint's grade without a quote in hand. Read-only and free; it doesn't make or block the payment itself. When allow is false, the reasons list explains why. API docs: https://github.com/Book0fEli/lumiere-paycheck/blob/main/docs/api.md
report
report_outcome
After paying an x402 endpoint, report whether you got what you paid for. Free, optional, and open to every agent: send the receipt from a Lumière PayCheck allow decision (paid plans), or the endpoint url plus the payment's transaction hash (anyone; we verify the payment on-chain, Base or Solana, within 24 hours). Answer the short questions in answers: gotResponse, matchedListing (yes/partly/no), charged (as_quoted/more/twice), dataUsable (yes/unsure/no), wouldPayAgain. Reports never change a grade by themselves: confirmations from independent buyers move the endpoint up our paid-test queue, and serious problems (nothing came back, charged more or twice) trigger a re-test; only our own paid test changes the grade. One report per payment; the seller's own wallet can't report on itself.
top
top_endpoints
List the x402 endpoints that are currently safest to pay (verdict proceed or caution, no payout-wallet incidents), best first, with score, grade, verdict, and whether a real test payment was delivered. Use it to discover reliable endpoints or pick between providers. To evaluate one specific endpoint use check_endpoint; to approve a payment use check_payment. Read-only and free; rankings update as monitoring runs (every 30 minutes).

Endpoints

URLTransportStateLatencyChecked
https://lumierepaycheck.org/mcp streamable-http answering 456 ms 7 min ago
https://lumierepaycheck.org/mcp?plans=1 streamable-http answering 371 ms 7 min ago

Alternatives to Lumière PayCheck

same job, measured the same way
Pulsefeed X402
by nikolife2016

Verify x402 payment endpoints before an AI agent pays: scam scan, on-chain checks, trust scores.

62 installs/wk 11 tools answering
Provenance MCP
by apeirontrade

Wash-traffic risk checks for Algorand x402 endpoints before your agent trusts or pays them.

49 installs/wk local only
Mizan
by higgsfield-mizan-bazar

Check an x402 endpoint before your agent pays it: avoid / caution / ok, proven on-chain.

3 tools answering
Endpoint Diligence
by x402supply

Live x402 endpoint trust/diligence check before you pay it. $0.02/call via x402.

3 tools answering
Deadchannel
by plus8bit

Check an x402 endpoint before you pay it: verdict, risk score and what is wrong. $0.005 in USDC.

36 installs/wk local only
Agent Wormhole
by runningoffcode

Check tokens, pages and x402 payments before your agent trusts them. Offline verdicts.

460 installs/wk local only
ProvenPaid
by provenpaid

Check an x402 endpoint before your agent pays it: challenge validity and on-chain payer evidence.

653 installs/wk local only
X402 Trust MCP
by jonasfuchss

Trust & reliability data for x402 endpoints before your agent pays them.

291 installs/wk local only

Lumière PayCheck — questions

Answers built from our own checks of this server.

What can Lumière PayCheck do?
It exposes 6 tools, read directly from the server on our last check. Among them: catalog_stats, check_endpoint, check_payment, get_full_report, report_outcome, top_endpoints. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Lumière PayCheck working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 184 of 184 checks got a reply (100.0%), average response time 533 ms. The bar chart above shows every period we have measured.
How do I connect Lumière PayCheck?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Lumière PayCheck need an API key?
No. Lumière PayCheck completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 6 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Lumière PayCheck?
It answers our handshake in 533 ms on average, which is faster than 23% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.
Is Lumière PayCheck open source?
Yes — it is published under the MIT licence, written in JavaScript and 0 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.