chinese-law-mcp
Related Servers
Alternatives to chinese-law-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityBmaintenanceMCP server for Chinese bar exam (法考) preparation with 2,027 past questions, chapter exercises, and spaced repetition. Enables AI agents to search, practice, and review legal exam questions.-
- AlicenseAqualityAmaintenanceA read-only Chinese legal evidence MCP server that provides deterministic retrieval of authentic legal sources with chain-of-custody receipts, designed for Codex, Claude Code, and OpenCode.16Apache 2.0
- FlicenseNot gradedqualityDmaintenanceMCP server for evidence-based Chinese legal consultation. It routes labor law questions to a knowledge base and other queries to public search, returning answers with citations and fallback reasons.1-
- FlicenseNot gradedqualityDmaintenanceA stateless MCP server for Hong Kong legal research, offering tools to analyze legal intent, search official HKeL statutes, fetch current law metadata, and check source status.-
- AlicenseAqualityBmaintenanceMCP server for querying French legislation and case law via the Legifrance API, enabling search and retrieval of laws, codes, and court decisions with verifiable citations.853 PyPI2Apache 2.0
- AlicenseAqualityDmaintenanceMCP server for searching and retrieving Japanese laws from the e-Gov API, enabling natural language queries for legal information.37 npmMIT
This server cannot be deployed
TDQS
Scored across 3 tools
search_laws (find a law by name) and search_in_law (keyword search within one law's articles) are superficially similar but the descriptions clearly distinguish scope: one operates over the catalog, the other within a single document. get_article is clearly distinct as a targeted retrieval. Minor risk of misselection only when an agent doesn't read carefully.
All three use snake_case verb_noun-ish patterns: search_laws, get_article, search_in_law. The phrasing between search_laws and search_in_law is slightly asymmetric (plural target vs prepositional scope), but the convention is otherwise predictable and readable.
Three tools is on the thin side for a legal research server covering 412 laws; there's little room for browsing, listing, or metadata exploration. It is not extreme, but it feels minimal rather than well-scoped.
Core retrieval (find law, get article, keyword-in-law) is covered, but notable gaps exist: no way to list/enumerate laws, browse by chapter or category, filter by effective date/domain, or follow cross-references. Agents needing discovery beyond a name search will hit a dead end.