app.wishpool/norway-invoice-mcp — MCP Server

This MCP server provides Norway Peppol/EHF BIS 3.0 e-invoice capabilities for AI agents, focusing on sending invoices, checking recipients, and retrieving delivery proof. It is exposed as an HTTP MCP server endpoint and is intended for integration in MCP-capable clients via configuration.

🛠️ Key Features

Send Norway Peppol/EHF BIS 3.0 e-invoices
Check invoice recipient
Get delivery proof
Runs as an HTTP MCP server (https://inv-no.wishpool.app/mcp)

🚀 Use Cases

Enable AI agents to transmit Norway e-invoices
Validate or verify invoice recipients before sending
Confirm delivery outcomes via delivery proof retrieval

⚡ Developer Benefits

No installation step; configure an MCP client with an HTTP server URL
Credentials, when required, are sent as HTTP headers per request and are not stored (per the referenced trust/threat model)

⚠️ Limitations

The documentation excerpt only partially describes self-hosting (“Or run it yourself” is truncated), and does not list supported operations beyond send, recipient checking, and delivery proof.

Norway Invoice MCP 🇳🇴 — How can my AI agent send a Peppol/EHF e-invoice in Norway?

Use it in 60 seconds

Paste this into your MCP client config (Claude Desktop, Cursor, Windsurf, or any MCP-capable agent):

json

{
  "mcpServers": {
    "norway-invoice": {
      "type": "http",
      "url": "https://inv-no.wishpool.app/mcp"
    }
  }
}

Nothing to install. Credentials, when you need them, travel as HTTP headers on each request and are never stored — see the threat model.

Or run it yourself

Would you rather not send production credentials to a server you do not control? Deploy this identical code to your own account and point your agent at your own URL:

bash

git clone https://github.com/junter1989k-ai/norway-invoice-mcp && cd norway-invoice-mcp && npx vercel --prod

MIT-licensed. Self-hosting removes us from the picture entirely, at no cost and with no loss of function.

Remote MCP server that lets any AI agent send Norway B2B electronic invoices over the Peppol network in Peppol BIS 3.0 / EHF (EN 16931) format via Storecove, a certified Peppol Access Point. It builds the structured invoice, computes the Norwegian VAT (MVA) breakdown, and delivers it under the merchant's own Storecove account. Stateless, bring-your-own credentials, never stores anything.

Live endpoint: https://inv-no.wishpool.app/mcp · Registry: app.wishpool/norway-invoice-mcp

Why now — the mandate (elektronisk faktura EHF)

Norway is moving to mandatory structured e-invoicing over Peppol BIS 3.0 / EHF for domestic B2B: the parliament (Stortinget) has adopted the reform and the sending obligation applies from 2027-01-01. EHF (Elektronisk Handelsformat) is Peppol BIS Billing 3.0 based. Paper and plain-PDF invoices no longer satisfy the B2B obligation.

Quick start

json

{
  "mcpServers": {
    "norway-invoice": {
      "type": "http",
      "url": "https://inv-no.wishpool.app/mcp",
      "headers": {
        "x-storecove-key": "your-storecove-api-key"
      }
    }
  }
}

Sign up at storecove.com — the merchant is the Peppol Access Point account holder. Request a free 30-day sandbox account from Storecove for a test key (sandbox does not need production onboarding). Create your sender under Senders to get the legalEntityId you pass as seller_legal_entity_id. Sandbox vs production is determined by the account your key belongs to — the base URL is the same. Authentication is HTTP Bearer with your key. Your key stays with you and travels per-request; this server never stores it.

Tools

Tool	What it does
`check_recipient`	Peppol participant discovery — is the buyer reachable on Peppol before you send? Pass the identifier (organisasjonsnummer scheme `0192`). Returns `can_receive`. The safe pre-flight.
`create_invoice`	Build a Peppol BIS 3.0 / EHF invoice from seller + buyer (Norwegian VAT `NO<9 digits>MVA` / organisasjonsnummer, address) and line items (description, net unit price, VAT rate 25/15/12/0, quantity), then submit over Peppol via Storecove. Returns a submission `guid` + computed VAT totals (`taxable`, `vat`, `total`).
`get_delivery_evidence`	Fetch the proof of what was sent and the Peppol delivery status by `guid`.

Amounts are in NOK. Norwegian VAT (MVA) rates: 25 (standard), 15 (food/groceries), 12 (transport/accommodation and other low-rate services), 0 (zero-rated/exempt/reverse charge). Parties identified by Norwegian VAT (NO<9 digits>MVA) and/or organisasjonsnummer (9 digits); Peppol routing scheme 0192.

No cancel over Peppol — to reverse an invoice you issue a credit note (a new invoice). create_invoice needs seller_legal_entity_id (your Storecove sender id). Owner policy guardrails ride optional headers (x-agentpay-max-amount, x-agentpay-approval-above, x-agentpay-allowed-tools) — set by the human owner in client config; the agent cannot relax them.

VAT math (deterministic)

Per line amountExcludingVat = round2(quantity × unit_price); grouped by (rate, category) into taxSubtotals (taxableAmount, taxAmount = round2(taxable × rate / 100)); gross amountIncludingVat = taxable + tax. Examples:

100 + 50 both @25% → taxable 150.00 / vat 37.50 / total 187.50
200 @25% + 100 @15% → taxable 300.00 / vat 65.00 (50 + 15) / total 365.00
2×50 @25% + 3×10 @15% + 1×40 @12% + 1×25 @0% → taxable 195.00 / vat 34.30 (25 + 4.50 + 4.80 + 0) / total 229.30
rounding: 33.33 @25% → 33.33 × 0.25 = 8.3325 → vat 8.33 / total 41.66

Endpoints wrapped (Storecove REST)

Base: https://api.storecove.com/api/v2 (single base URL; auth = HTTP Bearer with your API key)
Send: POST /document_submissions — JSON { legalEntityId, routing, document:{ documentType:"invoice", invoice:{…} } } → { guid }
Evidence: GET /document_submissions/{guid}/evidence — proof of what was sent + Peppol delivery status
Discovery: POST /discovery/receives — JSON { documentTypes, network, metaScheme, scheme, identifier } → { code:"OK", email }
Verified probe: a fake Bearer key really hits api.storecove.com/api/v2 → 403 {"errors":[{"source":"generic","details":"Not Authorized"}]} (endpoint alive; BYO = the merchant's own key validates).

Develop

bash

node test/serve.js   # local server on :3247
node test/e2e.js     # VAT math + Peppol/EHF JSON structure + protocol + validation + policy + fake-key live probe

Safety

Pure stateless translation layer over the Storecove REST API. Storecove is the certified Peppol Access Point under the merchant's own account; this service never signs, never onboards, and never stores anything. The API key travels per-request in a header, and funds are never touched — this issues tax invoices, it does not move money. Privacy policy.

Sister servers

Local invoices, one family: Denmark Peppol/NemHandel (inv-dk) · Belgium Peppol BIS (inv-be) · Italy FatturaPA (inv-it) · Malaysia MyInvois (inv-my) · Mexico CFDI (inv-mx) · Brazil NF-e (inv-br) · India GST (inv-in). Storecove also covers the Nordics, the Netherlands and Luxembourg on Peppol — those sister countries replicate this exact server. Local logistics: logi.wishpool.app. Local payments in 81 countries: mcp.wishpool.app.

MIT licensed.

seller_legal_entity_id	string	required	REQUIRED. The Storecove legalEntityId of the sender (created in your Storecove account under Senders). Numeric id, passed through to Storecove.
seller_name	string	required	Seller legal/company name.
seller_vat	string	optional	Seller Norwegian VAT number, format NO<9 digits>MVA (e.g. NO999999999MVA). Provide this and/or seller_org_number.
seller_org_number	string	optional	Optional seller Norwegian organisasjonsnummer (organization number), 9 digits.
seller_address	string	required	Seller street address.
seller_city	string	required	Seller city.
seller_zip	string	required	Seller postal code.
seller_country	string	optional	Seller country code. Default NO.
customer_name	string	required	Buyer legal/company name.
customer_vat	string	optional	Buyer Norwegian VAT number NO<9 digits>MVA. Provide this and/or customer_org_number (used to route on Peppol if no explicit recipient id is given).
customer_org_number	string	optional	Optional buyer Norwegian organisasjonsnummer (organization number), 9 digits.
customer_address	string	required	Buyer street address.
customer_city	string	required	Buyer city.
customer_zip	string	required	Buyer postal code.
customer_country	string	optional	Buyer country code. Default NO.
recipient_peppol_scheme	string	optional	Optional explicit Peppol routing scheme (EAS/ISO6523). Norway: 0192 (organisasjonsnummer). Default 0192 when routing by organization number.
recipient_peppol_id	string	optional	Optional explicit Peppol participant identifier to route to (overrides deriving from the customer organisasjonsnummer/VAT).
recipient_email	string	optional	Optional email fallback — used if the recipient is not on Peppol (Storecove can email a copy).
invoice_number	string	optional	Invoice number. Auto-generated if omitted.
issue_date	string	optional	Invoice issue date, YYYY-MM-DD. Default: today (UTC).
due_date	string	optional	Optional payment due date, YYYY-MM-DD.
currency	string	optional	Document currency. Default NOK.
note	string	optional	Optional free-text note on the invoice.
lines	array	required	Invoice line items. Each: description, unit_price (net, VAT-exclusive, NOK), vat_rate (25\|15\|12\|0), optional quantity (default 1), optional tax_category (S standard / Z zero-rated / E exempt / AE reverse charge; default S for rate>0, Z for rate 0), optional item_name.

identifier	string	required	The recipient Peppol identifier. Norway: the 9-digit organisasjonsnummer (scheme 0192).
scheme	string	optional	Peppol/ISO6523 scheme. Default 0192 (Norwegian organisasjonsnummer).
network	string	optional	Network to check. Default peppol.
document_types	array	optional	Document types to check receipt for. Default ["invoice"].

Norway Invoices (Peppol BIS 3.0 / EHF via Storecove)

app.wishpool/norway-invoice-mcp — MCP Server

🛠️ Key Features

🚀 Use Cases

⚡ Developer Benefits

⚠️ Limitations

Topics

create_invoice

check_recipient

get_delivery_evidence