Law Scrapper MCP
Related Servers
Alternatives to Law Scrapper MCP
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityBmaintenanceEnables AI clients to search, retrieve and cite over 600 Polish statutes and regulations from the Journal of Laws in full text, including the wording of a provision as of any date, in-force status checked against the ELI register, related provisions, annexes and tables. Access is read-only via a hosted endpoint with e-mail sign-in, optional free trial queries, and paid plans.-
- AlicenseAqualityAmaintenanceEnables AI assistants to query official Polish Sejm data and the ELI legal acts database for deputies, clubs, committees, votes, interpellations, bills, proceedings, transcripts, and legal acts, with source links.2931 npm1Apache 2.0
- 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.56 npmApache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients such as Claude to search and retrieve official Polish legislation from the Sejm ELI API and court decisions from SAOS, fetch exact provision wording, check amendments, and verify legal citations. Every result carries explicit, component-level verification statuses so users can distinguish sourced, confirmed material from claims that could not be established.MIT
- AlicenseAqualityDmaintenanceEnables 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
TDQS
Scored across 13 tools
Most tools target clearly distinct actions or resources, and the descriptions explicitly state when to use one tool versus another. There is some overlap between search_legal_acts, browse_acts, and track_legal_changes because all retrieve legal acts, but their intended scopes are differentiated well enough for an agent to choose correctly.
All tool names use snake_case and begin with a clear verb, generally following a verb_noun or verb_noun_noun pattern. Minor variations like search_in_act are still readable and consistent with the overall naming style.
The 13 tools are well-scoped for a legal-act retrieval and analysis server, with separate tools for search, browsing, content reading, relationship analysis, filtering, and date calculations. The auxiliary result-set and loaded-document listing tools support the stateful workflow rather than adding unnecessary surface area.
The surface covers the main legal-research lifecycle: metadata discovery, search, browsing, loading and reading act content, searching within an act, analyzing relationships, comparing metadata, tracking changes, and filtering result sets. A possible gap is full-text search across multiple acts at once, but the core workflows are otherwise well covered.