Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

emendrix

REMOTE · EMENDRIX.EU

Verified changes to watched EU acts, read-only, with each fact's source.

Available components

+4 this week 81 Trust /100

Last scanned (23 hours ago)

Scores higher than 84% of remote servers

Reachable. Last reached 4 Nov 2026.

Category Education and Research

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security80
Transport & Reachability100
Schema Quality & AI Usability73
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 2601 tokens (~260/item across 10 items; 8 tools + 2 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management53
  • Stability observed for 16 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 4 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.

  • 2 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

  • 31 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

  • 29 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

  • 27 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

  • 24 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

  • 22 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

  • 20 Oct 26 +1
    • Stability: unverified → 0.03 ▲ functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 4 Nov 2026 · Probed https://emendrix.eu/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=emendrix.eu CN=WE1,O=Google Trust Services,C=US 3 Nov 2026 1 Feb 2027 ECDSA 256 ECDSA-SHA256 73212013f321ab170e0b02e16829628b
SANs: emendrix.eu, *.emendrix.eu
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of emendrix.eu. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
eu. present 35926 8 Verified
emendrix.eu. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=31536000; includeSubDomains
content-security-policy default-src 'none'; script-src 'self'; style-src 'self'; font-src 'self'; img-src 'self'; connect-src 'self'; base-uri 'none'; form-action 'none'; frame-ancestors 'none'
x-content-type-options nosniff
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=(), interest-cohort=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://emendrix.eu/mcp Verified 200
http (plaintext) http://emendrix.eu/mcp HTTPS enforced 301 https://emendrix.eu/mcp
MCP tools · 8 exposed · ~2,373 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
changes_since ~340

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.

NameTypeReqDescription
acts––Act keys; all when omitted.
basisstring–Which stored date to compare.
include_disputedboolean–Keep disputed rows.
limitinteger–At most this many rows, 1 to 500.
sincestringyesThe earliest date, YYYY-MM-DD.
NameTypeReqDescription
basisstringyesWhich stored date was compared with `since`.
disclaimerstring–Not legal advice.
omittedintegeryesMatching rows left out because of `limit`.
rowsarrayyesMatching rows, newest first.
sincestringyesThe earliest date a row's basis date may carry.
unavailablearrayyesWhat could not be read, in words.

No examples provided.

find_provisions ~269

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.

NameTypeReqDescription
actstringyesThe act's key, or `corpus/key`, as `list_acts` gives it.
querystringyesPart of a location (`AR 5`) or a heading.
NameTypeReqDescription
disclaimerstring–Not legal advice.
provisionsarrayyesMatches, by canonical location.
unavailablearrayyesWhat could not be read, in words.

No examples provided.

find_substance ~279

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.

NameTypeReqDescription
identifierstringyesA CAS, EC or CLP Index number, hyphens optional.
NameTypeReqDescription
disclaimerstring–Not legal advice.
querystringyesThe value as typed.
readingsarrayyesOne answer per reading whose check digit passes; empty when none does.
sentencestringyesThe answer, or the reason the value is no number.
unavailablearrayyesWhat could not be read, in words.

No examples provided.

get_change ~410

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.

NameTypeReqDescription
actstringyesThe act's key, or `corpus/key`, as `list_acts` gives it.
locationstringyesA canonical location string such as `AR 50`, as the record stores it.
max_charsinteger–Characters per side, 1 to 50000.
occurrenceinteger–Which repeat, from 1.
offsetinteger–Where each side's page starts.
versionstringyesThe version an event produced, or its entry key, as stored.
NameTypeReqDescription
change–yesThe change; null when it could not be read.
disclaimerstring–Not legal advice.
unavailablearrayyesWhat could not be read, in words.

No examples provided.

get_event ~269

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.

NameTypeReqDescription
actstringyesThe act's key, or `corpus/key`, as `list_acts` gives it.
versionstringyesThe version an event produced, or its entry key, as stored.
NameTypeReqDescription
disclaimerstring–Not legal advice.
event–yesThe event; null when it could not be read.
unavailablearrayyesWhat could not be read, in words.

No examples provided.

list_acts ~264

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.

NameTypeReqDescription
domain––A catalogue sector.
query––Part of a key, title or alias.
NameTypeReqDescription
actsarrayyesMatching acts, sorted by corpus and key.
disclaimerstring–Not legal advice.
unavailablearrayyesWhat could not be read, in words.

No examples provided.

list_disputed ~272

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.

NameTypeReqDescription
act––One act's key; all when omitted.
limitinteger–At most this many rows, 1 to 2000.
reason––One `dispute_reason` code.
NameTypeReqDescription
disclaimerstring–Not legal advice.
groupsarrayyesOne group per reason code, by code.
omittedintegeryesDisputed rows left out because of `limit`.
unavailablearrayyesWhat could not be read, in words.

No examples provided.

provision_history ~270

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.

NameTypeReqDescription
actstringyesThe act's key, or `corpus/key`, as `list_acts` gives it.
locationstringyesA canonical location string such as `AR 50`, as the record stores it.
NameTypeReqDescription
disclaimerstring–Not legal advice.
locationstringyesThe canonical top-level location asked for.
rowsarrayyesThe provision's rows, newest first.
sentencestringyesWhat the rows, or their absence, mean, in words.
unavailablearrayyesWhat could not be read, in words.
window–yesWhat the record covers; null if unreadable.

No examples provided.

Install

How do I install the emendrix MCP server?

emendrix is a hosted endpoint at https://emendrix.eu/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · emendrix.eu

# add to Claude Code
claude mcp add --transport http eu-emendrix-emendrix 'https://emendrix.eu/mcp'
Common questions

What is the emendrix MCP server?

emendrix is an MCP server listed in the public MCP registry as eu.emendrix/emendrix. Verified changes to watched EU acts, read-only, with each fact's source. This page covers its hosted endpoint (https://emendrix.eu/mcp).

Is the emendrix MCP server safe to use?

emendrix scores 81 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the emendrix MCP server expose?

emendrix exposes 8 tools: list_acts, find_provisions, changes_since, provision_history, get_change, and 3 more. Their descriptions and schemas cost roughly 2,373 tokens of context every time the server is loaded.

Does the emendrix MCP server require authentication?

No. We connected to emendrix without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the emendrix MCP server still maintained?

emendrix is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.