getpeppr

dev.getpeppr由 getpeppr.dev 發布官方發布者v1.0.3更新於 Nov 7, 2026

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

已驗證Streamable HTTP可網頁執行金融知識與記憶開發者工具

概覽

AI 產生的概覽

僅限沙箱的 Peppol 電子發票助手:規劃整合、檢索文件、驗證發票、查詢參與者並寄送測試發票。

可以做什麼
  • 規劃整合:取得單一寄送方或平台情境的步驟、程式碼片段與文件連結
  • 檢索 getpeppr 公開文件並回傳相符頁面與摘要
  • 驗證 Peppol BIS Billing 3.0 UBL 或 getpeppr 發票 JSON,並逐項說明違規
  • 查詢某個 Peppol 識別碼是否已在正式網路註冊
  • 建立沙箱測試客戶,並向固定的比利時測試接收方寄送測試發票
  • 追蹤沙箱文件的狀態與生命週期事件,直到送達或失敗
適用情境
適合正在把 Peppol 電子發票整合進應用程式的開發者:讓助理草擬整合方式、依 Peppol 規則檢查發票文件,並在上線前完成一次端到端沙箱投遞測試。
執行需求
透過 streamable HTTP 連線 api.getpeppr.dev 遠端端點,無需本機安裝。驗證與參與者查詢不需要帳號。帳號類工具首次使用時需登入 getpeppr,或以 bearer 方式提供沙箱 API 金鑰;寄送還需要免費帳號及已註冊的公司。
安裝前請注意
僅限沙箱:不會寄送真實發票,也不會在正式環境操作,測試發票只會寄往固定的測試接收方。請勿將真實發票或真實個人資料送進 validate_invoice。帳號類工具會建立測試客戶並寄送文件,伺服器會要求登入或沙箱 API 金鑰;不要在其中使用正式金鑰。

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 getpeppr,將其新增到工作區。
  2. 為需要使用其工具的對話啟用該服務。

Web executable,透過 Streamable HTTP。 遠端服務在工作區中設定後即可從網頁執行環境執行。

交給代理程式安裝

把這段提示詞貼上到 Claude Code、Codex、Cursor 等代理程式,或 SourceWeft 對話中。代理程式會讀取該伺服器的安裝指南,先向你展示發布者、端點和登入方式,經你同意後再把它新增到你的客戶端。金鑰不會寫進任何命令。

閱讀 https://sourceweft.com/mcp/dev.getpeppr%2Fmcp/install.md,並按其中說明把這個 MCP 伺服器接入我的客戶端。修改任何設定之前,先告訴我它的發布者、端點和登入方式,等我確認。不要把 API 金鑰寫進命令或我會提交的檔案;問我金鑰應從哪裡取得。

檢視代理程式所依據的安裝指南

其他 MCP 客戶端

把它新增到你客戶端的 mcpServers 設定中。

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

README

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.

AddressWhen to use it
https://api.getpeppr.dev/mcpThe 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/authAsks 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:

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

Or from a terminal:

bash
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

bash
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

bash
codex mcp add getpeppr --url https://api.getpeppr.dev/mcpcodex 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

ToolAccountWhat it does
lookup_participantNoWhether an identifier is registered on the production Peppol network, with which provider, and what the directory says about it.
validate_invoiceNoChecks 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_integrationNoThe steps and code for your case (your own company, or a platform sending for customers) and your countries.
search_docsNoFinds getpeppr documentation pages, each with a short excerpt.
send_test_invoiceYes, writes (sandbox)Sends a sandbox invoice to the sandbox test receiver 9925:BE0314595348.
get_document_statusYes, readsThe status of one of your documents and its event timeline.
create_test_customerYes, writes (sandbox)Platform accounts: creates a sandbox customer company to send as.

From zero to a delivered test invoice

  1. plan_integration gives the steps and code for your case; search_docs finds the pages to read.
  2. validate_invoice and lookup_participant work without an account.
  3. Create a free getpeppr account and register your own company in the console.
  4. send_test_invoice sends to the sandbox test receiver. Platform accounts first call create_test_customer, then send as that customer.
  5. 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

來源:README.md,提交 48268d9

工具

7

plan_integration

Plan a getpeppr 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.

輸入參數mode必填countries必填

search_docs

Search the getpeppr documentation

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.

輸入參數query必填

validate_invoice

Validate an 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 data.

輸入參數xmlformat必填invoice

lookup_participant

Look up a Peppol 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.

輸入參數peppolId必填

create_test_customer

Create a sandbox 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 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.

輸入參數address必填country必填externalId必填identifiercompanyName必填identifiers

send_test_invoice

Send a sandbox 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 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.

輸入參數senderinvoice必填

get_document_status

Get a document's 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: final, with a failureCategory. In application code, subscribe to webhooks instead of polling. Requires signing in to getpeppr.

輸入參數documentId必填

版本歷史

2
  1. v1.0.3最新Nov 7, 2026
  2. v1.0.0Oct 19, 2026

評分

已滿足適用檢查項的 90%

該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。

  • 近 30 天內可連通必需25 分
  • 已宣告認證方式必需10 分
  • 已列出工具必需15 分
  • 描述必需15 分
  • 圖示10 分
  • 文件15 分
  • 授權條款10 分

    請在儲存庫或註冊中心條目中宣告授權條款。