Home / MCP registry index / dk.politikdata/mcp
Politikdata.dk MCP
dk.politikdata/mcp in the official MCP registry.
Endpoint https://mcp.politikdata.dk/mcp.
The registry describes it as: Danish parliamentary cases, votes, politicians, parties, elections, and comparison tools.
We read its 29 tools on 2026-10-28. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
compare fetch get_case get_case_debate get_document_text get_election get_election_candidates get_election_history get_election_votes get_legal_document get_party get_person get_question get_question_history get_verdict get_vote_cast get_vote_cast_votes list_elections resolve_person search search_cases search_keywords search_legal_documents search_party_votes search_person_votes search_persons search_questions search_verdicts search_vote_casts
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/dk-politikdata-mcp)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.