Finland Invoice MCP
Enables AI agents to send Finnish B2B/B2G electronic invoices (verkkolasku) over the Peppol network in Peppol BIS 3.0 format via Storecove, with tools for recipient discovery, invoice creation, and delivery evidence.
README
Finland Invoice MCP 🇫🇮 — How can my AI agent send a Peppol e-invoice (verkkolasku) in Finland?
<!-- install-cta -->
Use it in 60 seconds
Paste this into your MCP client config (Claude Desktop, Cursor, Windsurf, or any MCP-capable agent):
{
"mcpServers": {
"finland-invoice": {
"type": "http",
"url": "https://inv-fi.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:
git clone https://github.com/junter1989k-ai/finland-invoice-mcp && cd finland-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 Finland B2B/B2G electronic invoices (verkkolasku) over the Peppol network in Peppol BIS 3.0 / EN 16931 format via Storecove, a certified Peppol Access Point. It builds the structured invoice, computes the Finnish VAT (ALV) breakdown — including the 25.5% decimal standard rate — and delivers it under the merchant's own Storecove account. Stateless, bring-your-own credentials, never stores anything.
Live endpoint: https://inv-fi.wishpool.app/mcp · Registry: app.wishpool/finland-invoice-mcp
Why now — the Finnish mandate
Finland mandates structured e-invoicing (verkkolasku) for public-sector suppliers (B2G) since 2020-04-01. For B2B, a business has the right to require an e-invoice from another business (when turnover exceeds EUR 10,000) under the Act on Electronic Invoicing (241/2019) — a right to demand, not a blanket obligation to send. Peppol/Finvoice is the Finnish rail, so sending over Peppol now is future-proof.
The 25.5% decimal VAT rate
Finland's standard VAT (ALV) rate is 25.5% — a decimal rate, in force since 2024-09-01. This server's VAT math handles fractional rates. Valid rates: 25.5 (standard), 14 (food/restaurant), 10 (books/pharmaceuticals/passenger transport), 0 (zero-rated/exempt/reverse charge).
Quick start
{
"mcpServers": {
"finland-invoice": {
"type": "http",
"url": "https://inv-fi.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 (Y-tunnus scheme 0037, or VAT scheme 0213). Returns can_receive. The safe pre-flight. |
create_invoice |
Build a Peppol BIS 3.0 invoice from seller + buyer (Finnish VAT FIxxxxxxxx / Y-tunnus business ID, address) and line items (description, net unit price, VAT rate 25.5/14/10/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 EUR. Finnish VAT (ALV) rates: 25.5 (standard, decimal), 14 (food/restaurant), 10 (books/pharmaceuticals/passenger transport), 0 (zero-rated/exempt/reverse charge). Parties identified by Finnish VAT (FIxxxxxxxx) and/or Y-tunnus business ID (7+1 digits).
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 (note the decimal 25.5% rate):
100 + 50both @25.5% → taxable 150.00 / vat 38.25 / total 188.25200 @25.5% + 100 @14%→ taxable 300.00 / vat 65.00 (51 + 14) / total 365.002×50 @25.5% + 3×10 @10% + 1×25 @0%→ taxable 155.00 / vat 28.50 (25.50 + 3.00 + 0) / total 183.50- rounding at the decimal rate:
33.33 @25.5%→ vat 8.50 (from 8.49915) / total 41.83
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 (2026-07-10): 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
node test/serve.js # local server on :3238
node test/e2e.js # VAT math (incl. 25.5% decimal) + Peppol 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: Belgium Peppol (inv-be) · Sweden Peppol (inv-se) · Italy FatturaPA (inv-it) · Malaysia MyInvois (inv-my) · Mexico CFDI (inv-mx) · Brazil NF-e (inv-br) · India GST (inv-in). Storecove also covers Norway, Denmark, 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.
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
e2b-mcp-server
使用 MCP 通过 e2b 运行代码。
Neon MCP Server
用于与 Neon 管理 API 和数据库交互的 MCP 服务器
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。