F
license-
qualityD
maintenanceEU e-invoicing — UBL/CII conversion to XRechnung and FatturaPA
Luxembourg Invoices (Peppol BIS 3.0 via Storecove)
by app.wishpool
Server Details
Luxembourg Peppol BIS 3.0 e-invoices for AI agents: send, check recipient, get delivery proof.
- Status
- Unhealthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- junter1989k-ai/luxembourg-invoice-mcp
- GitHub Stars
- 0
- Server Listing
- Luxembourg Invoice MCP
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
MCP client
Glama
MCP server
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
100% free. Your data is private.
Tool Definition Quality
A4.6/5.0
Tool DescriptionsA
Average 4.7/5 across 3 of 3 tools scored.
Server CoherenceA
Disambiguation5/5
Each tool has a distinct purpose: checking recipient eligibility, creating an invoice, and fetching delivery evidence. No overlap in functionality.
Naming Consistency5/5
All tools follow a consistent verb_noun snake_case pattern (check_recipient, create_invoice, get_delivery_evidence), making them predictable.
Tool Count4/5
Three tools cover the essential workflow (pre-flight check, send, status). The count is appropriate for a focused invoicing server, though a few more optional tools could be added without bloat.
Completeness4/5
The set covers the core invoice sending process end-to-end. Minor gaps exist (e.g., no credit note tool, no bulk operations), but for a single-invoice workflow it is complete.
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!
Related MCP Servers
- Alicense-qualityDmaintenanceEnables autonomous agents to validate, audit, and correct e-invoices against European standards (EN16931) and Peppol regulations.1MIT
- Flicense-qualityAmaintenanceEnables AI agents to create and manage e-invoices through natural language, supporting EU compliance formats like ZUGFeRD and XRechnung, as well as US plain PDF invoices.7
- Alicense-qualityBmaintenanceEnables AI agents to send Belgium B2B electronic invoices over the Peppol network in Peppol BIS 3.0 format via Storecove, with recipient discovery, invoice creation, and delivery evidence retrieval.MIT
Try in Browser
Your Connectors
Sign in to create a connector for this server.