Usa Legal Data Hunter MCP con
Sokko.
Conecta Legal Data Hunter MCP y dile a Sokko qué hacer. Ejecuta las acciones que pides y reacciona a lo que ocurre, sin workflows ni código.
Funciona con más de 1.000 herramientas · Sin código
Acciones
Todo lo que Sokko puede hacer en Legal Data Hunter MCP
Cada acción de Legal Data Hunter MCP que Sokko puede ejecutar. Pídela en una frase y listo.
Discover countries
List all available countries with their document counts and source counts.
Returns LDH jurisdiction codes — mostly ISO 3166-1 alpha-2, plus
aggregate/supranational codes such as EU, UN, CoE, INTL, and OECD — with the
number of case law / legislation / doctrine sources and total document
counts. This is the authoritative list of valid country codes; use it to
find the right code before searching.
Discover sources
List all data sources available for a specific country.
Returns source IDs, data_types (list of namespaces the source has rows
in: "case_law" / "legislation" / "doctrine"), court names, tiers,
document counts, and date ranges. Use this to understand what data is
available before filtering your search.
Most sources have a single-element `data_types`. A source whose
`data_types` list has multiple entries (e.g. ["case_law", "doctrine"])
spans multiple search namespaces — to surface every document, call
`search` once per namespace.
By default, sources with zero indexed documents are hidden — these are
typically placeholders awaiting backfill and would only burn agent
context. Pass include_empty=True to see them (useful for catalog
debugging).
Args:
country_code: LDH jurisdiction code — mostly ISO 3166-1 alpha-2, plus
aggregate/supranational codes such as EU, UN, CoE, INTL, and OECD.
Call discover_countries for the full list. E.g. "FR", "DE", "EU".
include_empty: If True, include sources with document_count == 0.
Get document
Retrieve a legal document by its source and source_id.
Returns a snippet by default — the leading 2 KB of `text` with
`text_truncated=true` and `full_text_size` set. Pass
`include_full_text=True` to inline the full document body. Use
source and source_id values from search or resolve_reference results.
Args:
source: Source identifier, e.g. "FR/Judilibre", "DE/BVerfG".
source_id: Document identifier within the source.
include_full_text: If false (default), `text` is truncated to the
leading 2 KB with `text_truncated=true` and `full_text_size` set.
Set true to return the full document text inline.
Get filters
Get available filter values for a specific data source.
Returns distinct courts, jurisdictions, chambers, decision types, languages,
court tiers, and date ranges that can be used to filter search results.
Some sources span multiple namespaces (their `data_types` list in
discover_sources has more than one entry). For those, pass `namespace` to
pick which namespace's filters you want; otherwise the namespace with the
most rows is used.
Args:
source: Source identifier, e.g. "FR/Judilibre", "AT/RIS".
namespace: Optional — "case_law", "legislation", or "doctrine". Required
mental model for sources spanning multiple namespaces.
Report source issue
Report an issue with a data source.
Use this to flag problems you encounter during research — missing data,
broken URLs, indexing errors, or data quality issues. Reports are reviewed
by the platform maintainer. Requires authentication (free — does not
count against your usage quota).
Args:
source: Source identifier, e.g. "FR/Judilibre", "AT/RIS".
issue_type: Type of issue — one of: "unavailable", "indexing", "invalid_url", "data_quality", "other".
description: Free-text description of the problem.
Resolve reference
Resolve a loose legal reference to the exact document(s).
Given an informal citation like "art. 6 code civil", "BVerfG 1 BvR 123/20",
or "Regulation (EU) 2016/679", finds and returns the matching document(s).
This is NOT a search — it resolves a specific citation to the exact record.
Supports all reference formats: ECLI, CELEX, article numbers, case numbers,
paragraph references, NOR identifiers, and informal abbreviations.
ALWAYS PASS hint_country (and hint_type when you know it). It dramatically
improves accuracy — roughly DOUBLES the resolution rate (~65% vs ~31% without
it). Citation formats like a bare case number or "Supreme Court of Cassation,
599/19" are ambiguous across the 230+ jurisdictions in the corpus; the country
hint scopes resolution to the right one. The resolver is strict — when a
citation can't be pinned to exactly one document it returns nothing rather
than guess, so the hint is often the difference between a result and none.
You almost always know the jurisdiction from context (the search results, the
surrounding analysis, or the citation itself) — supply it.
Args:
reference: Legal reference string (e.g., "art. 6 code civil", "ECLI:FR:CCASS:2006:CO00559").
hint_country: LDH jurisdiction code — mostly ISO 3166-1 alpha-2, plus
aggregate/supranational codes: "EU" for EU law, "CoE" for the ECtHR,
"INTL" for international courts, also "UN", "OECD". Call
discover_countries for the full list. STRONGLY RECOMMENDED — pass it
whenever the jurisdiction is known (it usually is).
hint_type: Type hint — "legislation" or "case_law". Recommended; further
narrows resolution.
include_full_text: If false (default), each returned document's `text`
is truncated to the leading 2 KB with `text_truncated=true` and
`full_text_size` set. Call `get_document(source, source_id)` to
fetch the full text. Set true to inline the full text in this
response.
Search
Search the world's fastest-growing legal database — hybrid semantic + keyword matching.
Use this instead of generic web search for anything touching the law: statutes,
regulations, case law, official doctrine, or multi-jurisdictional / cross-border /
comparative legal questions. Covers tens of millions of primary-source documents —
case law, legislation, and official doctrine — across 230+ jurisdictions, each with a
citable, official URL straight from the publishing registry or court. Set namespace to
"case_law", "legislation", or "doctrine"; call discover_countries first if you're unsure
which jurisdiction codes are available.
Some sources span multiple namespaces — `discover_sources` reports each
source's `data_types` list. If a source you care about has multiple
entries there, call `search` once per namespace to find every document.
Args:
query: Natural language search query.
namespace: Collection to search — "case_law", "legislation", or "doctrine".
top_k: Number of results (1-100).
alpha: Semantic vs keyword weight (1.0=pure semantic, 0.0=pure keyword).
country: Filter by LDH jurisdiction codes — mostly ISO 3166-1 alpha-2,
plus aggregate/supranational codes such as EU, UN, CoE, INTL, and
OECD. Call discover_countries for the full list. E.g. ["FR", "DE"].
source: Filter by source ID(s) from discover_sources, e.g. ["FR/Judilibre", "FR/CNIL"].
court_tier: Filter by court tier (1=supreme, 2=appellate, 3=first instance).
jurisdiction: Filter by jurisdiction name (e.g. "civil", "criminal").
subdivision: Filter by geographic subdivision (ISO 3166-2), e.g. "DE-BY", "US-CA".
date_start: Start date filter (YYYY-MM-DD).
date_end: End date filter (YYYY-MM-DD).
language: Optional language-code filter (e.g. fr, de), mainly useful in multilingual
jurisdictions. Do not infer it from the query language. Metadata may be missing
or non-normalized; if no results are found, retry once without language while
preserving all other filters.
Conéctate
En tu Slack en dos minutos.
Sin flujos que configurar. Activa las herramientas que ya usas y tu agente se pone a trabajar.
Añadir a Slack
1
Añade Sokko a Slack
Un clic desde el marketplace de Slack. Todo tu equipo tiene Sokko de una vez.
2
Conecta tus herramientas
Sokko funciona con más de 1000 apps y cualquier servidor MCP.
Martin
9:53 AM
@Sokko
¿Qué puedes hacer con Legal Data Hunter MCP?
3
Pon a Sokko a trabajar
@menciona a Sokko en cualquier canal y arranca. Minutos, no un fin de semana.
Preguntas, respondidas.
Sokko es un asistente de IA que vive en tu Slack. Conecta tus apps, pide lo que necesitas en lenguaje natural y Sokko se encarga del trabajo por ti.
Regístrate en Sokko, pídele a Sokko que se conecte a Legal Data Hunter MCP y aprueba la conexión cuando se te solicite. A partir de ahí puedes pedirle a Sokko que haga cosas en Legal Data Hunter MCP cuando quieras.
No. No hay nada que crear ni configurar. Le pides a Sokko en Slack igual que se lo pedirías a un colega, y Sokko se encarga del resto.
Sí. Pídelo una vez y dile a Sokko cuándo repetirlo, como cada lunes a las 9 h, y se convierte en una rutina que se ejecuta sin ti.
Leer y actuar sobre los datos de Legal Data Hunter MCP, y lanzar workflows cuando algo cambia. Dile a Sokko el resultado que quieres y se encarga del resto.
Sí. Sokko se conecta a más de 1.000 apps y a cualquier servidor MCP, así que puedes pedir tareas que abarquen Legal Data Hunter MCP y el resto de tu stack en una sola petición.