NormAPI
REMOTE · NORMAPI.COM · 2 COMPONENTS
Validate, generate and read German e-invoices (XRechnung, ZUGFeRD) against the official KoSIT rules.
Available components
Last scanned (8 hours ago)
Scores higher than 91% of remote servers
Unreachable for 1 day in a row. Last reached 4 Nov 2026.
Category Finance and Payments
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. How we score → Why this is hard to score →
Endpoint Security11
- TLS not yet verified: we couldn't open a connection to check the certificate. View diagnostics → Unverified
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS not yet verified: we couldn't read the response headers to check for it. View diagnostics → Unverified
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but we couldn't connect to verify it. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
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.
Checks we ran (3)
- HTTPS
- DNSSEC
- Transport
Checks we could not complete (8)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- TLS certificate in Endpoint SecurityTLS not yet verified: we couldn't open a connection to check the certificate.
- Authorization in Endpoint SecurityAuthorisation not yet verified: we couldn't confirm whether this endpoint requires it.
- HSTS header in Endpoint SecurityHSTS not yet verified: we couldn't read the response headers to check for it.
- Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
- Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
- Tool coverage in Tool Coverage (scores 0 for this)Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- Tool safety in Tool Safety (scores 0 for this)Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- Capabilities in Capabilities (scores 0 for this)Capabilities not yet verified: we couldn't read the endpoint's capabilities.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
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.
- 5 Nov 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- Stability: 0.83 → unverified ▼ security
- Authorization: partial → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- TLS certificate: pass → unverified ▼ security
- HSTS header: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Schema quality: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 3 Nov 26 +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.
- 1 Nov 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- Server version: 1.3.0 → 1.3.1 functional
- 31 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Server version: 1.2.1 → 1.3.0 functional
- “generate_invoice” added an optional parameter “letterhead” cosmetic
- 30 Oct 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.
- 29 Oct 26 0
- Server version: 1.2.0 → 1.2.1 functional
- 28 Oct 26 +3
- 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 security
- 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” functional
- “validate_invoice” added an optional parameter “file” cosmetic
- “parse_invoice” added an optional parameter “file” cosmetic
- 26 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.
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 · Probed https://normapi.com/mcp
TLS unreached
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of normapi.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| normapi.com. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://normapi.com/mcp | Unreachable | ||
| http (plaintext) | http://normapi.com/mcp | HTTPS enforced |
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 | – | 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 | – | 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 | – | yes | The rule set the document passed before it was returned |
| scenario | – | 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 | – | 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 | – | 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 | – | 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 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.
remote · normapi.com
claude mcp add --transport http com-normapi-mcp 'https://normapi.com/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 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.