velora
First MCP server to execute real AFIP/ARCA invoicing in Argentina — not just docs/search.
https://tools.somosvelora.com/api/mcpCurrent 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
- velora-mcp-demo
- Version
- 1.0.0
- Capability keys
- tools
- Tool names
- validate_cuit, get_fiscal_readiness, emit_invoice, emit_nota, create_product, edit_product, stock_load, adjust_stock, delete_product, bulk_price_update, query_catalog, open_catalog_selector, register_sale, register_movement, return_sale, find_customer, upsert_customer, delete_customer, quote_shipping, create_shipment, track_shipment, get_package_profile, send_whatsapp_text, send_whatsapp_template, connection_status, caja_consultar_saldo, caja_ciclo_caja, caja_registrar_movimiento, get_payment_intent_status, open_payment_link_wizard, open_pending_orders, open_cobro_status, open_delivery_receipt, create_tracked_payment_link, list_suppliers, create_supplier, create_purchase_request, edit_supplier, delete_supplier, query_sales (first 40 recorded; the server may expose more)
DEMO MODE — this is a free, public, always-on demo of the Velora MCP toolkit, not the production server (which is paused). Pure tools (validate_cuit) run real logic. Read tools return a fixed, fictional dataset ('Almacén Demo SRL'), always labeled [DEMO] with _demo: true in structuredContent — never confuse this for real business data. Tools with a real side effect in production (fiscal emission, payments, WhatsApp sends, database writes) refuse to execute here and return isError: true with an honest explanation instead of a fabricated result — the schema and contract shown are the real production ones. See https://github.com/crossi-dev/velora-mcp-demo for source.
Reported Aug 17, 2026, 05:08 AM UTC.
Check history
Oldest to newest. Each row is one recorded check.
- not foundMCP initialize · 8s limit · HTTP 404 · 500ms
- not foundMCP initialize · 8s limit · HTTP 404 · 723ms
- respondsMCP initialize · 8s limit · HTTP 200 · 320ms
- respondsMCP initialize · 8s limit · HTTP 200 · 456ms