Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Conformo e-invoicing

NPM · @CONFORMO/MCP-SERVER

Create and check EU e-invoices (XRechnung, ZUGFeRD, Factur-X, Peppol) locally. Free, no API key.

+4 this week 82 Trust /100

Last scanned (19 hours ago)

Scores higher than 71% of npm servers

Category Finance and Payments

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security81
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
  • No install/post-install scripts declared.Pass
  • 39 of 137 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to arsalmurad/conformo). View diagnostics → Pass
  • Clear OSI-approved license (Apache-2.0).Pass
  • Actively maintained (last published 8 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability64
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 2256 tokens (~322/item across 7 items; 7 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management57
  • Stability observed for 17 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (16)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 21 Nov 26 +1

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

  • 19 Nov 26 +1

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

  • 17 Nov 26 +1

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

  • 15 Nov 26 +1

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

  • 13 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 12 Nov 26 −4
    • Malware scan: pass → unverified ▼ security
    • Provenance: fail → pass ▲ security
    • The attested source repository moved: arsalmurad/conformo security
    • Package version: 0.2.4 → 0.2.5 functional
  • 11 Nov 26 +16
    • Malware scan: unverified → pass ▲ security
  • 10 Nov 26 −15
    • Malware scan: pass → unverified ▼ security
    • Package version: 0.2.3 → 0.2.4 functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Analysed npm/@conformo/mcp-server@0.2.5

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo arsalmurad/conformo
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/arsalmurad/conformo/.github/workflows/release.yml@refs/tags/v0.2.5
Rekor log index 3835434537
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:4434673f38f0cbce8eb3f474d241c542d0e416ffb881932c2eee0f82b671a178a07cdf3f6a8092127915849e8e8ac7f4dd47869cf22010ce00752a82c

Background: How many MCP packages publish verified provenance →

Vulnerabilities 1 finding
ID CVE Severity Vector Fix available
GHSA-mrhx-c7xc-m3w5 CVE-2023-54404 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes

Background: What a vulnerability scan can and cannot prove →

Dependencies 137 packages
Packages resolved 137
Stale 39
No linked repository 1
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 7 exposed · ~2,113 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
convert_invoice ~417

Rewrites an existing e-invoice in another syntax, for example CII to UBL, or plain EN 16931 to XRechnung or Peppol BIS. Use it when you already hold an invoice document. To build one from data use create_invoice; to get a PDF from XML use parse_invoice, then create_invoice_pdf. Accepts XML or a Factur-X / ZUGFeRD PDF. Nothing is invented: a target such as XRechnung may need data the source lacks, so read `warnings` and run validate_invoice on the result. A document it cannot read comes back as an error result with the reason. Runs locally; nothing is sent anywhere.

NameTypeReqDescription
pdfBase64string–A Factur-X / ZUGFeRD PDF/A-3 as base64; the embedded XML is used. Provide this OR xml.
tostringyesOutput syntax. "cii" = UN/CEFACT CII, EN 16931 (Factur-X / ZUGFeRD EN 16931 profile, a.k.a. COMFORT); "cii-extended" = UN/CEFACT CII declared as Factur-X / ZUGFeRD EXTENDED (EN 16931 content only; no…
xmlstring–The invoice as XML text (CII, UBL Invoice/CreditNote, XRechnung, Peppol BIS). Provide this OR pdfBase64.
NameTypeReqDescription
formatstringyesThe syntax that was written.
fromstringyesSyntax of the source: cii, ubl-invoice or ubl-credit-note.
warningsarrayyesNon-fatal findings, e.g. data the target requires that the source does not have.
xmlstringyesThe invoice in the target syntax.

No examples provided.

create_invoice ~431

Builds e-invoice XML from structured invoice data: EN 16931 CII or UBL, XRechnung (CII or UBL) or Peppol BIS Billing 3.0, chosen by `format`. Use it for a new invoice that software will read. For a printable PDF with the XML inside, use create_invoice_pdf; to change the syntax of an invoice you already have, use convert_invoice. Pass `invoice` as a JSON object, not a string. Every money field ends in "Minor" and is an integer in minor units (EUR 12.34 = 1234); totals and the VAT breakdown are computed, so do not send them. If fields are missing or wrong it returns an error listing every problem (path, BT id, message) and produces nothing; fix them all and call again. It runs locally and does not send the invoice anywhere. It does not run the official rule sets: call validate_invoice on the XML before it goes out.

NameTypeReqDescription
formatstringyesOutput syntax. "cii" = UN/CEFACT CII, EN 16931 (Factur-X / ZUGFeRD EN 16931 profile, a.k.a. COMFORT); "cii-extended" = UN/CEFACT CII declared as Factur-X / ZUGFeRD EXTENDED (EN 16931 content only; no…
invoiceobjectyesThe invoice. Required: number, issueDate, currency, seller, buyer, lines.
NameTypeReqDescription
formatstringyesThe syntax that was written.
warningsarrayyesNon-fatal findings, e.g. a missing XRechnung precondition.
xmlstringyesThe e-invoice XML, ready to send or to pass to validate_invoice.

No examples provided.

create_invoice_pdf ~324

Builds a Factur-X / ZUGFeRD invoice: a PDF/A-3b page a person can read, with the EN 16931 XML embedded for software. Use it when the invoice goes to a person or by e-mail. For XML only, such as an XRechnung uploaded to a German public-sector portal, use create_invoice. Takes the same `invoice` object as create_invoice, money in integer minor units. `language` changes only the printed labels; the embedded XML is identical in every language. By default the PDF comes back as base64, which can be large; pass `outputPath` to write the file instead. Writing stays inside the server's working directory and never replaces an existing file unless `overwrite` is true. The same input always gives the same bytes, and nothing is sent anywhere. Check the result with validate_invoice (pass pdfBase64).

NameTypeReqDescription
invoiceobjectyesThe invoice. Required: number, issueDate, currency, seller, buyer, lines.
languagestring–Language of the printed labels: en, de or fr. Default en. Presentation only; the XML does not change.
outputPathstring–Write the PDF here instead of returning base64. Relative to the server working directory; must end in .pdf.
overwriteboolean–Allow replacing an existing file at outputPath. Default false.
profilestring–Factur-X / ZUGFeRD profile. Default en16931.
templatestring–Page layout. Default classic.
NameTypeReqDescription
byteLengthnumberyesSize of the PDF in bytes.
conformanceLevelstringyesConformance level declared in the PDF metadata, e.g. EN 16931.
outputPathstring–Absolute path written, when outputPath was given.
pdfBase64string–The PDF, base64. Absent when outputPath was given.
profilestringyesThe Factur-X / ZUGFeRD profile written.
sha256stringyesSHA-256 of the PDF bytes, hex; equal for equal input.
warningsarrayyesNon-fatal findings about the invoice data.
xmlFilenamestringyesName of the embedded XML attachment.

No examples provided.

explain_validation_rule ~173

Explains one validation rule id, such as BR-CO-15, BR-DE-15, PEPPOL-EN16931-R003 or BR-FR-05: the publisher's official wording from the compiled rule sets and, where available, a plain-language summary, the reason for the rule and how to fix it. Use it after validate_invoice reports a rule you need to explain or fix, or when a user asks what a rule means. It does not check an invoice; call validate_invoice for that. An unknown id is not an error: the result has `found` false and an empty `official` list; say so and do not guess. Reads the bundled rule sets; no network.

NameTypeReqDescription
ruleIdstringyesThe rule id, e.g. BR-CO-15.
NameTypeReqDescription
foundbooleanyesFalse when no compiled rule set knows this id.
officialarrayyesOfficial wording, one entry per rule set that defines the id.
plainLanguageobject–Plain-language explanation, when one exists for this rule.
ruleIdstringyesThe rule id as looked up.

No examples provided.

get_country_requirements ~179

Looks up the e-invoicing rules for one country in a sourced dataset: B2G and B2B mandates for issuing and receiving, start dates, turnover thresholds, required formats and official sources. Use it before create_invoice to decide which format a buyer in that country needs, or to answer when a mandate applies. It says nothing about a specific invoice; use validate_invoice to check one. Covers BE, DE, ES, FR, IT, NL, PL. `conformoSupport` says per format whether this server can create, read and validate it. Entries marked unverified are not confirmed from an official source; say so. Information, not legal advice. Reads a bundled dataset; no network.

NameTypeReqDescription
countrystringyesISO 3166-1 alpha-2 country code, e.g. DE, FR.
NameTypeReqDescription
conformoSupportobjectyesPer required format, what this server can do with it.
countrystringyesISO 3166-1 alpha-2 code of the country returned.

No examples provided.

parse_invoice ~227

Reads an e-invoice (CII, UBL, XRechnung or Peppol XML, or a Factur-X / ZUGFeRD PDF) into the structured invoice object that create_invoice accepts, with money in integer minor units. Use it to answer questions about a received invoice, to edit one, or to re-issue it with create_invoice. It does not check any rules, so use validate_invoice for that, and convert_invoice to change syntax directly. For a PDF, `visibleTotals` shows whether the totals printed on the page match the embedded XML, which exposes a tampered or mismatched PDF. A document it cannot read comes back as an error result with the reason. Runs locally.

NameTypeReqDescription
pdfBase64string–A Factur-X / ZUGFeRD PDF/A-3 as base64; the embedded XML is used. Provide this OR xml.
xmlstring–The invoice as XML text (CII, UBL Invoice/CreditNote, XRechnung, Peppol BIS). Provide this OR pdfBase64.
NameTypeReqDescription
embeddedFilenamestring–PDF only: name of the embedded XML that was read.
formatstringyesSyntax of the source document.
invoiceobjectyesThe Invoice object, in the shape of the create_invoice input schema.
originstringyesWhether the input was XML or a PDF.
visibleTotalsobject–PDF only: comparison of the printed totals with the embedded XML.

No examples provided.

validate_invoice ~362

Checks an e-invoice against the official rule sets on this machine: the XSD, the EN 16931 Schematron from CEN, and the KoSIT XRechnung or Peppol BIS rules when the document declares them. Use it before sending an invoice you created and when you receive one. To read the invoice's data use parse_invoice; to explain one failed rule in depth use explain_validation_rule. Accepts XML or a Factur-X / ZUGFeRD PDF, whose embedded XML is checked; syntax and profile are detected from the document. A `valid` result means the listed `ruleSets` passed, not that a tax authority or buyer will accept the invoice, so report which rule sets ran and never claim more. Each failure carries the publisher's message and, for common rules, a plain-language fix. Input that is not an invoice comes back as an error result, not as invalid. The check runs offline; nothing is uploaded.

NameTypeReqDescription
countrystring–Add a country layer: "FR" runs the French CTC rules (CII only); "DE" reports whether the profile is acceptable for German B2B (MINIMUM and BASIC WL are not).
pdfBase64string–A Factur-X / ZUGFeRD PDF/A-3 as base64; the embedded XML is used. Provide this OR xml.
profilestring–Force the rule set instead of reading it from BT-24.
xmlstring–The invoice as XML text (CII, UBL Invoice/CreditNote, XRechnung, Peppol BIS). Provide this OR pdfBase64.
xsdboolean–Run XSD validation too. Default true.
NameTypeReqDescription
advisoriesarrayyesWarning or info rules that fired; they do not make the invoice invalid.
detectedobjectyesWhat the document declares about itself.
embeddedFilenamestring–PDF only: name of the embedded XML that was checked.
failuresarrayyesError-level rules that failed; any entry makes valid false.
firedCountnumberyesSchematron rules that fired across all rule sets.
noticesarrayyesFindings about the document that are not Schematron rules, e.g. an unrecognised profile, or (with country DE) a profile not acceptable for German B2B. An error-level notice makes valid false.
originstringyesWhether the input was XML or a PDF.
ruleSetsarrayyesExactly the rule sets that ran. Report these; do not claim checks that are not listed.
summaryobjectyesThe verdict in numbers, with Conformo checks counted apart from the official rule sets.
validbooleanyesTrue only when no error-level rule failed, the XSD did not fail, and no error-level notice was raised.
xsdobjectyesXML Schema check.

No examples provided.

Install

How do I install the Conformo e-invoicing MCP server?

Conformo e-invoicing runs locally as an npm package, launched with npx -y @conformo/mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @conformo/mcp-server

# add to Claude Code
claude mcp add arsalmurad-conformo -- npx -y @conformo/mcp-server
Common questions

What is the Conformo e-invoicing MCP server?

Conformo e-invoicing is an MCP server listed in the public MCP registry as io.github.arsalmurad/conformo. Create and check EU e-invoices (XRechnung, ZUGFeRD, Factur-X, Peppol) locally. Free, no API key. This page covers its npm package (@conformo/mcp-server).

Is the Conformo e-invoicing MCP server safe to use?

Conformo e-invoicing scores 82 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 21 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 Conformo e-invoicing MCP server expose?

Conformo e-invoicing exposes 7 tools: create_invoice, create_invoice_pdf, validate_invoice, convert_invoice, parse_invoice, and 2 more. Their descriptions and schemas cost roughly 2,113 tokens of context every time the server is loaded.

Is the Conformo e-invoicing MCP server still maintained?

Conformo e-invoicing is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the Conformo e-invoicing MCP server under?

Conformo e-invoicing declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

What did VerifyMCP test on the Conformo e-invoicing MCP server?

VerifyMCP ran 16 checks on Conformo e-invoicing, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.