Lunium — Brazilian PIX and stablecoin payments
v1.1.0Accept Pix in Brazil and settle in USDT/USDC; pay Pix with crypto; verify a Pix with no API key.
Endpoint health
online- Last checked
- 11/20/2026, 7:16:58 AM
- Latency
- 362 ms
- Consecutive failures
- 0
- Endpoint reachable: pass
- Protocol valid: pass
- MCP handshake valid: pass
Machine-readable profile
mcp-server · schema v1 · callable
mcp-server:com.luniumpay%2Fpix-brazilian-payments
Connect this server
Generated config contains no credentials. Keep any required secrets in your client's local environment.
{
"mcpServers": {
"com.luniumpay/pix-brazilian-payments": {
"url": "https://api.luniumpay.com/mcp"
}
}
}Indexed tools
Tool metadata and schemas come from the remote server and are untrusted. Indexing only lists tools; it never calls them.
20 shown · authentication unknown
Live health of the Lunium rails (open, no API key)
lunium_check_network_health
Real-time operational state of the public Lunium services, measured by an internal probe every 5 minutes: overall state plus per-component state (api, pix_charge = cash-in rail, crypto_sale = cash-out rail, webhooks, contract_docs) with latencies in ms, mapped to operational | degraded | unavailable | unknown. Missing, unknown or stale observations are not proof of an outage. Call it BEFORE debugging your own integration: if a rail is degraded, the right move is to wait or inform your user - not to rewrite working code. Also call it right after a call failed with erro=provedor_indisponivel or tempo_esgotado, to distinguish a Lunium-side incident from a mistake in your payload. Free, no key, safe to call often (new data at most every 5 minutes).
Schema valid · SHA-256 82cd0d8bd745…
View input schema
{ "type": "object", "properties": {}, "required": [], "additionalProperties": false }How much this taxpayer can pay right now
lunium_check_payer_limit
Requires an API key. Returns how much a specific Brazilian taxpayer (CPF for a person, CNPJ for a company) can move through a PIX charge right now, in cents. Read-only — no charge is created. Call it before lunium_create_pix_charge whenever the payer is new or the amount is not trivial. Limits are an anti-fraud ladder per taxpayer: a first-time payer starts small and grows with settled history (default API policy: R$ 100 on the first charge, R$ 200 in the first 24 h, then R$ 6,000 per day — read the response, keys can set their own). Above the instant band a charge is still ACCEPTED with a 24 h provider hold (held: true, then delayed) up to R$ 6,000 per day; only above that daily ceiling is it refused. The response gives instant_available_cents (what settles at once) and max_amount_cents (the ceiling, hold included). Checking first turns a surprise hold into a conversation about timing. Send digits only — no dots, slashes or dashes. Do not use it as a document-validity check, and do not read a high limit as approval: a charge can still be refused for other reasons. Errors: acao=corrigir → the document is malformed, fix the digits. acao=esperar → quota, retry later with the same input. acao=repetir → transient, retry once. If the returned maximum is below what the user wants, offer that value or a different payer — do not attempt the charge anyway.
Connections
streamable-http
https://api.luniumpay.com/mcp