eCommerce
invoicehub.dev
Handles e-invoice validation, generation, and conversion across multiple formats.
ENDPOINT 1
https://api.invoicehub.dev/mcp
MCP server metadata
- Name
- invoicehub
- Version
- 1.3.0
Known tools 4
validate_invoiceValidate an EU e-invoice XML string against the official EN 16931 Schematron.
Potential side effectsconvert_invoiceConvert an e-invoice between formats via the shared EN 16931 canonical model: parse the source document, re-serialize as the target, and validate the result before returning it — never a document that has not been checked.
Potential side effectslist_supported_formatsList the e-invoice formats InvoiceHub validates today and what is on the roadmap.
Potential side effectsCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.invoicehub]
url = "https://api.invoicehub.dev/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"invoicehub": {
"type": "http",
"url": "https://api.invoicehub.dev/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: invoicehub
Remote MCP URL: https://api.invoicehub.dev/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"invoicehub": {
"url": "https://api.invoicehub.dev/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"invoicehub": {
"type": "http",
"url": "https://api.invoicehub.dev/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "invoicehub",
"transport": "streamable-http",
"url": "https://api.invoicehub.dev/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Trust Data Available
BuiltWith Trust API v2 evidence for invoicehub.dev was fetched 2026-07-30T21:37:34.571Z and is being refreshed.
invoicehub.dev is assessed as Trusted: Domain has an established technology history spanning over a year.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.