All servers · Payments & accounting
getpeppr
dev.getpeppr/mcp · v1.0.0
New (7 days)Tools changed (7 days)
Measured by MCP Station
| Last check | Reachable |
|---|---|
| Checked at | — |
| Check success 7 / 30 days | — |
| First-try success 30 days | — |
| Median response | — |
| Lookups 30 days | — |
| Authentication | No auth |
| MCP version | 2025-06-18 |
| Rank score | — |
| Declared risk | Can write (some tools are not declared read-only) |
| Capabilities declared | tools |
| Tool definitions | 7 tools · with description 100% · input schema is an object 100% · read/destructive hints 100% |
Description written by the publisher, not verified
Peppol e-invoicing: look up participants, validate invoices, and send sandbox test invoices.
Connect
streamable-http · https://api.getpeppr.dev/mcp
claude mcp add --transport http mcp https://api.getpeppr.dev/mcp{
"mcpServers": {
"mcp": {
"url": "https://api.getpeppr.dev/mcp"
}
}
}streamable-http · https://api.getpeppr.dev/mcp/auth
claude mcp add --transport http mcp https://api.getpeppr.dev/mcp/auth{
"mcpServers": {
"mcp": {
"url": "https://api.getpeppr.dev/mcp/auth"
}
}
}Tools as reported by the server
plan_integrationReturns 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.search_docsSearches 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.validate_invoiceValidates 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.lookup_participantSays 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.create_test_customerPlatform 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 argumentssend_test_invoiceSends 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 againget_document_statusReturns 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 failureCa
Tool changes
- 2026-10-21: plan_integration, search_docs, validate_invoice, lookup_participant, create_test_customer, send_test_invoice, get_document_status
- 2026-10-20: plan_integration, search_docs, validate_invoice, lookup_participant, create_test_customer, send_test_invoice, get_document_status
Website · JSON · Text for agents · Registry updated 2026-10-19