_ registry / mcp http-sse · checked 54m ago

einvoicewiz

https://einvoicewiz.com

Registry code: 7bd867c31d78e278

api record

Generate and validate EN 16931 e-invoices for the German and French mandates: Factur-X / ZUGFeRD 2.x (PDF/A-3 with embedded CII XML) and XRechnung 3.0 (pure XML, KOSIT rules). A plain PDF invoice is NOT a legal e-invoice in Germany (since 2025-01-01) or France (since 2026-09-01); use these tools when a recipient is an EU business or authority that requires a compliant file. Every file that passes validation receives a permanent verification certificate (EIW-…) the recipient can check. Validation failures are never charged. If you have no API key, call signup(email) first (20 free credits).

endpoint
https://einvoicewiz.com/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 einvoicewiz live?
Yes — it answered the hub's last check (checked 54m ago). It answered 99% of checks over the last 30 days.
Is einvoicewiz free to use?
Yes — the hub reached it with no key and no payment.
What tools does einvoicewiz have?
7 tools: generate_einvoice_xml, signup, lookup_certificate, check_credits, create_facturx_pdf, validate_einvoice, which_format_do_i_need.
Is einvoicewiz 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
98.9%

90 days 98.9%· all time 98.9%

latency
652ms

last good check

priced tools
0

of 7 tools

_ answered our checks, 90 days 453 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
_ what it is for
used for
  • generate a compliant e-invoice
  • validate a factur-x or xrechnung file
  • find which e-invoice format is required
  • convert a pdf invoice to factur-x
takes → gives
data, documents → documents, data
tools
6 reads1 changes data
_ 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 7 tools
7 never probed 0 of 7 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.

  • generate_einvoice_xml reads unknown never probed

    Invoice JSON → validated EN 16931 CII XML (1 credit; failures free). profile: "en16931" (Factur-X/ZUGFeRD data, B2B) or "xrechnung" (German public sector; needs invoice.buyer_reference = Leitweg-ID and seller contact_email/contact_phone). Invoice schema: see https://einvoicewiz.com/openapi.json (required: invoice_number, issue_date, currency, seller{name,country}, buyer{name,country}, lines[{name,qty,unit_price,vat_rate}]). Returns {xml, validation, verify:{id,url}, credits_left}. On 422 the body lists the violated rules.

    mcp-tool

    {
      "type": "object",
      "title": "generate_einvoice_xmlArguments",
      "required": [
        "invoice"
      ],
      "properties": {
        "api_key": {
          "type": "string",
          "title": "Api Key",
          "default": ""
        },
        "invoice": {
          "type": "object",
          "title": "Invoice",
          "additionalProperties": true
        },
        "profile": {
          "type": "string",
          "title": "Profile",
          "default": "en16931"
        }
      }
    }
    arguments 24 lines
  • signup changes data unknown never probed

    Create an einvoicewiz API key with 20 free credits (no card). The key is shown once — store it.

    mcp-tool

    {
      "type": "object",
      "title": "signupArguments",
      "required": [
        "email"
      ],
      "properties": {
        "email": {
          "type": "string",
          "title": "Email"
        }
      }
    }
    arguments 13 lines
  • lookup_certificate reads unknown 7h ago

    Look up a verification certificate (EIW-…) — free, no key. Confirms which file hashes passed validation and when.

    mcp-tool

    {
      "type": "object",
      "title": "lookup_certificateArguments",
      "required": [
        "cert_id"
      ],
      "properties": {
        "cert_id": {
          "type": "string",
          "title": "Cert Id"
        }
      }
    }
    arguments 13 lines
  • check_credits reads unknown never probed

    Credits remaining and calls used for an API key.

    mcp-tool

    {
      "type": "object",
      "title": "check_creditsArguments",
      "properties": {
        "api_key": {
          "type": "string",
          "title": "Api Key",
          "default": ""
        }
      }
    }
    arguments 11 lines
  • create_facturx_pdf reads unknown never probed

    Your existing PDF invoice + invoice JSON → Factur-X / ZUGFeRD PDF/A-3 with embedded XML (1 credit). pdf_base64: the original PDF, base64-encoded (max 15 MB). Returns {pdf_base64, cert_id, verify_url, credits_left}. The output is validated (EN 16931 + PDF/A-3) before delivery; failures are not charged.

    mcp-tool

    {
      "type": "object",
      "title": "create_facturx_pdfArguments",
      "required": [
        "pdf_base64",
        "invoice"
      ],
      "properties": {
        "api_key": {
          "type": "string",
          "title": "Api Key",
          "default": ""
        },
        "invoice": {
          "type": "object",
          "title": "Invoice",
          "additionalProperties": true
        },
        "pdf_base64": {
          "type": "string",
          "title": "Pdf Base64"
        }
      }
    }
    arguments 24 lines
  • validate_einvoice reads unknown never probed

    Validate a Factur-X / ZUGFeRD / XRechnung file (PDF or XML, base64) against EN 16931 + KOSIT + PDF/A (1 credit). Returns the rule-level report {result:{status, errors[], warnings[], profile}, verify, credits_left}. verify is set only when the file passed.

    mcp-tool

    {
      "type": "object",
      "title": "validate_einvoiceArguments",
      "required": [
        "file_base64"
      ],
      "properties": {
        "api_key": {
          "type": "string",
          "title": "Api Key",
          "default": ""
        },
        "file_base64": {
          "type": "string",
          "title": "File Base64"
        }
      }
    }
    arguments 18 lines
  • which_format_do_i_need reads unknown never probed

    Decision helper (free, no key): which e-invoice format a recipient needs and whether a plain PDF is still acceptable.

    mcp-tool

    {
      "type": "object",
      "title": "which_format_do_i_needArguments",
      "required": [
        "recipient_country"
      ],
      "properties": {
        "recipient_country": {
          "type": "string",
          "title": "Recipient Country"
        },
        "recipient_is_public_authority": {
          "type": "boolean",
          "title": "Recipient Is Public Authority",
          "default": false
        }
      }
    }
    arguments 18 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 7bd867c31d78e278.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/7bd867c31d78e278/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/7bd867c31d78e278/badge.svg)](https://brick.blue/agent/7bd867c31d78e278?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
100%

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.