Skip to content

getpeppr MCP server

dev.getpeppr/mcpgetpeppr.devstreamable-httpv1.0.3Scanned

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

7 tools: 1 do something that can't be undone, 1 change things and 5 only read.

Tools: 0 delete, 1 irreversible, 1 write, 5 read.
  • Reads private data · 3
  • Reads text others write · 4
  • Can send data out · 1
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here does something that can't be undone. Govern it.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the getpeppr MCP server can do

The getpeppr MCP server is published by getpeppr.dev, a domain the MCP Registry verified. It has 7 tools. It can do things that cannot be undone, such as sending, paying or publishing (send_test_invoice) and create or change data (1 tool: create_test_customer), but cannot delete data. 5 tools only read.

3 tools read private data (search_docs, lookup_participant and get_document_status); 4 tools bring in text other people can write (search_docs, lookup_participant, create_test_customer and 1 more); 1 tool can send data out of your system (send_test_invoice). On its own it has all three parts of a prompt-injection exfiltration path: private data, text others write, and a way out.

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 20, 2026, version 1.0.3.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

7 tools

Can't be undone 1Claude Code: ask
  • 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.Reads text others writeCan send data outNo findings

    Why it is in this group

    • The name "send_test_invoice" says "send": a word for sending, and what is sent cannot be taken back.
    • The input addresses people (input.invoice.to): what it sends cannot be taken back.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • outboundThe name "send_test_invoice" says "send": it sends or publishes something to other people.
    • outboundThe input takes a destination (input.invoice.to): what the tool writes goes there.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Send a sandbox test invoice
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
Changes things 1Claude Code: ask
  • create_test_customerPlatform accounts only: creates a test customer (sub-tenant legal entity) in the getpeppr sandbox and returns its registration state.Reads text others writeNo findings

    Why it is in this group

    • The name "create_test_customer" says "create": a word for a change.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Create a sandbox test customer
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
Only reads 5Show 5 read-only tools
  • 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.Reads private dataNo findings

    Why it is in this group

    • The name "get_document_status" says "get": a word for reading.

    What it can reach

    • private-dataThe name "get_document_status" says "get" and "document": it reads documents.
    • private-dataThe description's first sentence says "return" and "document": it reads documents.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Get a document's status
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • lookup_participantSays whether a Peppol identifier (scheme:identifier) is registered to receive documents on the production Peppol network, and which ones.Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "lookup_participant" says "lookup": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "document": it reads documents.
    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Look up a Peppol participant
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • 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 customer…No findings

    Why it is in this group

    • The description's first verb is "return": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Plan a getpeppr integration
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • search_docsSearches the prose of the public getpeppr documentation and returns up to 5 matching pages, each with its url and a short excerpt.Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "search_docs" says "search": a word for reading.

    What it can reach

    • private-dataThe name "search_docs" says "search" and "doc": it reads documents.
    • untrusted-inputThe description's first sentence says "search" and "url": it reads web pages, which anyone can write.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Search the getpeppr documentation
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • 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.No findings

    Why it is in this group

    • The name "validate_invoice" says "validate": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Validate an invoice
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

12 paths in this server alone from private data, through text someone else wrote, to a way out. Denying 1 outbound tool breaks every one.

Reads private data3
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write4
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out1
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
deny to break every path
{
  "permissions": {
    "deny": [
      "mcp__getpeppr__send_test_invoice"
    ]
  }
}

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:52 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
2
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
https://api.getpeppr.dev/.well-known/oauth-protected-resource/mcp
Authorization servers
https://clerk.getpeppr.dev
Legacy HTTP+SSE transport
no
Dynamic client registration
yes
Client ID metadata documents
yes
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 2 tools that change things (1 irreversible, 1 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://api.getpeppr.dev/mcp: tools/list returned 7 tools to an anonymous client, including send_test_invoice (irreversible), create_test_customer (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 1.0.3. Values in angle brackets are yours to fill in.

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

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__getpeppr__plan_integration",
      "mcp__getpeppr__search_docs",
      "mcp__getpeppr__validate_invoice",
      "mcp__getpeppr__lookup_participant",
      "mcp__getpeppr__get_document_status"
    ],
    "ask": [
      "mcp__getpeppr__create_test_customer",
      "mcp__getpeppr__send_test_invoice"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as getpeppr. Review it before you use it.

Capability tags behind 5 rules
  • mcp__getpeppr__search_docs private-data, untrusted-input
  • mcp__getpeppr__lookup_participant private-data, untrusted-input
  • mcp__getpeppr__create_test_customer untrusted-input
  • mcp__getpeppr__send_test_invoice untrusted-input, outbound
  • mcp__getpeppr__get_document_status private-data

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/dev.getpeppr/mcp/verify?hash=cb52d04ed1210c6f4d0b26d8d8d3c3cc86d6369f39bafc17065deeac5994e5f1" | jq -e '.changed == false'

Pinned hash cb52d04ed121, from Nov 20, 2026, 22:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/dev.getpeppr/mcp/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for dev.getpeppr/mcp
[![Anlyon Radar](https://radar.anlyon.com/badge/dev.getpeppr/mcp.svg)](https://radar.anlyon.com/servers/dev.getpeppr/mcp)

Source: MCP Registry · repository. Synced Nov 6, 2026, 20:17 UTC.

getpeppr MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the getpeppr MCP server safe?

No scan can promise that. What its definitions show: 7 tools, 2 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the getpeppr MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the getpeppr MCP server do things that cannot be undone?

Yes. 1 tool can send, pay, publish or merge: send_test_invoice.

What tools does the getpeppr MCP server have?

7 tools: 1 irreversible, 1 write, 5 read. send_test_invoice, create_test_customer, plan_integration, search_docs, validate_invoice, lookup_participant and get_document_status.

Does the getpeppr MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the getpeppr MCP server send data to outside services?

1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): send_test_invoice.

Has the getpeppr MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 20, 2026.