eu.emendrix/emendrix

Est-ce que eu.emendrix/emendrix est sûr ?

Au dernier audit MCP Hub, le serveur MCP « eu.emendrix/emendrix » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.

Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.

Les 8 outils

• changes_since≈ 2341 tokens

  List recorded changes whose `basis` date is on or after `since`, newest first, with each row's event and provision pages: `updated_on` (the event or its latest repair), `detected_on` (when the run saw the event) or `in_force` (the change's in-force date; rows without one are left out). `omitted` counts rows past `limit`. An empty list means no recorded change in the window has that date. Every list is complete for the watch window the record covers, from the oldest version an act was watched from to its newest, and says nothing about anything outside it. `disputed` means one of three independent signals (the text comparison, the EU's own amendment metadata, the amending act's instructions) disagreed; `dispute_reason` says which and how, and a dispute is a reading of the sources, not a judgement about the law. `applies_from: unknown` means no application date could be read deterministically, never that no date applies. Units named by only one signal are listed by name on their event (`metadata_only_units`, `instruction_only_units`), never as changes. Not legal advice: this output is machine-computed from published texts, carries no lawyer's review, and is engineering assistance only.

  Paramètres, retour & exemple (5)

  Paramètres

  • acts · ? · optionnel
    Act keys; all when omitted.
  • basis · string · optionnel · updated_on | detected_on | in_force
    Which stored date to compare.
  • limit · integer · optionnel
    At most this many rows, 1 to 500.
  • since · string · requis
    The earliest date, YYYY-MM-DD.
  • include_disputed · boolean · optionnel
    Keep disputed rows.

  Exemple d'appel

  {"name": "changes_since", "arguments": {"since": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"rows": [], "basis": "updated_on", "since": "texte", "omitted": 1, "disclaimer": "texte", "unavailable": []}}

• find_provisions≈ 2284 tokens

  Find touched provisions of one act whose canonical location string or stored heading contains `query`, each with its newest row. It never reads law text; an empty list means no touched provision of the act has that name in the window. Every list is complete for the watch window the record covers, from the oldest version an act was watched from to its newest, and says nothing about anything outside it. `disputed` means one of three independent signals (the text comparison, the EU's own amendment metadata, the amending act's instructions) disagreed; `dispute_reason` says which and how, and a dispute is a reading of the sources, not a judgement about the law. `applies_from: unknown` means no application date could be read deterministically, never that no date applies. Units named by only one signal are listed by name on their event (`metadata_only_units`, `instruction_only_units`), never as changes. Not legal advice: this output is machine-computed from published texts, carries no lawyer's review, and is engineering assistance only.

  Paramètres, retour & exemple (2)

  Paramètres

  • act · string · requis
    The act's key, or `corpus/key`, as `list_acts` gives it.
  • query · string · requis
    Part of a location (`AR 5`) or a heading.

  Exemple d'appel

  {"name": "find_provisions", "arguments": {"act": "texte", "query": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"disclaimer": "texte", "provisions": [], "unavailable": []}}

• find_substance≈ 2801 tokens

  Find the entries that print a CAS or EC number, given with or without hyphens, in the newest version of each act the record holds, and every recorded change to them, each with its date, the amending act the change names and the file it was read from. It reports where a number appears and decides nothing about legal status; many entries name a group and print no number. Every list is complete for the watch window the record covers, from the oldest version an act was watched from to its newest, and says nothing about anything outside it. `disputed` means one of three independent signals (the text comparison, the EU's own amendment metadata, the amending act's instructions) disagreed; `dispute_reason` says which and how, and a dispute is a reading of the sources, not a judgement about the law. `applies_from: unknown` means no application date could be read deterministically, never that no date applies. Units named by only one signal are listed by name on their event (`metadata_only_units`, `instruction_only_units`), never as changes. Not legal advice: this output is machine-computed from published texts, carries no lawyer's review, and is engineering assistance only.

  Paramètres, retour & exemple (1)

  Paramètres

  • identifier · string · requis
    A CAS, EC or CLP Index number, hyphens optional.

  Exemple d'appel

  {"name": "find_substance", "arguments": {"identifier": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"query": "texte", "readings": [], "sentence": "texte", "disclaimer": "texte", "unavailable": []}}

• get_change≈ 4382 tokens

  One change in full: the verbatim text before and after, each side cut at `max_chars` (1 to 50000) with a marker '[… N characters omitted, continue with offset=M]' and paged by `offset`; the cited sentences with their URLs; `changed_within`; the three signals with their detail; `dispute_reason` and its sentence; `in_force`; `applies_from` with its reason; amending acts; the gate outcome or why it is unexplained. `occurrence` counts repeats of one location in one event from 1. Every list is complete for the watch window the record covers, from the oldest version an act was watched from to its newest, and says nothing about anything outside it. `disputed` means one of three independent signals (the text comparison, the EU's own amendment metadata, the amending act's instructions) disagreed; `dispute_reason` says which and how, and a dispute is a reading of the sources, not a judgement about the law. `applies_from: unknown` means no application date could be read deterministically, never that no date applies. Units named by only one signal are listed by name on their event (`metadata_only_units`, `instruction_only_units`), never as changes. Not legal advice: this output is machine-computed from published texts, carries no lawyer's review, and is engineering assistance only.

  Paramètres, retour & exemple (6)

  Paramètres

  • act · string · requis
    The act's key, or `corpus/key`, as `list_acts` gives it.
  • offset · integer · optionnel
    Where each side's page starts.
  • version · string · requis
    The version an event produced, or its entry key, as stored.
  • location · string · requis
    A canonical location string such as `AR 50`, as the record stores it.
  • max_chars · integer · optionnel
    Characters per side, 1 to 50000.
  • occurrence · integer · optionnel
    Which repeat, from 1.

  Exemple d'appel

  {"name": "get_change", "arguments": {"act": "texte", "version": "texte", "location": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"change": "texte", "disclaimer": "texte", "unavailable": []}}

• get_event≈ 4338 tokens

  One event of one act: its counts, repairs and stored corroboration (each signal's units, the pairwise agreements and disagreements), the units only the metadata or only the instruction parse names, and every row of the event. Every list is complete for the watch window the record covers, from the oldest version an act was watched from to its newest, and says nothing about anything outside it. `disputed` means one of three independent signals (the text comparison, the EU's own amendment metadata, the amending act's instructions) disagreed; `dispute_reason` says which and how, and a dispute is a reading of the sources, not a judgement about the law. `applies_from: unknown` means no application date could be read deterministically, never that no date applies. Units named by only one signal are listed by name on their event (`metadata_only_units`, `instruction_only_units`), never as changes. Not legal advice: this output is machine-computed from published texts, carries no lawyer's review, and is engineering assistance only.

  Paramètres, retour & exemple (2)

  Paramètres

  • act · string · requis
    The act's key, or `corpus/key`, as `list_acts` gives it.
  • version · string · requis
    The version an event produced, or its entry key, as stored.

  Exemple d'appel

  {"name": "get_event", "arguments": {"act": "texte", "version": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"event": "texte", "disclaimer": "texte", "unavailable": []}}

• list_acts≈ 1430 tokens

  List the acts the record holds, with each act's label, aliases and sector from the site catalogue, its newest version, `updated_on` and the counts its index carries. `query` matches names case-insensitively; `domain` matches the catalogue's sector. An empty list means no held act matches. Every list is complete for the watch window the record covers, from the oldest version an act was watched from to its newest, and says nothing about anything outside it. `disputed` means one of three independent signals (the text comparison, the EU's own amendment metadata, the amending act's instructions) disagreed; `dispute_reason` says which and how, and a dispute is a reading of the sources, not a judgement about the law. `applies_from: unknown` means no application date could be read deterministically, never that no date applies. Units named by only one signal are listed by name on their event (`metadata_only_units`, `instruction_only_units`), never as changes. Not legal advice: this output is machine-computed from published texts, carries no lawyer's review, and is engineering assistance only.

  Paramètres, retour & exemple (2)

  Paramètres

  • query · ? · optionnel
    Part of a key, title or alias.
  • domain · ? · optionnel
    A catalogue sector.

  Exemple d'appel

  {"name": "list_acts", "arguments": {"query": "texte", "domain": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"acts": [], "disclaimer": "texte", "unavailable": []}}

• list_disputed≈ 2301 tokens

  Disputed rows grouped by their stored `dispute_reason`, each group with the sentence the site prints for that code. `omitted` counts rows past `limit`. An empty list means no recorded change in the window is disputed for that filter. Every list is complete for the watch window the record covers, from the oldest version an act was watched from to its newest, and says nothing about anything outside it. `disputed` means one of three independent signals (the text comparison, the EU's own amendment metadata, the amending act's instructions) disagreed; `dispute_reason` says which and how, and a dispute is a reading of the sources, not a judgement about the law. `applies_from: unknown` means no application date could be read deterministically, never that no date applies. Units named by only one signal are listed by name on their event (`metadata_only_units`, `instruction_only_units`), never as changes. Not legal advice: this output is machine-computed from published texts, carries no lawyer's review, and is engineering assistance only.

  Paramètres, retour & exemple (3)

  Paramètres

  • act · ? · optionnel
    One act's key; all when omitted.
  • limit · integer · optionnel
    At most this many rows, 1 to 2000.
  • reason · ? · optionnel
    One `dispute_reason` code.

  Exemple d'appel

  {"name": "list_disputed", "arguments": {"act": "texte", "limit": 1, "reason": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"groups": [], "omitted": 1, "disclaimer": "texte", "unavailable": []}}

• provision_history≈ 2461 tokens

  Every recorded change to one top-level provision, newest first, with the window the record covers for the act. An empty list means no recorded change to that provision in the window, and the result says so in words. Every list is complete for the watch window the record covers, from the oldest version an act was watched from to its newest, and says nothing about anything outside it. `disputed` means one of three independent signals (the text comparison, the EU's own amendment metadata, the amending act's instructions) disagreed; `dispute_reason` says which and how, and a dispute is a reading of the sources, not a judgement about the law. `applies_from: unknown` means no application date could be read deterministically, never that no date applies. Units named by only one signal are listed by name on their event (`metadata_only_units`, `instruction_only_units`), never as changes. Not legal advice: this output is machine-computed from published texts, carries no lawyer's review, and is engineering assistance only.

  Paramètres, retour & exemple (2)

  Paramètres

  • act · string · requis
    The act's key, or `corpus/key`, as `list_acts` gives it.
  • location · string · requis
    A canonical location string such as `AR 50`, as the record stores it.

  Exemple d'appel

  {"name": "provision_history", "arguments": {"act": "texte", "location": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"rows": [], "window": "texte", "location": "texte", "sentence": "texte", "disclaimer": "texte", "unavailable": []}}

C'est votre serveur ?

Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».

Créer un compte / revendiquer →

Source

https://emendrix.eu/mcp