NormAPI
NPM · @NORMAPI/MCP · 2 COMPONENTS
Validate, generate and read German e-invoices (XRechnung, ZUGFeRD) against the official KoSIT rules.
Available components
Last scanned (12 hours ago)
Scores higher than 51% of npm servers
Category Finance and Payments
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 Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 0 of 4 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency19
- Repository check failed: no source repository is declared. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 3 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability75
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management73
- Stability observed for 22 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage98
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 94% of tool parameters carry a description.Partial
- 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
- Supports UI / widget rendering.Pass
Checks we ran (17)
- 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
- Capabilities
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 →
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.
- 3 Nov 26 +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.
- 1 Nov 26 +16
- Tool safety: pass → unverified ▼ security
- Stability: 0.57 → unverified ▼ security
- Malware scan: unverified → pass ▲ security
- Schema quality: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Package version: 1.3.0 → 1.3.1 functional
- 31 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- Security disclosure: fail → unverified ▼ functional
- Package version: 1.2.1 → 1.3.0 functional
- 30 Oct 26 +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.
- 29 Oct 26 +2
- Tool safety: pass → unverified ▼ security
- Stability: 0.47 → unverified ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Schema quality: 273 → 231 ▲ functional
- Schema quality: unverified → 100 ▲ functional
- First check of Capabilities: pass functional
- Schema quality: excellent → good functional
- Package version: 1.2.0 → 1.2.1 functional
- 28 Oct 26 +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.
- 26 Oct 26 +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.
- 25 Oct 26 0
- Package version: 1.0.1 → 1.2.0 functional
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 5 Nov 2026 · Analysed npm/@normapi/mcp@1.3.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 4 packages
| Packages resolved | 4 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
explain_rule Explain an e-invoice rule ~130
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.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | The rule code, e.g. BR-DE-15 |
| language | string | – | Language of the plain-language explanations: en (default) or de |
| Name | Type | Req | Description |
|---|---|---|---|
| cause | string | yes | – |
| code | string | yes | – |
| fix | string | yes | – |
| language | string | yes | – |
| meaning | string | yes | – |
| url | string | yes | – |
No examples provided.
generate_invoice Generate an e-invoice ~266
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.
| Name | Type | Req | Description |
|---|---|---|---|
| invoice | object | yes | – |
| 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 |
| Name | Type | Req | Description |
|---|---|---|---|
| bytes | integer | yes | – |
| fileName | string | yes | – |
| letterhead | string|null | yes | 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 | yes | 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 | yes | – |
| profile | string | yes | 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 | yes | The rule set the document passed before it was returned |
| scenario | string|null | yes | – |
| syntax | string | yes | – |
| xml | string | – | The XML document; absent for the ZUGFeRD PDF, which is the attached resource |
No examples provided.
parse_invoice Read an e-invoice into data ~262
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 |
| Name | Type | Req | Description |
|---|---|---|---|
| businessProcess | string|null | yes | BT-23 |
| documentKind | string | yes | UBL says so by its root element; in CII the type code (BT-3) decides |
| invoice | object | yes | 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 | yes | What generate_invoice would refuse in `invoice`, field by field; empty when ready |
| notMapped | array | yes | 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 | – | yes | The generate_invoice profile that declares exactly this BT-24; null for any other declaration |
| readyToGenerate | boolean | yes | Whether `invoice` passes generate_invoice's schema as it is |
| source | object | yes | – |
| specificationId | string|null | yes | BT-24, the rules the document declares |
| stated | object | yes | – |
| syntax | string | yes | – |
| validation | – | yes | With validate: true, the verdict as validate_invoice returns it; otherwise null |
No examples provided.
validate_invoice Validate an e-invoice ~200
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 |
| Name | Type | Req | Description |
|---|---|---|---|
| acceptable | boolean | yes | The verdict: true when no ERROR-severity finding remains |
| businessRulesEvaluated | boolean | yes | False when a schema failure stopped the run, so an empty list is not a pass |
| errors | integer | yes | – |
| findings | array | yes | – |
| rulesetVersion | string | yes | The KoSIT rule set release that produced the verdict |
| scenario | string|null | yes | The rules that judged the document; null means nothing was checked |
| schemaValid | boolean | yes | – |
| warnings | integer | yes | – |
No examples provided.
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.
npm · @normapi/mcp
claude mcp add com-normapi-mcp -- npx -y @normapi/mcp
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.