← Registry

API Tools

e-invoice.be

Provides access to check Peppol business registrations and retrieve e-invoice.be pricing and API information.

1 endpoint3 known toolsFirst detected June 5, 2026Last detected September 6, 2026

ENDPOINT 1

https://e-invoice.be/.well-known/mcp

No auth detected

MCP server metadata

Name
e-invoice.be
Version
1.0.0
Capabilities
toolsresources

Known tools 3

check_peppol_registration

Check if a business is registered on the Peppol network by VAT number or Peppol ID

Inferred read-only
get_pricing_info

Get e-invoice.be pricing plans, features, and registration info

Potential side effects
get_api_info

Get e-invoice.be API endpoints, documentation links, and developer resources

Potential side effects

CONNECT 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.e-invoice-be]
url = "https://e-invoice.be/.well-known/mcp"
enabled = true
Claude Code

.mcp.json

{
  "mcpServers": {
    "e-invoice-be": {
      "type": "http",
      "url": "https://e-invoice.be/.well-known/mcp"
    }
  }
}
Claude Desktop

Settings → Connectors → Add custom connector

Name: e-invoice-be
Remote MCP URL: https://e-invoice.be/.well-known/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": {
    "e-invoice-be": {
      "url": "https://e-invoice.be/.well-known/mcp"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code
{
  "servers": {
    "e-invoice-be": {
      "type": "http",
      "url": "https://e-invoice.be/.well-known/mcp"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "e-invoice-be",
  "transport": "streamable-http",
  "url": "https://e-invoice.be/.well-known/mcp"
}
MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.