getpeppr
REMOTE · API.GETPEPPR.DEV · 2 COMPONENTS
Peppol e-invoicing: look up participants, validate invoices, and send sandbox test invoices.
Available components
Last scanned (16 hours ago)
Scores higher than 81% of remote servers
Reachable. Last reached 5 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 Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Partial
- 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
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability66
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management57
- Stability observed for 17 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
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 8 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
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 5 Nov 26 +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.
- 3 Nov 26 +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.
- 1 Nov 26 +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.
- 29 Oct 26 +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.
- 27 Oct 26 +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.
- 25 Oct 26 +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.
- 23 Oct 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.
- 21 Oct 26 +1
- 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 security
- “validate_invoice” reworded the description of “invoice” cosmetic
- “validate_invoice” reworded the description of “xml” cosmetic
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 5 Nov 2026 · Probed https://api.getpeppr.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=api.getpeppr.dev | CN=YR2,O=Let's Encrypt,C=US | 5 Oct 2026 | 3 Jan 2027 | RSA 2048 | SHA256-RSA | 63245944c044cb26f7fb053655aaf3ea2ff |
| SANs: api.getpeppr.dev | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.getpeppr.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | DS published | 60074 | 8 | Verified |
| getpeppr.dev. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains; preload |
| content-security-policy | default-src 'self'; script-src 'self' 'unsafe-inline' https://js.stripe.com https://*.clerk.accounts.dev https://clerk.getpeppr.dev https://challenges.cloudflare.com; worker-src 'self' blob:; frame-src https://js.stripe.com https://*.clerk.accounts.dev https://accounts.getpeppr.dev https://challenges.cloudflare.com; style-src 'self' 'unsafe-inline'; img-src 'self' data: https://getpeppr.dev https://*.clerk.com https://*.stripe.com https://img.clerk.com; connect-src 'self' https://*.clerk.accounts.dev https://clerk.getpeppr.dev https://challenges.cloudflare.com https://api.stripe.com https://*.ingest.sentry.io; font-src 'self'; object-src 'none'; base-uri 'self'; form-action 'self'; frame-ancestors 'none' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | origin |
| permissions-policy | camera=(), microphone=(), geolocation=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.getpeppr.dev/mcp | Verified | 200 | |
| http (plaintext) | http://api.getpeppr.dev/mcp | HTTPS enforced | 308 | https://api.getpeppr.dev/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 →
create_test_customer Create a sandbox test customer ~249
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.
| Name | Type | Req | Description |
|---|---|---|---|
| address | object | yes | The company's registered address. |
| companyName | string | yes | The test customer company's legal name. |
| country | string | yes | ISO 3166-1 alpha-2, e.g. "BE". |
| externalId | string | yes | 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. |
No output schema declared.
No examples provided.
get_document_status Get a document's status ~108
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.
| Name | Type | Req | Description |
|---|---|---|---|
| documentId | string | yes | The documentId send_test_invoice returned. |
No output schema declared.
No examples provided.
lookup_participant Look up a Peppol participant ~116
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.
| Name | Type | Req | Description |
|---|---|---|---|
| peppolId | string | yes | Peppol participant identifier, e.g. "9925:BE0314595348", "0208:0685660237" or "GB:VAT:123456789". |
No output schema declared.
No examples provided.
plan_integration Plan a getpeppr integration ~105
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.
| Name | Type | Req | Description |
|---|---|---|---|
| countries | array | yes | ISO 3166-1 alpha-2 codes of the senders' countries, e.g. ["BE", "DE"]. |
| mode | string | yes | "single_sender": your own company sends its invoices. "platform": your software sends for many customer companies. |
No output schema declared.
No examples provided.
search_docs Search the getpeppr documentation ~86
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.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | What to look for in the getpeppr documentation, e.g. "CustomizationID" or "webhook retries". |
No output schema declared.
No examples provided.
send_test_invoice Send a sandbox test invoice ~344
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.
| Name | Type | Req | Description |
|---|---|---|---|
| invoice | object | yes | 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… |
No output schema declared.
No examples provided.
validate_invoice Validate an invoice ~169
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.
| Name | Type | Req | Description |
|---|---|---|---|
| format | string | yes | "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). |
No output schema declared.
No examples provided.
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.
remote · api.getpeppr.dev
claude mcp add --transport http dev-getpeppr-mcp 'https://api.getpeppr.dev/mcp'
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.