Skip to content

NormAPI MCP server

com.normapi/mcpnormapi.comstreamable-httpv1.4.0Scanned

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

4 tools: 2 change things and 2 only read.

Tools: 0 delete, 0 irreversible, 2 write, 2 read.
  • Reads private data · 1
  • Reads text others write · 0
  • Can send data out · 0
  • 1 finding

Tools listed without sign-in. Remote posture

With Anlyon

2 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the NormAPI MCP server can do

The NormAPI MCP server is published by normapi.com, a domain the MCP Registry verified. It has 4 tools. It can create or change data (2 tools: generate_invoice and explain_rule), but cannot delete data. 2 tools only read.

1 tool reads private data (parse_invoice).

The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in, and its tools changed 4 times since Anlyon Radar first saw them.

Last scanned Nov 13, 2026, version 1.4.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

4 tools

Changes things 2Claude Code: ask
  • explain_ruleExplain one EN 16931 / XRechnung / Peppol business rule by its code (e.g.1 finding

    Why it is in this group

    • The name "explain_rule" says "explain": a word for reading.
    • The input takes a statement or command to run (input.code), which can change anything it can reach.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "explain_rule" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "explain_rule" says "explain": a word for reading.

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Explain an e-invoice rule
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • generate_invoiceProduce 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…No findings

    Why it is in this group

    • The name "generate_invoice" says "generate": a word for a change.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Generate an e-invoice
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
Only reads 2Show 2 read-only tools
  • parse_invoiceRead a received e-invoice — XRechnung or any EN 16931 invoice as UBL or CII XML, or a ZUGFeRD/Factur-X PDF — into structured data.Reads private dataNo findings

    Why it is in this group

    • The description's first verb is "read": a word for reading.

    What it can reach

    • private-dataThe input names a file (input.file), and the tool reads: it reads files.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Read an e-invoice into data
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • validate_invoiceCheck an XRechnung (UBL or CII XML) or a ZUGFeRD/Factur-X PDF against the official KoSIT rules.No findings

    Why it is in this group

    • The name "validate_invoice" says "validate": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Validate an e-invoice
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged untrusted-input or outbound.

Reads private data1
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:43 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
2
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
https://normapi.com/.well-known/oauth-protected-resource/mcp
Authorization servers
https://normapi.com
Legacy HTTP+SSE transport
no
Dynamic client registration
yes
Client ID metadata documents
yes
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 2 tools that change things (2 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://normapi.com/mcp: tools/list returned 4 tools to an anonymous client, including generate_invoice (write), explain_rule (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

1 warn
  • The server marks "explain_rule" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "explain_rule" says "explain": a word for reading.

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools1 changed.~1 changedView diff
  2. Tools4 changed.~4 changedView diff
  3. Tools1 added.+1 addedView diff
  4. Tools1 changed.~1 changedView diff

Install

Pinned to version 1.4.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http normapi https://normapi.com/mcp
claude mcp add --transport http normapi https://normapi.com/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__normapi__validate_invoice",
      "mcp__normapi__parse_invoice"
    ],
    "ask": [
      "mcp__normapi__generate_invoice",
      "mcp__normapi__explain_rule"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as normapi. Review it before you use it.

Capability tags behind 1 rule
  • mcp__normapi__parse_invoice private-data

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/com.normapi/mcp/verify?hash=dc9dcd86dde39e15560f37480d01f1a7348eced21bde825f34dd7a873b839c31" | jq -e '.changed == false'

Pinned hash dc9dcd86dde3, from Nov 13, 2026, 21:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/com.normapi/mcp/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for com.normapi/mcp
[![Anlyon Radar](https://radar.anlyon.com/badge/com.normapi/mcp.svg)](https://radar.anlyon.com/servers/com.normapi/mcp)

Source: MCP Registry. Synced Nov 13, 2026, 21:17 UTC.

NormAPI MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the NormAPI MCP server safe?

No scan can promise that. What its definitions show: 4 tools, 2 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the NormAPI MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the NormAPI MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the NormAPI MCP server have?

4 tools: 2 write, 2 read. generate_invoice, explain_rule, validate_invoice and parse_invoice.

Does the NormAPI MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the NormAPI MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the NormAPI MCP server changed its tools?

Yes, 4 times since Anlyon Radar started tracking it, most recently on Oct 31, 2026. Every change is on this page and in its Atom feed.