Zero-take-rate Stripe 2025-03-31.basil, Visa CE 3.0 & EU/XI VIES VAT guardrails MCP server.
Nothing to run from here
e-Factura Validator (Romania) is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
96/100
tool-list score
13
tools declared
remote
at its publisher
—
calls last 7d
What it does
Validate, fix and generate Romanian e-Factura; check SAF-T D406 (ANAF validator + consistency)
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http e-factura-validator-romania-mcp https://einvoice.alexhub.uk/mcp
# 2 — ask your agent for something these tools do
# validate_saft, validate_saft_free, validate_invoice and 10 more
e-Factura Validator (Romania) costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
ALAll 1 server
alexhub1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http e-factura-validator-romania-mcp https://einvoice.alexhub.uk/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
13 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Check a Romanian SAF-T file (D406) before filing it with ANAF: 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).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| xml | string | yes | 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) |
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).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| xml | string | yes | 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 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. If the report has 'autofix', fix_invoice can repair those errors.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| xml | string | yes | The UBL 2.1 Invoice or CreditNote XML document, as text |
| profile | string | no | Rule set; 'auto' reads it from the invoice's CustomizationID |
Repair the invoice automatically and return the corrected XML: 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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| xml | string | yes | The UBL 2.1 Invoice or CreditNote XML document, as text |
| profile | string | no | Rule set; 'auto' reads it from the invoice's CustomizationID |
Create a complete Romanian e-Factura (UBL 2.1 CIUS-RO XML) from simple data: invoice number, dates, seller and buyer CUI, lines (name, quantity, unit, price without VAT, VAT rate e.g. 21 or 11), optional IBAN. Company names, addresses, county codes, Bucharest sectors and VAT status are filled from ANAF; totals and VAT are computed; the XML is validated before it is returned. Paid: $0.05 USDC via x
| Parameter | Type | Required | Notes |
|---|---|---|---|
| invoice | object | yes | Invoice data, see the tool description for the shape |
Romanian company data by CUI (fiscal code) from ANAF, 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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| cui | string | yes | CUI, with or without RO, e.g. RO14399840 |
Same report as validate_invoice, free: 3 calls per day per client IP. When the quota is used up, switch to validate_invoice.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| xml | string | yes | The UBL 2.1 Invoice or CreditNote XML document, as text |
| profile | string | no | Rule set; 'auto' reads it from the invoice's CustomizationID |
Official BNR (National Bank of Romania) exchange 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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| currency | no | ISO code, e.g. EUR, USD | |
| date | no | YYYY-MM-DD |
Romanian public (legal) holidays for a year, incl. Orthodox Easter and Rusalii. Free.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| year | no | e.g. 2026, default current year |
Is a date a Romanian working day, which is the next one, and (optionally) the date N working days later. Free.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| date | no | YYYY-MM-DD, default today | |
| add_days | integer | no | working days to add |
Romanian 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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| period | no | reporting month YYYY-MM, default last month |
Check an IBAN (length and check digits) and name the Romanian bank. Free.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| iban | string | yes | IBAN, spaces allowed |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| rule_id | string | yes | Rule id as reported in findings[].rule |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install e-Factura Validator (Romania) or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATool-list grade · score 96 / 100
Release 1.9.0 · scanned 6 Nov 2026
Graded from the tools this server lists, not from its source code.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score96
Findings0 threat · 0 capability
Capabilityminimal
Coveragemanifest
Verificationnot in this report
Surface digeste3a34c7a87f3a34263fe35b5d6676e5e5c64c00dd3aa6694e7a6f08c0cd4c4c0
Score vectorthreat 100 → client 96
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
Tool surfaceread
Implementation sourcenot available
Package metadatanot available
Live transportnot available
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| validate_saft | no tags | |
| validate_saft_free | no tags | |
| validate_invoice | no tags | |
| fix_invoice | no tags | |
| generate_invoice | no tags | |
| lookup_company | no tags | |
| validate_invoice_free | no tags | |
| fx_rate | no tags | |
| ro_holidays | no tags | |
| ro_business_day | no tags | |
| ro_tax_deadlines | no tags | |
| validate_iban | no tags | |
| explain_rule | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digeste3a34c7a87f3a342
Scanned2026-11-06
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.9.0.
1.9.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish e-Factura Validator (Romania) can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.