Should my agent depend on the MCP server io.github.contentfactory/eu-verify?

Verdict: allow — mid-solo — safe to depend on As of 2026-08-16T06:17:03Z: a dated observation with receipts, not a warranty.

eu verify

io.github.contentfactory/eu-verify

European business verification for AI agents: registry, VAT, sanctions, IBAN. Pay-per-call x402.

— the operator's own registry description reported

Publisher io.github.contentfactory · first seen 2026-08-12 · endpoint https://data.greeneris.io/mcp

allow

verdict

mid-solo

cluster

ok_tools

answers

tools served

Dependency rating derived

allow
allow — alive & usable · action ● · V n/a

allow — because answers ●, 19 tools legible (band B) ●, no confirmed drift in 3 probes ●; not yet checked: truth (2 attempts unverifiable, 0 disagreements)

Cluster mid-solo · distinctiveness 0.425 (moderate). Every figure is a percentile or class within the 11,363-server census — see the whole spectrum.

Does it answer? Q1 · observed

answersalive_tools

latency163 ms

vs populationtypical

protocolcurrent

authopen

Can it be used? Q4 · observed

tools19

vs populationmid

capabilities4

harnessB

Did it hold when checked? Q3–Q4 · derived

identitysolo

servers on its host1

verifiabilityunassessed

duplicate inventoryno

drift events0

answers true0/0 agree

🔏 Signed receipt rr_048917ff5c64ace6728f97f3 · ed25519 · key rs-rcpt-2026-08 — this rating is tamper-evident; an agent gets the full signature from check_server and can verify it against the published key.

Q1Does it answer?alive & usable — 3 probes ●evidence ↓

Q2What is it?action ● evidence ↓

Q3Can it be checked?V n/a for this kind ◐evidence ↓

Q4Did it hold?harness B · truth not yet run · no drift ●evidence ↓

Q5What company does it keep?mid-solo · 1 on its host (context, not verdict) ◐evidence ↓

● observed · ◐ derived · ○ reported — the verdict synthesizes Q1–Q4; Q5 is context. Methodology →

History observed

Every probe we made, oldest → newest (3 shown, 2026-08-12 → 2026-08-16). Green answered · amber answered-but-walled · red no useful answer. A gap in our cadence is a gap in coverage, not evidence about the server.

changelog (1 events)

date	type	what changed
2026-08-12	outcome	first probe: ok_tools

What kind of tools these are derived

Verification only means something relative to a tool's NATURE — an email-sender has no "true answer", a generator has no answer key. Classification evidence: classified from tool names/descriptions/annotations WE OBSERVED. What checking applies to each kind (the full methodology →):

nature	tools	meaning	what checking applies
action	9	changes the world	no true answer exists; we check the CONTRACT (destructive/read-only/idempotent declarations, error legibility) and never fire real actions
retrieval-public	8	serves public facts	truth-checkable against a public source — the V-ladder applies in full
computational	1	deterministic transforms	self-checkable by re-computation and known-answer tests
unclassified	1	not classifiable from its text	Tier-1 only until its tools describe themselves

Tools last seen observed

business_days_fr catalog check_eori check_insolvency_fr find_public_tenders_eu invoice_ready_fr lei_ownership lookup_company_fr lookup_company_uk lookup_financials_fr lookup_lei screen_sanctions validate_email validate_iban validate_siret_fr validate_vat_eu verify_address_fr verify_company_eu verify_supplier_fr

Harness readiness observed

Can an agent's harness pick this tool and call it correctly? Graded on the three things an agent reads — name, description, typed parameters. Band B — usable, with rough edges.

legibility check	tools passing	ok
name is clear & specific	19/19	✓
has a description	19/19	✓
description is substantive	19/19	✓
parameters are typed	19/19	✓
parameters are described	1/19	1/19

19 of 19 tools graded · 19 with a captured input schema. RS-008, Tier-1 — no domain knowledge, applies to any tool. “Alive” is not the same as “usable”.

Truth checks observed

Not yet confirmed — 2 attempt(s) currently unverifiable (rate limits, walls, or unmappable schemas — never counted against the server) · 0 disagreements.

claim class	key	verdict	primary source
OFAC SDN screening (vs the official list)	ISLAMIC REVOLUTIONARY GUARD CORPS	unverifiable	ofac-sdn
OFAC SDN screening (vs the official list)	MAERSK LINE	unverifiable	ofac-sdn

Protocol conformance observed

2025-06-18

protocol version

—

session model

1.28.1

server version eu-verify

Capabilities: experimental prompts resources tools

Drift observed

No confirmed drift on record. Baseline set 2026-08-16; changes appear here after human review.

raw probe records

probed (UTC)	outcome	http	ms	protocol
2026-08-16T06:13:00Z	ok_tools	200	163	2025-06-18
2026-08-14T19:59:27Z	ok_tools	200	157	2025-06-18
2026-08-12T05:34:39Z	ok_tools	200	155	2025-06-18

Watch or embed this verdict

Operators: put the live verdict in your README — it updates with every census, links back here, and is a dated observation, never a warranty:

[![Robin Saige verdict](https://robinsaige.com/badge/io.github.contentfactory/eu-verify.svg)](https://robinsaige.com/s/io.github.contentfactory/eu-verify)

Depend on it? Subscribe to its change feed — outcome changes and confirmed drift, no account needed. Building on it? The full dossier as JSON — verdict, rating, truth checks, history — stable enough to gate CI on.

← overview

Operator of this server? Everything we hold about it is on this page — free, no account, for anyone. Wrong attribution, stale probe, misclassification? Dispute this record →