Consent Proof Record Lint
io.github.jmshinhwaPublished by GitHub account jmshinhwav1.0.1Updated Oct 24, 2026
Reads the consent record your code stored and names every proof field GDPR Article 7(1) needs and yo
The publisher's own server: Proof Holdings
Overview
Local stdio MCP server that reads a stored consent record and names the proof fields GDPR Article 7(1) requires and what is missing.
- What you can do
- Read a stored consent record and check it against GDPR Article 7(1) proof requirements.
- Name each proof field the regulation expects and point out which ones the record lacks.
- No tool list is published, so the exact operations are not documented; the description only covers this consent-record linting.
- When to use it
- Useful when you keep consent records for a product and want an assistant to check whether they contain the evidence GDPR Article 7(1) requires before an audit or review.
- Requirements
- Runs as a local process over stdio, started with npx from the npm package @readystack/consent-proof-record-lint, so Node.js and network access for the package download are needed. No authentication, environment variables or headers are declared. Desktop only.
Installation
In SourceWeft
- Open Consent Proof Record Lint in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
readystack-themes
Made by ReadyStack · free calculators and templates at getreadystack.com VS Code themes by ReadyStack
Source: README.md at commit ee1c884
Tools
0Version history
1- v1.0.1LatestSep 19, 2026
Score
40% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts
Declare a license in the repository or the registry entry.
Other Proof integrations
Proof Holdings
holdings.proofOfficial publisher
Proof Holdings MCP server lets an assistant run identity and control verifications (phone, email, domain, wallet), manage proof tokens and delegations, and…
Proof of Work
Published by GitHub account kivtxs
Lets an assistant read the rules of Proof of Work, check for a local account, and create an agent account to post, vote and back claims.
QuietProof
Published by GitHub account frankjie3-create
QuietProof offers free discovery tools for a catalog of deterministic, read-only audits that are paid per call in USDC on Base via x402.
SCRIPTMASTERLABS — 402Proof
com.scriptmasterlabs
Remote MCP endpoint for creating, verifying and scoring invoices settled with RLUSD on the XRPL ledger, with self-proof of settlements.
ZKStamp Proof-100
Published by GitHub account ZKStamp
Remote MCP server that writes SHA-256 fingerprints to the BitcoinZ blockchain as shielded, dated proof-of-existence timestamps.