# io.github.CloudCorpRecords/dsarguide (oci · ghcr.io/cloudcorprecords/dsarguide)

DSAR deadlines, breach clocks and triage, AI-tool checks, HR retention and letter templates.

- Trust score: 41/100 (low)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- npm · `@reneturcios/dsarguide`: 70/100, [markdown](https://verifymcp.io/servers/cloudcorprecords-dsarguide/reneturcios-dsarguide.md), [page](https://verifymcp.io/servers/cloudcorprecords-dsarguide/reneturcios-dsarguide)
- oci · `ghcr.io/cloudcorprecords/dsarguide`: 41/100 (this document), [markdown](https://verifymcp.io/servers/cloudcorprecords-dsarguide/ghcr-io-cloudcorprecords-dsarguide.md), [page](https://verifymcp.io/servers/cloudcorprecords-dsarguide/ghcr-io-cloudcorprecords-dsarguide)

## Channel facts

- Registry: `oci`
- Package: `ghcr.io/cloudcorprecords/dsarguide`
- Version: `0.1.0`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, 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-21.

- **Supply Chain Security**: 0/100
  - No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.
  - Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.
  - Install-script risk not yet assessed.
  - Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 5 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 65/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1567 tokens (~156/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**: 17/100
  - Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% 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 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

**Unverified: 1 category.** A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

## Install

### How do I install the io.github.CloudCorpRecords/dsarguide MCP server?

io.github.CloudCorpRecords/dsarguide runs locally as a container image, launched with docker run --rm -i ghcr.io/cloudcorprecords/dsarguide:0.1.0 mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add cloudcorprecords-dsarguide -- docker run --rm -i ghcr.io/cloudcorprecords/dsarguide:0.1.0 mcp
```

### Cursor

```json
{
  "mcpServers": {
    "cloudcorprecords-dsarguide": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/cloudcorprecords/dsarguide:0.1.0",
        "mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "cloudcorprecords-dsarguide": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/cloudcorprecords/dsarguide:0.1.0",
        "mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add cloudcorprecords-dsarguide -- docker run --rm -i ghcr.io/cloudcorprecords/dsarguide:0.1.0 mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "cloudcorprecords-dsarguide": {
      "type": "local",
      "command": [
        "docker",
        "run",
        "--rm",
        "-i",
        "ghcr.io/cloudcorprecords/dsarguide:0.1.0",
        "mcp"
      ],
      "enabled": true
    }
  }
}
```

### Hermes

```yaml
mcp_servers:
  cloudcorprecords-dsarguide:
    command: "docker"
    args: ["run", "--rm", "-i", "ghcr.io/cloudcorprecords/dsarguide:0.1.0", "mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "cloudcorprecords-dsarguide": {
      "Transport": "stdio",
      "Command": "docker",
      "Arguments": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/cloudcorprecords/dsarguide:0.1.0",
        "mcp"
      ]
    }
  }
}
```

### Other

```json
{
  "mcpServers": {
    "cloudcorprecords-dsarguide": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/cloudcorprecords/dsarguide:0.1.0",
        "mcp"
      ]
    }
  }
}
```

## 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-20 (score 41, +1)

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

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

### 2026-11-16 (score 39)

First indexed and scored.

## 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` (~163 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): Jurisdiction for the scoping guidance: UK, EU, or CH
- `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` (~163 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): Kind of letter template: acknowledgement, extension, or clarification
- `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` (~303 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): Whether the processing is large scale
- `new_technology` (boolean, required): True if it is an innovative use or new technology for the organisation.
- `processes_personal_data` (boolean, required): Whether the planned AI tool processes personal data
- `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` (~103 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): Jurisdiction for the retention guidance
- `record_type` (string, required): Type of HR record to look up the retention period for

### `dsar_search_checklist` (~123 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): Type of organisation the search checklist is for

## Diagnostics

Captured diagnostic sections: Provenance. The full working is on the page: https://verifymcp.io/servers/cloudcorprecords-dsarguide/ghcr-io-cloudcorprecords-dsarguide#diagnostics

## Score history

- 2026-11-21: 41
- 2026-11-20: 41
- 2026-11-19: 40
- 2026-11-18: 40
- 2026-11-17: 39
- 2026-11-16: 39

## Common questions

### What is the io.github.CloudCorpRecords/dsarguide MCP server?

io.github.CloudCorpRecords/dsarguide is an MCP server listed in the public MCP registry as io.github.CloudCorpRecords/dsarguide. DSAR deadlines, breach clocks and triage, AI-tool checks, HR retention and letter templates. This page covers its container image (ghcr.io/cloudcorprecords/dsarguide).

### Is the io.github.CloudCorpRecords/dsarguide MCP server safe to use?

io.github.CloudCorpRecords/dsarguide scores 41 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 io.github.CloudCorpRecords/dsarguide MCP server expose?

io.github.CloudCorpRecords/dsarguide 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,567 tokens of context every time the server is loaded.

### Is the io.github.CloudCorpRecords/dsarguide MCP server still maintained?

io.github.CloudCorpRecords/dsarguide 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 licence is the io.github.CloudCorpRecords/dsarguide MCP server under?

io.github.CloudCorpRecords/dsarguide declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

### What did VerifyMCP test on the io.github.CloudCorpRecords/dsarguide MCP server?

VerifyMCP ran 12 checks on io.github.CloudCorpRecords/dsarguide, covering Source repository, Provenance, License, Maintenance and 8 more. 4 items could not be completed, a gap on our side rather than a finding about io.github.CloudCorpRecords/dsarguide: Malware scan, Known CVEs, Install scripts and Dependency health. One category scores 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to a container image, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- GitHub Container Registry: https://ghcr.io/cloudcorprecords/dsarguide
- Repository: https://github.com/CloudCorpRecords/dsarguide
- Changelog RSS feed: https://verifymcp.io/servers/cloudcorprecords-dsarguide/ghcr-io-cloudcorprecords-dsarguide.xml
- Changelog JSON feed: https://verifymcp.io/servers/cloudcorprecords-dsarguide/ghcr-io-cloudcorprecords-dsarguide/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/cloudcorprecords-dsarguide/ghcr-io-cloudcorprecords-dsarguide.json
- HTML version of this page: https://verifymcp.io/servers/cloudcorprecords-dsarguide/ghcr-io-cloudcorprecords-dsarguide
