Audits websites for cookie consent compliance across major privacy frameworks. Point it at any URL and get a structured PASS/FAIL checklist with regulatory citations and fix recommendations — no browser, no manual inspection required.
Glama couldn't complete the latest health check. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.
If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.
Scored across 6 tools
Each tool has a clearly distinct purpose: starting a scan, polling status, retrieving reports, listing history, focusing on failures, and purchasing credits. No two tools overlap in functionality.
All tool names follow a consistent verb_noun pattern (scan_url, get_scan_status, get_scan_report, get_failing_checks, list_my_scans, get_payment_link) using snake_case, making them predictable and easy to navigate.
With 6 tools, the set is well-scoped for a cookie consent compliance analyser. It covers the complete scan lifecycle (initiate, poll, retrieve results) plus history and payment, without unnecessary clutter.
The tool surface covers the primary workflow: scanning, status polling, full report, failing checks, history, and payment. Minor gaps exist (e.g., no delete or rescan), but the core compliance analysis task is fully supported.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
scan_url5 fields changedInput schema / properties / login_passwordAdded value: +{
+ "anyOf": [
+ {
+ "type": "string"
+ },
+ {
+ "type": "null"
+ }
+ ],
+ "default": null,
+ "description": "Optional. Password for the login_username. Required if login_username is provided.",
+ "title": "Login Password"
+}Input schema / properties / login_urlAdded value: +{
+ "anyOf": [
+ {
+ "type": "string"
+ },
+ {
+ "type": "null"
+ }
+ ],
+ "default": null,
+ "description": "Optional. URL of the login page. If omitted, the scan target URL is used as the login page.",
+ "title": "Login Url"
+}Input schema / properties / login_usernameAdded value: +{
+ "anyOf": [
+ {
+ "type": "string"
+ },
+ {
+ "type": "null"
+ }
+ ],
+ "default": null,
+ "description": "Optional. Username or email address to log in to the site before scanning. When provided together with login_password, two linked scans are run: one before login and one after. Only one credit is consumed.",
+ "title": "Login Username"
+}Output schema / properties / paired_run_idAdded value: +{
+ "anyOf": [
+ {
+ "type": "string"
+ },
+ {
+ "type": "null"
+ }
+ ],
+ "default": null,
+ "description": "Present only for paired scans. The run_id of the complementary (post-login) scan.",
+ "title": "Paired Run Id"
+}Output schema / properties / scan_group_idAdded value: +{
+ "anyOf": [
+ {
+ "type": "string"
+ },
+ {
+ "type": "null"
+ }
+ ],
+ "default": null,
+ "description": "Present only for paired pre/post-login scans. Links the two runs together.",
+ "title": "Scan Group Id"
+}get_payment_linkget_failing_checksget_scan_reportget_scan_statuslist_my_scansscan_url
Add one secure layer between your agents and this server.