Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.CloudCorpRecords/dsarguide

OCI · GHCR.IO/CLOUDCORPRECORDS/DSARGUIDE · 2 COMPONENTS

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

41 Trust /100

Last scanned (13 hours ago)

Scores higher than 37% of OCI servers

Category Security

Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Supply Chain Security0
  • 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.Unverified
  • Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
  • Install-script risk not yet assessed.Unverified
  • Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
Provenance & Transparency45
Schema Quality & AI Usability65
  • AI-judged instruction clarity (good).Pass
  • 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. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management17
  • Stability observed for 5 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
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 10 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

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.

What we tested

Checks we ran (12)

  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (4)

These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Malware scan in Supply Chain Security (scores 0 for this)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 in Supply Chain Security (scores 0 for this)Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.
  • Install scripts in Supply Chain Security (scores 0 for this)Install-script risk not yet assessed.
  • Dependency health in Supply Chain Security (scores 0 for this)Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 20 Nov 26 +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.

  • 18 Nov 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 Nov 26 39

    First indexed and scored.

Diagnostics

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 21 Nov 2026 · Analysed oci/ghcr.io/cloudcorprecords/dsarguide@0.1.0

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem oci
Reason No attestation published

Background: How many MCP packages publish verified provenance →

MCP tools · 10 exposed · ~1,567 tokens

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 →

Tool Tokens
ai_tool_check ~303

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.

NameTypeReqDescription
automated_decisions_with_significant_effectbooleanyesTrue if it makes or drives decisions with legal or similarly significant effects without meaningful human involvement.
employees_or_candidatesbooleanyesTrue if it processes data about staff or job candidates.
jurisdictionstringyesUK, EU (EU/EEA) or CH (Switzerland).
large_scalebooleanyesWhether the processing is large scale
new_technologybooleanyesTrue if it is an innovative use or new technology for the organisation.
processes_personal_databooleanyesWhether the planned AI tool processes personal data
special_categorybooleanyesHealth, biometric, criminal offence data and the like.
use_casestringyesShort description of what the AI tool does. No personal data. Not stored.

No output schema declared.

No examples provided.

breach_clock ~163

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.

NameTypeReqDescription
aware_atstringyesISO date and time, with time zone, when the controller became aware of the breach. Example: 2026-10-17T09:30:00+01:00.
jurisdictionstringyesUK, EU (EU/EEA GDPR) or CH (Switzerland).

No output schema declared.

No examples provided.

breach_triage ~290

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.

NameTypeReqDescription
aware_atstringyesISO date and time, with time zone, when the controller became aware of the breach. Example: 2026-10-17T09:30:00+01:00.
encryptedbooleanyesTrue if the data was strongly encrypted and the key was not compromised.
jurisdictionstringyesUK, EU (EU/EEA GDPR) or CH (Switzerland).
people_affected–yesApproximate number of people affected, or "unknown".
recipientstringyesWho received or could access the data: a trusted internal person, a trusted external professional, unknown or the public, or a malicious actor.
recoverablestringyesWhether the data has been recovered or deletion confirmed, is likely to be, or not.
special_categorybooleanyesTrue if special category or criminal offence data is involved (health, biometric, criminal records, etc.).

No output schema declared.

No examples provided.

dsar_deadline ~119

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.

NameTypeReqDescription
extendedboolean–Also calculate the extended deadline where an extension is available.
jurisdictionstringyesUK, EU (EU/EEA GDPR) or CH (Switzerland).
received_datestringyesISO date the clock starts. For the UK, the later of receipt and receipt of any requested ID or fee.

No output schema declared.

No examples provided.

dsar_letter_template ~163

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.

NameTypeReqDescription
due_datestring–Optional ISO due date, used in place of the calculated one.
jurisdictionstringyesUK, EU (EU/EEA GDPR) or CH (Switzerland).
kindstringyesKind of letter template: acknowledgement, extension, or clarification
received_datestring–Optional ISO date the clock started. For the UK, the later of receipt and receipt of any requested ID or fee.

No output schema declared.

No examples provided.

dsar_quote ~87

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.

NameTypeReqDescription
currencystring–GBP (UK), EUR (EU/EEA) or CHF (Switzerland).
pagesintegeryesNumber of pages after de-duplication.

No output schema declared.

No examples provided.

dsar_request_scoping ~163

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.

NameTypeReqDescription
approx_volumestring–Optional rough volume, for example "two mailboxes, about 3 years".
contact_emailstringyesEmail of that person.
contact_namestringyesName of the person at the organisation handling the request (not the requester).
date_receivedstringyesISO date the request was received.
jurisdictionstringyesJurisdiction for the scoping guidance: UK, EU, or CH
organisationstringyesThe controller organisation that received the request.

No output schema declared.

No examples provided.

dsar_search_checklist ~123

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.

NameTypeReqDescription
organisation_typestringyesType of organisation the search checklist is for

No output schema declared.

No examples provided.

dsar_service_info ~53

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

hr_retention ~103

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.

NameTypeReqDescription
jurisdictionstring–Jurisdiction for the retention guidance
record_typestringyesType of HR record to look up the retention period for

No output schema declared.

No examples provided.

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.

oci · ghcr.io/cloudcorprecords/dsarguide

# add to Claude Code
claude mcp add cloudcorprecords-dsarguide -- docker run --rm -i ghcr.io/cloudcorprecords/dsarguide:0.1.0 mcp
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.