_ registry / mcp http-sse · checked 7h ago

zugferd-validator

https://api.zugferd-validator.de

Registry code: 4c753df4faa6e223

api record

Validiert E-Rechnungen (ZUGFeRD/Factur-X, XRechnung) gegen EN 16931 mit Korrekturvorschlägen.

from a public catalogue that lists it, not from the operator

endpoint
https://api.zugferd-validator.de/mcp
protocol
http-sse ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is zugferd-validator live?
Yes — it answered the hub's last check (checked 7h ago). It answered 99% of checks over the last 30 days.
Is zugferd-validator free to use?
Yes — the hub reached it with no key and no payment.
What tools does zugferd-validator have?
5 tools: create_invoice, validate_invoice, extract_xml, validation_report, check_consistency.
Is zugferd-validator safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
99.1%

90 days 99.1%· all time 99.1%

latency
88ms

last good check

priced tools
0

of 5 tools

_ answered our checks, 90 days 342 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • down → live
_ what it is for
topic
finance & markets accounting & tax
used for
  • validate a zugferd or xrechnung invoice
  • create a valid e-invoice
  • extract xml from a zugferd pdf
  • generate an invoice validation report
takes → gives
documents, data → data, documents
tools
5 reads
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

inferred, not observed

Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run

_ what it can do 5 tools
5 never probed 0 of 5 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • create_invoice reads unknown never probed

    Erstellt aus strukturierten Daten eine valide E-Rechnung — entweder als ZUGFeRD-PDF (PDF/A-3 mit eingebettetem XML) oder als reines XRechnung-XML (mit Leitweg-ID für B2G). Unterstützt mehrere Positionen, alle USt-Kategorien, Rabatte/Zuschläge und Zahlungsangaben. Stateless — es wird nichts gespeichert.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "format",
    "number",
    "date",
    "buyer",
    "lines"
  ],
  "properties": {
    "date": {
      "type": "string",
      "description": "Belegdatum (YYYY-MM-DD)"
    },
    "note": {
      "type": "string",
      "description": "Freitext-Hinweis"
    },
    "buyer": {
      "type": "object",
      "required": [
        "name"
      ],
      "properties": {
        "zip": {
          "$ref": "#/properties/seller/properties/zip"
        },
        "city": {
          "$ref": "#/properties/seller/properties/city"
        },
        "name": {
          "$ref": "#/properties/seller/properties/name"
        },
        "email": {
          "$ref": "#/properties/seller/properties/email"
        },
        "phone": {
          "$ref": "#/properties/seller/properties/phone"
        },
        "street": {
          "$ref": "#/properties/seller/properties/street"
        },
        "vat_id": {
          "$ref": "#/properties/seller/properties/vat_id"
        },
        "country": {
          "$ref": "#/properties/seller/properties/country"
        },
        "contact_name": {
          "$ref": "#/properties/seller/properties/contact_name"
        }
      },
      "description": "Käufer / Rechnungsempfänger",
      "additionalProperties": false
    },
    "lines": {
      "type": "array",
      "items": {
        "type": "object",
        "required": [
          "name",
          "quantity",
          "unit_net_price_cents",
          "vat_rate"
        ],
        "properties": {
          "name": {
            "type": "string",
            "minLength": 1,
            "description": "Bezeichnung der Position"
          },
          "unit": {
            "type": "string",
            "description": "Einheit (UN/ECE Rec 20, Standard C62 = Stück)"
          },
          "quantity": {
            "type": "number",
            "description": "Menge"
          },
          "vat_rate": {
            "type": "number",
            "description": "USt-Satz in Prozent (0 bei Z/E/AE)"
          },
          "description": {
            "type": "string",
            "description": "Optionale Detailbeschreibung"
          },
          "vat_category": {
            "enum": [
              "S",
              "Z",
              "E",
              "AE",
              "K",
              "G",
              "O"
            ],
            "type": "string",
            "description": "USt-Kategorie (Standard S). Z=0%, E=befreit, AE=Reverse-Charge"
          },
          "unit_net_price_cents": {
            "type": "integer",
            "description": "Netto-Einzelpreis in Cent"
          }
        },
        "additionalProperties": false
      },
      "minItems": 1,
      "description": "Rechnungspositionen (mindestens eine)"
    },
    "format": {
      "enum": [
        "zugferd",
        "xrechnung"
      ],
      "type": "string",
      "description": "'zugferd' = PDF/A-3 mit eingebettetem XML, 'xrechnung' = reines XML"
    },
    "number": {
      "type": "string",
      "minLength": 1,
      "description": "Belegnummer"
    },
    "seller": {
      "type": "object",
      "required": [
        "name"
      ],
      "properties": {
        "zip": {
          "type": "string",
          "description": "Postleitzahl"
        },
        "city": {
          "type": "string",
          "description": "Ort"
        },
        "name": {
          "type": "string",
          "minLength": 1,
          "description": "Firmenname / Name"
        },
        "email": {
          "type": "string",
          "description": "E-Mail / elektronische Adresse (für XRechnung Pflicht)"
        },
        "phone": {
          "type": "string",
          "description": "Telefon (Kontakt)"
        },
        "street": {
          "type": "string",
          "description": "Straße und Hausnummer"
        },
        "vat_id": {
          "type": "string",
          "description": "USt-IdNr. (z.B. DE123456789)"
        },
        "country": {
          "type": "string",
          "maxLength": 2,
          "minLength": 2,
          "description": "ISO-3166 Alpha-2 Ländercode, Standard DE"
        },
        "contact_name": {
          "type": "string",
          "description": "Ansprechpartner"
        }
      },
      "description": "Verkäufer / Rechnungssteller. Weglassen, wenn im Konto feste Absenderdaten hinterlegt sind — sie werden dann eingesetzt.",
      "additionalProperties": false
    },
    "currency": {
      "type": "string",
      "description": "Währung (Standard EUR)"
    },
    "due_date": {
      "type": "string",
      "description": "Fälligkeitsdatum (YYYY-MM-DD)"
    },
    "type_code": {
      "type": "string",
      "description": "Roher UNTDID-1001-Code (überschreibt document_type; für seltene Typen wie 875-877 Bauleistung)"
    },
    "self_check": {
      "type": "boolean",
      "description": "Wenn true, wird die erzeugte Rechnung sofort gegen EN 16931 geprüft (langsamer). Standard: false."
    },
    "seller_logo": {
      "type": "string",
      "description": "Logo als Base64 (PNG/JPG) — nur im Pro/Ultra-Tarif"
    },
    "delivery_date": {
      "type": "string",
      "description": "Leistungs-/Lieferdatum (BT-72, YYYY-MM-DD). In Deutschland Pflichtangabe; ohne Angabe gilt das Belegdatum."
    },
    "document_type": {
      "enum": [
        "invoice",
        "credit_note",
        "corrected",
        "self_billed",
        "prepayment",
        "partial",
        "debit_note"
      ],
      "type": "string",
      "description": "Dokumenttyp (Standard invoice). credit_note=Gutschrift/Storno, corrected=Korrektur, self_billed=Gutschriftverfahren, prepayment=Anzahlung, partial=Teilrechnung, debit_note=Belastungsanzeige. Mappt auf BT-3."
    },
    "payment_means": {
      "type": "object",
      "properties": {
        "bic": {
          "type": "string",
          "description": "BIC"
        },
        "iban": {
          "type": "string",
          "description": "IBAN des Zahlungsempfängers"
        },
        "type_code": {
          "type": "string",
          "description": "BT-81 UNTDID-4461-Code (z.B. 58 = SEPA-Überweisung)"
        },
        "account_name": {
          "type": "string",
          "description": "Kontoinhaber"
        }
      },
      "description": "Zahlungsangaben (IBAN etc.)",
      "additionalProperties": false
    },
    "payment_terms": {
      "type": "string",
      "description": "Zahlungsbedingungen (Freitext)"
    },
    "billing_period": {
      "type": "object",
      "required": [
        "start",
        "end"
      ],
      "properties": {
        "end": {
          "type": "string"
        },
        "start": {
          "type": "string"
        }
      },
      "description": "Leistungszeitraum (BG-14, BT-73/74) bei laufenden Leistungen, jeweils YYYY-MM-DD. Ersetzt delivery_date.",
      "additionalProperties": false
    },
    "buyer_reference": {
      "type": "string",
      "description": "Leitweg-ID / Käuferreferenz (BT-10, bei XRechnung Pflicht)"
    },
    "preceding_invoice": {
      "type": "object",
      "required": [
        "number"
      ],
      "properties": {
        "date": {
          "type": "string",
          "description": "YYYY-MM-DD"
        },
        "number": {
          "type": "string"
        }
      },
      "description": "Bezug auf die Ursprungsrechnung (BT-25/26) — bei Storno, Korrektur oder Gutschrift angeben",
      "additionalProperties": false
    },
    "allowances_charges": {
      "type": "array",
      "items": {
        "type": "object",
        "required": [
          "charge",
          "amount_cents",
          "vat_rate"
        ],
        "properties": {
          "charge": {
            "type": "boolean",
            "description": "true = Zuschlag, false = Rabatt (auf Dokumentebene)"
          },
          "reason": {
            "type": "string",
            "description": "Begründung"
          },
          "vat_rate": {
            "type": "number",
            "description": "Zugehöriger USt-Satz in Prozent"
          },
          "amount_cents": {
            "type": "integer",
            "description": "Betrag in Cent (positiv)"
          },
          "vat_category": {
            "$ref": "#/properties/lines/items/properties/vat_category",
            "description": "Zugehörige USt-Kategorie (Standard S)"
          }
        },
        "additionalProperties": false
      },
      "description": "Rabatte/Zuschläge auf Dokumentebene"
    }
  },
  "additionalProperties": false
}
    arguments 313 lines
  • validate_invoice reads unknown never probed

    Validiert eine E-Rechnung (ZUGFeRD/Factur-X PDF oder XRechnung XML) gegen EN 16931 und gibt strukturierte Ergebnisse mit Korrekturvorschlägen zurück.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "file_content",
    "file_type"
  ],
  "properties": {
    "profile": {
      "enum": [
        "minimum",
        "basic_wl",
        "basic",
        "en16931",
        "extended",
        "xrechnung"
      ],
      "type": "string",
      "description": "Erwartetes Profil (optional, wird automatisch erkannt)"
    },
    "file_type": {
      "enum": [
        "pdf",
        "xml"
      ],
      "type": "string",
      "description": "'pdf' für ZUGFeRD/Factur-X, 'xml' für XRechnung"
    },
    "file_content": {
      "type": "string",
      "description": "Base64-kodierter Inhalt der PDF- oder XML-Datei"
    }
  },
  "additionalProperties": false
}
    arguments 35 lines
  • extract_xml reads unknown never probed

    Extrahiert die eingebettete XML-Datei aus einem ZUGFeRD/Factur-X PDF.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "pdf_content"
  ],
  "properties": {
    "pdf_content": {
      "type": "string",
      "description": "Base64-kodierter Inhalt der ZUGFeRD-PDF-Datei"
    }
  },
  "additionalProperties": false
}
    arguments 14 lines
  • validation_report reads unknown never probed

    Erzeugt aus einer E-Rechnung einen Validierungsbericht als PDF (PDF/A-3b) zum Ablegen und Weitergeben. Der Bericht nennt Ergebnis, alle Meldungen mit Regel-ID und Feld, den Prüfzeitpunkt, Format und Profil, die SHA-256-Prüfsumme der geprüften Datei sowie die Versionen der Prüfwerkzeuge. Auf Wunsch wird die geprüfte Rechnung sichtbar angehängt. Gibt das PDF base64-kodiert zurück. Ab dem Tarif Automatisieren.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "file_content",
    "file_type"
  ],
  "properties": {
    "lang": {
      "enum": [
        "de",
        "en",
        "fr"
      ],
      "type": "string",
      "description": "Sprache des Berichts. Standard 'de'."
    },
    "file_name": {
      "type": "string",
      "description": "Dateiname, der im Bericht steht."
    },
    "file_type": {
      "enum": [
        "pdf",
        "xml"
      ],
      "type": "string",
      "description": "Dateityp: 'pdf' für ZUGFeRD/Factur-X, 'xml' für XRechnung/CII"
    },
    "file_content": {
      "type": "string",
      "description": "Base64-kodierter Inhalt der PDF- oder XML-Datei"
    },
    "attach_source": {
      "type": "boolean",
      "description": "Geprüfte Rechnung sichtbar anhängen (PDF-Seiten bzw. abgedruckter XML-Inhalt). Standard false."
    }
  },
  "additionalProperties": false
}
    arguments 40 lines
  • check_consistency reads unknown 14h ago

    Prüft ob die sichtbaren PDF-Daten mit den eingebetteten XML-Daten übereinstimmen.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "pdf_content"
  ],
  "properties": {
    "pdf_content": {
      "type": "string",
      "description": "Base64-kodierter Inhalt der ZUGFeRD-PDF-Datei"
    }
  },
  "additionalProperties": false
}
    arguments 14 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 4c753df4faa6e223.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/4c753df4faa6e223/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/4c753df4faa6e223/badge.svg)](https://brick.blue/agent/4c753df4faa6e223?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
90%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.