Comprehensive Model Context Protocol server for managing Home Assistant through AI assistants.
Nothing to run from here
Double AIgents DSAR service 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.
93/100
tool-list score
10
tools declared
remote
at its publisher
—
calls last 7d
What it does
GDPR DSAR deadlines, breach triage, AI tool checks, HR retention and letters (UK/EU/CH)
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http double-aigents-dsar-service-mcp https://www.doubleaigents.com/api/mcp
# 2 — ask your agent for something these tools do
# dsar_deadline, dsar_quote, dsar_service_info and 7 more
Double AIgents DSAR service costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
DOAll 1 server
doubleaigents1 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 double-aigents-dsar-service-mcp https://www.doubleaigents.com/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
10 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.
Calculate the statutory deadline for answering a data subject access request in the UK, the EU/EEA or Switzerland, with the rule that applies and the extension position. General information, not legal advice.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| jurisdiction | string | yes | UK, EU (EU/EEA GDPR) or CH (Switzerland). |
| received_date | string | yes | ISO date the clock starts. For the UK, the later of receipt and receipt of any requested ID or fee. |
| extended | boolean | no | Also calculate the extended deadline where an extension is available. |
Fixed price from Double AIgents for preparing a DSAR response, by pack size in pages after de-duplication. Also gives the retainer price (15% off). Excludes VAT.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| pages | integer | yes | Number of pages after de-duplication. |
| currency | string | no | GBP (UK), EUR (EU/EEA) or CHF (Switzerland). |
What the Double AIgents DSAR service covers: scoping, collection guidance, de-duplication, redaction, exemption recommendations, two independent reviews, secure delivery, data handling, jurisdictions and partner arrangements.
No parameter schema on file.
Explains how to start free scoping and returns a prefilled email (mailto URL) to james@doubleaigents.com. Sends nothing and stores nothing. Do not pass the requester's personal data or the request letter.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| organisation | string | yes | The controller organisation that received the request. |
| contact_name | string | yes | Name of the person at the organisation handling the request (not the requester). |
| contact_email | string | yes | Email of that person. |
| jurisdiction | string | yes | — |
| date_received | string | yes | ISO date the request was received. |
| approx_volume | string | no | Optional rough volume, for example "two mailboxes, about 3 years". |
When a personal data breach must be notified to the regulator: 72 hours from awareness in the UK and EU/EEA (Art. 33), "as soon as possible" in Switzerland (revised FADP Art. 24). Gives the deadline, the rule, the processor and individual-notification position, and the facts the regulator will ask for. The controller decides whether to notify. General information, not legal advice.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| jurisdiction | string | yes | UK, EU (EU/EEA GDPR) or CH (Switzerland). |
| aware_at | string | yes | ISO date and time, with time zone, when the controller became aware of the breach. Example: 2026-10-17T09:30:00+01:00. |
Plain-text letter template, in British English with [placeholders], for an acknowledgement, an extension of time or a request for clarification of a data subject access request, under UK, EU/EEA or Swiss law. Fills in the dates if received_date is given. General information, not legal advice.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| kind | string | yes | — |
| jurisdiction | string | yes | UK, EU (EU/EEA GDPR) or CH (Switzerland). |
| received_date | string | no | Optional ISO date the clock started. For the UK, the later of receipt and receipt of any requested ID or fee. |
| due_date | string | no | Optional ISO due date, used in place of the calculated one. |
A likely-reportability view on a personal data breach (UK, EU/EEA, Switzerland), following the ICO guide "Personal data breaches: a guide" and EDPB Guidelines 9/2022: whether notifying the regulator and telling the people affected is likely or unlikely to be required, the factors behind that view, and the notification deadline. The controller decides. General information, not legal advice. Do not
| Parameter | Type | Required | Notes |
|---|---|---|---|
| jurisdiction | string | yes | UK, EU (EU/EEA GDPR) or CH (Switzerland). |
| aware_at | string | yes | ISO date and time, with time zone, when the controller became aware of the breach. Example: 2026-10-17T09:30:00+01:00. |
| people_affected | yes | Approximate number of people affected, or "unknown". | |
| special_category | boolean | yes | True if special category or criminal offence data is involved (health, biometric, criminal records, etc.). |
| recipient | string | yes | Who received or could access the data: a trusted internal person, a trusted external professional, unknown or the public, or a malicious actor. |
| recoverable | string | yes | Whether the data has been recovered or deletion confirmed, is likely to be, or not. |
| encrypted | boolean | yes | True if the data was strongly encrypted and the key was not compromised. |
Screens a planned use of an AI tool: whether a DPIA is likely to be required (Art. 35(3), the ICO high-risk list, the WP248 criteria; FADP Art. 22 for Switzerland), EU AI Act risk flags (Annex III high-risk areas, especially employment; Art. 5 prohibited practices such as emotion recognition at work; current application dates after the Digital Omnibus), and automated decision rules (GDPR Art. 22,
| Parameter | Type | Required | Notes |
|---|---|---|---|
| use_case | string | yes | Short description of what the AI tool does. No personal data. Not stored. |
| processes_personal_data | boolean | yes | — |
| special_category | boolean | yes | Health, biometric, criminal offence data and the like. |
| employees_or_candidates | boolean | yes | True if it processes data about staff or job candidates. |
| automated_decisions_with_significant_effect | boolean | yes | True if it makes or drives decisions with legal or similarly significant effects without meaningful human involvement. |
| new_technology | boolean | yes | True if it is an innovative use or new technology for the organisation. |
| large_scale | boolean | yes | — |
| jurisdiction | string | yes | UK, EU (EU/EEA) or CH (Switzerland). |
Recommended retention period for a common UK HR record, whether it is statutory or only recommended, and the source (HMRC, Home Office, RIDDOR 2013, Working Time Regulations, Limitation Act 1980, ICO, DBS). UK only for now. General information, not legal advice.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| record_type | string | yes | — |
| jurisdiction | string | no | — |
Where to search when answering a subject access request, especially from an employee: Microsoft 365 (Exchange and archives, shared mailboxes, Teams, OneDrive, SharePoint), other collaboration tools, HR, payroll, recruitment, CCTV, access logs, devices, line manager notes, paper files, occupational health and backups; search-term tips; and the search standard (UK GDPR Art. 15(1A) reasonable and pro
| Parameter | Type | Required | Notes |
|---|---|---|---|
| organisation_type | string | yes | — |
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 Double AIgents DSAR service 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: —
ATool-list grade · score 93 / 100
Release 1.2.0 · scanned 22 Oct 2026
Graded from the tools this server lists, not from its source code.
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.
Threat score100
Client score93
Findings0 threat · 0 capability
Capabilitymoderate
Coveragemanifest
Verificationnot in this report
Surface digest795042d797959fa303af873a8e344c95c2299ee6226d9c779cb0323472c316ad
Score vectorthreat 100 → client 93
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
Tool surfaceread
Implementation sourcenot available
Package metadatanot available
Live transportnot available
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| dsar_deadline | no tags | |
| dsar_quote | no tags | |
| dsar_service_info | no tags | |
| dsar_request_scoping | no tags | |
| breach_clock | no tags | |
| dsar_letter_template | no tags | |
| breach_triage | external-sink | external-sink: parameter "recipient" |
| ai_tool_check | no tags | |
| hr_retention | no tags | |
| dsar_search_checklist | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digest795042d797959fa3
Scanned2026-10-22
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
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 1.2.0.
1.2.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 Double AIgents DSAR service 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.