e-Factura Validator (Romania)

Check Romanian e-Factura (CIUS-RO) XML before ANAF: exact fix per error. Also Peppol, EN 16931

Should I use this

Quality & Safety

A
Description quality
90%
Schema completeness
100%
Naming quality
93%
Poisoning risk
100%
Permission match
100%
Protocol compliance
100%

Findings (1)

  • LOWTool 'explain_rule' description lacks action verbin explain_rule

Based on automated analysis of tool definitions and protocol compliance.

Context Cost

~431Tokens (tool definitions)
~947 BTypical response size
Minimal attention impact (0.34% of 128k context)

This is the approximate number of tokens consumed each time the server's tools are loaded into a model's context. Higher counts reduce the attention available for other tasks.

Install

One-Click Install

Add this to your `claude_desktop_config.json` file:

{
  "mcpServers": {
    "einvoice-validator": {
      "url": "https://einvoice.alexhub.uk/mcp"
    }
  }
}

Remote endpoints

https://einvoice.alexhub.uk/mcpstreamable-http

What it can do

Tool inventory

Tools (3)

🟢 Read-only🟡 Write🔴 Delete⚪ Unknown
⚪validate_invoice(xml, profile)

Validate a UBL 2.1 invoice: every rule violation with a plain-English fix, the UBL path of the field and, for amount errors, the correct value. Paid: $0.01 USDC per call via x402 (network eip155:8453); without a payment it returns the payment requirements. Only real invoices are charged.

Input Schema

{
  "type": "object",
  "properties": {
    "xml": {
      "description": "The UBL 2.1 Invoice or CreditNote XML document, as text",
      "title": "Xml",
      "type": "string"
    },
    "profile": {
      "default": "auto",
      "description": "Rule set; 'auto' reads it from the invoice's CustomizationID",
      "enum": [
        "auto",
        "ro",
        "peppol",
        "en16931"
      ],
      "title": "Profile",
      "type": "string"
    }
  },
  "required": [
    "xml"
  ],
  "title": "validate_invoiceArguments"
}
⚪validate_invoice_free(xml, profile)

Same report as validate_invoice, free: 3 calls per day per client IP. When the quota is used up, switch to validate_invoice.

Input Schema

{
  "type": "object",
  "properties": {
    "xml": {
      "description": "The UBL 2.1 Invoice or CreditNote XML document, as text",
      "title": "Xml",
      "type": "string"
    },
    "profile": {
      "default": "auto",
      "description": "Rule set; 'auto' reads it from the invoice's CustomizationID",
      "enum": [
        "auto",
        "ro",
        "peppol",
        "en16931"
      ],
      "title": "Profile",
      "type": "string"
    }
  },
  "required": [
    "xml"
  ],
  "title": "validate_invoice_freeArguments"
}
🟢explain_rule(rule_id)

Explain one business rule by its id (e.g. BR-CO-15, BR-RO-110, PEPPOL-EN16931-R001): official text, plain-English fix and where the field lives in UBL. Free.

Input Schema

{
  "type": "object",
  "properties": {
    "rule_id": {
      "description": "Rule id as reported in findings[].rule",
      "title": "Rule Id",
      "type": "string"
    }
  },
  "required": [
    "rule_id"
  ],
  "title": "explain_ruleArguments"
}

Community

Rate this Server

Evidence

Recent observations

verifiedversion not recorded3 tools