# NormAPI (npm · @normapi/mcp)

Validate, generate and read German e-invoices (XRechnung, ZUGFeRD) against the official KoSIT rules.

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

## Components

- remote · `normapi.com`: 85/100, [markdown](https://verifymcp.io/servers/com-normapi-mcp/normapi.md), [page](https://verifymcp.io/servers/com-normapi-mcp/normapi)
- npm · `@normapi/mcp`: 75/100 (this document), [markdown](https://verifymcp.io/servers/com-normapi-mcp/normapi-mcp.md), [page](https://verifymcp.io/servers/com-normapi-mcp/normapi-mcp)

## Channel facts

- Registry: `npm`
- Package: `@normapi/mcp`
- Version: `1.3.1`
- 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-05.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 0 of 4 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 19/100
  - Repository check failed: no source repository is declared.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 3 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 75/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1236 tokens (~247/item across 5 items; 4 tools + 1 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 73/100
  - Stability observed for 22 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 98/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 94% 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).
  - Supports UI / widget rendering.

## Install

### How do I install the NormAPI MCP server?

NormAPI runs locally as an npm package, launched with npx -y @normapi/mcp. 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 com-normapi-mcp -- npx -y @normapi/mcp
```

### Cursor

```json
{
  "mcpServers": {
    "com-normapi-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@normapi/mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-normapi-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@normapi/mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add com-normapi-mcp -- npx -y @normapi/mcp
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add com-normapi-mcp --command npx --arg -y --arg @normapi/mcp
```

### Hermes

```yaml
mcp_servers:
  com-normapi-mcp:
    command: "npx"
    args: ["-y", "@normapi/mcp"]
```

### Netclaw

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

### Vellum

```bash
assistant mcp add com-normapi-mcp -t stdio -c npx -a -y @normapi/mcp
```

### Other

```json
{
  "mcpServers": {
    "com-normapi-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@normapi/mcp"
      ]
    }
  }
}
```

## 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-03 (score 75, +1)

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

### 2026-11-01 (score 74, +16)

- [security regression] Tool safety: pass → unverified
- [security regression] Stability: 0.57 → unverified
- [security improvement] Malware scan: unverified → pass
- [functional regression] Schema quality: 100 → unverified
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional] Package version: 1.3.0 → 1.3.1

### 2026-10-31 (score 58, −15)

- [security regression] Malware scan: pass → unverified
- [functional regression] Security disclosure: fail → unverified
- [functional] Package version: 1.2.1 → 1.3.0

### 2026-10-30 (score 73, +1)

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

### 2026-10-29 (score 72, +2)

- [security regression] Tool safety: pass → unverified
- [security regression] Stability: 0.47 → unverified
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional improvement] Schema quality: 273 → 231
- [functional improvement] Schema quality: unverified → 100
- [functional] First check of Capabilities: pass
- [functional] Schema quality: excellent → good
- [functional] Package version: 1.2.0 → 1.2.1

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

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

### 2026-10-26 (score 69, +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-10-25 (score 68, 0)

- [functional] Package version: 1.0.1 → 1.2.0

## MCP tools (4)

### `validate_invoice` (~200 tokens)

Validate an e-invoice

Check an XRechnung (UBL or CII XML) or a ZUGFeRD/Factur-X PDF against the official KoSIT rules. Returns the verdict, the rule set version, and every finding; each business-rule finding comes with a plain-language meaning, cause and fix. Send the XML as text in `xml`, the PDF base64-encoded in `pdfBase64`, or an uploaded file in `file` — exactly one. No account needed; 5 MB at most.

Input parameters:

- `file` (object): An uploaded file, handed over as a download link
- `fileName` (string): The file name, echoed into the report only
- `language` (string): Language of the plain-language explanations: en (default) or de
- `pdfBase64` (string): A ZUGFeRD or Factur-X PDF, base64-encoded
- `xml` (string): The invoice XML as text

Output parameters:

- `acceptable` (boolean): The verdict: true when no ERROR-severity finding remains
- `businessRulesEvaluated` (boolean): False when a schema failure stopped the run, so an empty list is not a pass
- `errors` (integer)
- `findings` (array)
- `rulesetVersion` (string): The KoSIT rule set release that produced the verdict
- `scenario` (string|null): The rules that judged the document; null means nothing was checked
- `schemaValid` (boolean)
- `warnings` (integer)

### `parse_invoice` (~262 tokens)

Read an e-invoice into data

Read a received e-invoice — XRechnung or any EN 16931 invoice as UBL or CII XML, or a ZUGFeRD/Factur-X PDF — into structured data. `invoice` is in exactly the shape generate_invoice takes (fields the document lacks are left out); `stated` has the totals, the VAT breakdown and each line net as the document states them, as exact decimal strings; `notMapped` lists by path every value of the document the data does not carry. Send the XML as text in `xml`, the PDF base64-encoded in `pdfBase64`, or an uploaded file in `file` — exactly one. `validate: true` adds the KoSIT verdict. No account needed; 5 MB at most.

Input parameters:

- `file` (object): An uploaded file, handed over as a download link
- `language` (string): Language of the plain-language explanations: en (default) or de
- `pdfBase64` (string): A ZUGFeRD or Factur-X PDF, base64-encoded
- `validate` (boolean): Also check the invoice against the KoSIT rules and return the verdict
- `xml` (string): The invoice XML as text

Output parameters:

- `businessProcess` (string|null): BT-23
- `documentKind` (string): UBL says so by its root element; in CII the type code (BT-3) decides
- `invoice` (object): The invoice in the shape generate_invoice takes, with what the document lacks left out. Amounts are numbers; the exact decimals of the totals are in `stated`.
- `missingForGeneration` (array): What generate_invoice would refuse in `invoice`, field by field; empty when ready
- `notMapped` (array): Every value of the document `invoice` and `stated` do not carry: a path without positions and how often. Empty for an invoice NormAPI generated.
- `profile`: The generate_invoice profile that declares exactly this BT-24; null for any other declaration
- `readyToGenerate` (boolean): Whether `invoice` passes generate_invoice's schema as it is
- `source` (object)
- `specificationId` (string|null): BT-24, the rules the document declares
- `stated` (object)
- `syntax` (string)
- `validation`: With validate: true, the verdict as validate_invoice returns it; otherwise null

### `generate_invoice` (~266 tokens)

Generate an e-invoice

Produce an e-invoice as `ubl` or `cii` XML or a ZUGFeRD hybrid PDF (`zugferd`) from invoice data: an XRechnung for a public-sector buyer (profile `xrechnung`, the default), a plain EN 16931 invoice for a business (profile `en16931`). Totals are computed server-side in decimal arithmetic, and the document is validated against the official rules before it is returned. Data the rules do not permit is refused with the broken rules and how to fix each. Needs the user's NormAPI account; each generated document counts against that account's monthly allowance.

Input parameters:

- `invoice` (object, required)
- `language` (string): Language of the plain-language explanations: en (default) or de
- `letterhead` (string): zugferd only: 'none' for NormAPI's standard layout instead of the account's letterhead
- `profile` (string): xrechnung for public-sector buyers: it requires buyerReference (the Leitweg-ID), a seller contact and both electronic addresses. en16931 for businesses (§ 14 UStG accepts it), without those.
- `syntax` (string): ubl or cii for XML, zugferd for the PDF/A-3 with the invoice embedded

Output parameters:

- `bytes` (integer)
- `fileName` (string)
- `letterhead` (string|null): The id of the account's letterhead the ZUGFeRD PDF is printed on; null when it is not, for XML, and for an account without a letterhead
- `letterheadSkipped` (string|null): Why the account's letterhead was left out: requested, customer-call, seller-mismatch, needs-confirmation, recheck-failed or render-failed; null when it was used, for XML, and for an account without a…
- `mimeType` (string)
- `profile` (string): xrechnung for public-sector buyers: it requires buyerReference (the Leitweg-ID), a seller contact and both electronic addresses. en16931 for businesses (§ 14 UStG accepts it), without those.
- `rulesetVersion` (string|null): The rule set the document passed before it was returned
- `scenario` (string|null)
- `syntax` (string)
- `xml` (string): The XML document; absent for the ZUGFeRD PDF, which is the attached resource

### `explain_rule` (~130 tokens)

Explain an e-invoice rule

Explain one EN 16931 / XRechnung / Peppol business rule by its code (e.g. BR-DE-15, BR-CO-10, PEPPOL-EN16931-R010): what it requires, why invoices typically break it, and how to fix it, with a link to the full page. Case does not matter. Schema findings (cvc-*) have no explanation.

Input parameters:

- `code` (string, required): The rule code, e.g. BR-DE-15
- `language` (string): Language of the plain-language explanations: en (default) or de

Output parameters:

- `cause` (string)
- `code` (string)
- `fix` (string)
- `language` (string)
- `meaning` (string)
- `url` (string)

## Diagnostics

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

## Score history

- 2026-11-05: 75
- 2026-11-04: 75
- 2026-11-03: 75
- 2026-11-02: 74
- 2026-11-01: 74
- 2026-10-31: 58
- 2026-10-30: 73
- 2026-10-29: 72
- 2026-10-28: 70
- 2026-10-27: 69
- 2026-10-26: 69
- 2026-10-25: 68
- 2026-10-24: 68
- 2026-10-23: 52
- 2026-10-22: 52
- 2026-10-21: 52
- 2026-10-20: 64
- 2026-10-19: 64
- 2026-10-18: 64
- 2026-10-17: 64
- 2026-10-16: 64
- 2026-10-15: 64
- 2026-10-14: 64
- 2026-10-13: 34
- 2026-10-12: 34
- 2026-10-11: 34

## Common questions

### What is the NormAPI MCP server?

NormAPI is an MCP server listed in the public MCP registry as com.normapi/mcp. Validate, generate and read German e-invoices (XRechnung, ZUGFeRD) against the official KoSIT rules. This page covers its npm package (@normapi/mcp).

### Is the NormAPI MCP server safe to use?

NormAPI scores 75 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. 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 NormAPI MCP server expose?

NormAPI exposes 4 tools: validate_invoice, parse_invoice, generate_invoice, explain_rule. Their descriptions and schemas cost roughly 858 tokens of context every time the server is loaded.

### Is the NormAPI MCP server still maintained?

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

### What licence is the NormAPI MCP server under?

NormAPI declares the MIT 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 NormAPI MCP server?

VerifyMCP ran 17 checks on NormAPI, covering Malware scan, Known CVEs, Install scripts, Dependency health and 13 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/@normapi/mcp
- Socket report: https://socket.dev/npm/package/@normapi/mcp
- Website: https://normapi.com/en/docs/mcp
- Changelog RSS feed: https://verifymcp.io/servers/com-normapi-mcp/normapi-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-normapi-mcp/normapi-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-normapi-mcp/normapi-mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-normapi-mcp/normapi-mcp