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

invoiceverify

https://peppol-invoice-compass.lovable.app

Registry code: 02c7e91931d4802e

api record

EU e-invoicing tools (InvoiceVerify). Without signing in, check_peppol_receivability checks whether one Belgian company can receive Peppol invoices under its two Belgian IDs — 0208 (enterprise number) and 9925 (VAT number) — free, 20 checks per hour. With an InvoiceVerify account (OAuth sign-in): validate UBL / Peppol BIS 3 / XRechnung / CII / Factur-X XML against EN 16931 and Peppol rules, generate or convert compliant invoice XML, read invoices into JSON, check whether a company in any country can receive Peppol invoices (and under which Peppol ID), check lists of up to 25 Belgian companies…

endpoint
https://peppol-invoice-compass.lovable.app/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 invoiceverify live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is invoiceverify free to use?
Not anonymously — it asks for a key or a login before it will serve. Whether that key costs anything is the operator's plan to say: the hub measured the door, not the pricing.
What tools does invoiceverify have?
9 tools: check_peppol_receivability, validate_invoice, get_usage, check_belgian_peppol_list, generate_invoice, convert_invoice, parse_invoice, lookup_peppol_participant, ….
Is invoiceverify 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
100%

90 days 100%· all time 100%

latency
1,846ms

last good check

priced tools
0

of 9 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ 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

_ what it can do 9 tools
8 auth-required 1 never probed 8 of 9 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.

  • validate_invoice auth-required never probed

    Validate a UBL 2.1, Peppol BIS Billing 3.0, XRechnung or CII / Factur-X XML invoice against EN 16931 and Peppol rules; returns pass/fail with rule IDs, line numbers and fixes. Uses one metered call. Requires an InvoiceVerify account (OAuth sign-in).

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "xml"
      ],
      "properties": {
        "xml": {
          "type": "string",
          "maxLength": 5242880,
          "minLength": 1,
          "description": "The complete invoice XML document."
        },
        "profile": {
          "enum": [
            "auto",
            "peppol",
            "en16931",
            "xrechnung"
          ],
          "type": "string",
          "description": "Rule set to apply. 'auto' (default) detects it from the CustomizationID."
        }
      },
      "additionalProperties": false
    }
    arguments 26 lines
  • get_usage auth-required 1h ago

    Show this month's metered calls, the included allowance, remaining call-pack credits and the reset date for the signed-in account. Free. Requires an InvoiceVerify account (OAuth sign-in).

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "properties": {},
      "additionalProperties": false
    }
    arguments 6 lines
  • check_belgian_peppol_list auth-required 1h ago

    Check up to 25 Belgian companies (enterprise or VAT numbers) for Peppol receivability under both Belgian IDs — 0208 (enterprise number) and 9925 (VAT number). Returns per company: receivable under both, only 0208, only 9925, neither, or unknown, with the risk and what to fix in Dutch, French or English. Uses one metered call per valid company; unreadable numbers are free. Requires an InvoiceVerify account (OAuth sign-in).

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "companies"
      ],
      "properties": {
        "lang": {
          "enum": [
            "en",
            "nl",
            "fr"
          ],
          "type": "string",
          "description": "Language of the explanations: en (default), nl or fr."
        },
        "companies": {
          "type": "array",
          "items": {
            "anyOf": [
              {
                "type": "string",
                "maxLength": 80,
                "minLength": 1
              },
              {
                "type": "object",
                "required": [
                  "id"
                ],
                "properties": {
                  "id": {
                    "type": "string",
                    "maxLength": 80,
                    "minLength": 1,
                    "description": "Enterprise or VAT number, e.g. BE0403170701 or 0403.170.701"
                  },
                  "name": {
                    "type": "string",
                    "maxLength": 200,
                    "description": "Optional client name to echo back"
                  }
                },
                "additionalProperties": false
              }
            ]
          },
          "maxItems": 25,
          "minItems": 1,
          "description": "1 to 25 Belgian enterprise or VAT numbers (strings or {id, name}). Split longer lists into several calls."
        }
      },
      "additionalProperties": false
    }
    arguments 54 lines
  • generate_invoice auth-required never probed

    Create a Peppol BIS 3 UBL, XRechnung (UBL or CII) or Factur-X/ZUGFeRD CII XML invoice from structured invoice data, with totals and VAT computed and the result validated. Uses one metered call. Requires an InvoiceVerify account (OAuth sign-in).

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "invoice"
      ],
      "properties": {
        "format": {
          "enum": [
            "peppol",
            "xrechnung-ubl",
            "xrechnung-cii",
            "cii"
          ],
          "type": "string",
          "description": "Output format. Default 'peppol' (Peppol BIS Billing 3.0 UBL)."
        },
        "invoice": {
          "type": "object",
          "description": "Invoice data: {number, issueDate (YYYY-MM-DD), dueDate?, currency?, buyerReference?, seller: Party, buyer: Party, payment?: {meansCode, iban, bic}, lines: [{name, quantity, unitPrice, unitCode?, vatCategory? (S,Z,E,AE,K,G,O), vatRate?}]}. Party: {name, vatId?, companyId?, endpointId, endpointScheme (EAS code, e.g. 0208, 9930), street?, city?, postalCode?, country (ISO 2)}. Full schema: InvoiceData in /openapi.json.",
          "additionalProperties": {}
        }
      },
      "additionalProperties": false
    }
    arguments 25 lines
  • convert_invoice auth-required never probed

    Convert an existing UBL or CII / Factur-X invoice XML into Peppol BIS 3 UBL, XRechnung UBL, XRechnung CII or Factur-X CII, and validate the result. Uses one metered call. Requires an InvoiceVerify account (OAuth sign-in).

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "xml",
        "format"
      ],
      "properties": {
        "xml": {
          "type": "string",
          "maxLength": 5242880,
          "minLength": 1,
          "description": "The source invoice XML."
        },
        "format": {
          "enum": [
            "peppol",
            "xrechnung-ubl",
            "xrechnung-cii",
            "cii"
          ],
          "type": "string",
          "description": "Target format, e.g. 'peppol' or 'xrechnung-ubl'."
        }
      },
      "additionalProperties": false
    }
    arguments 27 lines
  • parse_invoice auth-required never probed

    Read a UBL or CII / Factur-X invoice XML into structured JSON (parties, lines, VAT, totals, payment) for booking or reconciliation. Uses one metered call. Requires an InvoiceVerify account (OAuth sign-in).

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "xml"
      ],
      "properties": {
        "xml": {
          "type": "string",
          "maxLength": 5242880,
          "minLength": 1,
          "description": "The invoice XML."
        }
      },
      "additionalProperties": false
    }
    arguments 16 lines
  • lookup_peppol_participant auth-required never probed

    Check whether a company can receive Peppol e-invoices: give a VAT number, company number (KBO/BCE, KvK, SIREN/SIRET), GLN or Peppol ID and it checks every relevant scheme (e.g. Belgian 0208 and 9925) in the live Peppol SML/SMP, lists supported document types and says which ID to send to. Uses one metered call. Requires an InvoiceVerify account (OAuth sign-in).

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "id"
      ],
      "properties": {
        "id": {
          "type": "string",
          "maxLength": 80,
          "minLength": 1,
          "description": "VAT number (BE0403170701), company number or Peppol ID (0208:0403170701)."
        },
        "country": {
          "type": "string",
          "pattern": "^[A-Za-z]{2}$",
          "description": "ISO country code hint for ambiguous numbers, e.g. 'BE' or 'FR'."
        }
      },
      "additionalProperties": false
    }
    arguments 21 lines
  • explain_rule auth-required never probed

    Explain an EN 16931, Peppol or XRechnung business rule (e.g. BR-CO-15, PEPPOL-EN16931-R003) in plain English, Dutch or French, with typical causes and fix steps. Free. Requires an InvoiceVerify account (OAuth sign-in).

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "rule_id"
      ],
      "properties": {
        "rule_id": {
          "type": "string",
          "maxLength": 40,
          "minLength": 2,
          "description": "Rule ID as reported by validate_invoice, e.g. BR-CO-15."
        },
        "language": {
          "enum": [
            "en",
            "nl",
            "fr"
          ],
          "type": "string",
          "description": "Explanation language. Default 'en'."
        }
      },
      "additionalProperties": false
    }
    arguments 25 lines
  • check_peppol_receivability unknown 1h ago

    Free, no sign-in needed: check whether one Belgian company can receive Peppol e-invoices under each of its two Belgian Peppol IDs — 0208 (enterprise/KBO-BCE number) and 9925 (VAT number). Returns receivable under both, only 0208, only 9925, neither or unknown, which ID to send to, the access point (service provider) per ID, and the risk and fix in English, Dutch or French. Limited to 20 checks per hour per connection; for client lists use check_belgian_peppol_list (sign-in).

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "id"
      ],
      "properties": {
        "id": {
          "type": "string",
          "maxLength": 80,
          "minLength": 1,
          "description": "Belgian enterprise or VAT number, e.g. BE0403170701, 0403.170.701 or 0403170701."
        },
        "lang": {
          "enum": [
            "en",
            "nl",
            "fr"
          ],
          "type": "string",
          "description": "Language of the explanation: en (default), nl or fr."
        }
      },
      "additionalProperties": false
    }
    arguments 25 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 02c7e91931d4802e.

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

_ also on lovable.app 9 entries

Served from the same domain, which is what was measured. Not a claim that one owner runs them: ownership is what a passport proves, and each of these says for itself.

1 more sit on this domain. All of them.