rechtssysteem-mcp
Related Servers
Alternatives to rechtssysteem-mcp
- AlicenseNot gradedqualityDmaintenanceAn MCP server that provides comprehensive US legislation.35 npm38MIT

Vaquill-AI/vaquill-mcpofficial
AlicenseAqualityBmaintenanceMCP server for Vaquill legal research API. Covers US federal + 50-state law (USC, CFR, state legislation, CourtListener case law)257MIT- AlicenseAqualityAmaintenanceMCP server for the Federal Register of Legislation, enabling point-in-time searches, retrieval, and verification of Australian Commonwealth law, including citation checking.863 npm2MIT
Related Servers
- AlicenseNot gradedqualityCmaintenanceProvides tools to predict Dutch court case outcomes with probabilities, retrieve benchmark statistics, and check legal texts for outcome leakage.Apache 2.0
- AlicenseAqualityCmaintenanceEnables searching and retrieving Dutch case law (uitspraken) via the Rechtspraak Open Data API, including full text and citation graph exploration.640 npm1MIT

conformi-searchofficial
AlicenseAqualityAmaintenanceInstallable MCP server for EU legal research with verifiable CELEX citations from the EUR-Lex corpus (DE/EN/FR).21MIT- FlicenseNot gradedqualityCmaintenanceEnables semantic search, outcome prediction, and legal document drafting across 67M+ Brazilian court decisions from 55 tribunals, with tools for jurimetric analysis and citation verification.-
- AlicenseNot gradedqualityCmaintenanceai-detect is a free AI text detector that runs entirely on your own hardware. It scores writing sentence by sentence using desklib/ai-text-detector-v1.01, a 304-million-parameter DeBERTa-v3-large model that ranks first on the RAID detection benchmark. No API key, no per-word pricing and no upload: after a one-off 1.7 GB model download it just works offline. by Houtini6MIT
- AlicenseAqualityCmaintenanceEnables local, LLM-free probabilistic decisions (choice, classification, scoring, yes/no) with real probabilities in 100+ languages, as a drop-in replacement for jev-local tools.4MIT
TDQS
Scored across 3 tools
Each tool targets a clearly distinct concern: predicting case outcomes, retrieving benchmark metrics, and checking for verdict leakage. The descriptions explicitly cross-reference each other to prevent misselection.
All names are lowercase snake_case, but the pattern is mixed: voorspel_uitkomst is verb+object, while rechtspraak_cijfers and lekkage_check are noun phrases. The names are readable and coherent within the domain, but there is no consistent verb_noun convention.
Three tools form a tight, well-scoped set: predict an outcome, retrieve the underlying benchmark metrics, and measure leakage. Each tool earns its place with minimal overlap.
The surface covers the full workflow for this specialized purpose: model prediction, benchmark verification, and data-quality/leakage checking. No obvious missing operations for the stated domain.