Consent Proof Record Lint runs on your own machine — the client starts it, so there is no endpoint to ping. 114 installs a week from npm. Last commit 2 Nov 2026.
Reads the consent record your code stored and names every proof field GDPR Article 7(1) needs and yo
Today is the operative word: we check Consent Proof Record Lint every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add consent-proof-record-lint -- npx -y @readystack/consent-proof-record-lint
{
"mcpServers": {
"consent-proof-record-lint": {
"command": "npx",
"args": [
"-y",
"@readystack/consent-proof-record-lint"
]
}
}
}
[mcp_servers.consent-proof-record-lint]
command = "npx"
args = ["-y", "@readystack/consent-proof-record-lint"]
{
"mcpServers": {
"consent-proof-record-lint": {
"command": "npx",
"args": [
"-y",
"@readystack/consent-proof-record-lint"
]
}
}
}
{
"servers": {
"consent-proof-record-lint": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@readystack/consent-proof-record-lint"
]
}
}
}
Reads your cloud contract text and names every clause Chapter VI no longer allows, with the article
Reads the licence field in the open manifest and names every deprecated SPDX id, invalid string, PEP
Names every image, font, badge and embed in your docs that sends an EU reader's IP outside the EEA
Finds the 12 author-side privacy duties your plugin PHP breaks, with the article and the fix on ever
Reads security headers and CSP line by line in your config file and names the lines that silently do
Your customers tell Deacon's chat what broke. Your coding agent reads it and fixes the code.
Reads your incident-response runbook and says which of the three Article 23 clocks it gets wrong
16 rules read your privacy.md the way Articles 13 and 14 read it
Answers built from our own checks of this server.