fizzgig__cookie_monster
checks cookie consent — banner presence, parity, withdrawal, pre-consent script firing.
the cookie banner ships, but google tag manager fires in the layout before anyone clicks accept. or 'reject all' takes 5 clicks while 'accept all' takes 1. either way you've technically complied and practically ignored the rule.
7 regulator-aligned checks: CMP detection, reject-button parity (is 'reject all' as easy as 'accept all'), granular consent toggles, withdrawal mechanism, cookie max-age compliance, pre-consent script firing detection (tag-manager scripts hard-coded into layout that fire before the CMP loads), marketing tracker disclosure.
the banner exists AND it actually does what it claims to do. catches the 'we shipped a banner but the analytics still fire' bug.
caught a policy that would have leaked every user's comments. shipped a fix in 4 minutes.
first tool i installed. it's the one that pays for itself.
works great. one false positive on a join table — easy to ignore.
{
"fizzgig": {
"url": "https://mcp.fizzgig.ai",
"tools": ["cookie_monster"]
}
}