tk-mcp
Related Servers
Alternatives to tk-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables access to Polish Constitutional Tribunal rulings, including search by keywords or case signature, listing recent decisions, and retrieving full judgment texts with metadata and official links. Supports section-wise and chunked retrieval of long documents to manage context budgets.4MIT
- FlicenseNot gradedqualityDmaintenanceEnables searching and retrieving Korean Constitutional Court decisions using the official Open API, with search filters and full-text retrieval.-
- AlicenseAqualityBmaintenanceEnables searching and reading full texts of anonymised Czech court decisions from the Ministry of Justice public database, with filters by court, legal keywords, statutory provision, judge and dates, plus lookup by case number or ECLI and browsing by publication date. Decisions can be exported as DOCX/TXT and cached locally in SQLite with diacritic-insensitive full-text search.11MIT
- AlicenseAqualityCmaintenanceProvides access to Polish court judgments from the SAOS database. Enables search and retrieval of judgments with full-text search, filtering, and detailed case information.320 npm1Apache 2.0
- AlicenseAqualityAmaintenanceEnables searching and reading Peruvian Constitutional Court jurisprudence by querying both the current thematic systematization and the 2001-2018 historical resolutions inventory at once, returning them fused and deduplicated as a single source. Supports full-text search, exact filters (case number, parties, dates, chamber, district, type, keywords), thesaurus and thematic browsing, and full metadata plus complete reasoning text with public PDF links, without credentials or browser automation.91Apache 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
TDQS
Scored across 3 tools
search_judgments (find judgments) and get_judgment_text (fetch full text of a known judgment) target clearly different actions, and tk_coverage is an explicit meta/coverage declaration tool that plays a distinct role. No overlap or plausible misselection.
search_judgments and get_judgment_text follow a clean snake_case verb_noun pattern. tk_coverage breaks it by using a namespace prefix and no verb, but it is still readable and only a single deviation.
Three tools is lean for a read-only judgment connector but each earns its place: search, retrieve, and a coverage/gap disclaimer. Slightly thin but well-scoped rather than padded.
The core read lifecycle (search then fetch full text) plus a coverage/gap declaration is covered for this domain. Minor gaps remain around pagination beyond one page and metadata-only listing, which the coverage tool at least documents.