# InvoiceVerify (remote · peppol-invoice-compass.lovable.app)

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

- Trust score: 81/100 (high trust)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `peppol-invoice-compass.lovable.app`: 81/100 (this document), [markdown](https://verifymcp.io/servers/app-lovable-peppol-invoice-compass-invoiceverify/peppol-invoice-compass.md), [page](https://verifymcp.io/servers/app-lovable-peppol-invoice-compass-invoiceverify/peppol-invoice-compass)

## Channel facts

- Endpoint: `https://peppol-invoice-compass.lovable.app/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 94/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
  - The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 69/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 20/100
  - Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### 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.

### Claude

```bash
claude mcp add --transport http app-lovable-peppol-invoice-compass-invoiceverify 'https://peppol-invoice-compass.lovable.app/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "app-lovable-peppol-invoice-compass-invoiceverify": {
      "url": "https://peppol-invoice-compass.lovable.app/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "app-lovable-peppol-invoice-compass-invoiceverify": {
      "type": "http",
      "url": "https://peppol-invoice-compass.lovable.app/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.app-lovable-peppol-invoice-compass-invoiceverify]
url = "https://peppol-invoice-compass.lovable.app/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "app-lovable-peppol-invoice-compass-invoiceverify": {
      "type": "remote",
      "url": "https://peppol-invoice-compass.lovable.app/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add app-lovable-peppol-invoice-compass-invoiceverify --url 'https://peppol-invoice-compass.lovable.app/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  app-lovable-peppol-invoice-compass-invoiceverify:
    url: "https://peppol-invoice-compass.lovable.app/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "app-lovable-peppol-invoice-compass-invoiceverify": {
      "Transport": "http",
      "Url": "https://peppol-invoice-compass.lovable.app/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add app-lovable-peppol-invoice-compass-invoiceverify -t streamable-http -u 'https://peppol-invoice-compass.lovable.app/mcp'
```

### Other

```json
{
  "mcpServers": {
    "app-lovable-peppol-invoice-compass-invoiceverify": {
      "type": "http",
      "url": "https://peppol-invoice-compass.lovable.app/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 81, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-03 (score 80, +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.

### 2026-11-01 (score 79, +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.

### 2026-10-31 (score 78, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-30 (score 78)

First indexed and scored.

## MCP tools (9)

### `check_peppol_receivability` (~192 tokens)

Check Belgian Peppol receivability (free)

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).

Input parameters:

- `id` (string, required): Belgian enterprise or VAT number, e.g. BE0403170701, 0403.170.701 or 0403170701.
- `lang` (string): Language of the explanation: en (default), nl or fr.

### `validate_invoice` (~116 tokens)

Validate e-invoice

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).

Input parameters:

- `profile` (string): Rule set to apply. 'auto' (default) detects it from the CustomizationID.
- `xml` (string, required): The complete invoice XML document.

### `generate_invoice` (~232 tokens)

Generate e-invoice XML

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).

Input parameters:

- `format` (string): Output format. Default 'peppol' (Peppol BIS Billing 3.0 UBL).
- `invoice` (object, required): Invoice data: {number, issueDate (YYYY-MM-DD), dueDate?, currency?, buyerReference?, seller: Party, buyer: Party, payment?: {meansCode, iban, bic}, lines: [{name, quantity, unitPrice, unitCode?, vatC…

### `convert_invoice` (~106 tokens)

Convert e-invoice format

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).

Input parameters:

- `format` (string, required): Target format, e.g. 'peppol' or 'xrechnung-ubl'.
- `xml` (string, required): The source invoice XML.

### `parse_invoice` (~67 tokens)

Read e-invoice into JSON

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).

Input parameters:

- `xml` (string, required): The invoice XML.

### `lookup_peppol_participant` (~168 tokens)

Check Peppol receivability

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).

Input parameters:

- `country` (string): ISO country code hint for ambiguous numbers, e.g. 'BE' or 'FR'.
- `id` (string, required): VAT number (BE0403170701), company number or Peppol ID (0208:0403170701).

### `check_belgian_peppol_list` (~168 tokens)

Check a Belgian client list on Peppol

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).

Input parameters:

- `companies` (array, required): 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.

### `explain_rule` (~108 tokens)

Explain validation rule

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).

Input parameters:

- `language` (string): Explanation language. Default 'en'.
- `rule_id` (string, required): Rule ID as reported by validate_invoice, e.g. BR-CO-15.

### `get_usage` (~45 tokens)

Show API usage

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).

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/app-lovable-peppol-invoice-compass-invoiceverify/peppol-invoice-compass#diagnostics

## Score history

- 2026-11-05: 81
- 2026-11-04: 80
- 2026-11-03: 80
- 2026-11-02: 79
- 2026-11-01: 79
- 2026-10-31: 78
- 2026-10-30: 78

## Common questions

### 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 81 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 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://peppol-invoice-compass.lovable.app/mcp
- Website: https://peppol-invoice-compass.lovable.app/docs/mcp
- Changelog RSS feed: https://verifymcp.io/servers/app-lovable-peppol-invoice-compass-invoiceverify/peppol-invoice-compass.xml
- Changelog JSON feed: https://verifymcp.io/servers/app-lovable-peppol-invoice-compass-invoiceverify/peppol-invoice-compass.json
- HTML version of this page: https://verifymcp.io/servers/app-lovable-peppol-invoice-compass-invoiceverify/peppol-invoice-compass