getpeppr
dev.getpeppr/mcpVersion 1.0.3Peppol e-invoicing: look up participants, validate invoices, and send sandbox test invoices.
Status
Responds332 msAnswered our handshake without sign-in.- Last checked
- Nov 14, 2026, 14:27 UTC
- Latency
- 332 ms
- Remotes responding
- 2 of 2
- Sign-in
- OAuth sign-in, No sign-in
- Hosting
- Hosted outside the EU (detected)
- Registry data as of
- Nov 14, 2026, 21:12 UTC
Data from the official MCP Registry, checked by run.zero. How we check
Connect
Streamable HTTP
https://api.getpeppr.dev/mcpResponds428 msNo sign-in
Claude Code
claude mcp add --transport http getpeppr https://api.getpeppr.dev/mcpClaude Desktop and claude.ai
Settings > Connectors > Add custom connector
Name: getpeppr
Remote MCP server URL: https://api.getpeppr.dev/mcpCursor
{
"mcpServers": {
"getpeppr": {
"url": "https://api.getpeppr.dev/mcp"
}
}
}VS Code
code --add-mcp '{"name":"getpeppr","type":"http","url":"https://api.getpeppr.dev/mcp"}'Streamable HTTP
https://api.getpeppr.dev/mcp/authSign-in required332 msOAuth sign-in
Claude Code
This server asks for sign-in. Your client opens the sign-in when it connects.
claude mcp add --transport http getpeppr https://api.getpeppr.dev/mcp/authClaude Desktop and claude.ai
Settings > Connectors > Add custom connector
Name: getpeppr
Remote MCP server URL: https://api.getpeppr.dev/mcp/authCursor
{
"mcpServers": {
"getpeppr": {
"url": "https://api.getpeppr.dev/mcp/auth"
}
}
}VS Code
code --add-mcp '{"name":"getpeppr","type":"http","url":"https://api.getpeppr.dev/mcp/auth"}'Built your own server? run.zero hosts MCP servers on European infrastructure.
Tools
7 tools
Read-only | Idempotent | Open world | ||
|---|---|---|---|---|
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 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. | No | No | Yes | Yes |
get_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 failureCategory. In application code, subscribe to webhooks instead of polling. Requires signing in to getpeppr. | No | Yes | Yes | No |
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. | No | Yes | Yes | Yes |
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. | No | Yes | Yes | No |
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. | No | Yes | Yes | No |
send_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 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. | No | No | Yes | Yes |
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. | No | Yes | Yes | No |
Details
- Registry status
- Active
- Published
- Nov 6, 2026
- Updated
- Nov 6, 2026
- Categories (suggested)
- Invoicing and accountingSuggested categories are assigned automatically from the registry text and may be wrong. Verified operators can correct them.
- GDPR
- Not declared