REP27 — EU & UK legal representative
REMOTE · GDPRREPRESENTATIVE.COM
Check EU/UK GDPR Art. 27 and GPSR Art. 16 obligations, see plans, start a free trial
Available components
Last scanned (19 hours ago)
Scores higher than 47% of remote servers
Reachable. Last reached 18 Oct 2026.
Category Security
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 Security74
- 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. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- 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 Usability35
- 0% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Fail
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1552 tokens (~221/item across 7 items; 6 tools + 1 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 Management10
- Stability observed for 3 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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
- Supports UI / widget rendering.Pass
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.
- 17 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 15 Oct 26 64
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 18 Oct 2026 · Probed https://gdprrepresentative.com/mcp-claude
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=gdprrepresentative.com | CN=YE1,O=Let's Encrypt,C=US | 29 Sept 2026 | 28 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 652138fcf8588477fe0a62b774120880c43 |
| SANs: gdprrepresentative.com, www.gdprrepresentative.com | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of gdprrepresentative.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| gdprrepresentative.com. | 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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://gdprrepresentative.com/mcp-claude | Verified | 200 | |
| http (plaintext) | http://gdprrepresentative.com/mcp-claude | HTTPS enforced | 301 | https://gdprrepresentative.com/mcp-claude |
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 →
about_rep27 About REP27 ~25
Who provides the REP27 service, legal entities, contacts, terms and verification.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
check_obligations Check which EU/UK representative obligations apply ~512
Checks, from a few facts about the company, whether it legally needs an EU GDPR Art. 27 representative, a UK GDPR Art. 27 representative and/or a GPSR Art. 16 EU responsible person, explains why with the legal basis and lists exemptions. Recommends the cheapest REP27 combination. Returns result_url, a personal page with the result.
| Name | Type | Req | Description |
|---|---|---|---|
| currency | string | – | Currency to also show prices in: EUR, USD, GBP, CAD, AUD, NZD, CHF, CZK, JPY or NOK (ECB rate) |
| data_requests_per_year | integer | – | Expected data-subject requests per year (access, erasure…), 0 if unknown |
| established_in | string | yes | Country where the company is established, name or ISO code (e.g. United States, US, China) |
| has_eu_branch | boolean | – | True if the company has an establishment (branch or subsidiary) in the EU |
| has_eu_importer_or_manufacturer_in_eu | boolean | – | True if an EU-based manufacturer, importer or authorised representative already covers the products |
| has_uk_branch | boolean | – | True if the company has an establishment in the UK |
| health_or_special_category_data | boolean | – | True if it processes health or other special-category data (Art. 9) or criminal-offence data at scale |
| lang | string | – | Language code for the answer (ISO 639-1, e.g. en, it, es, fr, de, pt, nl, pl, ja, zh) |
| occasional_low_risk_processing_only | boolean | – | True if personal data of EU/UK people is processed only occasionally, at low risk and without special categories (Art. 27(2) exemption) |
| offers_to_eu | boolean | yes | True if the company offers goods or services to people in the EU/EEA or monitors their behaviour (tracking, ad profiling) |
| offers_to_uk | boolean | – | True if the company offers goods or services to people in the UK or monitors their behaviour |
| public_authority | boolean | – | True if the organisation is a public authority or body |
| sells_consumer_products_eu | boolean | – | True if it places physical consumer products on the EU market (own shop or marketplaces like Amazon, Etsy, eBay) |
| sells_consumer_products_uk | boolean | – | True if it places physical consumer products on the UK market |
Structured output declared, but exposes no named fields.
No examples provided.
create_checkout Create secure checkout ~338
Creates the secure Mollie checkout for the chosen REP27 plan with the buyer's company, country, contact name and email, and returns the payment link. Payment happens on Mollie's page, never in the chat.
| Name | Type | Req | Description |
|---|---|---|---|
| billing | string | – | yearly, or monthly only for GPSR responsible-person plans |
| company | string | yes | Legal name of the buying company |
| country | string | yes | Country where the company is established |
| currency | string | – | Currency to pay in: EUR, USD, GBP, CAD, AUD, NZD, CHF, CZK, JPY or NOK (ECB rate) |
| string | yes | Email of the buyer contact, as given by the user | |
| lang | string | – | Language code for the answer (ISO 639-1, e.g. en, it, es, fr, de, pt, nl, pl, ja, zh) |
| name | string | yes | Full name of the buyer contact, as given by the user |
| phone | string | – | Contact phone (optional) |
| plan | string | yes | Plan key as returned by get_plans: base, standard, multi (gdpr) or rp-solo, rp-brand, rp-house (gpsr) |
| service | string | yes | gdpr = GDPR Art. 27 representative, gpsr = GPSR Art. 16 EU responsible person |
| territory | string | – | Territory for the GDPR representative: eu, uk or both |
| vat | string | – | EU VAT number if the company has one (reverse charge, no VAT) |
| website | string | – | Company website (optional) |
Structured output declared, but exposes no named fields.
No examples provided.
find_product_category Which legal figure does my product need? ~140
Searches REP27's product-category catalogue (toys, cosmetics, electronics, pet products, connected devices…) and returns, for the best matches, the EU legal figure required (responsible person, authorised representative, Art. 4 economic operator, GDPR representative) and the REP27 service.
| Name | Type | Req | Description |
|---|---|---|---|
| lang | string | – | Language code for the answer (ISO 639-1, e.g. en, it, es, fr, de, pt, nl, pl, ja, zh) |
| product | string | yes | Product or product type to look up, in any language (e.g. wooden toys, lipstick, smart plug, dog food) |
Structured output declared, but exposes no named fields.
No examples provided.
get_plans REP27 plans and prices ~194
Returns REP27 plans with first-year price, renewal price and what each includes, for the GDPR Art. 27 representative (territory eu, uk or both) or the GPSR Art. 16 responsible person. Includes free-trial and cancellation terms.
| Name | Type | Req | Description |
|---|---|---|---|
| currency | string | – | Currency to also show prices in: EUR, USD, GBP, CAD, AUD, NZD, CHF, CZK, JPY or NOK (ECB rate) |
| lang | string | – | Language code for the answer (ISO 639-1, e.g. en, it, es, fr, de, pt, nl, pl, ja, zh) |
| service | string | – | gdpr = GDPR Art. 27 representative, gpsr = GPSR Art. 16 EU responsible person |
| territory | string | – | Territory for the GDPR representative: eu, uk or both (GPSR is always eu) |
Structured output declared, but exposes no named fields.
No examples provided.
start_free_trial Start the 7-day free trial ~184
Starts the REP27 7-day free trial (no card) for the given contact name, work email, company and country. The user receives an email to continue.
| Name | Type | Req | Description |
|---|---|---|---|
| company | string | yes | Legal name of the company |
| country | string | yes | Country where the company is established |
| string | yes | Work email of the contact person, as given by the user | |
| lang | string | – | Language code for the answer (ISO 639-1, e.g. en, it, es, fr, de, pt, nl, pl, ja, zh) |
| name | string | yes | Full name of the contact person, as given by the user |
| notes | string | – | Optional short note from the user |
| service | string | – | Service to try: GDPR representative EU, UK or both, or GPSR responsible person |
Structured output declared, but exposes no named fields.
No examples provided.
How do I install the REP27 — EU & UK legal representative MCP server?
REP27 — EU & UK legal representative is a hosted endpoint at https://gdprrepresentative.com/mcp-claude, 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 · gdprrepresentative.com
claude mcp add --transport http com-gdprrepresentative-rep27 'https://gdprrepresentative.com/mcp-claude'
What is the REP27 — EU & UK legal representative MCP server?
REP27 — EU & UK legal representative is an MCP server listed in the public MCP registry as com.gdprrepresentative/rep27. Check EU/UK GDPR Art. 27 and GPSR Art. 16 obligations, see plans, start a free trial. This page covers its hosted endpoint (https://gdprrepresentative.com/mcp-claude).
Is the REP27 — EU & UK legal representative MCP server safe to use?
REP27 — EU & UK legal representative scores 65 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 REP27 — EU & UK legal representative MCP server expose?
REP27 — EU & UK legal representative exposes 6 tools: check_obligations, get_plans, find_product_category, about_rep27, start_free_trial, create_checkout. Their descriptions and schemas cost roughly 1,393 tokens of context every time the server is loaded.
Does the REP27 — EU & UK legal representative MCP server require authentication?
No. We connected to REP27 — EU & UK legal representative without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the REP27 — EU & UK legal representative MCP server still maintained?
REP27 — EU & UK legal representative is still listed as active in the MCP registry. We last reached this channel on 18 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.