EUR-Lex, UK and Dutch law
REMOTE · API.BOSCOLABS.DEV
EU legislation from EUR-Lex, UK and Dutch statutes and Dutch case law, article by article
Available components
Last scanned (14 hours ago)
Scores higher than 57% of remote servers
Reachable. Last reached 21 Nov 2026.
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
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability57
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 3389 tokens (~423/item across 8 items; 8 tools + 0 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 Management13
- Stability observed for 4 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 (63% 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 9 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
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 20 Nov 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.
- 18 Nov 26 +1
- Tool “get_eu_law” rewrote its description, which is the text the model reads security
- Tool “search_dutch_case_law” rewrote its description, which is the text the model reads security
- Tool “get_uk_dutch_law” rewrote its description, which is the text the model reads security
- Schema quality: 2084 → 3389 ▼ functional
- Stability: unverified → 0.03 ▲ functional
- Tool “get_eu_law” now declares an output schema ▲ functional
- Tool “search_dutch_case_law” now declares an output schema ▲ functional
- Tool “get_uk_dutch_law” now declares an output schema ▲ functional
- First check of Tool coverage: 63 functional
- Schema quality: good → excellent functional
- New tool “get_lei_record” functional
- New tool “find_sec_company” functional
- New tool “describe_records_tool” functional
- 17 Nov 26 70
First indexed and scored.
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 21 Nov 2026 · Probed https://api.boscolabs.dev/mcp?tools=get_eu_law,get_uk_dutch_law,search_dutch_case_law,plan_records_query
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.boscolabs.dev | CN=YR2,O=Let's Encrypt,C=US | 6 Nov 2026 | 4 Feb 2027 | RSA 2048 | SHA256-RSA | 6bf6bfb80557ba04d475c922e603399695c |
| SANs: *.boscolabs.dev, boscolabs.dev | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.boscolabs.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | DS published | 60074 | 8 | Verified |
| boscolabs.dev. | No DS | 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=63072000 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.boscolabs.dev/mcp?tools=get_eu_law,get_uk_dutch_law,search_dutch_case_law,plan_records_query | Verified | 200 | |
| http (plaintext) | http://api.boscolabs.dev/mcp?tools=get_eu_law,get_uk_dutch_law,search_dutch_case_law,plan_records_query | HTTPS enforced | 308 | https://api.boscolabs.dev/mcp?tools=get_eu_law,get_uk_dutch_law,search_dutch_case_law,plan_records_query |
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 →
describe_records_tool Describe an official-records tool ~106
Free, no key needed. One Bosco Labs tool's full input schema, example input, example rows, output fields, price per row, caps and sources. Use it before calling a tool whose input you are unsure of: the tool list shortens each input field to one sentence, and this shows every field, its allowed values and a working example. An unknown name returns the closest names.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Tool name, e.g. search_eu_tenders. |
No output schema declared.
No examples provided.
find_sec_company SEC company lookup: ticker to CIK (free) ~308
Free, no API token needed. Identify a US-listed (SEC-registered) company: CIK, official name, ticker(s), exchange(s), industry (SIC code) and state of incorporation (source: SEC EDGAR company tickers file and submissions API). Use it to turn a ticker or name into the CIK that SEC tools take, or to check which exchange a stock trades on. Pass a ticker, a CIK or part of the name (best matches first, then by company size; check `name`). A name search covers companies with a listed ticker (about 10,000); a CIK also finds filers without one. Returns one row per company: cik, name, tickers, exchanges, sic, sic_description, state_of_incorporation, fiscal_year_end (MMDD), source_url (the EDGAR company page; cite it) and next_steps (the paid Bosco Labs calls for its filings and insider trades). Inputs: `query` is a ticker, a CIK or part of the name; `max_results` (1-5, default 3) applies to a name search only. Read-only, no key, no charge; at most 30 free lookups a minute per caller.
| Name | Type | Req | Description |
|---|---|---|---|
| max_results | integer | – | Max companies for a name search (1-5). |
| query | string | yes | A ticker (AAPL), a CIK (320193) or part of the company name ("apple") |
| Name | Type | Req | Description |
|---|---|---|---|
| balance_usd | number|null | – | – |
| charged_usd | number|null | – | – |
| count | number|null | yes | – |
| duration_seconds | number|null | – | – |
| message | string|null | – | – |
| rows | array | yes | – |
| tool | string|null | – | – |
| warnings | array|null | – | – |
No examples provided.
get_eu_law EUR-Lex Scraper API: EU law article text, in force, amendments ~778
One call answers "what does Article 50 of the AI Act say today, is it in force, and what amended it?": the article as plain text from the current consolidated version (or the one in force on any date), the act's in-force status and dates, and the acts that amend, correct or repeal it. A second mode lists new acts in the Official Journal L series. Pass `query` (GDPR, AI Act, a citation, CELEX or ELI), or `ojSince` alone to list new Official Journal acts. For UK or Dutch statutes use get_uk_dutch_law; for Dutch court rulings use search_dutch_case_law. Inputs: with `article` (e.g. "6(1)", up to 10) one row per article; without it one row for the whole act with its table of contents. `include` adds amendments, citing acts or the full text; `asOf` gives the version in force on a date; `language` is one of the 24 EU languages (English when a text is missing). Read-only, no side effects. Charged per row returned, at the price below; a call that fails or runs out of time (55 s) is free. If one source does not answer, the rest still comes back and `warnings` names the gap. Limit: 60 calls a minute per key (10 on a new free key); past it the call is refused (rate_limited, free): retry after about 10 seconds. Price: $0.005 per `act-lookup`.
| Name | Type | Req | Description |
|---|---|---|---|
| article | string | – | Article number, optionally with a paragraph: "5", "6(1)", "4a"; several separated by commas ("5, 6(1)", up to 10) |
| asOf | string | – | YYYY-MM-DD, e.g. "2025-01-01": return the consolidated version that applied on that date |
| include | array | – | Any of "metadata" (always on), "amendments" (amended_by, corrected_by, repealed_by, amends, repeals), "citing" (acts and judgments that cite this act, newest first) and "text" |
| keywords | string | – | OJ mode only: comma-separated words or phrases; an act is kept when its title (in the chosen language) contains any of them, case-insensitive, e.g. "artificial intelligence, data" |
| language | string | – | EU language code of the text and titles: BG, CS, DA, DE, EL, EN, ES, ET, FI, FR, GA, HR, HU, IT, LT, LV, MT, NL, PL, PT, RO, SK, SL, SV |
| maxCiting | integer | – | With include "citing": how many citing acts to list, newest first, e.g. 20 (default) |
| maxResults | integer | – | OJ mode only: the most acts to return, newest first, e.g. 50 (default) |
| maxTextChars | integer | – | Cap on article_text and text, in characters, e.g. 30000 (default) |
| ojSince | string | – | Switches to Official Journal mode: list acts published in the OJ L series from this date (YYYY-MM-DD, e.g. "2026-11-03") until today, newest first, at most 31 days back |
| query | string | – | The EU act to look up: a short name ("GDPR", "AI Act", "DSA", "NIS2", "DORA", "MiCA", "CSRD"...), a citation ("Regulation |
| Name | Type | Req | Description |
|---|---|---|---|
| balance_usd | number|null | – | – |
| charged_usd | number|null | – | – |
| count | number|null | yes | – |
| duration_seconds | number|null | – | – |
| message | string|null | – | – |
| rows | array | yes | – |
| tool | string|null | – | – |
| warnings | array|null | – | – |
No examples provided.
get_lei_record LEI lookup (GLEIF, free) ~355
Free, no API token needed. Legal Entity Identifier (LEI) lookup in the official GLEIF register: about 2.9 million companies, funds and other legal entities worldwide (source: GLEIF API, CC0 open data). Use it to identify a company: its exact legal name, LEI, whether it is active, its jurisdiction and country, its local registration number and its ultimate parent company. Pass an LEI (exact record) or a company name (best matches first; check `legal_name`). Returns one row per entity: lei, legal_name, entity_status (ACTIVE/INACTIVE), registration_status (ISSUED, LAPSED, ...), jurisdiction, legal_address_country, legal_address_city, headquarters_country, registered_as (local registry number), ultimate_parent (lei, legal_name; when reported), source_url (the GLEIF record; cite it) and next_steps (the paid Bosco Labs call for this company's financials: the tool and arguments to call next). Inputs: `query` is either a 20-character LEI (one exact record) or a company name (best matches first); `max_results` (1-5, default 3) applies to a name search only. Read-only, no key, no charge; at most 30 free lookups a minute per caller. Nothing found: an error that says what to try.
| Name | Type | Req | Description |
|---|---|---|---|
| max_results | integer | – | Max companies for a name search (1-5). |
| query | string | yes | A 20-character LEI, e.g. 724500Y6DUVHQD6OXN27, or a company name, e.g. "Heineken" |
| Name | Type | Req | Description |
|---|---|---|---|
| balance_usd | number|null | – | – |
| charged_usd | number|null | – | – |
| count | number|null | yes | – |
| duration_seconds | number|null | – | – |
| message | string|null | – | – |
| rows | array | yes | – |
| tool | string|null | – | – |
| warnings | array|null | – | – |
No examples provided.
get_uk_dutch_law UK & Dutch Law Lookup API: article text by date, in force ~478
One call answers "what does section 172 of the Companies Act 2006 say?" or "wat zegt artikel 7:658 BW?": the section or article as plain text from the official consolidated version in force today (or on any date), whether it is in force, and what changed it. Needs `query`, a citation. UK and Dutch law only: for EU acts use get_eu_law; for Dutch court rulings use search_dutch_case_law. Inputs: `query` holds the act and optionally the article, e.g. "Companies Act 2006 s 172" or "BW 7:658", or a legislation.gov.uk or BWB path. `article` overrides it (up to 5, comma-separated); `asOf` gives the text in force on a date; set `jurisdiction` (UK or NL) only when a bare name is ambiguous. Read-only, no side effects. Charged per row returned, at the price below; a call that fails or runs out of time (55 s) is free. If one source does not answer, the rest still comes back and `warnings` names the gap. Limit: 60 calls a minute per key (10 on a new free key); past it the call is refused (rate_limited, free): retry after about 10 seconds. Price: $0.005 per `act-lookup`.
| Name | Type | Req | Description |
|---|---|---|---|
| article | string | – | Section, regulation or article number, optionally with a subsection or lid: "172", "172(1)", "7:658", "13 lid 2", "8:1"; several separated by commas (up to 5, e.g. "171, 172") |
| asOf | string | – | YYYY-MM-DD, e.g. "2025-01-01": return the text as in force on that date (UK point-in-time version; NL consolidated version, newest correction) |
| jurisdiction | string | – | "UK" or "NL" |
| language | string | – | Optional, "EN" or "NL" |
| maxTextChars | integer | – | Cap on article_text, in characters, e.g. 30000 (default) |
| query | string | yes | The act, optionally with the article |
| Name | Type | Req | Description |
|---|---|---|---|
| balance_usd | number|null | – | – |
| charged_usd | number|null | – | – |
| count | number|null | yes | – |
| duration_seconds | number|null | – | – |
| message | string|null | – | – |
| rows | array | yes | – |
| tool | string|null | – | – |
| warnings | array|null | – | – |
No examples provided.
plan_records_query Plan an official-records query ~316
Free, no key needed. Turns a question in plain words into the exact typed Bosco Labs calls that answer it: tool, input, why, and the maximum price of each step, plus what is not covered. Pass the user's question verbatim AND the entities you extracted from it (company_names, tickers, identifiers, countries, dates, law references...): the planner trusts your entities over its own parsing and puts them in the right input fields. The plan echoes them in entities_used and lists in `missing` what to pass for a better plan. Rules and examples first; only when they are unsure and you passed no entities does a small AI step extract the entities (budget-capped, marked `assisted`). Same steps, same plan_id. Run it with run_records_plan (paid, max_usd) or call the listed tools directly. Low confidence returns the top 3 candidate tools instead. Questions are kept 30 days in a cut-down form; leave out personal details.
| Name | Type | Req | Description |
|---|---|---|---|
| entities | object | – | What you (the calling agent) already extracted from the user's question. Extract these from the question yourself; the planner trusts them over its own parsing and puts them in the right input fields… |
| question | string | yes | The user's question, verbatim, e.g. "Is Rosneft on the EU sanctions list?" (English, Dutch, German or French). |
No output schema declared.
No examples provided.
run_records_plan Run an official-records plan ~208
Runs a plan from plan_records_query (its plan_id) or explicit steps, all steps in parallel, under a hard max_usd: if the worst case could exceed it, nothing runs. Each step is charged to the caller's key exactly like a direct tool call (failed steps are free). Returns one section per step (via_tool, via_input, rows with source_url), a receipt and the citations. Reaches all 30 tools; to list them as MCP tools, add ?tools=all to the MCP URL.
| Name | Type | Req | Description |
|---|---|---|---|
| max_usd | number | yes | Hard cap in USD: refused, nothing run, if the steps' worst case could cost more. |
| plan_id | string | – | The plan_id plan_records_query returned (or pass steps). |
| steps | array | – | Explicit steps instead of a plan_id: [{tool, input}], tool a name from GET /v1/tools (eu-tenders or search_eu_tenders), input that tool's input. |
No output schema declared.
No examples provided.
search_dutch_case_law Dutch Case Law API (Rechtspraak): court rulings by ECLI ~624
Look up Dutch court decisions (uitspraken) by ECLI, or search them by court, legal area, date and keywords: court, decision and publication dates, case numbers, legal areas, procedure, the court's own summary (inhoudsindicatie), appeal / cassation / Advocate-General relations, referenced laws, and optionally the full text. Pass `ecli` for one decision, or `query` and filters to search. For the text of a statute use get_uk_dutch_law, or get_eu_law for EU law. Inputs: `ecli` (up to 100, comma-separated) fetches decisions directly. Otherwise `query` searches titles and summaries (commas separate alternatives, the words of one alternative must all appear), narrowed by `courts` (ECLI codes such as HR, RVS), `legalAreas`, dates and `documentType`. `includeText` adds the full text at the same price, cut at `maxTextChars`. Read-only, no side effects. Charged per row returned, at the price below; a call that fails or runs out of time (55 s) is free. If one source does not answer, the rest still comes back and `warnings` names the gap. Limit: 60 calls a minute per key (10 on a new free key); past it the call is refused (rate_limited, free): retry after about 10 seconds. Price: $0.005 per `decision`.
| Name | Type | Req | Description |
|---|---|---|---|
| courts | array | – | Court codes as used in the ECLI |
| dateFrom | string | – | Earliest decision date (uitspraakdatum), YYYY-MM-DD, e.g. "2024-01-01" |
| dateTo | string | – | Latest decision date, inclusive, YYYY-MM-DD, e.g. "2024-12-31" |
| documentType | string | – | "uitspraak" = court decisions only, "conclusie" = opinions of the Advocate-General at the Hoge Raad only |
| ecli | string | – | One or more Dutch ECLIs, separated by commas or spaces, e.g. "ECLI:NL:HR:2024:123" or "ECLI:NL:HR:2024:123, ECLI:NL:RVS:2024:1000" (max 100) |
| includeText | boolean | – | true = add the full decision as plain text (section headings as '## ', numbered paragraphs kept), cut at maxTextChars |
| legalAreas | array | – | Rechtsgebied names |
| maxResults | integer | – | Most decisions to return from a search, most recently published or updated first, e.g. 20 (default) |
| maxTextChars | integer | – | With includeText: cap on the text per decision in characters, e.g. 20000 (default) |
| query | string | – | Words to find in the decision's title and summary (inhoudsindicatie), case-insensitive |
| Name | Type | Req | Description |
|---|---|---|---|
| balance_usd | number|null | – | – |
| charged_usd | number|null | – | – |
| count | number|null | yes | – |
| duration_seconds | number|null | – | – |
| message | string|null | – | – |
| rows | array | yes | – |
| tool | string|null | – | – |
| warnings | array|null | – | – |
No examples provided.
How do I install the EUR-Lex, UK and Dutch law MCP server?
EUR-Lex, UK and Dutch law is a hosted endpoint at https://api.boscolabs.dev/mcp?tools=get_eu_law,get_uk_dutch_law,search_dutch_case_law,plan_records_query, 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 · api.boscolabs.dev
claude mcp add --transport http bosco-labs-eur-lex-uk-dutch-law 'https://api.boscolabs.dev/mcp?tools=get_eu_law,get_uk_dutch_law,search_dutch_case_law,plan_records_query'
What is the EUR-Lex, UK and Dutch law MCP server?
EUR-Lex, UK and Dutch law is an MCP server listed in the public MCP registry as io.github.Bosco-Labs/eur-lex-uk-dutch-law. EU legislation from EUR-Lex, UK and Dutch statutes and Dutch case law, article by article. This page covers its hosted endpoint (https://api.boscolabs.dev/mcp?tools=get_eu_law,get_uk_dutch_law,search_dutch_case_law,plan_records_query).
Is the EUR-Lex, UK and Dutch law MCP server safe to use?
EUR-Lex, UK and Dutch law scores 72 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 EUR-Lex, UK and Dutch law MCP server expose?
EUR-Lex, UK and Dutch law exposes 8 tools: plan_records_query, describe_records_tool, run_records_plan, search_dutch_case_law, get_eu_law, and 3 more. Their descriptions and schemas cost roughly 3,173 tokens of context every time the server is loaded.
Does the EUR-Lex, UK and Dutch law MCP server require authentication?
No. We connected to EUR-Lex, UK and Dutch law without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the EUR-Lex, UK and Dutch law MCP server still maintained?
EUR-Lex, UK and Dutch law is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the EUR-Lex, UK and Dutch law MCP server?
VerifyMCP ran 13 checks on EUR-Lex, UK and Dutch law, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.