Lumière PayCheck
https://server.smithery.ai/jahman-el/paycheck/mcp**Check any x402 endpoint before your agent pays it.** Lumière PayCheck monitors 19,000+ x402 endpoints from the Bazaar every 30 minutes and makes real test payments to confirm they deliver what they charge for. Your agent gets a clear answer before any money moves. ### What your agent can do - **Check an endpoint:** trust score (0–100), grade (A–F), and a verdict: *proceed*, *caution*, or *avoid* - **Authorize a payment:** confirm the price isn't inflated and the payout wallet hasn't been swapped (hijack detection) before paying - **Find safe endpoints:** the most trustworthy x402 services right now, ranked - **Report outcomes:** flag a paid call that didn't deliver, which triggers an independent re-test ### Why trust it - Real paid delivery tests, not just uptime pings - Payout-wallet changes checked against seller declarations and on-chain evidence - Published scoring formula; grades are never paid for ### Free to use No API key or signup. Add the server and ask your agent to check before it pays. ### For teams Running several agents? Plans give each agent its own key with spend limits, human review for unusual payments, signed receipts, and a full audit trail. **Builder** $9/mo · **Business** $49/mo · **Enterprise** custom → [lumierepaycheck.org/subscribe](https://lumierepaycheck.org/subscribe) [Website](https://lumierepaycheck.org) · [Docs](https://github.com/Book0fEli/lumiere-paycheck)
MCP readiness
Readiness is how fully this listing follows its protocol and how it behaved in our probes over 30 days. It is shown for reference and does not move it in search. Search order and leaderboards use the separate quality grade (here C+, 70.0/100), which weighs availability, conformance, p95 speed and descriptor. How the two differ
| Valid MCP handshake | 10/10 | initialize and tools/list both answered. |
| Live MCP endpoint | 23/25 | Endpoint answers the MCP initialize handshake (7399 ms); very slow response -2. |
| Protocol revision | 8/10 | Speaks MCP 2025-11-25, 1 revision(s) behind 2026-07-28. |
| Signed descriptor | n/a | No MCP standard defines a signed server descriptor. |
| Uptime (30 days) | 15/15 | 30/30 probes succeeded over 30 days (100%). |
| Tool declaration | 10/10 | Lists 10 tool(s) with descriptions. |
| Verified identity | 5/10 | Publisher declared (repository, package or homepage); claim this listing to verify domain control. |
| Freshness + modern flags | 4/5 | seen in a source within 7 days. |
| Auth declaration | 2/5 | Declares credential scheme: smithery_api_key. |
Compared with peers
Against 53,039 reachable MCP servers in our daily snapshot (2026-11-12 06:46 UTC). Display only; it does not change search order.
- Readiness
- Higher than 80% of peers
- This listing 86 · peer median 81
- Latency
- Faster than 33% of peers
- This listing 475 ms · peer median 326 ms
Where it loses the most points, and how to win them back
- Verified identity −5
— Claim the listing and prove control of its domain.
Now: Publisher declared (repository, package or homepage); claim this listing to verify domain control.
- Auth declaration −3
— State how to authenticate (an auth scheme, or that none is needed).
Now: Declares credential scheme: smithery_api_key.
- Live MCP endpoint −2
— Answer initialize and tools/list at the declared endpoint.
Now: Endpoint answers the MCP initialize handshake (7399 ms); very slow response -2.
Listed in
Directories this entry was found in.
How to connect
https://server.smithery.ai/jahman-el/paycheck/mcpcurl -X POST https://server.smithery.ai/jahman-el/paycheck/mcp \
-H 'Content-Type: application/json' \
-H 'Accept: application/json, text/event-stream' \
-d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{}}'