Eudigo – EUDI Wallet index
REMOTE · MCP.EUDIGO.EU
Independent EUDI Wallet index: status in all 27 EU states, deadlines, registers, standards, news.
Available components
Last scanned (15 hours ago)
Scores higher than 84% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Security
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability67
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 941 tokens (~117/item across 8 items; 8 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management80
- Stability observed for 24 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 23 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://mcp.eudigo.eu/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=api.eudigo.eu | CN=YE2,O=Let's Encrypt,C=US | 12 Oct 2026 | 10 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 5d44dbfa2f6e6366f47a01b2eede1ac404b |
| SANs: api.eudigo.eu, mcp.eudigo.eu | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.eudigo.eu. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| eu. | DS published | 35926 | 8 | Verified |
| eudigo.eu. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000 |
| x-content-type-options | nosniff |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.eudigo.eu/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.eudigo.eu/mcp | HTTPS enforced | 301 | https://mcp.eudigo.eu/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_country EUDI Wallet status of one country ~76
Details for one EU member state: wallet, status, sources (official or not), dated history and the state of its relying party register. `code` is the EU country code (DE, FR, AT, EL for Greece …) or ISO code.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | – |
| lang | string | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_deadlines Key EUDI Wallet deadlines ~83
Key dates of the EUDI Wallet rollout with legal source: public relying party registers, launch of the German wallet d-you, mandatory acceptance for banks, energy, telecoms, very large platforms and others. status: confirmed (in the regulation), derived (calculated from it), expected (announced, not binding).
| Name | Type | Req | Description |
|---|---|---|---|
| lang | string | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_news Latest EUDI Wallet news ~106
Eudigo's weekly news on the EUDI Wallet, newest first: one overview for Germany (d-you, legislation, authorities) and one for the EU (Commission and member states). Each item has a date, summary, sources (marked official or not) and the Eudigo URL. `weeks` limits to the latest n weekly overviews (1-52).
| Name | Type | Req | Description |
|---|---|---|---|
| lang | string | – | – |
| region | – | – | – |
| weeks | integer | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_registers Relying party register status ~78
Daily availability check of the national registers of relying parties (public API in every member state from 24 December 2026 under Implementing Regulation (EU) 2025/848): status per country, last check, HTTP status, number of records, 7-day uptime. Before the deadline all registers are 'expected'.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
get_standard EUDI Wallet standards and versions ~138
Standards behind the EUDI Wallet (OpenID4VCI, OpenID4VP, HAIP, SD-JWT VC, ISO/IEC 18013-5/-7 mdoc, Token Status List, ETSI profiles, ARF …): latest version at the publisher, the version the implementing regulations refer to, and the result of Eudigo's daily version check. Without `name` all standards are listed briefly; with `name` (id or abbreviation, e.g. 'openid4vp', 'HAIP') one standard in detail.
| Name | Type | Req | Description |
|---|---|---|---|
| lang | string | – | – |
| name | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
list_countries List EUDI Wallets by country ~126
Overview of the EUDI Wallet in all 27 EU member states: wallet name, status and short note. Status meaning: certified (listed as certified EUDI Wallet), live (precursor app with digital credentials in operation), pilot (tests with real users or public test version), upgrade (existing government app officially set to become the EUDI Wallet), announced (project known, no public app), unclear. Optionally filter by status. Use get_country for sources and history of one country.
| Name | Type | Req | Description |
|---|---|---|---|
| lang | string | – | – |
| status | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
lookup_term Look up EUDI Wallet terms ~73
Definitions of EUDI Wallet and eIDAS terms (German/English) with reference to the regulation or specification, e.g. 'PID', 'relying party', 'access certificate', 'Zugangszertifikat', 'WUA'.
| Name | Type | Req | Description |
|---|---|---|---|
| lang | string | – | – |
| query | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
search_articles Search Eudigo articles ~91
Search Eudigo's reviewed articles (German and English) on the EUDI Wallet and d-you: for citizens (setup, security, where to use it), businesses (mandatory acceptance, registration as relying party, access certificates, KYC) and developers. Returns title, summary, FAQ and URL – link the URL as source.
| Name | Type | Req | Description |
|---|---|---|---|
| lang | – | – | – |
| query | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
How do I install the Eudigo – EUDI Wallet index MCP server?
Eudigo – EUDI Wallet index is a hosted endpoint at https://mcp.eudigo.eu/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.eudigo.eu
claude mcp add --transport http eu-eudigo-eudi-wallet 'https://mcp.eudigo.eu/mcp'
What is the Eudigo – EUDI Wallet index MCP server?
Eudigo – EUDI Wallet index is an MCP server listed in the public MCP registry as eu.eudigo/eudi-wallet. Independent EUDI Wallet index: status in all 27 EU states, deadlines, registers, standards, news. This page covers its hosted endpoint (https://mcp.eudigo.eu/mcp).
Is the Eudigo – EUDI Wallet index MCP server safe to use?
Eudigo – EUDI Wallet index scores 81 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Eudigo – EUDI Wallet index MCP server expose?
Eudigo – EUDI Wallet index exposes 8 tools: list_countries, get_country, get_deadlines, get_registers, get_standard, and 3 more. Their descriptions and schemas cost roughly 771 tokens of context every time the server is loaded.
Does the Eudigo – EUDI Wallet index MCP server require authentication?
No. We connected to Eudigo – EUDI Wallet index without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Eudigo – EUDI Wallet index MCP server still maintained?
Eudigo – EUDI Wallet index is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Eudigo – EUDI Wallet index MCP server?
VerifyMCP ran 13 checks on Eudigo – EUDI Wallet index, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.