# Double AIgents DSAR service (remote · www.doubleaigents.com)

GDPR DSAR deadlines, breach triage, AI tool checks, HR retention and letters (UK/EU/CH)

- Trust score: 79/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `www.doubleaigents.com`: 79/100 (this document), [markdown](https://verifymcp.io/servers/com-doubleaigents-www-dsar/api-mcp.md), [page](https://verifymcp.io/servers/com-doubleaigents-www-dsar/api-mcp)

## Channel facts

- Endpoint: `https://www.doubleaigents.com/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.2.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 60/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1708 tokens (~170/item across 10 items; 10 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 60/100
  - Stability observed for 18 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 93/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 80% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the Double AIgents DSAR service MCP server?

Double AIgents DSAR service is a hosted endpoint at https://www.doubleaigents.com/api/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.

### Claude

```bash
claude mcp add --transport http com-doubleaigents-www-dsar 'https://www.doubleaigents.com/api/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-doubleaigents-www-dsar": {
      "url": "https://www.doubleaigents.com/api/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-doubleaigents-www-dsar": {
      "type": "http",
      "url": "https://www.doubleaigents.com/api/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-doubleaigents-www-dsar]
url = "https://www.doubleaigents.com/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-doubleaigents-www-dsar": {
      "type": "remote",
      "url": "https://www.doubleaigents.com/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-doubleaigents-www-dsar --url 'https://www.doubleaigents.com/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-doubleaigents-www-dsar:
    url: "https://www.doubleaigents.com/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-doubleaigents-www-dsar": {
      "Transport": "http",
      "Url": "https://www.doubleaigents.com/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-doubleaigents-www-dsar -t streamable-http -u 'https://www.doubleaigents.com/api/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-doubleaigents-www-dsar": {
      "type": "http",
      "url": "https://www.doubleaigents.com/api/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 79, +1)

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

### 2026-11-03 (score 78, +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.

### 2026-11-01 (score 77, +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.

### 2026-10-30 (score 76, +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.

### 2026-10-28 (score 75, +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.

### 2026-10-26 (score 74, +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.

### 2026-10-23 (score 73, +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.

### 2026-10-21 (score 72, +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.

## MCP tools (10)

### `dsar_deadline` (~119 tokens)

DSAR response deadline

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.

Input parameters:

- `extended` (boolean): Also calculate the extended deadline where an extension is available.
- `jurisdiction` (string, required): UK, EU (EU/EEA GDPR) or CH (Switzerland).
- `received_date` (string, required): ISO date the clock starts. For the UK, the later of receipt and receipt of any requested ID or fee.

### `dsar_quote` (~87 tokens)

DSAR fixed-price quote

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.

Input parameters:

- `currency` (string): GBP (UK), EUR (EU/EEA) or CHF (Switzerland).
- `pages` (integer, required): Number of pages after de-duplication.

### `dsar_service_info` (~53 tokens)

DSAR service information

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.

### `dsar_request_scoping` (~149 tokens)

Start DSAR scoping

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.

Input parameters:

- `approx_volume` (string): Optional rough volume, for example "two mailboxes, about 3 years".
- `contact_email` (string, required): Email of that person.
- `contact_name` (string, required): Name of the person at the organisation handling the request (not the requester).
- `date_received` (string, required): ISO date the request was received.
- `jurisdiction` (string, required)
- `organisation` (string, required): The controller organisation that received the request.

### `breach_clock` (~163 tokens)

Personal data breach notification clock

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.

Input parameters:

- `aware_at` (string, required): ISO date and time, with time zone, when the controller became aware of the breach. Example: 2026-10-17T09:30:00+01:00.
- `jurisdiction` (string, required): UK, EU (EU/EEA GDPR) or CH (Switzerland).

### `dsar_letter_template` (~152 tokens)

DSAR letter template

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.

Input parameters:

- `due_date` (string): Optional ISO due date, used in place of the calculated one.
- `jurisdiction` (string, required): UK, EU (EU/EEA GDPR) or CH (Switzerland).
- `kind` (string, required)
- `received_date` (string): Optional ISO date the clock started. For the UK, the later of receipt and receipt of any requested ID or fee.

### `breach_triage` (~290 tokens)

Personal data breach triage

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 pass names or other personal data.

Input parameters:

- `aware_at` (string, required): ISO date and time, with time zone, when the controller became aware of the breach. Example: 2026-10-17T09:30:00+01:00.
- `encrypted` (boolean, required): True if the data was strongly encrypted and the key was not compromised.
- `jurisdiction` (string, required): UK, EU (EU/EEA GDPR) or CH (Switzerland).
- `people_affected` (required): Approximate number of people affected, or "unknown".
- `recipient` (string, required): 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, required): Whether the data has been recovered or deletion confirmed, is likely to be, or not.
- `special_category` (boolean, required): True if special category or criminal offence data is involved (health, biometric, criminal records, etc.).

### `ai_tool_check` (~289 tokens)

AI tool check: DPIA and EU AI Act screening

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, UK GDPR Arts 22A to 22D). Findings with sources. The use_case text is not stored or returned. General information, not legal advice.

Input parameters:

- `automated_decisions_with_significant_effect` (boolean, required): True if it makes or drives decisions with legal or similarly significant effects without meaningful human involvement.
- `employees_or_candidates` (boolean, required): True if it processes data about staff or job candidates.
- `jurisdiction` (string, required): UK, EU (EU/EEA) or CH (Switzerland).
- `large_scale` (boolean, required)
- `new_technology` (boolean, required): True if it is an innovative use or new technology for the organisation.
- `processes_personal_data` (boolean, required)
- `special_category` (boolean, required): Health, biometric, criminal offence data and the like.
- `use_case` (string, required): Short description of what the AI tool does. No personal data. Not stored.

### `hr_retention` (~86 tokens)

HR record retention periods (UK)

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.

Input parameters:

- `jurisdiction` (string)
- `record_type` (string, required)

### `dsar_search_checklist` (~115 tokens)

DSAR search checklist

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 proportionate searches). General information, not legal advice.

Input parameters:

- `organisation_type` (string, required)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-doubleaigents-www-dsar/api-mcp#diagnostics

## Score history

- 2026-11-05: 79
- 2026-11-04: 78
- 2026-11-03: 78
- 2026-11-02: 77
- 2026-11-01: 77
- 2026-10-31: 76
- 2026-10-30: 76
- 2026-10-29: 75
- 2026-10-28: 75
- 2026-10-27: 74
- 2026-10-26: 74
- 2026-10-25: 73
- 2026-10-24: 73
- 2026-10-23: 73
- 2026-10-22: 72
- 2026-10-21: 72
- 2026-10-20: 71
- 2026-10-19: 71
- 2026-10-18: 70

## Common questions

### What is the Double AIgents DSAR service MCP server?

Double AIgents DSAR service is an MCP server listed in the public MCP registry as com.doubleaigents.www/dsar. GDPR DSAR deadlines, breach triage, AI tool checks, HR retention and letters (UK/EU/CH). This page covers its hosted endpoint (https://www.doubleaigents.com/api/mcp).

### Is the Double AIgents DSAR service MCP server safe to use?

Double AIgents DSAR service scores 79 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 Double AIgents DSAR service MCP server expose?

Double AIgents DSAR service exposes 10 tools: dsar_deadline, dsar_quote, dsar_service_info, dsar_request_scoping, breach_clock, and 5 more. Their descriptions and schemas cost roughly 1,503 tokens of context every time the server is loaded.

### Does the Double AIgents DSAR service MCP server require authentication?

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

### Is the Double AIgents DSAR service MCP server still maintained?

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

## Links

- Remote endpoint: https://www.doubleaigents.com/api/mcp
- Repository: https://github.com/JimmyBoy-Git/doubleaigents-dsar-mcp
- Website: https://www.doubleaigents.com/#sar
- Changelog RSS feed: https://verifymcp.io/servers/com-doubleaigents-www-dsar/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-doubleaigents-www-dsar/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-doubleaigents-www-dsar/api-mcp