fedlex-mcp
Related Servers
Alternatives to fedlex-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceMCP server for searching Swiss court decisions from federal and cantonal courts via entscheidsuche.ch. Enables full-text search, law reference lookup, and filtering by canton, court level, and date without API keys.847 PyPI1MIT
- AlicenseAqualityAmaintenanceMCP server for Swiss federal legislation metadata via Fedlex, enabling search and retrieval of act details with ELI URIs, SR numbers, and multilingual support.350 PyPIApache 2.0
- AlicenseAqualityFmaintenanceEnables querying Swiss data protection regulations, FDPIC/EDOB decisions, and guidelines directly from MCP-compatible clients like Claude.6Apache 2.0
- AlicenseAqualityAmaintenanceMCP Server for Canton Zurich legislation (ZH-Lex) — full-text search, article extraction, and education law tools for ~970 cantonal laws.8MIT
- FlicenseBqualityFmaintenanceAn MCP server providing standardized access to Swiss court decisions through the entscheidsuche.ch API, allowing LLMs to search, retrieve, and analyze legal documents from Swiss jurisdictions.35-

entscheidsuche-mcpofficial
AlicenseNot gradedqualityBmaintenanceMCP server for Swiss court decisions, enabling full-text search and retrieval of published decisions from all Swiss federal and cantonal courts in German, French, and Italian.4MIT
TDQS
Scored across 12 tools
Each tool targets a distinct operation: law search, law detail, history, recent publications, upcoming changes, gazette search, treaty search, open consultations, consultation search, consultation detail, term lookup, and concept detail. No overlap in functionality.
All tools follow a consistent prefix (fedlex_ or termdat_) followed by verb_noun pattern (e.g., fedlex_search_laws, fedlex_get_law_by_sr, termdat_lookup_term). Naming is uniform and predictable.
12 tools cover a broad domain (laws, treaties, gazette, consultations, terminology) without being excessive. Each tool serves a clear purpose, and the count is well-scoped for the server's function.
Core workflows are covered: search, detail, history, monitoring for laws and consultations, plus terminology lookup. Minor gaps: no full text retrieval for laws (only link provided) and no treaty detail tool, but agents can work around with links.