Lumi Verdict: check an x402 seller before paying
LocalAbout Lumi Verdict: check an x402 seller before paying
One signed label before paying an x402 seller, from Lumi's test-buys on XRPL, Base and Stellar
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
npx -y lumi-verdict-mcpEVM_PRIVATE_KEYSecret0x private key of your Base wallet that pays in USDC (gasless, signed locally)XRPL_SEEDSecretSeed of your XRPL wallet that pays in XRP/RLUSD/USDC (signed locally)LUMI_PAY_ASSETBASE_USDC, XRP, RLUSD or USDC (XRPL). Default: BASE_USDC if only EVM_PRIVATE_KEY is set, else XRPLUMI_MAX_USD_PER_CALLPer-call cap in USD for stablecoins (covers every Lumi endpoint)LUMI_MAX_XRP_PER_CALLPer-call cap in XRPLUMI_SESSION_BUDGETMax total spend per server processXRPL_NETWORKxrpl:0 mainnet or xrpl:1 testnetLocal servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.
Tools
2Saved tool list · updated 3d ago
| Parameter | Type | Required | Description |
|---|---|---|---|
| url | string | Yes | The x402 resource URL (or the seller's domain) you are about to pay |
| payTo | string | No | Optional: the payTo address in its 402 quote |
| amount | string | No | Optional: the quoted price in USD, e.g. 0.01 |
Details
The maintainer has not added details yet. Check the README in the repository.
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.