Skip to content
External endpointresponds

lunium

Verify a Brazilian PIX payment settled — no API key. Crypto↔PIX with Central Bank receipts.

Endpoint URL
https://api.luniumpay.com/mcp
Current status
responds
Last checked
Aug 17, 2026, 04:59 AM UTC
Check
MCP initialize · 8s limit
Latency
577 ms
Response record
4 of 4 rounds
Transport
streamable-http
Source
mcp_registry
Registry name
com.luniumpay/lunium

Current observation

This endpoint answered at its latest recorded check.

What this server reports about itself

Self-reported at initialize. Not verified by Licium.

Server name
lunium-mcp
Version
1.0.0
Capability keys
tools
Tool names
lunium_create_sandbox_key, lunium_verify_pix_payment, lunium_list_settlement_options, lunium_check_payer_limit, lunium_get_crypto_sale, lunium_get_pix_charge, lunium_quote_crypto_sale, lunium_confirm_crypto_sale, lunium_create_pix_charge
Instructions excerpt

Lunium settles between Brazilian PIX and stablecoins, and issues Central Bank end-to-end receipts. START HERE, NO CREDENTIALS NEEDED: lunium_verify_pix_payment confirms that a PIX payment actually settled, from its E2E identifier alone. It is open — no API key, no account. Use it to check a payment a counterparty claims to have made, before you release goods, credit or a next step. It never returns the PIX key, the full name or the tax number of either party. EVERY OTHER TOOL REQUIRES AN API KEY, sent by the host as the X-API-Key HTTP header. If it is absent, those tools fail with erro="chave_ausente" and acao="parar": tell your user the Lunium connector has no key configured instead of retrying. Keys are provisioned out of band at https://api.luniumpay.com — never through a tool. RESPONSE SHAPE: every tool returns {"dados": ..., "fonte": "lunium-api", "aviso": ...}. Field names inside "dados" are Portuguese and stable — verificado, pago, valor_brl, pago_em, erro, acao. Do not

Reported Aug 17, 2026, 04:59 AM UTC.

Check history

Oldest to newest. Each row is one recorded check.

  1. responds
    MCP initialize · 8s limit · HTTP 200 · 579ms
  2. responds
    MCP initialize · 8s limit · HTTP 200 · 778ms
  3. responds
    MCP initialize · 8s limit · HTTP 200 · 563ms
  4. responds
    MCP initialize · 8s limit · HTTP 200 · 577ms