emendrix

endpoint

https://emendrix.eu/mcp

protocol

streamable-http ·2025-06-18

authentication

none observed

public key

none — nobody has proven they own this listing · is it yours? claim it

karma

0 · newcomer

Is emendrix live?

Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.

Is emendrix free to use?

Yes — the hub reached it with no key and no payment.

What tools does emendrix have?

8 tools: provision_history, get_change, get_event, list_disputed, find_substance, changes_since, find_provisions, list_acts.

Is emendrix safe to connect?

The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

• list_acts open 2h ago

  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.

  mcp-tool

  1234567891011121314151617181920212223242526272829303132

  {
    "type": "object",
    "title": "list_acts_toolArguments",
    "properties": {
      "query": {
        "anyOf": [
          {
            "type": "string"
          },
          {
            "type": "null"
          }
        ],
        "title": "Query",
        "default": null,
        "description": "Part of a key, title or alias."
      },
      "domain": {
        "anyOf": [
          {
            "type": "string"
          },
          {
            "type": "null"
          }
        ],
        "title": "Domain",
        "default": null,
        "description": "A catalogue sector."
      }
    }
  }

  arguments 32 lines copy
• provision_history unknown never probed

  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.

  mcp-tool

  1234567891011121314151617181920

  {
    "type": "object",
    "title": "provision_history_toolArguments",
    "required": [
      "act",
      "location"
    ],
    "properties": {
      "act": {
        "type": "string",
        "title": "Act",
        "description": "The act's key, or `corpus/key`, as `list_acts` gives it."
      },
      "location": {
        "type": "string",
        "title": "Location",
        "description": "A canonical location string such as `AR 50`, as the record stores it."
      }
    }
  }

  arguments 20 lines copy
• get_change unknown never probed

  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.

  mcp-tool

  1234567891011121314151617181920212223242526272829303132333435363738394041424344

  {
    "type": "object",
    "title": "get_change_toolArguments",
    "required": [
      "act",
      "version",
      "location"
    ],
    "properties": {
      "act": {
        "type": "string",
        "title": "Act",
        "description": "The act's key, or `corpus/key`, as `list_acts` gives it."
      },
      "offset": {
        "type": "integer",
        "title": "Offset",
        "default": 0,
        "description": "Where each side's page starts."
      },
      "version": {
        "type": "string",
        "title": "Version",
        "description": "The version an event produced, or its entry key, as stored."
      },
      "location": {
        "type": "string",
        "title": "Location",
        "description": "A canonical location string such as `AR 50`, as the record stores it."
      },
      "max_chars": {
        "type": "integer",
        "title": "Max Chars",
        "default": 8000,
        "description": "Characters per side, 1 to 50000."
      },
      "occurrence": {
        "type": "integer",
        "title": "Occurrence",
        "default": 1,
        "description": "Which repeat, from 1."
      }
    }
  }

  arguments 44 lines copy
• get_event unknown never probed

  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.

  mcp-tool

  1234567891011121314151617181920

  {
    "type": "object",
    "title": "get_event_toolArguments",
    "required": [
      "act",
      "version"
    ],
    "properties": {
      "act": {
        "type": "string",
        "title": "Act",
        "description": "The act's key, or `corpus/key`, as `list_acts` gives it."
      },
      "version": {
        "type": "string",
        "title": "Version",
        "description": "The version an event produced, or its entry key, as stored."
      }
    }
  }

  arguments 20 lines copy
• list_disputed unknown never probed

  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.

  mcp-tool

  1234567891011121314151617181920212223242526272829303132333435363738

  {
    "type": "object",
    "title": "list_disputed_toolArguments",
    "properties": {
      "act": {
        "anyOf": [
          {
            "type": "string"
          },
          {
            "type": "null"
          }
        ],
        "title": "Act",
        "default": null,
        "description": "One act's key; all when omitted."
      },
      "limit": {
        "type": "integer",
        "title": "Limit",
        "default": 200,
        "description": "At most this many rows, 1 to 2000."
      },
      "reason": {
        "anyOf": [
          {
            "type": "string"
          },
          {
            "type": "null"
          }
        ],
        "title": "Reason",
        "default": null,
        "description": "One `dispute_reason` code."
      }
    }
  }

  arguments 38 lines copy
• find_substance unknown never probed

  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.

  mcp-tool

  1234567891011121314

  {
    "type": "object",
    "title": "find_substance_toolArguments",
    "required": [
      "identifier"
    ],
    "properties": {
      "identifier": {
        "type": "string",
        "title": "Identifier",
        "description": "A CAS, EC or CLP Index number, hyphens optional."
      }
    }
  }

  arguments 14 lines copy
• changes_since unknown 2h ago

  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.

  mcp-tool

  123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354

  {
    "type": "object",
    "title": "changes_since_toolArguments",
    "required": [
      "since"
    ],
    "properties": {
      "acts": {
        "anyOf": [
          {
            "type": "array",
            "items": {
              "type": "string"
            }
          },
          {
            "type": "null"
          }
        ],
        "title": "Acts",
        "default": null,
        "description": "Act keys; all when omitted."
      },
      "basis": {
        "enum": [
          "updated_on",
          "detected_on",
          "in_force"
        ],
        "type": "string",
        "title": "Basis",
        "default": "updated_on",
        "description": "Which stored date to compare."
      },
      "limit": {
        "type": "integer",
        "title": "Limit",
        "default": 50,
        "description": "At most this many rows, 1 to 500."
      },
      "since": {
        "type": "string",
        "title": "Since",
        "format": "date",
        "description": "The earliest date, YYYY-MM-DD."
      },
      "include_disputed": {
        "type": "boolean",
        "title": "Include Disputed",
        "default": true,
        "description": "Keep disputed rows."
      }
    }
  }

  arguments 54 lines copy
• find_provisions unknown 2h ago

  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.

  mcp-tool

  1234567891011121314151617181920

  {
    "type": "object",
    "title": "find_provisions_toolArguments",
    "required": [
      "act",
      "query"
    ],
    "properties": {
      "act": {
        "type": "string",
        "title": "Act",
        "description": "The act's key, or `corpus/key`, as `list_acts` gives it."
      },
      "query": {
        "type": "string",
        "title": "Query",
        "description": "Part of a location (`AR 5`) or a heading."
      }
    }
  }

  arguments 20 lines copy

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.