hk-criminal-law
Related Servers
Alternatives to hk-criminal-law
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables law knowledge Q&A with traceable, citation-verified answers from a shared 38-law article-level index, plus single and batch police incident risk assessment grounded in retrieved statutes. Exposed as stdio MCP tools (law_qa, risk_assess, risk_assess_batch) for dsh, Claude Desktop, Cline, and other MCP clients.1MIT
- AlicenseAqualityCmaintenanceEnables MCP clients such as Claude to look up Korean statutes, individual articles, annexes, amendment history, precedents, and interpretive rulings from the Ministry of Government Legislation's national law information open API, and to run guided research scenarios, citation audits, contract risk scans, and citation tracing — all read-only. Supports both a hosted HTTP endpoint with per-user tokens and a local stdio installation using your own API key.12MIT
- 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.-
- AlicenseNot gradedqualityFmaintenanceQuery 3,241 UK statutes directly from Claude, Cursor, or any MCP-compatible client.58 npm5Apache 2.0
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to search the official text of India's new criminal laws (BNS, BNSS, BSA) and return the exact Act, section, and Gazette page for each claim. Provides citation lookup, keyword and vector search with reranking, plus full-section retrieval, so answers are grounded in current statute rather than recalled from memory.MIT
- FlicenseNot gradedqualityDmaintenanceRemote MCP server exposing the CounselStack citation engine as nine legal research tools, enabling read-only citation lookup, statute search, and case text retrieval through Claude.-
TDQS
Scored across 30 tools
Core families are distinguishable (legislation fetch, case fetch, DOJ, semantic atlas), but several tools sit close together: verify_citation vs verify_citations, get_section vs get_section_range vs statute_history vs list_section_versions, and four separate *_status tools. The five semantic_* tools and the three research pack tools (doctrine_research, sentencing_research, authority_ranking) also overlap in 'find leads' territory, relying on descriptions rather than distinct names to separate them.
The dominant pattern is snake_case verb_noun (search_cases, get_case, verify_citation, sync_doj), which is readable and predictable. However, a sizeable minority are noun phrases with no verb (note_up, statute_history, case_graph, authority_ranking, corpus_status, sync_status, doj_status, semantic_status), and the semantic_* prefix namespace breaks the verb-first convention.
At 30 tools the surface is heavy, and much of the weight is infrastructure/plumbing rather than capability: four *_status tools plus sync_doj/sync_status and five semantic_* tools. A research agent must pick among many near-equivalent entry points, which is more than the domain's core workflows justify.
Coverage is strong for the stated domain: search and retrieval of legislation and judgments, historical versions, range reads, citation extraction/verification, note-up/graph traversal, DOJ policy corpus, and corpus freshness reporting. Gaps are acknowledged rather than hidden (no citator of record, sentence-tariff tables), and agents can work around them by reading full judgments and sections.