← Registry

Security & Testing

lumierepaycheck.org

Assesses x402 payment endpoints by providing trust scores, verdicts, allow/deny payment decisions, and catalog safety statistics.

x402 supported2 endpoints12 known toolsFirst detected October 1, 2026Last detected October 6, 2026

ENDPOINT 1

https://lumierepaycheck.org/mcp

No auth detected

MCP server metadata

Name
lumiere-paycheck
Version
1.4.1
Capabilities
tools.listChangedprompts.listChangedresources.listChanged
Server instructions

Lumière PayCheck checks x402 endpoints before an agent pays them. Call check_endpoint for a trust verdict, or check_payment with the amount and payTo from the 402 quote before paying; pay only when allow is true. After paying, call report_outcome. Free to use. For teams running several agents, paid plans (Builder $9/month, Business $49/month, Enterprise custom) add a key per agent with spend limits, human review for unusual payments, signed receipts, and an audit trail: https://lumierepaycheck.org/subscribe

Known tools 6

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, and payout-wallet incidents.

Inferred read-only
check_payment

Decide whether a specific x402 payment should go through: returns allow true/false with reasons.

Potential side effects
report_outcome

Report whether a paid x402 call delivered a usable response, using the receipt from a Lumière PayCheck allow decision (the paid /v1/authorize API).

Inferred read-only
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.

Potential side effects
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.

Inferred read-only
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).

Potential side effects

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.lumiere-paycheck]
url = "https://lumierepaycheck.org/mcp"
enabled = true
Claude Code

.mcp.json

{
  "mcpServers": {
    "lumiere-paycheck": {
      "type": "http",
      "url": "https://lumierepaycheck.org/mcp"
    }
  }
}
Claude Desktop

Settings → Connectors → Add custom connector

Name: lumiere-paycheck
Remote MCP URL: https://lumierepaycheck.org/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "lumiere-paycheck": {
      "url": "https://lumierepaycheck.org/mcp"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code
{
  "servers": {
    "lumiere-paycheck": {
      "type": "http",
      "url": "https://lumierepaycheck.org/mcp"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "lumiere-paycheck",
  "transport": "streamable-http",
  "url": "https://lumierepaycheck.org/mcp"
}
MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

ENDPOINT 2

https://lumierepaycheck.org/mcp?plans=1

No auth detected

MCP server metadata

Name
lumiere-paycheck
Version
1.5.0
Capabilities
tools.listChangedprompts.listChangedresources.listChanged
Server instructions

Lumière PayCheck checks x402 endpoints before an agent pays them. Call check_endpoint for a trust verdict, or check_payment with the amount and payTo from the 402 quote before paying; check_payment returns allow true only when every rule passes. report_outcome records whether a payment made with a Lumière PayCheck receipt delivered. Free to use. Teams running several agents can add a plan: a key per agent with spend limits, human review for unusual payments, signed receipts, and an audit trail. Agents can buy a plan themselves with USDC over x402: GET https://lumierepaycheck.org/v1/plans lists them; POST https://lumierepaycheck.org/v1/plans/builder ($9) or https://lumierepaycheck.org/v1/plans/business ($49) buys 30 days and returns an owner key; then POST https://lumierepaycheck.org/v1/agents creates agent keys. People can pay by card at https://lumierepaycheck.org/subscribe. Enterprise is custom.

Known tools 6

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, and payout-wallet incidents.

Inferred read-only
check_payment

Decide whether a specific x402 payment should go through: returns allow true/false with reasons.

Potential side effects
report_outcome

Report whether a paid x402 call delivered a usable response, using the receipt from a Lumière PayCheck allow decision (the paid /v1/authorize API).

Inferred read-only
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.

Potential side effects
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.

Inferred read-only
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).

Potential side effects

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.lumiere-paycheck]
url = "https://lumierepaycheck.org/mcp?plans=1"
enabled = true
Claude Code

.mcp.json

{
  "mcpServers": {
    "lumiere-paycheck": {
      "type": "http",
      "url": "https://lumierepaycheck.org/mcp?plans=1"
    }
  }
}
Claude Desktop

Settings → Connectors → Add custom connector

Name: lumiere-paycheck
Remote MCP URL: https://lumierepaycheck.org/mcp?plans=1

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "lumiere-paycheck": {
      "url": "https://lumierepaycheck.org/mcp?plans=1"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code
{
  "servers": {
    "lumiere-paycheck": {
      "type": "http",
      "url": "https://lumierepaycheck.org/mcp?plans=1"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "lumiere-paycheck",
  "transport": "streamable-http",
  "url": "https://lumierepaycheck.org/mcp?plans=1"
}
MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Trust Data Available

BuiltWith Trust API v2 evidence for lumierepaycheck.org was fetched 2026-10-03T07:59:48.912Z.

Trust status Neutral

lumierepaycheck.org is assessed as Neutral: No suspicious signals found, but no strong positive signal either

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.