# getpeppr (remote · api.getpeppr.dev)

Peppol e-invoicing: look up participants, validate invoices, and send sandbox test invoices.

- Trust score: 80/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `api.getpeppr.dev`: 80/100 (this document), [markdown](https://verifymcp.io/servers/dev-getpeppr-mcp/api.md), [page](https://verifymcp.io/servers/dev-getpeppr-mcp/api)
- remote · `api.getpeppr.dev`: 39/100, [markdown](https://verifymcp.io/servers/dev-getpeppr-mcp/mcp-auth.md), [page](https://verifymcp.io/servers/dev-getpeppr-mcp/mcp-auth)

## Channel facts

- Endpoint: `https://api.getpeppr.dev/mcp`
- Transports: `streamable-http`
- Auth: `none`
- 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**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - 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.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 66/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1536 tokens (~219/item across 7 items; 7 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 57/100
  - Stability observed for 17 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.
  - All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 8 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 getpeppr MCP server?

getpeppr is a hosted endpoint at https://api.getpeppr.dev/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 dev-getpeppr-mcp 'https://api.getpeppr.dev/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "dev-getpeppr-mcp": {
      "url": "https://api.getpeppr.dev/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "dev-getpeppr-mcp": {
      "type": "http",
      "url": "https://api.getpeppr.dev/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.dev-getpeppr-mcp]
url = "https://api.getpeppr.dev/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dev-getpeppr-mcp": {
      "type": "remote",
      "url": "https://api.getpeppr.dev/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add dev-getpeppr-mcp --url 'https://api.getpeppr.dev/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  dev-getpeppr-mcp:
    url: "https://api.getpeppr.dev/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "dev-getpeppr-mcp": {
      "Transport": "http",
      "Url": "https://api.getpeppr.dev/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add dev-getpeppr-mcp -t streamable-http -u 'https://api.getpeppr.dev/mcp'
```

### Other

```json
{
  "mcpServers": {
    "dev-getpeppr-mcp": {
      "type": "http",
      "url": "https://api.getpeppr.dev/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 80, +1)

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

### 2026-11-03 (score 79, +1)

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

### 2026-11-01 (score 78, +1)

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

### 2026-10-29 (score 77, +1)

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

### 2026-10-27 (score 76, +1)

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

### 2026-10-25 (score 75, +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-10-23 (score 74, +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-10-21 (score 73, +1)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “validate_invoice” rewrote its description, which is the text the model reads
- [cosmetic] “validate_invoice” reworded the description of “invoice”
- [cosmetic] “validate_invoice” reworded the description of “xml”

## MCP tools (7)

### `plan_integration` (~105 tokens)

Plan a getpeppr integration

Returns the integration steps, code snippets and documentation links for adding Peppol to an application, for a single sender or for a platform that sends on behalf of its customers.

Input parameters:

- `countries` (array, required): ISO 3166-1 alpha-2 codes of the senders' countries, e.g. ["BE", "DE"].
- `mode` (string, required): "single_sender": your own company sends its invoices. "platform": your software sends for many customer companies.

### `search_docs` (~86 tokens)

Search the getpeppr documentation

Searches the prose of the public getpeppr documentation and returns up to 5 matching pages, each with its url and a short excerpt. Excerpts carry no code: open the returned url, or call plan_integration, for code.

Input parameters:

- `query` (string, required): What to look for in the getpeppr documentation, e.g. "CustomizationID" or "webhook retries".

### `validate_invoice` (~169 tokens)

Validate an invoice

Validates a Peppol BIS Billing 3.0 UBL document against the Peppol rules, or a getpeppr invoice JSON against the SDK rules, and explains each violation. It does not check whether the invoice can be sent. Send sample or test invoices only, never a real invoice or real people's data.

Input parameters:

- `format` (string, required): "ubl" for a Peppol BIS 3 UBL document, "json" for a getpeppr SDK invoice.
- `invoice` (object): A sample or test invoice in the getpeppr SDK shape, never a real one, when format is "json".
- `xml` (string): A sample or test UBL document, never a real invoice, when format is "ubl" (at most 1 MiB).

### `lookup_participant` (~116 tokens)

Look up a Peppol participant

Says whether a Peppol identifier (scheme:identifier) is registered to receive documents on the production Peppol network, and which ones. A sandbox test customer is never on it, and send_test_invoice only targets the test receiver 9925:BE0314595348 whatever this answers.

Input parameters:

- `peppolId` (string, required): Peppol participant identifier, e.g. "9925:BE0314595348", "0208:0685660237" or "GB:VAT:123456789".

### `create_test_customer` (~249 tokens)

Create a sandbox test customer

Platform accounts only: creates a test customer (sub-tenant legal entity) in the getpeppr sandbox and returns its registration state. Up to 10 active test customers per account; identifier rules per country: https://getpeppr.dev/docs/platform/legal-entities/. Calling it again with the same arguments returns the same test customer with its current status, never a second one. Pass the returned legalEntity.id as sender.legalEntityId to send_test_invoice once its status allows sending. Requires the admin role and signing in to getpeppr.

Input parameters:

- `address` (object, required): The company's registered address.
- `companyName` (string, required): The test customer company's legal name.
- `country` (string, required): ISO 3166-1 alpha-2, e.g. "BE".
- `externalId` (string, required): Your own id for this customer company. Calling again with the same arguments returns the same test customer, with its current status.
- `identifier` (object): One Peppol identifier, e.g. { "scheme": "0208", "value": "0123456789" }.
- `identifiers` (array): Several identifiers, in the order the country guide gives.

### `send_test_invoice` (~344 tokens)

Send a sandbox test invoice

Sends an invoice in the getpeppr sandbox to the Belgian test receiver 9925:BE0314595348, for your own company or for one of your test customers. Never sends a real invoice. Lines without tax fields get your account's sandbox tax profile. While your sandbox tax profile is unchanged, calling it again with the same arguments returns the same document, never a second one. Returns a documentId to pass to get_document_status. Requires signing in to getpeppr.

Input parameters:

- `invoice` (object, required): An invoice in the getpeppr SDK shape (https://getpeppr.dev/docs/types/). Minimal example: {"number":"INV-001","to":{"name":"SPF Economie (test receiver)","peppolId":"9925:BE0314595348","street":"Rue…
- `sender` (object): Platform accounts: send as one of your test customers (the legalEntity.id create_test_customer returned). Its tax fields are then yours to set: O with vatRate 0 for a test customer without a VAT numb…

### `get_document_status` (~108 tokens)

Get a document's status

Returns the status and lifecycle events of a sandbox document sent from your getpeppr account; call it with the documentId send_test_invoice returned. submitted: getpeppr accepted it. delivered: the test receiver's access point received it, the goal of a sandbox test. failed: final, with a failureCategory. In application code, subscribe to webhooks instead of polling. Requires signing in to getpeppr.

Input parameters:

- `documentId` (string, required): The documentId send_test_invoice returned.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/dev-getpeppr-mcp/api#diagnostics

## Score history

- 2026-11-05: 80
- 2026-11-04: 79
- 2026-11-03: 79
- 2026-11-02: 78
- 2026-11-01: 78
- 2026-10-31: 77
- 2026-10-30: 77
- 2026-10-29: 77
- 2026-10-28: 76
- 2026-10-27: 76
- 2026-10-26: 75
- 2026-10-25: 75
- 2026-10-24: 74
- 2026-10-23: 74
- 2026-10-22: 73
- 2026-10-21: 73
- 2026-10-20: 72
- 2026-10-19: 72

## Common questions

### What is the getpeppr MCP server?

getpeppr is an MCP server listed in the public MCP registry as dev.getpeppr/mcp. Peppol e-invoicing: look up participants, validate invoices, and send sandbox test invoices. This page covers its hosted endpoint (https://api.getpeppr.dev/mcp).

### Is the getpeppr MCP server safe to use?

getpeppr 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 getpeppr MCP server expose?

getpeppr exposes 7 tools: plan_integration, search_docs, validate_invoice, lookup_participant, create_test_customer, and 2 more. Their descriptions and schemas cost roughly 1,177 tokens of context every time the server is loaded.

### Does the getpeppr MCP server require authentication?

No. We connected to getpeppr without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the getpeppr MCP server still maintained?

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

### What did VerifyMCP test on the getpeppr MCP server?

VerifyMCP ran 13 checks on getpeppr, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://api.getpeppr.dev/mcp
- Website: https://getpeppr.dev/docs/mcp/
- Changelog RSS feed: https://verifymcp.io/servers/dev-getpeppr-mcp/api.xml
- Changelog JSON feed: https://verifymcp.io/servers/dev-getpeppr-mcp/api/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/dev-getpeppr-mcp/api.json
- HTML version of this page: https://verifymcp.io/servers/dev-getpeppr-mcp/api