EasyLPD MCP server

• Registry namech.easylpd/fadpverified in the MCP registry

The registry name sits under easylpd.ch. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

• Stateanswerschecked 2026-10-29
• Tools8
• Server calls itselfeasylpd
• Server version1.0.0
• Protocol version2025-06-18

On 2026-10-29 the server answered initialize and tools/list without a sign-in. First answer in 223 ms.

• Whether its tools do the product's job has not been judged yet.
• Checked on 6 of the 7 days it takes to judge reliability.

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: 6 so far
• Answeredmeasuring6 of the 7 daily checks it takes to print a share
• Median first answer289 ms
• Space in an agent's context≈ 2,594 tokensthe definitions of all its tools (8), which an agent carries on every turn
• Tool definitionsA · 100 of 100
• Typed results0 of 8 toolsdeclared outputSchema: results come typed, read once

• Every tool passes all six checks.

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 →

• which_laws_apply

  Use first when someone asks which data protection laws their organisation must follow (Swiss FADP/nLPD/DSG, EU GDPR, EU AI Act), for example a Swiss company selling online to the EU. Returns the core obligations that follow for that…

• assessment_questions

  Use when someone wants to check where their organisation stands with data protection. The questions of EasyLPD's self-assessment that apply to an organisation's profile, each with its id, area, why it matters, its weight and the legal…

• score_assessment

  Use after the questions of assessment_questions have been answered. Scores them per applicable law, with the risk level and the three gaps to start from, and returns openInEasyLPD: a link that shows the same result in EasyLPD, to give to…

• transfer_check

  Use when someone asks whether they may use a provider or send personal data to another country (cloud, hosting, CRM, US services). Whether sending personal data to a country is allowed without further safeguards under the Swiss FADP and…

• fadp_obligations

  Use for an overview of the new Swiss FADP/nLPD/revDSG. The main duties of the Swiss Federal Act on Data Protection (in force since 1 September 2023) for SMEs, each with its FADP and GDPR articles: who it applies to, the risk, eight…

• action_plan

  Use when someone asks what their organisation must do about data protection, or how to start. The steps that apply to its profile under the Swiss FADP, the GDPR and the AI Act, in the order EasyLPD's path follows (six stages), each with…

• document_templates

  Use when someone needs a privacy notice, a processor agreement (DPA), a breach procedure, a DPIA or another data protection document under the Swiss FADP or the GDPR. The 39 templates of EasyLPD with what each is for and the link to its…

• fadp_questions

  Use when someone asks a common question on the Swiss FADP/nLPD/revDSG: whether it applies, differences with the GDPR, what changed in 2023, fines, personal and sensitive data, consent, the FDPIC, the Swiss representative, the record of…