Ext Ops Panel
Open dashboard
Comparison

io.github.4robot/hexadata-tools vs EU e-invoicing and business checks (EN 16931, Peppol, VAT, sanctions)

io.github.4robot/hexadata-tools is an MCP server published by 4robot. Marketplaces we read that list it: 1 (Official MCP Registry). EU e-invoicing and business checks (EN 16931, Peppol, VAT, sanctions) is an MCP server published by wsystemdev. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-13. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
Marketplaceio.github.4robot/hexadata-toolsEU e-invoicing and business checks (EN 16931, Peppol, VAT, sanctions)
Official MCP Registry Listed
Version: 1.0.0
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Listed
Version: 1.0.5
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

io.github.4robot/hexadata-tools vs EU e-invoicing and business checks (EN 16931, Peppol, VAT, sanctions)
Factio.github.4robot/hexadata-toolsEU e-invoicing and business checks (EN 16931, Peppol, VAT, sanctions)
Marketplaces that list it11
Stars (GitHub)00
Forks (GitHub)00
Last release (differs)Not published2026-11-09
Where it runs (differs)Remote server (hexadatalabs--business-validation-tools-mcp.apify.actor/mcp)Remote server (api.wsystem.dev/mcp)
TransportStreamable HTTPStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
LicenceNot statedNot stated
Repository (differs)github.com/4robot/hexadata-tools-mcpgithub.com/wsystemdev/eu-business-data-mcp
Changes in the last 7 days (differs)01
First seen (differs)2026-10-292026-10-26
Endpoint at the last check (differs)Responded 14 h ago, requires authenticationResponded 11 h ago

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

io.github.4robot/hexadata-tools

In its own words, on Official MCP Registry:

15 deterministic validation tools for AI agents: tax IDs (15 countries), VAT, IBAN, LEI, HS codes.

EU e-invoicing and business checks (EN 16931, Peppol, VAT, sanctions)

In its own words, on Official MCP Registry:

EN 16931/XRechnung e-invoice validate+create, Peppol routing, EU VAT/EORI, sanctions, KYB. Free tier

How to run each

io.github.4robot/hexadata-tools As a remote MCP server

Claude Code
claude mcp add --transport http hexadata-tools https://hexadatalabs--business-validation-tools-mcp.apify.actor/mcp --header "Authorization: Bearer <YOUR_TOKEN>"

Requires: Authorization header

EU e-invoicing and business checks (EN 16931, Peppol, VAT, sanctions) As a remote MCP server

Claude Code
claude mcp add --transport http eu-business-data-mcp https://api.wsystem.dev/mcp/

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Both endpoints responded at the last daily check. How we check endpoints

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

Neither one's marketplaces publish the settings it asks for.

What it can do: io.github.4robot/hexadata-tools · What it can do: EU e-invoicing and business checks (EN 16931, Peppol, VAT, sanctions) · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built