dk-eli-mcp
Related Servers
Alternatives to dk-eli-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityFmaintenanceEnables querying and analyzing Danish legislation, including search, citation validation, currency checks, and EU law integration, directly from AI assistants.1533 npm1Apache 2.0
- AlicenseAqualityAmaintenanceEnables AI agents to search and retrieve consolidated Swedish statutes (SFS) from the Riksdagen open data API, with verifiable citations and persistent identifiers.441 PyPIApache 2.0
- AlicenseAqualityBmaintenanceEnables access to Slovak legislation from the Collection of Laws via static.slov-lex.sk. Supports listing consolidated versions, retrieving act metadata, and fetching full text with verifiable citations.424 PyPI1Apache 2.0
- AlicenseNot gradedqualityFmaintenanceEnables querying Portuguese legislation, including statutes, provisions, and EU law implementations, with tools for search, citation validation, and currency checks.30 npmApache 2.0

Legalizeofficial
AlicenseNot gradedqualityBmaintenanceEnables AI assistants to search and read consolidated legislation from multiple countries, retrieve exact law texts as of any historical date with citations and git commit SHAs, and create webhook or email subscriptions to track legal changes.2MIT- AlicenseAqualityAmaintenanceEnables searching and retrieval of UK legislation (Acts, Statutory Instruments) from legislation.gov.uk with persistent identifiers and verifiable citations.942 PyPIApache 2.0
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose: metadata retrieval, full-text retrieval, coverage declaration, and change listing. No two tools overlap in what they return, making misselection unlikely.
All tools share the dk_ prefix, and most follow a verb_noun pattern (dk_get_act, dk_get_text). dk_coverage and dk_recent_changes deviate slightly by using nouns rather than verbs, but the pattern remains readable and predictable.
With four tools, the set is compact but sufficient for its narrow scope. It could benefit from a search tool, but the count is reasonable and each tool earns its place.
The core needs are covered: fetch metadata, fetch full text, list recent changes, and explicitly declare coverage gaps. Minor gaps exist—such as no search-by-keyword or version-history tool—but the dk_coverage tool mitigates uncertainty and provides fallbacks.