MCP.Market

getpeppr MCP server

online · 100% uptime
by getpeppr.dev·dev.getpeppr/mcp·v1.0.0
No reviews yet

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

B81/100grade B
Write a reviewRun it
What users say
No reviews yet
Be the first
Safety scan
B81/100

full report

Adoption
New

Little public usage data yet

Reviews

Write one

Nobody has reviewed getpeppr yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

getpeppr tools (7, 2 write)

write = sends, deletes, buys or posts
  • create_test_customerwrite actionFree

    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.

  • get_document_statusFree

    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.

  • lookup_participantFree

    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.

  • plan_integrationFree

    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.

  • search_docsFree

    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.

  • send_test_invoicewrite actionFree

    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.

  • validate_invoiceFree

    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.

Public scan report

scanner v0.1.10 · 2026-10-27 · same rubric, same numbers if you re-run it

1 low
  • –Code scanremote-only server, no package to scann/a
  • Live reliabilityremote reachable in 1497ms20/20
  • Tool poisoning7 tool descriptions checked15/15
  • Auth qualityOAuth resource metadata advertised on 40115/15
  • Maintenanceno repository listed3/15
  • Maintainer identityendpoint served from the registry-verified namespace domain8/10

Findings (1)

  • lowNo source repository listedmaint.no-repo
Overall 81/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How getpeppr compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
81/100
higher than 62% of 48,255 servers
Tools
7
the typical server has 7
Tools that change things
29%
typical: 0%. Fewer write tools means less an agent can break
Uptime
100%
of our recent checks; the typical remote server answers 100%
Response time
752 ms
faster than 18% of 30,031 servers

What its tools let an agent do: 5 read · 1 create · 1 send or post

Install getpeppr in Claude Code, Cursor or VS Code

claude mcp add --transport http mcp https://api.getpeppr.dev/mcp
Add to Cursor

getpeppr: common questions

Is getpeppr MCP server safe?
Mostly: it is graded B (81/100). Read the getpeppr safety report
How do I install getpeppr?
It runs remotely at api.getpeppr.dev. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does getpeppr need an API key?
No key to paste: it signs you in with OAuth when your client connects.
Is getpeppr maintained?
The latest release is v1.0.0.
Is getpeppr up?
100% of our last 28 checks got an answer. We check remote servers about four times a day.
How does getpeppr compare with other MCP servers?
safety score 81/100 (higher than 62% of 48,255 servers); tools 7 (the typical server has 7); tools that change things 29% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.