# e-Factura Validator (Romania) (remote · einvoice.alexhub.uk)

Validate, fix and generate Romanian e-Factura; check SAF-T D406 (ANAF validator + consistency)

- Trust score: 72/100 (medium)
- Change this week: +10
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `einvoice.alexhub.uk`: 72/100 (this document), [markdown](https://verifymcp.io/servers/uk-alexhub-einvoice-validator/einvoice.md), [page](https://verifymcp.io/servers/uk-alexhub-einvoice-validator/einvoice)

## Channel facts

- Endpoint: `https://einvoice.alexhub.uk/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.8.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 69/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 406, which proves neither a plaintext path nor enforcement.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 58/100
  - 29% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 2115 tokens (~124/item across 17 items; 14 tools + 3 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 40/100
  - Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 14 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 16 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the e-Factura Validator (Romania) MCP server?

e-Factura Validator (Romania) is a hosted endpoint at https://einvoice.alexhub.uk/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http uk-alexhub-einvoice-validator 'https://einvoice.alexhub.uk/mcp'
```

### Cursor

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

### VS Code

```json
{
  "servers": {
    "uk-alexhub-einvoice-validator": {
      "type": "http",
      "url": "https://einvoice.alexhub.uk/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.uk-alexhub-einvoice-validator]
url = "https://einvoice.alexhub.uk/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "uk-alexhub-einvoice-validator": {
      "type": "remote",
      "url": "https://einvoice.alexhub.uk/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add uk-alexhub-einvoice-validator --url 'https://einvoice.alexhub.uk/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  uk-alexhub-einvoice-validator:
    url: "https://einvoice.alexhub.uk/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "uk-alexhub-einvoice-validator": {
      "Transport": "http",
      "Url": "https://einvoice.alexhub.uk/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add uk-alexhub-einvoice-validator -t streamable-http -u 'https://einvoice.alexhub.uk/mcp'
```

### Other

```json
{
  "mcpServers": {
    "uk-alexhub-einvoice-validator": {
      "type": "http",
      "url": "https://einvoice.alexhub.uk/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 72, +1)

No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-04 (score 71, 0)

- [functional] New tool “company_financials”

### 2026-11-03 (score 71, +3)

- [security improvement] HSTS header: fail → pass

### 2026-11-02 (score 68, +1)

No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-31 (score 67, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-30 (score 66, +4)

- [security improvement] Authorization: unverified → partial
- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “explain_rule” rewrote its description, which is the text the model reads
- [security] Tool “fix_invoice” rewrote its description, which is the text the model reads
- [security] Tool “fx_rate” rewrote its description, which is the text the model reads
- [security] Tool “generate_invoice” rewrote its description, which is the text the model reads
- [security] Tool “lookup_company” rewrote its description, which is the text the model reads
- [security] Tool “ro_business_day” rewrote its description, which is the text the model reads
- [security] Tool “ro_holidays” rewrote its description, which is the text the model reads
- [security] Tool “ro_tax_deadlines” rewrote its description, which is the text the model reads
- [security] Tool “validate_iban” rewrote its description, which is the text the model reads
- [security] Tool “validate_saft” rewrote its description, which is the text the model reads
- [security] Tool “validate_saft_free” rewrote its description, which is the text the model reads
- [security] Tool “validate_invoice” rewrote its description, which is the text the model reads
- [security] Tool “validate_invoice_free” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 1594 → 1974
- [functional] First check of Schema quality: 29
- [functional] New prompt “check_invoice_before_anaf”
- [functional] New prompt “check_saft_before_filing”
- [functional] New prompt “fix_anaf_rejection”
- [functional] New prompt “invoice_from_data”
- [functional] New resource “guide”
- [functional] New resource “pricing”
- [functional] New resource “sample-invoice”
- [cosmetic] “explain_rule” reworded the description of “rule_id”
- [cosmetic] “fx_rate” reworded the description of “currency”
- [cosmetic] “lookup_company” reworded the description of “cui”
- [cosmetic] “ro_holidays” reworded the description of “year”

### 2026-10-28 (score 62, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-27 (score 61, 0)

- [security] The server rewrote its instructions, which are the text every model session reads
- [functional regression] Schema quality: 1257 → 1594
- [functional] Schema quality: good → excellent
- [functional] New tool “validate_saft”
- [functional] New tool “validate_saft_free”

## MCP tools (14)

### `validate_invoice_free` (~190 tokens)

Use before uploading an e-Factura to ANAF SPV, after generating invoice XML, or when ANAF rejected an invoice: validates a UBL 2.1 Invoice/CreditNote (Romanian CIUS-RO 1.0.9, Peppol BIS 3.0, EN 16931) and returns every error with the fix in words, the UBL path of the field and, for amounts, the correct value. Start here: free, no wallet, account or key, 3 calls per day per client IP. Fix the XML from the report and call again. When the quota is used up, switch to validate_invoice.

Input parameters:

- `profile` (string): Rule set; 'auto' reads it from the invoice's CustomizationID
- `xml` (string, required): The UBL 2.1 Invoice or CreditNote XML document, as text

### `validate_invoice` (~175 tokens)

Use before uploading an e-Factura to ANAF SPV or sending a Peppol invoice, once the free quota of validate_invoice_free is used up (same report). 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, payment in the request _meta); without a payment it returns the payment requirements. Only real invoices are charged. If the report has 'autofix', fix_invoice can repair those errors.

Input parameters:

- `profile` (string): Rule set; 'auto' reads it from the invoice's CustomizationID
- `xml` (string, required): The UBL 2.1 Invoice or CreditNote XML document, as text

### `fix_invoice` (~164 tokens)

Use when a validation report lists 'autofix' rules, or ANAF rejected an invoice for codes, dates or totals, and you want the corrected XML instead of editing it yourself: fixes county/sector/country/currency/unit codes, date formats, VAT-id prefixes, decimals, totals and VAT recomputed from the lines. Lists every change (field, old, new) and re-validates the result. Paid: $0.05 USDC via x402, charged only if something was fixed. Review the changes before sending the invoice.

Input parameters:

- `profile` (string): Rule set; 'auto' reads it from the invoice's CustomizationID
- `xml` (string, required): The UBL 2.1 Invoice or CreditNote XML document, as text

### `generate_invoice` (~293 tokens)

Use when you have invoice data but no XML and need a Romanian e-Factura ANAF accepts: builds UBL 2.1 CIUS-RO XML from simple data (number, dates, seller and buyer CUI, lines with name, quantity, unit, price without VAT and VAT rate e.g. 21 or 11, optional IBAN). Company names, addresses, county codes, Bucharest sectors and VAT status come from ANAF; totals and VAT are computed; the XML is validated before it is returned. Paid: $0.05 USDC via x402, charged only when a valid invoice is returned. Other currencies: add 'currency': 'EUR' (BNR rate used unless you pass exchange_rate). Example invoice: {"number": "FCT-0001", "issue_date": "2026-10-24", "due_date": "2026-11-23", "seller": {"cui": "RO12345678"}, "buyer": {"cui": "87654321"}, "payment": {"iban": "RO49AAAA1B31007593840000"}, "lines": [{"name": "Servicii consultanta", "quantity": 10, "unit": "ore", "price": 150, "vat_rate": 21}]}

Input parameters:

- `invoice` (object, required): Invoice data, see the tool description for the shape

### `lookup_company` (~127 tokens)

Use when building or checking an invoice for a Romanian company and you only have its CUI, or to check a partner before invoicing: ANAF data already in e-Factura form: legal name, VAT id (RO… only for VAT payers), trade register number, address with county as ISO code (RO-CJ) and Bucharest city as SECTOR1..6, plus flags: inactive, VAT on collection, e-Factura registry. Free, 100 lookups per day per IP.

Input parameters:

- `cui` (string, required): CUI, with or without RO

### `company_financials` (~141 tokens)

Use when you need a Romanian company's size or financial health from its CUI (credit check before invoicing or selling on terms, lead qualification, due diligence): the annual statement filed with ANAF: CAEN code, turnover, revenue, expenses, net_result (profit positive, loss negative), employees, assets, debts, equity. Without year: the last closed year with a statement. Only companies file statements (not PFA). Free, shares the 100 lookups per day per IP of lookup_company.

Input parameters:

- `cui` (string, required): CUI, with or without RO
- `year`: Financial year (omit for the last filed one)

### `explain_rule` (~112 tokens)

Use when ANAF SPV, a Peppol access point or a validation report names a rule (e.g. BR-CO-15, BR-RO-110, PEPPOL-EN16931-R001) and you need to know what it means and how to fix it: official text in English and Romanian, plain-English fix and where the field lives in UBL. Free.

Input parameters:

- `rule_id` (string, required): Rule id as reported in findings[].rule or in the ANAF error message

### `validate_saft_free` (~116 tokens)

Use before filing a Romanian SAF-T (D406) with ANAF, or when ANAF's DUKIntegrator reported errors: same check as validate_saft, free: 1 file(s) per day per client IP, report limited to the first 10 findings (the total count is given).

Input parameters:

- `xml` (string, required): The SAF-T D406 XML file content, as text (up to 25 MB here; bigger files: HTTP POST /v1/saft/validate, up to 100 MB)

### `validate_saft` (~202 tokens)

Use before filing a Romanian SAF-T (D406) with ANAF, for the full report: runs ANAF's official validator (DUKIntegrator) for the reporting period and the consistency checks it does not do offline (balanced entries, GL totals, opening + movements = closing per account, trial balance, partner balances, invoice totals, VAT = base x rate, VAT codes valid for the period, CUI/IBAN check digits, chart of accounts). Every finding has a fix in Romanian and English and the correct value where computable. Paid: $0.50 USDC via x402 (network eip155:8453), charged only if a D406 was checked; without a payment it returns the payment requirements.

Input parameters:

- `xml` (string, required): The SAF-T D406 XML file content, as text (up to 25 MB here; bigger files: HTTP POST /v1/saft/validate, up to 100 MB)

### `fx_rate` (~98 tokens)

Use for an invoice in a foreign currency (e-Factura needs the VAT in RON) or any RON conversion: official BNR (National Bank of Romania) rate, RON per 1 unit of the currency, for a date (default today; weekends/holidays return the last publication). Omit currency for all rates. Free.

Input parameters:

- `currency`: ISO 4217 code
- `date`: YYYY-MM-DD

### `ro_holidays` (~46 tokens)

Use when planning payment or filing dates in Romania: public (legal) holidays for a year, incl. Orthodox Easter and Rusalii. Free.

Input parameters:

- `year`: default current year

### `ro_business_day` (~82 tokens)

Use to compute a due date in Romanian working days (e.g. the 5 working days to upload an e-Factura): is a date a working day, which is the next one, and the date N working days later. Free.

Input parameters:

- `add_days` (integer): working days to add
- `date`: YYYY-MM-DD, default today

### `ro_tax_deadlines` (~86 tokens)

Use to know when Romanian returns are due: monthly filing deadlines (D112, D300, D100, D390, D394, D406) for a reporting month, moved to the next working day when they fall on a weekend or holiday. General rules; confirm special regimes with ANAF. Free.

Input parameters:

- `period`: reporting month YYYY-MM, default last month

### `validate_iban` (~53 tokens)

Use before putting an IBAN on an invoice or paying to one: checks length and check digits and names the Romanian bank (or the State Treasury). Free.

Input parameters:

- `iban` (string, required): IBAN, spaces allowed

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/uk-alexhub-einvoice-validator/einvoice#diagnostics

## Score history

- 2026-11-05: 72
- 2026-11-04: 71
- 2026-11-03: 71
- 2026-11-02: 68
- 2026-11-01: 67
- 2026-10-31: 67
- 2026-10-30: 66
- 2026-10-29: 62
- 2026-10-28: 62
- 2026-10-27: 61
- 2026-10-26: 61
- 2026-10-25: 61
- 2026-10-24: 60

## Common questions

### What is the e-Factura Validator (Romania) MCP server?

e-Factura Validator (Romania) is an MCP server listed in the public MCP registry as uk.alexhub/einvoice-validator. Validate, fix and generate Romanian e-Factura; check SAF-T D406 (ANAF validator + consistency). This page covers its hosted endpoint (https://einvoice.alexhub.uk/mcp).

### Is the e-Factura Validator (Romania) MCP server safe to use?

e-Factura Validator (Romania) scores 72 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the e-Factura Validator (Romania) MCP server expose?

e-Factura Validator (Romania) exposes 14 tools: validate_invoice_free, validate_invoice, fix_invoice, generate_invoice, lookup_company, and 9 more. Their descriptions and schemas cost roughly 1,885 tokens of context every time the server is loaded.

### Does the e-Factura Validator (Romania) MCP server require authentication?

No. We connected to e-Factura Validator (Romania) without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the e-Factura Validator (Romania) MCP server still maintained?

e-Factura Validator (Romania) is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://einvoice.alexhub.uk/mcp
- Website: https://einvoice.alexhub.uk/
- Changelog RSS feed: https://verifymcp.io/servers/uk-alexhub-einvoice-validator/einvoice.xml
- Changelog JSON feed: https://verifymcp.io/servers/uk-alexhub-einvoice-validator/einvoice.json
- HTML version of this page: https://verifymcp.io/servers/uk-alexhub-einvoice-validator/einvoice