# NormAPI (remote · normapi.com)

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

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

## Components

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

## Channel facts

- Endpoint: `https://normapi.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.3.1`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, 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.

- **Endpoint Security**: 11/100
  - TLS not yet verified: we couldn't open a connection to check the certificate.
  - Authorisation not yet verified: we couldn't confirm whether this endpoint requires it.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS not yet verified: we couldn't read the response headers to check for it.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 0/100
  - Transport check failed: declared streamable-http, but we couldn't connect to verify it.
- **Schema Quality & AI Usability**: 0/100
  - Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 0/100
  - Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- **Tool Safety**: 0/100
  - Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- **Capabilities**: 0/100
  - Capabilities not yet verified: we couldn't read the endpoint's capabilities.

**Unverified: 5 categories.** Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

## Install

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

NormAPI is a hosted endpoint at https://normapi.com/mcp, so there is nothing to install locally. 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 --transport http com-normapi-mcp 'https://normapi.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-normapi-mcp": {
      "url": "https://normapi.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-normapi-mcp": {
      "type": "http",
      "url": "https://normapi.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-normapi-mcp]
url = "https://normapi.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-normapi-mcp": {
      "type": "remote",
      "url": "https://normapi.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-normapi-mcp --url 'https://normapi.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-normapi-mcp:
    url: "https://normapi.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-normapi-mcp": {
      "Transport": "http",
      "Url": "https://normapi.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-normapi-mcp -t streamable-http -u 'https://normapi.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-normapi-mcp": {
      "type": "http",
      "url": "https://normapi.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## 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-05 (score 85, 0)

- [security regression] Endpoint reachability: reachable → unreachable
- [security regression] Stability: 0.83 → unverified
- [security regression] Authorization: partial → unverified
- [security regression] Tool safety: pass → unverified
- [security regression] TLS certificate: pass → unverified
- [security regression] HSTS header: pass → unverified
- [security regression] Transport: pass → fail
- [functional regression] Schema quality: 100 → unverified
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified

### 2026-11-03 (score 85, +1)

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

### 2026-11-01 (score 84, +1)

- [security] The server rewrote its instructions, which are the text every model session reads
- [functional] Server version: 1.3.0 → 1.3.1

### 2026-10-31 (score 83, 0)

- [security] The server rewrote its instructions, which are the text every model session reads
- [functional] Server version: 1.2.1 → 1.3.0
- [cosmetic] “generate_invoice” added an optional parameter “letterhead”

### 2026-10-30 (score 83, +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-10-29 (score 82, 0)

- [functional] Server version: 1.2.0 → 1.2.1

### 2026-10-28 (score 82, +3)

- [security] Tool “validate_invoice” rewrote its description, which is the text the model reads
- [security] Tool “parse_invoice” rewrote its description, which is the text the model reads
- [security] Tool “generate_invoice” rewrote its description, which is the text the model reads
- [functional improvement] Schema quality: 273 → 231
- [functional] The server now declares the “resources” capability
- [functional] First check of Schema quality: 100
- [functional] First check of Capabilities: pass
- [functional] Schema quality: excellent → good
- [functional] New resource “invoice-card”
- [cosmetic] “validate_invoice” added an optional parameter “file”
- [cosmetic] “parse_invoice” added an optional parameter “file”

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

## 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`: 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`: 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`: 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`: 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`: 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`: The rule set the document passed before it was returned
- `scenario`
- `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: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-normapi-mcp/normapi#diagnostics

## Score history

- 2026-11-05: 85
- 2026-11-04: 85
- 2026-11-03: 85
- 2026-11-02: 84
- 2026-11-01: 84
- 2026-10-31: 83
- 2026-10-30: 83
- 2026-10-29: 82
- 2026-10-28: 82
- 2026-10-27: 79
- 2026-10-26: 79
- 2026-10-25: 78
- 2026-10-24: 78
- 2026-10-23: 77
- 2026-10-22: 77
- 2026-10-21: 77
- 2026-10-20: 77
- 2026-10-19: 76
- 2026-10-18: 76
- 2026-10-17: 75
- 2026-10-16: 75
- 2026-10-15: 74
- 2026-10-14: 74
- 2026-10-13: 73
- 2026-10-12: 73
- 2026-10-10: 72

## 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 hosted endpoint (https://normapi.com/mcp).

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

NormAPI scores 85 out of 100 on VerifyMCP. 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.

### Does the NormAPI MCP server require authentication?

Its publisher declares no required credentials for NormAPI. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.

### Is the NormAPI MCP server still maintained?

NormAPI is still listed in the MCP registry, though our most recent checks did not reach this channel. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the NormAPI MCP server?

VerifyMCP ran 3 checks on NormAPI, covering HTTPS, DNSSEC and Transport. 8 items could not be completed, a gap on our side rather than a finding about NormAPI: TLS certificate, Authorization, HSTS header, Schema quality and 4 more. 5 categories score 0 for that reason, because we only credit what we can confirm. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://normapi.com/mcp
- Website: https://normapi.com/en/docs/mcp
- Changelog RSS feed: https://verifymcp.io/servers/com-normapi-mcp/normapi.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-normapi-mcp/normapi/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-normapi-mcp/normapi.json
- HTML version of this page: https://verifymcp.io/servers/com-normapi-mcp/normapi