Comprehensive Model Context Protocol server for managing Home Assistant through AI assistants.
Nothing to run from here
Hermetics RGPD is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
8
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
EU data protection law for AI agents: GDPR, AI Act, EDPB, CJEU and national law, with status.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http hermetics-rgpd-mcp https://hermetics.fr/api/mcp
# 2 — ask your agent for something these tools do
# search_law, gdpr_obligations, save_processing_record and 5 more
Hermetics RGPD costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
HEAll 1 server
hermetics1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http hermetics-rgpd-mcp https://hermetics.fr/api/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
8 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Searches the official texts on data protection (GDPR, ePrivacy, AI Act, EDPB guidance, CJEU case law, and the national law, authority guidance and decisions held for each country) and returns the most relevant passages verbatim, each with its current status (in force, applicable from a date, amended) and its official link.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| question | string | yes | The legal question, in any language (French gives the best results today). Names and personal data are not needed. |
| country | string | no | ISO code of an EU or EEA country (e.g. FR, DE, ES) to add its national law and authority guidance to the EU texts; omit for EU texts only. |
Lists the GDPR obligations of a company established in an EU or EEA country from a few facts (size, website and cookies, e-mail marketing, sensitive data, video surveillance, AI...). Deterministic rules: each obligation comes with its legal basis and a suggested search_law query for the official text. A fact left out is treated as unknown, except processors, which are assumed.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| country | string | yes | Country where the company is established (ISO code of an EU or EEA country, e.g. FR, DE, ES, IT). |
| employees | integer | no | Number of employees (0 if none). |
| public_sector | boolean | no | True if the organisation is a public authority or public body. |
| website | boolean | no | True if the company has a website or app. |
| non_essential_cookies | boolean | no | True if the website or app uses non-essential cookies or trackers (analytics, advertising, social media pixels). |
| email_marketing | boolean | no | True if the company sends marketing e-mails or SMS to individuals. |
| processors | boolean | no | True if providers process personal data on its behalf (hosting, SaaS, payroll, CRM). Assumed true if omitted. |
| transfers_outside_eea | boolean | no | True if personal data is sent to providers or entities outside the EEA (e.g. US SaaS). |
| special_category_data | boolean | no | True if it processes special category data (health, biometrics, genetic data, religion, union membership, sex life or orientation, ethnic origin, political opinions). |
| large_scale | boolean | no | True if the processing concerns a large number of people (large scale). |
| systematic_monitoring | boolean | no | True if it systematically monitors people (online behaviour tracking, geolocation, profiling for advertising, CCTV of public areas). |
| evaluation_or_scoring | boolean | no | True if it evaluates or scores people (credit scoring, profiling, performance rating). |
| automated_decisions | boolean | no | True if it takes automated decisions with legal or similarly significant effects on people. |
| vulnerable_people | boolean | no | True if it processes data of vulnerable people (children, patients, elderly people). |
| cctv | boolean | no | True if it uses video surveillance (CCTV). |
| ai | boolean | no | True if it develops or uses AI systems that interact with or make decisions about people. |
Saves one entry of the record of processing activities (GDPR art. 30(1)) in the Hermetics account linked to the connection: new records get a code and every change is kept as a new version, in the account's own register on the Hermetics platform (the free account has no DPO: the user checks the records). When the account belongs to a Hermetics client organization, records go to that organization's
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | Short name of the processing activity (e.g. "Payroll", "Newsletter"). |
| purpose | string | yes | Purpose of the processing (art. 30(1)(b)). |
| legal_basis | string | yes | Legal basis under art. 6(1). |
| legal_basis_details | string | no | Details of the legal basis: the legal obligation, the contract, or the legitimate interest pursued. |
| data_subjects | array | yes | Categories of data subjects (art. 30(1)(c)), e.g. "employees", "customers". |
| data_categories | array | yes | Categories of personal data (art. 30(1)(c)), e.g. "identity", "bank details". |
| special_category_data | boolean | no | True if special category data (art. 9) are processed. |
| art9_exception | string | no | The art. 9(2) exception relied on, if special category data are processed. |
| recipients | array | yes | Categories of recipients, internal and external (art. 30(1)(d)). |
| processors | array | no | Processors acting on behalf of the company (art. 28). |
| transfers_outside_eea | object | no | Transfers to third countries (art. 30(1)(e)); omit if none. |
| retention | string | yes | Retention period or the criteria used to determine it (art. 30(1)(f)). |
| security_measures | array | no | General description of technical and organisational security measures (art. 30(1)(g)). |
| record_id | string | no | Code of an existing record (e.g. RT-001, or AT-001 in an organization register) to save a new version of it; omit to create a new record. |
Lists the records of processing activities (GDPR art. 30(1)) saved in the Hermetics account linked to the connection, in their latest version, with their full content. For an account of a Hermetics client organization, lists the organization's whole register on the Hermetics platform, whatever the origin of each record, with its status.
No parameter schema on file.
Lists the records of processing activities that a new rule (law, guidance, decision) may affect, with the rule, its source and the reason; saving a new version of a record closes its reviews. Reviews are part of the paid plans.
No parameter schema on file.
Paid plans. Prepares, in the Hermetics space of the organization, the analysis of a record of the register with the same engines as the Hermetics platform: legal basis, DPIA, legitimate interests assessment, transfer impact assessment, information notice (art. 13 and 14), the privacy policy of the whole register, or the art. 28 review of a processor agreement received by the company (Hermetics nev
| Parameter | Type | Required | Notes |
|---|---|---|---|
| record_id | string | no | Code of the record in the register (e.g. AT-001); required for every type except privacy_policy. |
| type | string | yes | legal_basis (art. 6), dpia (art. 35), lia (legitimate interests assessment), tia (transfer impact assessment, art. 44 to 49), information_notice (art. 13 and 14), privacy_policy (the whole register), |
| notes | string | no | Facts or context from the user for the preparation; no personal data needed. |
| processor_name | string | no | Name of the processor whose agreement is reviewed (processor_agreement_review only). |
| agreement_text | string | no | Full text of the processor agreement received by the company (processor_agreement_review only). |
Paid plans. Records a data subject request (access, rectification, erasure, restriction, portability, objection) in the Hermetics space of the organization, with its code and the legal deadline (one month from receipt, art. 12(3), extendable). Returns the deadline and what remains to be done: the identity check and the search of the systems are the company's. Nothing is sent to the requester. Prep
| Parameter | Type | Required | Notes |
|---|---|---|---|
| right | string | yes | The right exercised (GDPR art. 15 to 21). |
| received_on | string | yes | Date the company received the request (YYYY-MM-DD): the one-month period runs from it. |
| requester_description | string | yes | Who made the request and what was asked (e.g. "a former customer asking for a copy of their order history"); no sensitive data beyond what the request needs. |
| channel | string | no | How the request arrived (e-mail, letter, phone, in person...). |
| notes | string | no | Other context for the handling of the request. |
Paid plans. Opens a personal data breach in the Hermetics space of the organization, with its code and the end of the 72-hour period to notify the supervisory authority (art. 33(1)), counted from when the company became aware of it. Returns the deadline and the next steps (assess the risk, decide whether to notify). The designated DPO, when there is one, is alerted; nothing is notified to the auth
| Parameter | Type | Required | Notes |
|---|---|---|---|
| discovered_at | string | yes | When the company became aware of the breach (ISO 8601 date and time with time zone): the 72-hour period runs from it. |
| description | string | yes | What happened, the systems involved and the measures already taken; no personal data needed. |
| data_categories | array | no | Categories of personal data concerned, e.g. "identity", "bank details". |
| people_count_estimate | integer | no | Approximate number of people concerned. |
| ongoing | boolean | no | True if the breach is still ongoing. |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Hermetics RGPD or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
—Grade not published
No rule-by-rule report on file for this release
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 0.4.0.
0.4.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Hermetics RGPD can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.