Skip to content

InvoiceVerify MCP server

app.lovable.peppol-invoice-compass/invoiceverifypeppol-invoice-compass.lovable.appstreamable-httpv1.0.0Scanned

Check Peppol receivability (incl. Belgian client lists) and validate EU e-invoices. Free check.

9 tools: 3 change things and 6 only read.

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

Tools listed without sign-in. Remote posture

With Anlyon

3 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 InvoiceVerify MCP server can do

The InvoiceVerify MCP server is published by peppol-invoice-compass.lovable.app, a domain the MCP Registry verified. It has 9 tools. It can create or change data (3 tools: check_peppol_receivability, generate_invoice and convert_invoice), but cannot delete data. 6 tools only read.

3 tools bring in text other people can write (check_peppol_receivability, lookup_peppol_participant and check_belgian_peppol_list).

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

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

Last scanned Nov 12, 2026, version 1.0.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.

9 tools

Changes things 3Claude Code: ask
  • check_peppol_receivabilityFree, 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 n…Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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).

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: true
  • convert_invoiceConvert 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.1 finding

    Why it is in this group

    • The name "convert_invoice" says "convert": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

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

      Matched text

      annotations: {"readOnlyHint":true,"idempotentHint":true,"openWorldHint":false}; The name "convert_invoice" says "convert": a word for a change.

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

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: false
  • generate_invoiceCreate 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.1 finding

    Why it is in this group

    • The name "generate_invoice" says "generate": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

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

      Matched text

      annotations: {"readOnlyHint":true,"idempotentHint":true,"openWorldHint":false}; The name "generate_invoice" says "generate": a word for a change.

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

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: false
Only reads 6Show 6 read-only tools
  • check_belgian_peppol_listCheck up to 25 Belgian companies (enterprise or VAT numbers) for Peppol receivability under both Belgian IDs — 0208 (enterprise number) and 9925 (VAT number).Reads text others writeNo findings

    Why it is in this group

    • The name "check_belgian_peppol_list" says "list": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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).

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: true
  • explain_ruleExplain an EN 16931, Peppol or XRechnung business rule (e.g.No findings

    Why it is in this group

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

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: false
  • get_usageShow this month's metered calls, the included allowance, remaining call-pack credits and the reset date for the signed-in account.No findings

    Why it is in this group

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

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: false
  • lookup_peppol_participantCheck 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.Reads text others writeNo findings

    Why it is in this group

    • The name "lookup_peppol_participant" says "lookup": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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).

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: true
  • parse_invoiceRead a UBL or CII / Factur-X invoice XML into structured JSON (parties, lines, VAT, totals, payment) for booking or reconciliation.No findings

    Why it is in this group

    • The description's first verb is "read": a word for reading.
    Description, as the server wrote it
    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).

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: false
  • validate_invoiceValidate 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.No findings

    Why it is in this group

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

    Annotations the server declares

    • readOnlyHint: true
    • 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 private-data or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write3
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 21, 2026, 19:24 UTC, unchanged since Nov 21, 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
6
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
https://peppol-invoice-compass.lovable.app/.well-known/oauth-protected-resource/mcp
Authorization servers
https://xdgwjwcgdbzgpwkwyyjd.supabase.co/auth/v1
Legacy HTTP+SSE transport
no
Dynamic client registration
yes
Client ID metadata documents
no
  • WarnThe whole server

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

    Matched text

    https://peppol-invoice-compass.lovable.app/mcp: tools/list returned 13 tools to an anonymous client, including check_peppol_receivability (write), check_factur_x (write), check_si_ubl (write), generate_invoice (write), generate_factur_x (write) and 1 more

    What this check looks for

Posture changes

  1. Nov 21, 2026
    • Tools that change things, listed without credentials: 5 to 6
  2. Nov 14, 2026
    • Tools that change things, listed without credentials: 3 to 5
  3. Nov 7, 2026
    • RFC 9728 protected resource metadata: https://peppol-invoice-compass.lovable.app/.well-known/oauth-protected-resource to https://peppol-invoice-compass.lovable.app/.well-known/oauth-protected-resource/mcp

Findings

Matches of fixed checks, with the text they matched.

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

    Matched text

    annotations: {"readOnlyHint":true,"idempotentHint":true,"openWorldHint":false}; The name "generate_invoice" says "generate": a word for a change.

    What this check looks for
  • The server marks "convert_invoice" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"idempotentHint":true,"openWorldHint":false}; The name "convert_invoice" says "convert": a word for a change.

    What this check looks for

History

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

  1. PostureRemote posture changed. Tools that change things, listed without credentials: 5 -> 6.View diff
    • Tools that change things, listed without credentials: 5 to 6
  2. PostureRemote posture changed. Tools that change things, listed without credentials: 3 -> 5.View diff
    • Tools that change things, listed without credentials: 3 to 5
  3. Tools8 changed.~8 changedView diff
  4. PostureRemote posture changed. RFC 9728 protected resource metadata: https://peppol-invoice-compass.lovable.app/.well-known/oauth-protected-resource -> https://peppol-invoice-compass.lovable.app/.well-known/oauth-protected-resource/mcp.View diff
    • RFC 9728 protected resource metadata: https://peppol-invoice-compass.lovable.app/.well-known/oauth-protected-resource to https://peppol-invoice-compass.lovable.app/.well-known/oauth-protected-resource/mcp

Install

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

claude mcp add --transport http invoiceverify https://peppol-invoice-compass.lovable.app/mcp
claude mcp add --transport http invoiceverify https://peppol-invoice-compass.lovable.app/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__invoiceverify__validate_invoice",
      "mcp__invoiceverify__parse_invoice",
      "mcp__invoiceverify__lookup_peppol_participant",
      "mcp__invoiceverify__check_belgian_peppol_list",
      "mcp__invoiceverify__explain_rule",
      "mcp__invoiceverify__get_usage"
    ],
    "ask": [
      "mcp__invoiceverify__check_peppol_receivability",
      "mcp__invoiceverify__generate_invoice",
      "mcp__invoiceverify__convert_invoice"
    ],
    "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 invoiceverify. Review it before you use it.

Capability tags behind 3 rules
  • mcp__invoiceverify__check_peppol_receivability untrusted-input
  • mcp__invoiceverify__lookup_peppol_participant untrusted-input
  • mcp__invoiceverify__check_belgian_peppol_list untrusted-input

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/app.lovable.peppol-invoice-compass/invoiceverify/verify?hash=05b7cbabb24141ae350406a28893eaa17bb3001ac64f3f2466a738105383d5b0" | jq -e '.changed == false'

Pinned hash 05b7cbabb241, from Nov 12, 2026, 13:18 UTC.

Watch

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

https://radar.anlyon.com/servers/app.lovable.peppol-invoice-compass/invoiceverify/changes.xml

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

Badge

Anlyon Radar badge for app.lovable.peppol-invoice-compass/invoiceverify
[![Anlyon Radar](https://radar.anlyon.com/badge/app.lovable.peppol-invoice-compass/invoiceverify.svg)](https://radar.anlyon.com/servers/app.lovable.peppol-invoice-compass/invoiceverify)

Source: MCP Registry. Synced Oct 30, 2026, 19:17 UTC.

InvoiceVerify MCP server: questions and answers

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

Is the InvoiceVerify MCP server safe?

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

Can the InvoiceVerify MCP server delete data?

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

Can the InvoiceVerify 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 InvoiceVerify MCP server have?

9 tools: 3 write, 6 read. check_peppol_receivability, generate_invoice, convert_invoice, validate_invoice, parse_invoice, lookup_peppol_participant, check_belgian_peppol_list, explain_rule and 1 more.

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

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

Does the InvoiceVerify MCP server send data to outside services?

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

Has the InvoiceVerify MCP server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Nov 12, 2026. Every change is on this page and in its Atom feed.