Yargı MCP
Related Servers
Alternatives to Yargı MCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceA FastMCP server providing access to the Turkish Ministry of Justice's Legislative Information System, allowing LLM applications to search legislation, retrieve article lists, and get article contents in Markdown format.326115 PyPI234MIT
- AlicenseNot gradedqualityBmaintenanceA Türk hukuk MCP sunucusu that enables searching and retrieving Turkish legal decisions (Yargıtay, Danıştay, etc.) with semantic search via NVIDIA embeddings and a Turkish chat tool powered by Llama 3.3 70B.MIT
- FlicenseNot gradedqualityCmaintenanceMCP server for searching Turkish legal texts using ChromaDB, with PDF indexing and Claude Desktop support.-
- AlicenseAqualityAmaintenanceAn MCP server for accessing Turkish legislation (laws, regulations, decrees) via the Adalet Bakanligi API, providing search, full-text retrieval, and structured citations.51Apache 2.0
- AlicenseNot gradedqualityBmaintenanceMCP server for Turkish legal semantic search using NVIDIA nv-embed-v1 embeddings, with rate-limit resilience and query embedding caching for fast RAG responses.MIT
- FlicenseBqualityFmaintenanceAn MCP server providing standardized access to Swiss court decisions through the entscheidsuche.ch API, allowing LLMs to search, retrieve, and analyze legal documents from Swiss jurisdictions.35-
TDQS
Scored across 17 tools
Each tool targets a distinct legal domain (Emsal, Bedesten, Uyuşmazlık, Anayasa, KİK, Rekabet, Sayıştay, BDDK, GİB, Sigorta Tahkim) with clear search vs. get operations per domain. The two Deep Research tools (fetch, search) are explicitly labeled as for ChatGPT Deep Research, and their descriptions clarify they should not be used for regular MCP, eliminating ambiguity.
The naming follows a verb_noun pattern (search_* and get_*) but with inconsistencies: some get tools include 'markdown' while others do not (e.g., get_rekabet_kurumu_document vs. get_bddk_document_markdown), some have special suffixes like '_unified' or '_from_url', and two tools ('fetch', 'search') break the pattern entirely. The core pattern is recognizable but not uniform.
With 17 tools, the server is slightly above the ideal 3-15 range but still reasonable for a multi-jurisdiction legal research platform. Each tool serves a distinct domain, and the count is justified by the breadth of sources covered, though it may feel heavy for agents to navigate.
Several domains lack either a search or get tool: Emsal has only a getter, Sayıştay has only a getter, GİB has only a getter, and Anayasa has only a search (no document retrieval). Additionally, a referenced 'search_bedesten_unified' is not included, leaving gaps in the Bedesten workflow. The surface is incomplete for a comprehensive legal research tool.