
Eudigo MCP server
Which MCP servers are Eudigo's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.
read 2026-10-27
- Registry nameeu.eudigo/eudi-walletverified in the MCP registry
The registry name sits under eudigo.eu. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.
- Stateanswerschecked 2026-10-27
- Tools8
- Server calls itselfeudigo
- Server version1.1.0
- Protocol version2025-06-18
On 2026-10-27 the server answered initialize and tools/list without a sign-in. First answer in 511 ms.
- Whether its tools do the product's job has not been judged yet.
- Checked on 2 of the 7 days it takes to judge reliability.
Once connected
- Parameters are untyped or undescribed in 7 of 8 tools: check arguments before calling.
Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.
- INITE MCP scoreafter a weeka score needs 7 daily checks: 2 so far
- Answeredmeasuring2 of the 7 daily checks it takes to print a share
- Median first answer538 ms
- Space in an agent's context≈ 1,190 tokensthe definitions of all its tools (8), which an agent carries on every turn
- Tool definitionsB · 85 of 100
- Typed results8 of 8 toolsdeclared outputSchema: results come typed, read once
- Parameters without a description: in 7 of 8
Worth a look
None of the five warning signs in these definitions.
A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →
list_countriesOverview 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…
get_countryDetails 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.
get_deadlinesKey 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…
get_registersDaily 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…
get_standardStandards 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…
lookup_termDefinitions of EUDI Wallet and eIDAS terms (German/English) with reference to the regulation or specification, e.g. 'PID', 'relying party', 'access certificate', 'Zugangszertifikat', 'WUA'.
search_articlesSearch 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…
get_newsEudigo'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…
How to connect
Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:
{
"mcpServers": {
"eudi-wallet": {
"type": "http",
"url": "https://mcp.eudigo.eu/mcp"
}
}
}Add it
Claude Code, in a terminal
claude mcp add --transport http eudigo https://mcp.eudigo.eu/mcpclaude.ai, ChatGPT and other clients: add https://mcp.eudigo.eu/mcp as a custom connector in the settings.
Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.
Cookies
Before we count this visit
Analytics and ad measurement tell us which pages and which of our ads do their job: Google Analytics and Google Ads, the Meta pixel, Yandex Metrica, and one first-party id of our own. Nothing is stored until you answer, and declining changes nothing about the site.