MCP server for minia2a.uk — discover and call 1,600+ x402 pay-per-call APIs with USDC payments.
Nothing to run from here
Electronic Invoice API 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.
93/100
tool-list score
7
tools declared
remote
at its publisher
—
calls last 7d
What it does
Validate, generate, convert and extract EN 16931 e-invoices for businesses.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http electronic-invoice-api-mcp https://mcp.electronic-invoice.app/mcp
# 2 — ask your agent for something these tools do
# validate_invoice, generate_invoice, convert_invoice and 4 more
Electronic Invoice API costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
EIAll 1 server
electronic-invoice1 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 electronic-invoice-api-mcp https://mcp.electronic-invoice.app/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
7 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.
Validate an existing e-invoice file without changing it. Accepts UBL Invoice/CreditNote XML, UN/CEFACT CII XML, or a ZUGFeRD/Factur-X/XRechnung PDF. Checks EN 16931 and the XRechnung 3.0 CIUS, and returns verdict, findings and rule set versions. A PDF is also checked as a PDF/A-3 container, but only if the PDF itself is sent. Report the result of this tool; do not replace it with your own analysis
| Parameter | Type | Required | Notes |
|---|---|---|---|
| file | no | The invoice file the user attached in ChatGPT. Always prefer this when the user attached a file: the server fetches the original bytes and passes them on unchanged, so a PDF is checked as a whole. Onl | |
| content | string | no | Raw invoice XML as UTF-8 text (UBL Invoice/CreditNote or UN/CEFACT CII). Use this only when the XML itself is the invoice. Do not use it for PDFs, and do not extract the XML from a PDF to send it here |
| contentBase64 | string | no | Base64-encoded raw bytes of an invoice XML or PDF file. Use this for PDFs and for binary-safe XML when file is not available. Exactly one of file, content and contentBase64 is required. |
| filename | string | no | Optional original filename, for example rechnung.xml or rechnung.pdf. It is used only to derive the result filename and is not sent to the API. |
| contentType | string | no | Optional MIME type of the supplied document. Defaults to application/xml for content and to a value derived from filename for contentBase64. Ignored for file, where the file content decides. |
| country | string | no | Rule set country. DE checks XRechnung and EN 16931. FR uses EN 16931 plus an info finding about French rules that are not covered. Default DE. |
| checks | string | no | Optional opt-in plausibility checks (PL rules): mandatory items of section 14(4) UStG, arithmetic, dates, Skonto, VAT rates, VAT id form. They are an aid, not legal or tax advice. |
Create a new e-invoice file from structured JSON. Builds XRechnung UBL/CII or a ZUGFeRD/Factur-X PDF, validates the result with the same rule sets, and returns the file only if it is valid. Use this when no invoice file exists yet. Do not use it to validate an existing file (use validate_invoice) or to change an existing file's syntax (use convert_invoice). Supports invoice, credit note, corrected
| Parameter | Type | Required | Notes |
|---|---|---|---|
| invoice | object | yes | Invoice data per the Electronic Invoice API schema. Required fields: number, issueDate, seller, buyer, lines. Optional fields include typeCode, dueDate, deliveryDate, currency, buyerReference, notes, |
| format | string | yes | Output format. xrechnung-ubl and xrechnung-cii return XML. zugferd-en16931, zugferd-xrechnung and facturx-en16931 return a PDF/A-3 file. Required. |
| lang | string | no | Language of the PDF visual. Default de. |
| qr | boolean | no | Add an EPC QR payment page to PDF output when IBAN and amount due are present. The response header X-Payment-QR says added or skipped with a reason. Ignored for XML output. |
| country | string | no | Rule set country for validation of the generated invoice. Default DE. |
Convert an existing e-invoice from UBL to CII, CII to UBL, or XML to a ZUGFeRD/Factur-X PDF. Also accepts a ZUGFeRD/Factur-X PDF and converts its embedded XML. Validates every output and returns it only if valid. Use this for a format or container change. Do not use it to create an invoice from data (use generate_invoice), to validate only (use validate_invoice), or to extract data (use extract_in
| Parameter | Type | Required | Notes |
|---|---|---|---|
| file | no | The invoice file the user attached in ChatGPT. Always prefer this when the user attached a file: the server fetches the original bytes and passes them on unchanged, so a PDF is checked as a whole. Onl | |
| content | string | no | Raw invoice XML as UTF-8 text (UBL Invoice/CreditNote or UN/CEFACT CII). Use this only when the XML itself is the invoice. Do not use it for PDFs, and do not extract the XML from a PDF to send it here |
| contentBase64 | string | no | Base64-encoded raw bytes of an invoice XML or PDF file. Use this for PDFs and for binary-safe XML when file is not available. Exactly one of file, content and contentBase64 is required. |
| filename | string | no | Optional original filename, for example rechnung.xml or rechnung.pdf. It is used only to derive the result filename and is not sent to the API. |
| contentType | string | no | Optional MIME type of the supplied document. Defaults to application/xml for content and to a value derived from filename for contentBase64. Ignored for file, where the file content decides. |
| to | string | yes | Target. ubl and cii return XML. zugferd and facturx return a PDF/A-3 file. Required. |
| profile | string | no | PDF profile for to=zugferd or to=facturx. Default follows the input profile. Not valid for ubl or cii. |
| lang | string | no | Language of the PDF visual. Default de. |
| qr | boolean | no | Add an EPC QR payment page to PDF output. See generate_invoice. |
| country | string | no | Rule set country for validation. Default DE. |
Read data from an existing UBL/CII XML or ZUGFeRD/Factur-X PDF. Returns JSON business terms keyed by BT/BG numbers, CSV with one row per line, or a DATEV Buchungsstapel (EXTF). Does not validate the invoice. Use this for accounting import or data analysis. Do not use it to check validity (use validate_invoice). DATEV export has hard limits: EUR only, one invoice per file, issue date inside the fis
| Parameter | Type | Required | Notes |
|---|---|---|---|
| file | no | The invoice file the user attached in ChatGPT. Always prefer this when the user attached a file: the server fetches the original bytes and passes them on unchanged, so a PDF is checked as a whole. Onl | |
| content | string | no | Raw invoice XML as UTF-8 text (UBL Invoice/CreditNote or UN/CEFACT CII). Use this only when the XML itself is the invoice. Do not use it for PDFs, and do not extract the XML from a PDF to send it here |
| contentBase64 | string | no | Base64-encoded raw bytes of an invoice XML or PDF file. Use this for PDFs and for binary-safe XML when file is not available. Exactly one of file, content and contentBase64 is required. |
| filename | string | no | Optional original filename, for example rechnung.xml or rechnung.pdf. It is used only to derive the result filename and is not sent to the API. |
| contentType | string | no | Optional MIME type of the supplied document. Defaults to application/xml for content and to a value derived from filename for contentBase64. Ignored for file, where the file content decides. |
| format | string | no | Output. json returns the EN 16931 term model plus a summary. csv returns one row per line. datev returns a DATEV Buchungsstapel (EXTF, Windows-1252). Default json. |
| labels | boolean | no | json only: add a map from BT number to xr element name. |
| attachments | boolean | no | json only: include embedded files as base64. |
| delimiter | string | no | csv only: field delimiter. Default semicolon. |
| datevConsultant | integer | no | datev only, required: Beraternummer 1001 to 9999999. |
| datevClient | integer | no | datev only, required: Mandantennummer 1 to 99999. |
| datevFiscalYearStart | string | no | datev only, required: start of the fiscal year as YYYY-MM-DD. The year of the document date is derived from it. |
| datevAccountLength | integer | no | datev only, required: Sachkontenlaenge 4 to 8. |
| datevDirection | string | no | datev only, required: incoming (expense) or outgoing (revenue). |
| datevCounterAccount | string | no | datev only, required: personal account (creditor or debtor), digits only. |
| datevLedgerAccount | string | no | datev only, required: expense or revenue account, digits only. |
| datevBookingKeys | string | no | datev only, optional: BU-Schluessel per VAT category and rate, for example S19=9,S7=8. |
| datevChartOfAccounts | string | no | datev only, optional: Sachkontenrahmen, for example 03 or 04. |
| datevLabel | string | no | datev only, optional: Bezeichnung, at most 30 characters. |
| datevDueDate | boolean | no | datev only, optional: write the due date into the DATEV field Faelligkeit. |
Use this when the user asks whether an attached or local invoice file is valid and you cannot pass the file itself. Open an upload field in the chat where the user chooses an invoice PDF or XML file. The file then goes straight to validate_invoice without passing through the model, so a PDF is checked as a whole, including its PDF/A-3 container. Use this when the user wants a file checked and this
No parameter schema on file.
Check whether the Electronic Invoice API is up and which rule set versions it currently runs. Calls GET /v1/health without an API key. Free, not billable, works without an account. B2B only. Use this before diagnosing a failing invoice call, but do not use it as proof that a specific API key or quota is valid.
No parameter schema on file.
Explain the plans, monthly quotas, rate limits, concurrency limits, billable status codes and body size limits of the Electronic Invoice API. Works without an API key and does not call the API. B2B only. Prices and monthly quotas are published on https://electronic-invoice.app/de/api/. Use this for commercial or quota questions, not for invoice validation.
No parameter schema on file.
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 Electronic Invoice API 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 93 / 100
Release 0.2.0 · scanned 7 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 score93
Findings0 threat · 0 capability
Capabilitymoderate
Coveragemanifest
Verificationnot in this report
Surface digest23aef87e5aef417b854006826e64382162ec352e328085c5c3692bb9d264169b
Score vectorthreat 100 → client 93
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| 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. moderate is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| validate_invoice | no tags | |
| generate_invoice | state-write | state-write: declares readOnlyHint: false |
| convert_invoice | state-write | state-write: declares readOnlyHint: false |
| extract_invoice | no tags | |
| open_invoice_check | no tags | |
| get_service_status | no tags | |
| get_pricing_and_limits | 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 digest23aef87e5aef417b
Scanned2026-11-07
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 0.2.0.
0.2.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 Electronic Invoice API 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.