Law Scrapper MCP
Related Servers
Alternatives to Law Scrapper MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to search and retrieve Polish statutes, provisions, and EU law cross-references with verified citations, supporting legal research and compliance checks.30 npmApache 2.0
- AlicenseAqualityBmaintenanceEnables searching Polish parliamentary prints and retrieving the full legislative process history, including links to final legal acts, via the official Sejm API.3MIT
- AlicenseNot gradedqualityDmaintenanceEnables semantic search over Polish court judgments and legislative acts via MCP. Allows LLMs to retrieve legal documents using natural language queries.Apache 2.0
- AlicenseAqualityBmaintenanceMCP server for Polish legislation (ISAP / Sejm) — search acts (Dz.U., M.P.) and fetch full texts with ELI identifiers and verifiable citations.348 npm1MIT
- AlicenseNot gradedqualityFmaintenanceEnables querying and analyzing Slovak legislation via natural language, including full-text search, provision retrieval, and EU law integration.38 npm2Apache 2.0
- FlicenseNot gradedqualityCmaintenanceEnables AI assistants to access and search Slovak legal regulations from Slov-Lex.sk, including retrieving full law texts, paragraphs, and recent legislative updates.9-
TDQS
Scored across 13 tools
Most tools have clear, distinct roles and the descriptions include explicit guidance on when to use or avoid each tool. The main ambiguity is between search_legal_acts and track_legal_changes, since both accept date and keyword filters and return sets of acts, which could lead an agent to select the wrong one for date-based discovery.
All tool names use snake_case with a leading verb and a noun target, e.g. get_act_details, search_legal_acts, filter_results, compare_acts. Minor variations like search_in_act and list_loaded_documents are still consistent in style and do not break the overall predictable pattern.
13 tools is well within the ideal range for a legal-research server. Each tool covers a distinct part of the research workflow — discovery, loading, reading, searching, filtering, relationships, and date calculation — so none feels redundant or unnecessary.
The toolset covers the core legal-research lifecycle: browse/search acts, load and read content, search within documents, filter result sets, track changes, and compare metadata. Minor gaps include no direct way to fetch the advertised HTML/PDF document formats and no one-step tool for comparing full content between two versions of an act.