servers / norway-invoices-peppol-bis-3-0-ehf-via-storecove

Norway Invoices (Peppol BIS 3.0 / EHF via Storecove) MCP server

communitystreamable_httpremotewrite capablehealthy

Norway Peppol/EHF BIS 3.0 e-invoices for AI agents: send, check recipient, get delivery proof.


01Tools · 3

How to read this: tool names here are observed from a live tools/list handshake. The Risk label is a heuristic inferred from the tool name (write/destructive verbs), not from executing the tool — a conservative guess, not a verified capability. We never escalate risk from a description. Found one that's wrong? Tell us — we fix on report.

ToolRiskSide effectsApproval
create_invoice
Send a Norway B2B electronic invoice over the Peppol network in Peppol BIS 3.0 / EHF (EN 16931) format via Storecove (a certified Peppol Access Point). Norway is moving to mandatory structured e-invoicing for domestic B2B: the parliament (Stortinget) has adopted the reform and the sending obligation applies from 2027-01-01. Builds the structured invoice JSON from seller + buyer (name, Norwegian VAT NO<9 digits>MVA and/or organisasjonsnummer 9 digits, address) and line items (description, quantity, net unit price, VAT rate 25/15/12/0), computes the Norwegian VAT (MVA) breakdown, and submits it under YOUR OWN Storecove credentials. Bring your own credential as header x-storecove-key. You must also pass seller_legal_entity_id — the legalEntityId of the sender you created in your Storecove account. Norwegian VAT (MVA) rates: 25 (standard), 15 (food/groceries), 12 (transport/accommodation and other low-rate services), 0 (zero-rated/exempt/reverse charge). Amounts in NOK. Delivery over Peppol is asynchronous: this returns a submission guid — use get_delivery_evidence with it to fetch the delivery proof/status. Tip: call check_recipient first to confirm the buyer is reachable on Peppol. There is no cancel over Peppol: to reverse an invoice you issue a credit note (a new invoice).
writetrueunknown
check_recipient
Check whether a business can receive electronic invoices on the Peppol network before you send (Storecove POST /discovery/receives). This is the safe pre-flight for Norwegian B2B: pass the recipient identifier and scheme and learn if they are a registered Peppol participant. For Norway use scheme 0192 with the 9-digit organisasjonsnummer. Returns can_receive=true when the party is reachable (Storecove code OK). If can_receive is false, the recipient is not on Peppol — fall back to recipient_email in create_invoice or ask them to register.
readfalseunknown
get_delivery_evidence
Fetch the delivery evidence for an invoice sent by create_invoice, using its submission guid (Storecove GET /document_submissions/{guid}/evidence). Peppol delivery is asynchronous — this returns the proof of what was sent and the delivery status/receipt from the recipient Access Point. Call it shortly after create_invoice and poll until it reports delivery. Safe to call anytime.
readfalseunknown

02Install & source
https://inv-no.wishpool.app/mcp
remote_url

03Access granted
Process payments · write

The access this server can exercise, inferred from its verified tools — not a declared OAuth scope.


05Provenance & freshness
sourcesOfficial MCP Registry [p1]
last_checked2026-07-10 09:21Z
next_check2026-07-11 14:08Z
cadenceevery 29h
verifiedtools_list:passed handshake:passed metadata:passed
index_statusindex9 unique facts >= 5

06Badge

Add the “as seen on MCPExplorer” badge to your README. Norway Invoices (Peppol BIS 3.0 / EHF via Storecove) MCP — as seen on mcpexplorer.com

[![Norway Invoices (Peppol BIS 3.0 / EHF via Storecove) MCP — as seen on mcpexplorer.com](https://mcpexplorer.com/badge/norway-invoices-peppol-bis-3-0-ehf-via-storecove.svg)](https://mcpexplorer.com/servers/norway-invoices-peppol-bis-3-0-ehf-via-storecove)

Next step

This is one server. A loadout combines the right servers, governance, and proven plays for a whole job — assembled deliberately, not tool-dumped.

Explore loadouts →
Norway Invoices (Peppol BIS 3.0 / EHF via Storecove) MCP server — MCPExplorer