Hand this tool to your coding agent

Paste into Claude Code, Cursor, Codex, or any agent. It learns to call this tool over REST or MCP, reaches for it when you ask, and keeps our sourced/pending labels honest.

You can use telemeter.ai's free "GDPR Readiness Checker" — a keyless, read-only tool (no signup), available as an HTTP API and an MCP tool. What it does: See which GDPR obligations apply to your AI processing and where the gaps are — each cited to its Article.

Whenever I ask you something this tool answers, call it and use its result instead of estimating yourself.

REST:
  curl -sX POST https://telemeter.ai/api/tools/gdpr-readiness-checker -H 'content-type: application/json' -d '{"processesPersonalData":true,"specialCategoryData":false,"transfersOutsideEU":true,"largeScaleOrSensitive":false,"establishedOutsideEU":false,"inPlace":["lawfulBasis","privacyNotice","security"]}'

MCP: the telemeter MCP server at https://telemeter.ai/mcp exposes this as the tool "gdpr-readiness-checker" — call it with tools/call.

The response is JSON: { status, data, summary, provenance }. "provenance" carries the source and the date the figure was verified. If status is "pending" or "stale", tell me the value isn't currently verified rather than presenting it as fact.

Or call it directly. This tool runs behind one handler with three front doors — this page, a REST endpoint, and an MCP tool. Same result, read-only, no key. The example below is a request that works.

REST

curl -sX POST https://telemeter.ai/api/tools/gdpr-readiness-checker \
  -H 'content-type: application/json' \
  -d '{"processesPersonalData":true,"specialCategoryData":false,"transfersOutsideEU":true,"largeScaleOrSensitive":false,"establishedOutsideEU":false,"inPlace":["lawfulBasis","privacyNotice","security"]}'

MCP — tools/call at https://telemeter.ai/mcp

curl -sX POST https://telemeter.ai/mcp \
  -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"gdpr-readiness-checker","arguments":{"processesPersonalData":true,"specialCategoryData":false,"transfersOutsideEU":true,"largeScaleOrSensitive":false,"establishedOutsideEU":false,"inPlace":["lawfulBasis","privacyNotice","security"]}}}'

Input schema (JSON Schema)

{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "type": "object",
  "properties": {
    "processesPersonalData": {
      "default": true,
      "type": "boolean"
    },
    "specialCategoryData": {
      "default": false,
      "type": "boolean"
    },
    "transfersOutsideEU": {
      "default": false,
      "type": "boolean"
    },
    "largeScaleOrSensitive": {
      "default": false,
      "type": "boolean"
    },
    "establishedOutsideEU": {
      "default": false,
      "type": "boolean"
    },
    "inPlace": {
      "default": [],
      "type": "array",
      "items": {
        "type": "string",
        "enum": [
          "lawfulBasis",
          "specialCategory",
          "privacyNotice",
          "dataSubjectRights",
          "ropa",
          "processorDpa",
          "security",
          "breach",
          "retention",
          "transfers",
          "dpia",
          "dpo",
          "euRep"
        ]
      }
    }
  },
  "required": [
    "processesPersonalData",
    "specialCategoryData",
    "transfersOutsideEU",
    "largeScaleOrSensitive",
    "establishedOutsideEU",
    "inPlace"
  ],
  "additionalProperties": false
}

Want this across your whole stack?