io.github.contentfactory/eu-verify vs ENTIA Entity Verification
io.github.contentfactory/eu-verify is an MCP server published by contentfactory. Marketplaces we read that list it: 1 (Official MCP Registry). ENTIA Entity Verification is an MCP server published by entia-systems-core. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-19. 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
| Marketplace |  io.github.contentfactory/eu-verify |  ENTIA Entity Verification |
|---|---|---|
| Official MCP Registry | Listed Version: 1.4.0 Forks (GitHub): 1 Stars (GitHub): 1 Not marked · First seen |
Listed Version: 4.4.0 Forks (GitHub): 2 Stars (GitHub): 1 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
| Fact | io.github.contentfactory/eu-verify | ENTIA Entity Verification |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) | 1 | 1 |
| Forks (GitHub) (differs) | 1 (worse) | 2 (better) |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (data.greeneris.io/mcp) | Remote server (mcp.entia.systems/mcp) |
| Transport | Streamable HTTP | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/contentfactory/eu-verify | github.com/entia-ia/entia-mcp-server |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check | Responded 2 days ago | Responded 2 days 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.contentfactory/eu-verify
European business verification for AI agents: registry, VAT, sanctions, IBAN. Pay-per-call x402.
ENTIA Entity Verification
11.3M entities, 10 countries, 12 tools. EU VAT (VIES), BORME, GLEIF, KYB. Free: 100 req/month.
How to run each
io.github.contentfactory/eu-verify As a remote MCP server
claude mcp add --transport http eu-verify https://data.greeneris.io/mcpENTIA Entity Verification As a remote MCP server
claude mcp add --transport http entity-verification https://mcp.entia.systems/mcpCommands 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.contentfactory/eu-verify · What it can do: ENTIA Entity Verification · 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.