accueil / serveurs / Finance & Paiement / dev.getpeppr/mcp
dev.getpeppr/mcp
serveur MCP (Model Context Protocol) · getpeppr 1.0.0
Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur.
Est-ce que dev.getpeppr/mcp est sûr ?
Au dernier audit MCP Hub, le serveur MCP « dev.getpeppr/mcp » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.
Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.
Les 7 outils
- create_test_customer≈ 617 tokens
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.
Paramètres, retour & exemple (6)
Paramètresaddress· object · requis
The company's registered address.country· string · requis
ISO 3166-1 alpha-2, e.g. "BE".externalId· string · requis
Your own id for this customer company. Calling again with the same arguments returns the same test customer, with its current status.identifier· object · optionnel
One Peppol identifier, e.g. { "scheme": "0208", "value": "0123456789" }.companyName· string · requis
The test customer company's legal name.identifiers· array · optionnel
Several identifiers, in the order the country guide gives.
Exemple d'appel{"name": "create_test_customer", "arguments": {"address": {}, "country": "texte", "externalId": "texte", "companyName": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - get_document_status≈ 226 tokens
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.
Paramètres, retour & exemple (1)
ParamètresdocumentId· string · requis
The documentId send_test_invoice returned.
Exemple d'appel{"name": "get_document_status", "arguments": {"documentId": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - lookup_participant≈ 210 tokens
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.
Paramètres, retour & exemple (1)
ParamètrespeppolId· string · requis
Peppol participant identifier, e.g. "9925:BE0314595348", "0208:0685660237" or "GB:VAT:123456789".
Exemple d'appel{"name": "lookup_participant", "arguments": {"peppolId": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - plan_integration≈ 242 tokens
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.
Paramètres, retour & exemple (2)
Paramètresmode· string · requis · single_sender | platform
"single_sender": your own company sends its invoices. "platform": your software sends for many customer companies.countries· array · requis
ISO 3166-1 alpha-2 codes of the senders' countries, e.g. ["BE", "DE"].
Exemple d'appel{"name": "plan_integration", "arguments": {"mode": "single_sender", "countries": []}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - search_docs≈ 193 tokens
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.
Paramètres, retour & exemple (1)
Paramètresquery· string · requis
What to look for in the getpeppr documentation, e.g. "CustomizationID" or "webhook retries".
Exemple d'appel{"name": "search_docs", "arguments": {"query": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - send_test_invoice≈ 532 tokens
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.
Paramètres, retour & exemple (2)
Paramètressender· object · optionnel
Platform accounts: send as one of your test customers (the legalEntity.id create_test_customer returned). Its tax fields are then yours to set: O with vatRate 0 for a test customer without a VAT number, AE with vatRate 0 for one with a VAT number.invoice· object · requis
An invoice in the getpeppr SDK shape (https://getpeppr.dev/docs/types/). Minimal example: {"number":"INV-001","to":{"name":"SPF Economie (test receiver)","peppolId":"9925:BE0314595348","street":"Rue du Progrès 50","city":"Brussels","postalCode":"1210","country":"BE"},"lines":[{"description":"Consulting","quantity":1,"unitPrice":1000}]}. to.peppolId must be the sandbox test receiver 9925:BE0314595348. Omit "from": the sender is your registered company. Omit the line tax fields (vatRate, vatCategory, taxExemptReason): the server applies your account's sandbox tax profile to lines that carry none.
Exemple d'appel{"name": "send_test_invoice", "arguments": {"invoice": {}}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - validate_invoice≈ 268 tokens
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.
Paramètres, retour & exemple (3)
Paramètresxml· string · optionnel
A sample or test UBL document, never a real invoice, when format is "ubl" (at most 1 MiB).format· string · requis · ubl | json
"ubl" for a Peppol BIS 3 UBL document, "json" for a getpeppr SDK invoice.invoice· object · optionnel
A sample or test invoice in the getpeppr SDK shape, never a real one, when format is "json".
Exemple d'appel{"name": "validate_invoice", "arguments": {"format": "ubl"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]}
C'est votre serveur ?
Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».