getpeppr

Name: getpeppr
Author: zerolooplabs

作者：zerolooplabs版本 1.0.2i★ –i在云端运行

注册名称dev.getpeppr/mcp

安装

概览

作者提供的说明（英文原文）

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

PopNx MCP 的三大支柱

这三项永远不会合并成一个分数：意见、测量和人气是不同的东西。

用户评价i暂无评价评价功能将在后续阶段与账户功能一起开放
我们的基础检查i3 项中通过 3 项依据公开信息检查；尚未扫描代码
使用情况i尚未统计★ –

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

连接方式: 在云端运行
传输方式: Streamable HTTP
分类: 其他

安装

选择你使用的 AI 应用，然后复制设置。

安装之前

基础检查：3 项中通过 3 项
在作者的服务器上运行：你向它提出的内容会经过他们的服务器。
可以做 7 件事（工具） plan_integration, search_docs, validate_invoice, lookup_participant …
注册中心没有列出需要填写的密钥。

你需要

在云端运行无需安装任何东西，通过互联网连接

你用的是哪个应用？

ClaudeClaude CodeCursorVS CodeChatGPT

在上方选择你的应用。我们会记住它，下次按钮会显示“安装到 …”。

适用于网页版、桌面版和手机版 Claude：

打开 Settings → Connectors
点击 Add custom connector
粘贴下面的地址，然后点击 Add
如果要求登录，请登录作者的服务

https://api.getpeppr.dev/mcp

在终端中运行这条命令

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

在 Cursor 中打开

或者自己复制设置

粘贴到项目中的 .cursor/mcp.json，或 ~/.cursor/mcp.json

{
  "mcpServers": {
    "getpeppr": {
      "url": "https://api.getpeppr.dev/mcp"
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

在 VS Code 中打开

或者自己复制设置

粘贴到项目中的 .vscode/mcp.json

{
  "servers": {
    "getpeppr": {
      "type": "http",
      "url": "https://api.getpeppr.dev/mcp"
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

ChatGPT 只能连接互联网上的服务器：

打开网页版 ChatGPT → Settings → Connectors (Apps)
点击 Create 或 Add（部分套餐需要先在 Advanced 中开启 Developer mode）
粘贴下面的地址，起个名字，然后保存
如果要求登录，请登录作者的服务

https://api.getpeppr.dev/mcp

菜单名称可能因套餐和版本不同而略有差异。

你的选择通过 Cookie 保存在这台设备上，无需账户。

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同，请以 README 为准。

它能做什么

工具名称和描述与服务器在 2026年11月6日报告的完全一致。这些内容由作者撰写，不是我们写的；我们以纯文本形式显示。

plan_integration
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_docs
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.
validate_invoice
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 dat
lookup_participant
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.
create_test_customer
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 wit
send_test_invoice
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 unchange
get_document_status
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: fin

基础检查i

我们检查的是任何人都能看到的信息；我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月7日

✓ 通过
作者与仓库一致
注册名称已通过域名 getpeppr.dev 验证（注册中心会核实域名所有权）
… 尚未检查
仍在维护
我们还没有从 GitHub 读取这个仓库
… 尚未检查
有许可证
我们还没有从 GitHub 读取这个仓库
✓ 通过
端点有响应
在 360 毫秒内响应（HTTP 200）
– 不适用
使用 OAuth 登录
无需登录
✓ 通过
工具描述中没有隐藏指令
已读取 7 个工具描述，未发现针对 AI 的隐藏指令

与“其他”中的其他服务器比较i

星标数多于此分类中其他 32568 个服务器的 0%
发布到注册中心的时间比此分类中其他 32568 个服务器的 100% 更新
基础检查结果等于或优于此分类中其他 32568 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时，星标数才计入。

常见问题

getpeppr 安全吗？

它在 3 项适用的基础检查中通过了 3 项。我们没有阅读代码。在添加密钥或令牌之前，请先看看这个服务器要求哪些权限，并使用只具备所需权限的密钥。

它需要哪些密钥或代码？

注册中心没有列出必需的密钥，不过有些服务器会在首次使用时要求你登录。

它在我的电脑上运行还是在云端？

它在作者的云端运行。通过互联网连接，无需安装，但你发送的内容会经过作者的服务器。

它还在维护吗？

GitHub 仓库最后更新于–，最新版本（1.0.2）于今天进入注册中心。

哪些应用可以使用它？

支持 MCP 的应用，例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接，所以接受远程 MCP 服务器的应用也可以使用，例如开启开发者模式的 ChatGPT。

有什么可以替代它？

同一分类中有：Spec Driven Development, Remote Desktop Commander, FlyDocs

替代选择

同一分类中其他作者的服务器，按星标数排序。

如何看卡片：★ GitHub 星标i三大支柱：评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

Spec Driven Development

作者：formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

在你的电脑上运行★ 440MIT14个月前更新

安装

Remote Desktop Commander

作者：desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

在云端运行★ 211昨天更新

安装

FlyDocs

作者：flydocs.ai

Spec-driven development workflow: your agent works issues, sessions and the status lifecycle.

在你的电脑上运行今天更新

安装

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

getpeppr MCP server

A hosted Model Context Protocol server for Peppol e-invoicing, run by getpeppr.

Your assistant can plan a getpeppr integration, search the getpeppr documentation, check a test invoice against the Peppol rules and look up a participant on the Peppol network. With a free getpeppr sandbox account, it can also send test invoices and follow their status.

This repository holds no source code. The server is hosted and operated by getpeppr (Zero Loop Labs Ltd, UK). This repository describes it for MCP registries and directories. Nothing to install: you add an address to your assistant.

Full documentation: https://getpeppr.dev/docs/mcp/

Sandbox only. The server never sends a real invoice and never acts in production. Test invoices go to the sandbox test receiver 9925:BE0314595348, and a production key (sk_live_…) is refused: keep it out of your assistant's configuration. The participant lookup, on the other hand, reads the live Peppol network.

Addresses

Registry name: dev.getpeppr/mcp · transport: streamable HTTP.

Address	When to use it
`https://api.getpeppr.dev/mcp`	The four public tools work at once, without an account. The account tools ask you to sign in the first time you use one. For clients that open a sign-in page when a tool asks, such as Claude Code and Codex.
`https://api.getpeppr.dev/mcp/auth`	Asks you to sign in to getpeppr when you connect. For clients that sign in at connection time, such as VS Code, Cursor and Claude (web & desktop).

Configure your assistant

VS Code (GitHub Copilot)

Add to .vscode/mcp.json in your workspace, or to your user mcp.json:

"servers": { "getpeppr": { "type": "http", "url": "https://api.getpeppr.dev/mcp/auth" } } }

Or from a terminal:

code --add-mcp '{"name":"getpeppr","type":"http","url":"https://api.getpeppr.dev/mcp/auth"}'

VS Code asks you to sign in to getpeppr when it connects.

Claude Code

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

When you first call an account tool, run /mcp in Claude Code and sign in to getpeppr.

Codex

codex mcp add getpeppr --url https://api.getpeppr.dev/mcp

codex mcp login getpeppr

Run the login before using the account tools.

Cursor and Claude (web & desktop)

Both connect through https://api.getpeppr.dev/mcp/auth. getpeppr is also listed in Claude's connector directory. See the documentation for the one-click Cursor install.

Signing in

Signing in uses your getpeppr account; there is no API key to copy. You choose the organisation the assistant acts for. You can also pass a sandbox API key (sk_sandbox_…) as a bearer token instead of signing in.

No account yet? Create a free sandbox account.

Tools

Tool	Account	What it does
`lookup_participant`	No	Whether an identifier is registered on the production Peppol network, with which provider, and what the directory says about it.
`validate_invoice`	No	Checks a UBL document against the official Peppol rulebooks, or a JSON invoice against the getpeppr SDK's rules. Give it sample or test invoices only, never a real invoice or real people's data.
`plan_integration`	No	The steps and code for your case (your own company, or a platform sending for customers) and your countries.
`search_docs`	No	Finds getpeppr documentation pages, each with a short excerpt.
`send_test_invoice`	Yes, writes (sandbox)	Sends a sandbox invoice to the sandbox test receiver `9925:BE0314595348`.
`get_document_status`	Yes, reads	The status of one of your documents and its event timeline.
`create_test_customer`	Yes, writes (sandbox)	Platform accounts: creates a sandbox customer company to send as.

From zero to a delivered test invoice

plan_integration gives the steps and code for your case; search_docs finds the pages to read.
validate_invoice and lookup_participant work without an account.
Create a free getpeppr account and register your own company in the console.
send_test_invoice sends to the sandbox test receiver. Platform accounts first call create_test_customer, then send as that customer.
get_document_status follows the document until it is delivered or failed.

Going live (an sk_live_ key, real receivers, webhooks) happens in the getpeppr console and in your own code, never through this server.

Limits

Public tools are rate limited per network address, and account tools per account. getpeppr can turn the MCP tools off without notice to protect the service; they then answer mcp.temporarily_disabled, and the API itself is not affected. Details: Limits.

Privacy and contact

Privacy policy: https://getpeppr.dev/privacy/
Questions: hello@getpeppr.dev