ComplianceSME
Two filters on one standard. Between them they cover what gets built with AI: the software, and the words.
Software built with AI needs two things before it ships: the law it must meet, and the standard of work a customer can trust. This checks both in one run.
The compliance half checks a site or a build against the duties in the ComplianceSME register, the privacy notice, trackers before consent, accessibility, trader information, AI disclosure, the vulnerability route, and cites every failure to the article in the instrument's own words, naming the system that closes the gap.
The standard half applies the ComplianceSME Anti-Slop Doctrine to everything the build says: interface copy, documentation, generated content, error messages, the words a customer reads. Machine fingerprints found and named, line by line. High standards are how work gets simpler, faster and trusted, and this holds the build to them on every run.
Connect it as a Claude connector at this address, add it to a build as a Netlify plugin, or run it from the command line. The cited report needs a ComplianceSME account.
Address on this site: /developer/mcp
The same standard, turned on what you publish. It reads a draft or a page you have already put out, names every machine fingerprint in it line by line, and holds the claims to the doctrine's floor: state only what your material supports, promise only what you control, match a claim's confidence to its evidence.
The compliance half checks a published page, and a draft, against the duties the ComplianceSME register holds for what a page says, what it claims and what it collects: the transparency and reach of your privacy information under the GDPR, consent before trackers under the ePrivacy Directive and PECR, the trader information a buyer is owed, the total price up front, the reviews you publish, and the information and the way out of a subscription under the DMCC Act, environmental claims under the Green Transition Directive, and consent and a route to stop before marketing by electronic mail under PECR, with the disclosure the AI Act requires when a machine wrote it or drew it. Every failure is cited to the duty in the register's own words, and names the system that closes the gap. The reading also says how much of each instrument a page cannot answer, so you know what it did not look at.
Connect it as a Claude connector at this address. Your Claude then writes under the doctrine and checks the work before you publish it. The cited report needs a ComplianceSME account.
Address on this site: /content/mcp