InvoiceVerify
REMOTE · PEPPOL-INVOICE-COMPASS.LOVABLE.APP
Check Peppol receivability (incl. Belgian client lists) and validate EU e-invoices. Free check.
Available components
Last scanned (19 hours ago)
Scores higher than 81% of remote servers
Reachable. Last reached 4 Nov 2026.
Category Finance and Payments
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security94
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability69
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1400 tokens (~155/item across 9 items; 9 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management17
- Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 30 Oct 26 78
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Nov 2026 · Probed https://peppol-invoice-compass.lovable.app/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=lovable.app | CN=WE1,O=Google Trust Services,C=US | 10 Oct 2026 | 9 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | a0305f14b2a99af130a9e43af07d3e5 |
| SANs: lovable.app, *.lovable.app | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of peppol-invoice-compass.lovable.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| lovable.app. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer realm="mcp", resource_metadata="https://peppol-invoice-compass.lovable.app/.well-known/oauth-protected-resource"
Bearer realm="mcp", resource_metadata="https://peppol-invoice-compass.lovable.app/.well-known/oauth-protected-resource"| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| x-content-type-options | nosniff |
| referrer-policy | strict-origin-when-cross-origin |
Protected resource metadata
| Document | https://peppol-invoice-compass.lovable.app/.well-known/oauth-protected-resource |
|---|---|
| Retrieved | Yes |
| Resource | https://peppol-invoice-compass.lovable.app/mcp |
| Authorisation server | https://xdgwjwcgdbzgpwkwyyjd.supabase.co/auth/v1 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://peppol-invoice-compass.lovable.app/mcp | Verified | 200 | |
| http (plaintext) | http://peppol-invoice-compass.lovable.app/mcp | HTTPS enforced | 301 | https://peppol-invoice-compass.lovable.app/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_belgian_peppol_list Check a Belgian client list on Peppol ~168
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).
| Name | Type | Req | Description |
|---|---|---|---|
| companies | array | yes | 1 to 25 Belgian enterprise or VAT numbers (strings or {id, name}). Split longer lists into several calls. |
| lang | string | – | Language of the explanations: en (default), nl or fr. |
No output schema declared.
No examples provided.
check_peppol_receivability Check Belgian Peppol receivability (free) ~192
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).
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Belgian enterprise or VAT number, e.g. BE0403170701, 0403.170.701 or 0403170701. |
| lang | string | – | Language of the explanation: en (default), nl or fr. |
No output schema declared.
No examples provided.
convert_invoice Convert e-invoice format ~106
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).
| Name | Type | Req | Description |
|---|---|---|---|
| format | string | yes | Target format, e.g. 'peppol' or 'xrechnung-ubl'. |
| xml | string | yes | The source invoice XML. |
No output schema declared.
No examples provided.
explain_rule Explain validation rule ~108
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).
| Name | Type | Req | Description |
|---|---|---|---|
| language | string | – | Explanation language. Default 'en'. |
| rule_id | string | yes | Rule ID as reported by validate_invoice, e.g. BR-CO-15. |
No output schema declared.
No examples provided.
generate_invoice Generate e-invoice XML ~232
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).
| Name | Type | Req | Description |
|---|---|---|---|
| format | string | – | Output format. Default 'peppol' (Peppol BIS Billing 3.0 UBL). |
| invoice | object | yes | Invoice data: {number, issueDate (YYYY-MM-DD), dueDate?, currency?, buyerReference?, seller: Party, buyer: Party, payment?: {meansCode, iban, bic}, lines: [{name, quantity, unitPrice, unitCode?, vatC… |
No output schema declared.
No examples provided.
get_usage Show API usage ~45
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).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
lookup_peppol_participant Check Peppol receivability ~168
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).
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | – | ISO country code hint for ambiguous numbers, e.g. 'BE' or 'FR'. |
| id | string | yes | VAT number (BE0403170701), company number or Peppol ID (0208:0403170701). |
No output schema declared.
No examples provided.
parse_invoice Read e-invoice into JSON ~67
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).
| Name | Type | Req | Description |
|---|---|---|---|
| xml | string | yes | The invoice XML. |
No output schema declared.
No examples provided.
validate_invoice Validate e-invoice ~116
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).
| Name | Type | Req | Description |
|---|---|---|---|
| profile | string | – | Rule set to apply. 'auto' (default) detects it from the CustomizationID. |
| xml | string | yes | The complete invoice XML document. |
No output schema declared.
No examples provided.
How do I install the InvoiceVerify MCP server?
InvoiceVerify is a hosted endpoint at https://peppol-invoice-compass.lovable.app/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · peppol-invoice-compass.lovable.app
claude mcp add --transport http app-lovable-peppol-invoice-compass-invoiceverify 'https://peppol-invoice-compass.lovable.app/mcp'
What is the InvoiceVerify MCP server?
InvoiceVerify is an MCP server listed in the public MCP registry as app.lovable.peppol-invoice-compass/invoiceverify. Check Peppol receivability (incl. Belgian client lists) and validate EU e-invoices. Free check. This page covers its hosted endpoint (https://peppol-invoice-compass.lovable.app/mcp).
Is the InvoiceVerify MCP server safe to use?
InvoiceVerify scores 80 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the InvoiceVerify MCP server expose?
InvoiceVerify exposes 9 tools: check_peppol_receivability, validate_invoice, generate_invoice, convert_invoice, parse_invoice, and 4 more. Their descriptions and schemas cost roughly 1,202 tokens of context every time the server is loaded.
Does the InvoiceVerify MCP server require authentication?
Yes. InvoiceVerify asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the InvoiceVerify MCP server still maintained?
InvoiceVerify is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.