# Conformo e-invoicing (npm · @conformo/mcp-server)

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

- Trust score: 82/100 (high trust)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- npm · `@conformo/mcp-server`: 82/100 (this document), [markdown](https://verifymcp.io/servers/arsalmurad-conformo/conformo-mcp-server.md), [page](https://verifymcp.io/servers/arsalmurad-conformo/conformo-mcp-server)

## Channel facts

- Registry: `npm`
- Package: `@conformo/mcp-server`
- Version: `0.2.5`
- Transport: `stdio`

## Trust breakdown

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. 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-21.

- **Supply Chain Security**: 81/100
  - No malware found by supply-chain analysis.
  - CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available.
  - No install/post-install scripts declared.
  - 39 of 137 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 100/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to arsalmurad/conformo).
  - Clear OSI-approved license (Apache-2.0).
  - Actively maintained (last published 8 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 64/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 57/100
  - Stability observed for 17 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.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 8 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 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.

### Claude

```bash
claude mcp add arsalmurad-conformo -- npx -y @conformo/mcp-server
```

### Cursor

```json
{
  "mcpServers": {
    "arsalmurad-conformo": {
      "command": "npx",
      "args": [
        "-y",
        "@conformo/mcp-server"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "arsalmurad-conformo": {
      "command": "npx",
      "args": [
        "-y",
        "@conformo/mcp-server"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add arsalmurad-conformo -- npx -y @conformo/mcp-server
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "arsalmurad-conformo": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@conformo/mcp-server"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add arsalmurad-conformo --command npx --arg -y --arg @conformo/mcp-server
```

### Hermes

```yaml
mcp_servers:
  arsalmurad-conformo:
    command: "npx"
    args: ["-y", "@conformo/mcp-server"]
```

### Netclaw

```json
{
  "McpServers": {
    "arsalmurad-conformo": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@conformo/mcp-server"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add arsalmurad-conformo -t stdio -c npx -a -y @conformo/mcp-server
```

### Other

```json
{
  "mcpServers": {
    "arsalmurad-conformo": {
      "command": "npx",
      "args": [
        "-y",
        "@conformo/mcp-server"
      ]
    }
  }
}
```

## 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-21 (score 82, +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.

### 2026-11-19 (score 81, +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.

### 2026-11-17 (score 80, +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.

### 2026-11-15 (score 79, +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.

### 2026-11-13 (score 78, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-11-12 (score 63, −4)

- [security regression] Malware scan: pass → unverified
- [security improvement] Provenance: fail → pass
- [security] The attested source repository moved: arsalmurad/conformo
- [functional] Package version: 0.2.4 → 0.2.5

### 2026-11-11 (score 67, +16)

- [security improvement] Malware scan: unverified → pass

### 2026-11-10 (score 51, −15)

- [security regression] Malware scan: pass → unverified
- [functional] Package version: 0.2.3 → 0.2.4

## MCP tools (7)

### `create_invoice` (~431 tokens)

Create an e-invoice (XML)

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.

Input parameters:

- `format` (string, required): Output 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…
- `invoice` (object, required): The invoice. Required: number, issueDate, currency, seller, buyer, lines.

Output parameters:

- `format` (string): The syntax that was written.
- `warnings` (array): Non-fatal findings, e.g. a missing XRechnung precondition.
- `xml` (string): The e-invoice XML, ready to send or to pass to validate_invoice.

### `create_invoice_pdf` (~324 tokens)

Create a Factur-X / ZUGFeRD PDF

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).

Input parameters:

- `invoice` (object, required): The invoice. Required: number, issueDate, currency, seller, buyer, lines.
- `language` (string): Language of the printed labels: en, de or fr. Default en. Presentation only; the XML does not change.
- `outputPath` (string): Write the PDF here instead of returning base64. Relative to the server working directory; must end in .pdf.
- `overwrite` (boolean): Allow replacing an existing file at outputPath. Default false.
- `profile` (string): Factur-X / ZUGFeRD profile. Default en16931.
- `template` (string): Page layout. Default classic.

Output parameters:

- `byteLength` (number): Size of the PDF in bytes.
- `conformanceLevel` (string): Conformance level declared in the PDF metadata, e.g. EN 16931.
- `outputPath` (string): Absolute path written, when outputPath was given.
- `pdfBase64` (string): The PDF, base64. Absent when outputPath was given.
- `profile` (string): The Factur-X / ZUGFeRD profile written.
- `sha256` (string): SHA-256 of the PDF bytes, hex; equal for equal input.
- `warnings` (array): Non-fatal findings about the invoice data.
- `xmlFilename` (string): Name of the embedded XML attachment.

### `validate_invoice` (~362 tokens)

Validate an e-invoice

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.

Input parameters:

- `country` (string): 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).
- `pdfBase64` (string): A Factur-X / ZUGFeRD PDF/A-3 as base64; the embedded XML is used. Provide this OR xml.
- `profile` (string): Force the rule set instead of reading it from BT-24.
- `xml` (string): The invoice as XML text (CII, UBL Invoice/CreditNote, XRechnung, Peppol BIS). Provide this OR pdfBase64.
- `xsd` (boolean): Run XSD validation too. Default true.

Output parameters:

- `advisories` (array): Warning or info rules that fired; they do not make the invoice invalid.
- `detected` (object): What the document declares about itself.
- `embeddedFilename` (string): PDF only: name of the embedded XML that was checked.
- `failures` (array): Error-level rules that failed; any entry makes valid false.
- `firedCount` (number): Schematron rules that fired across all rule sets.
- `notices` (array): Findings 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.
- `origin` (string): Whether the input was XML or a PDF.
- `ruleSets` (array): Exactly the rule sets that ran. Report these; do not claim checks that are not listed.
- `summary` (object): The verdict in numbers, with Conformo checks counted apart from the official rule sets.
- `valid` (boolean): True only when no error-level rule failed, the XSD did not fail, and no error-level notice was raised.
- `xsd` (object): XML Schema check.

### `convert_invoice` (~417 tokens)

Convert an e-invoice between syntaxes

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.

Input parameters:

- `pdfBase64` (string): A Factur-X / ZUGFeRD PDF/A-3 as base64; the embedded XML is used. Provide this OR xml.
- `to` (string, required): Output 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…
- `xml` (string): The invoice as XML text (CII, UBL Invoice/CreditNote, XRechnung, Peppol BIS). Provide this OR pdfBase64.

Output parameters:

- `format` (string): The syntax that was written.
- `from` (string): Syntax of the source: cii, ubl-invoice or ubl-credit-note.
- `warnings` (array): Non-fatal findings, e.g. data the target requires that the source does not have.
- `xml` (string): The invoice in the target syntax.

### `parse_invoice` (~227 tokens)

Parse an e-invoice into JSON

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.

Input parameters:

- `pdfBase64` (string): A Factur-X / ZUGFeRD PDF/A-3 as base64; the embedded XML is used. Provide this OR xml.
- `xml` (string): The invoice as XML text (CII, UBL Invoice/CreditNote, XRechnung, Peppol BIS). Provide this OR pdfBase64.

Output parameters:

- `embeddedFilename` (string): PDF only: name of the embedded XML that was read.
- `format` (string): Syntax of the source document.
- `invoice` (object): The Invoice object, in the shape of the create_invoice input schema.
- `origin` (string): Whether the input was XML or a PDF.
- `visibleTotals` (object): PDF only: comparison of the printed totals with the embedded XML.

### `get_country_requirements` (~179 tokens)

E-invoicing requirements for a country

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.

Input parameters:

- `country` (string, required): ISO 3166-1 alpha-2 country code, e.g. DE, FR.

Output parameters:

- `conformoSupport` (object): Per required format, what this server can do with it.
- `country` (string): ISO 3166-1 alpha-2 code of the country returned.

### `explain_validation_rule` (~173 tokens)

Explain a validation rule

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.

Input parameters:

- `ruleId` (string, required): The rule id, e.g. BR-CO-15.

Output parameters:

- `found` (boolean): False when no compiled rule set knows this id.
- `official` (array): Official wording, one entry per rule set that defines the id.
- `plainLanguage` (object): Plain-language explanation, when one exists for this rule.
- `ruleId` (string): The rule id as looked up.

## Diagnostics

Captured diagnostic sections: Provenance, Vulnerabilities, Dependencies. The full working is on the page: https://verifymcp.io/servers/arsalmurad-conformo/conformo-mcp-server#diagnostics

## Score history

- 2026-11-21: 82
- 2026-11-20: 81
- 2026-11-19: 81
- 2026-11-18: 80
- 2026-11-17: 80
- 2026-11-16: 79
- 2026-11-15: 79
- 2026-11-14: 78
- 2026-11-13: 78
- 2026-11-12: 63
- 2026-11-11: 67
- 2026-11-10: 51
- 2026-11-09: 66
- 2026-11-08: 65
- 2026-11-07: 65
- 2026-11-06: 64
- 2026-11-05: 64
- 2026-11-04: 63

## 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.

## Links

- npm package: https://www.npmjs.com/package/@conformo/mcp-server
- Socket report: https://socket.dev/npm/package/@conformo/mcp-server
- Repository: https://github.com/arsalmurad/conformo
- Website: https://conformo-docs.vercel.app/
- Changelog RSS feed: https://verifymcp.io/servers/arsalmurad-conformo/conformo-mcp-server.xml
- Changelog JSON feed: https://verifymcp.io/servers/arsalmurad-conformo/conformo-mcp-server/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/arsalmurad-conformo/conformo-mcp-server.json
- HTML version of this page: https://verifymcp.io/servers/arsalmurad-conformo/conformo-mcp-server
