Paperloo Compliance MCP server
io.github.yassinemohamedali/paperlooyassinemohamedalistreamable-httpv1.0.0Scanned
Automated website compliance infrastructure and GDPR/CCPA auditing.
19 tools: 1 can delete or cancel things, 15 change things and 3 only read.
- Reads private data · 3
- Reads text others write · 8
- Can send data out · 5
- 7 findings
Tools listed without sign-in. Remote posture
With Anlyon
1 tool here can delete or cancel things. Govern it.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the Paperloo Compliance MCP server can do
The Paperloo Compliance MCP server is published by the GitHub account yassinemohamedali. It has 19 tools. It can delete or cancel things (1 tool: delete_site) and create or change data (15 tools: audit_site, audit_accessibility, audit_ai_transparency, configure_cookie_banner and 11 more). 3 tools only read.
3 tools read private data (list_sites, get_site and get_questionnaire_schema); 8 tools bring in text other people can write (audit_site, audit_accessibility, audit_ai_transparency and 5 more); 5 tools can send data out of your system (audit_site, audit_accessibility, audit_ai_transparency and 2 more). On its own it has all three parts of a prompt-injection exfiltration path: private data, text others write, and a way out.
The fixed checks matched 7 findings (annotation-conflict). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.
Last scanned Nov 20, 2026, version 1.0.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
19 tools
Deletes or cancels 1Claude Code: deny
delete_sitePermanently removes a monitored website property and all of its stored banner configurations, GTM bindings, audit history, and cached legal documents from the active Paperloo regis…No findings
Why it is in this group
- The name "delete_site" says "delete": a word for removing or ending something.
- The description says "Permanently removes".
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it Permanently removes a monitored website property and all of its stored banner configurations, GTM bindings, audit history, and cached legal documents from the active Paperloo registry. When to use vs. related tools: Call 'delete_site' only when a site should be permanently decommissioned from monitoring. Use 'list_sites' or 'get_site' first to confirm the exact 'siteId'. Preconditions & side effects: 'siteId' must match an existing site ID or exact URL/hostname in the registry. Destructive mutation—immediately deletes the matching site from 'activeSites'. Returns: JSON object with 'success: true', deleted 'siteId', 'name', 'url', 'deleted_at', and 'message' (or 'success: false', 'error', and 'available_sites' if not found).
Annotations the server declares
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: false
- openWorldHint: false
Changes things 15Claude Code: ask
add_siteCreates and registers a new website property in the Paperloo compliance registry, initializing default GDPR/CCPA jurisdictions, default Google Consent Mode v2 denied banner setting…Can send data outNo findings
Why it is in this group
- The name "add_site" says "add": a word for a change.
What it can reach
- outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
Description, as the server wrote it Creates and registers a new website property in the Paperloo compliance registry, initializing default GDPR/CCPA jurisdictions, default Google Consent Mode v2 denied banner settings, a pending GTM slot, an initial compliance grade (A-, 91/100), a live API key, and an embed script tag. When to use vs. related tools: Call 'add_site' before configuring persistent banners ('configure_cookie_banner'), GTM ('configure_gtm_integration'), or attaching documents to a siteId. Do not call 'add_site' if you only want a one-off audit ('audit_site'), cookie scan ('scan_cookies'), or ephemeral policy generation ('generate_documents' without 'siteId'). Preconditions & side effects: Requires non-empty 'name' and valid HTTP(S) 'url'. Mutates the active site registry by prepending the newly created site record. Returns: JSON object containing 'success: true', created 'site' object, generated 'apiKey', 'embed_script', and 'message' (or 'success: false' and 'error' on invalid input).
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
audit_accessibilityPerforms a focused HTML DOM accessibility evaluation on a target URL against WCAG 2.1 AA, WCAG 2.1 AAA, or U.S.Reads text others writeCan send data outNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
- outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
Description, as the server wrote it Performs a focused HTML DOM accessibility evaluation on a target URL against WCAG 2.1 AA, WCAG 2.1 AAA, or U.S. Section 508 standards. Inspects missing image 'alt' attributes (SC 1.1.1), HTML5 semantic/ARIA landmarks (SC 1.3.1), programmatic form input labels (SC 3.3.2), document '<title>' presence (SC 2.4.2), and '<html lang>' declaration (SC 3.1.1), applying standard-specific grading thresholds. When to use vs. related tools: Call 'audit_accessibility' when you need granular accessibility counts, standard-specific grading (including WCAG_2.1_AAA or Section_508), and remediation items without privacy/cookie auditing. Call 'audit_site' for combined privacy + security + accessibility scoring. Preconditions & side effects: Requires a reachable public HTTP(S) URL; no registry siteId or authentication required. Read-only live HTTP inspection with zero state mutation. Returns: JSON object containing 'success', 'audit_id', 'target_url', 'standard', 'accessibility_score' (0-100), 'wcag_compliance_grade' ('AAA' | 'AA' | 'A' | 'CONFORMANT' | 'NON_COMPLIANT'), itemized 'metrics', 'violations', 'remediation_actions', 'timestamp', and optional 'error'.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
audit_ai_transparencyEvaluates a live website URL for European Union Artificial Intelligence Act (Regulation (EU) 2024/1689) Article 50 transparency compliance and GDPR Article 22 automated decision-ma…Reads text others writeCan send data out1 finding
Why it is in this group
- The description's first verb is "evaluate": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
- outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
Findings
- Warn
The server marks "audit_ai_transparency" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":false,"openWorldHint":true}; The description's first verb is "evaluate": a word for a change.
Description, as the server wrote it Evaluates a live website URL for European Union Artificial Intelligence Act (Regulation (EU) 2024/1689) Article 50 transparency compliance and GDPR Article 22 automated decision-making readiness. Scans page HTML for embedded conversational AI assistants (Intercom Fin, Crisp, Chatbase, Voiceflow, Botpress, Tidio Lyro, Zendesk AI), checks for explicit AI/synthetic-content disclosure language, and reports tracked AI crawler policy slots (GPTBot, CCBot, ClaudeBot, Anthropic-ai, Google-Extended). When to use vs. related tools: Call 'audit_ai_transparency' when specifically assessing EU AI Act Article 50 chatbot/synthetic disclosures and statutory mandates. Call 'audit_site' for a full GDPR/CCPA/security/WCAG/AI combined audit. Preconditions & side effects: Requires a public HTTP(S) URL; no authentication or site registration needed. Read-only live HTTP inspection. Returns: JSON object containing 'success', 'audit_id', 'target_url', 'ai_act_compliance_status' ('COMPLIANT' | 'NEEDS_DISCLOSURE' | 'HIGH_RISK_REVIEW'), 'regulatory_framework', 'findings', 'statutory_mandates', 'action_items', 'timestamp', and optional 'error'.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
audit_siteExecutes a live HTTP/HTTPS multi-vector compliance audit against any public website URL.Reads text others writeCan send data out1 finding
Why it is in this group
- The description's first verb is "execute": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
- outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
Findings
- Warn
The server marks "audit_site" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":false,"openWorldHint":true}; The description's first verb is "execute": a word for a change.
Description, as the server wrote it Executes a live HTTP/HTTPS multi-vector compliance audit against any public website URL. Inspects TLS transport, HTTP security headers (HSTS, CSP, X-Frame-Options, X-Content-Type-Options), Set-Cookie headers, client-side tracking scripts, Consent Management Platform (CMP) and Google Consent Mode v2 default 'denied' enforcement (GDPR Art. 5(3)), footer legal policy links (Privacy, Terms, Cookie Policy, CCPA Do Not Sell), and—when deep_scan is true—WCAG 2.1 AA DOM accessibility metrics and EU AI Act Article 50 chatbot disclosures. When to use vs. related tools: Call 'audit_site' for an overall 0-100 compliance score, letter grade (A+ to F / FAILED), and cross-framework findings. Use 'scan_cookies' when you only need a categorized cookie/tracker inventory without grading; use 'audit_accessibility' when you need grading against WCAG_2.1_AAA or Section_508; use 'audit_ai_transparency' when you only need EU AI Act Art. 50 & GDPR Art. 22 findings. Preconditions & side effects: Requires a publicly DNS-resolvable HTTP/HTTPS URL; no authentication or prior 'add_site' registration is required. Read-only operation—performs live outbound HTTP GET inspection and never mutates registered sites. Returns: JSON object containing 'success', 'audit_id', 'target_url', 'deep_scan', 'compliance_score' (0-100), 'compliance_grade', 'status' ('COMPLETED' | 'FAILED'), 'is_https', 'timestamp', structured 'tests' sub-reports, 'findings', 'recommendations', 'cookie_inventory', and 'error' if unreachable or invalid.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
configure_cookie_bannerUpdates and persists the cookie consent banner UI configuration, Google Consent Mode v2 synchronization, and pre-consent tracker blocking rules for an existing monitored site.No findings
Why it is in this group
- The description's first verb is "update": a word for a change.
Description, as the server wrote it Updates and persists the cookie consent banner UI configuration, Google Consent Mode v2 synchronization, and pre-consent tracker blocking rules for an existing monitored site. When to use vs. related tools: Call 'configure_cookie_banner' first to customize visual theme, placement, copy, accent hex color, and GCM v2 blocking flags on a registered site; afterward, call 'get_cookie_banner_script' (for CMS/web embeds) or 'get_consent_banner_code' (for GCM v2 Basic/Advanced code). Call 'list_sites' or 'add_site' first if you do not have a valid 'siteId'. Preconditions & side effects: 'siteId' MUST match an existing site ID or registered domain in the workspace registry (no silent fallback to default sites). Mutates the target site's 'cookie_banner' configuration in-memory. Returns: On success, returns 'success: true', 'siteId', 'site_name', persisted 'banner_configuration', 'preview_url', 'embed_script', and 'message'. On invalid accent color or unknown siteId, returns 'success: false', 'error', and 'available_sites'.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
configure_gtm_integrationConfigures and saves a Google Tag Manager (GTM) container binding and initial Google Consent Mode v2 storage signal defaults ('ad_storage', 'analytics_storage', 'ad_user_data', 'ad…No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Configures and saves a Google Tag Manager (GTM) container binding and initial Google Consent Mode v2 storage signal defaults ('ad_storage', 'analytics_storage', 'ad_user_data', 'ad_personalization') plus 'paperloo_consent_update' dataLayer trigger settings for a registered site. When to use vs. related tools: Call 'configure_gtm_integration' to store a GTM container ID and default consent states on a site; call 'get_gtm_container_setup' afterward to retrieve the rendered '<head>'/'<body>' GTM snippets reflecting those saved defaults. Preconditions & side effects: 'siteId' must match a registered site, and 'gtm_container_id' must match '^GTM-[A-Z0-9]{4,12}$'. Mutates the site's 'gtm' object in the active registry. Returns: JSON object with 'success: true', 'siteId', 'site_name', saved 'gtm_configuration', and 'message' (or 'success: false' and 'error').
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
export_documentsExports all legal compliance documents currently attached to a registered website in clean Markdown ('markdown'), semantic HTML ('html'), or structured JSON ('json') format.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it Exports all legal compliance documents currently attached to a registered website in clean Markdown ('markdown'), semantic HTML ('html'), or structured JSON ('json') format. When to use vs. related tools: Call 'export_documents' AFTER generating and attaching documents to a siteId via 'generate_documents' or 'generate_docs_questionnaire' (or for a pre-seeded site like 'site_paperloo_sandbox'). Note: calling 'export_documents' on a site with zero attached documents returns an empty 'documents' array—generate documents with that 'siteId' first. Preconditions & side effects: 'siteId' must exist in the active registry. Read-only transformation—does not mutate stored documents. Returns: JSON object containing 'success: true', 'siteId', 'format', 'total_documents', 'documents' (each with 'type', 'title', 'version', 'word_count', 'content'), and 'message' (or 'error' + 'available_sites').
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
generate_docs_questionnaireSynthesizes a tailored statutory legal document suite (Privacy Policy, Terms of Service, Cookie Policy, EULA, Acceptable Use Policy, Disclaimer, Return Policy, Accessibility Statem…No findings
Why it is in this group
- The name "generate_docs_questionnaire" says "generate": a word for a change.
Description, as the server wrote it Synthesizes a tailored statutory legal document suite (Privacy Policy, Terms of Service, Cookie Policy, EULA, Acceptable Use Policy, Disclaimer, Return Policy, Accessibility Statement) from answers gathered against the standardized 'get_questionnaire_schema' intake form. When to use vs. related tools: Pair 'get_questionnaire_schema' -> 'generate_docs_questionnaire' in conversational intake workflows where you collect structured business, tracker, minor-protection, and retention answers from a user before drafting documents. For direct programmatic generation without a questionnaire UI step, 'generate_documents' accepts the exact same payload. Preconditions & side effects: Requires 'company_name', 'website_url', and 'contact_email'. If 'siteId' is omitted, creates an isolated ephemeral tenant output with no registry mutation. If 'siteId' is explicitly supplied, it must match a registered site and will persist 'documents' and upgrade the site's compliance grade to 'A+'. Returns: JSON object with 'success', 'siteId', 'company_name', 'tenant_mode', 'documents_generated', full 'documents' array, and 'message' (or 'error').
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
generate_documentsSynthesizes a tailored suite of legal compliance documents (Privacy Policy, Terms of Service, Cookie Policy, EULA, Acceptable Use Policy, Disclaimer, Return & Refund Policy, WCAG A…No findings
Why it is in this group
- The name "generate_documents" says "generate": a word for a change.
Description, as the server wrote it Synthesizes a tailored suite of legal compliance documents (Privacy Policy, Terms of Service, Cookie Policy, EULA, Acceptable Use Policy, Disclaimer, Return & Refund Policy, WCAG Accessibility Statement) directly from company metadata, jurisdictions (GDPR, CCPA, EU_AI_ACT), data practices, and sub-processor flags. When to use vs. related tools: Use 'generate_documents' when you already have all company and technical parameters ready to synthesize policies immediately. Use 'get_questionnaire_schema' followed by 'generate_docs_questionnaire' when conducting an interactive user intake flow. Use 'generate_dpa' specifically for a GDPR Article 28 Data Processing Addendum contract between Controller and Processor. Use 'export_documents' afterward to convert saved documents into HTML or JSON. Preconditions & side effects: Requires 'company_name', 'website_url', and 'contact_email'. If 'siteId' is omitted, operates in 'isolated_ephemeral_client' mode with a temporary ID and zero registry side effects. If 'siteId' is provided, it MUST match a registered site—on match, persists the generated documents onto that site and updates its compliance score (>= 95) and grade ('A+'); if unknown, returns an error. Returns: JSON object with 'success', 'siteId', 'company_name', 'tenant_mode', 'documents_generated' summaries, full 'documents' Markdown array, and 'message' (or 'error').
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
generate_dpaGenerates a standalone GDPR Article 28 Data Processing Addendum (DPA) Markdown contract between a named Data Controller (client) and Data Processor (vendor/agency), incorporating A…1 finding
Why it is in this group
- The name "generate_dpa" says "generate": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
The server marks "generate_dpa" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":false,"openWorldHint":false}; The name "generate_dpa" says "generate": a word for a change.
Description, as the server wrote it Generates a standalone GDPR Article 28 Data Processing Addendum (DPA) Markdown contract between a named Data Controller (client) and Data Processor (vendor/agency), incorporating Art. 28(3) processor obligations, Art. 32 technical security controls, governing law, and authorized sub-processors. When to use vs. related tools: Call 'generate_dpa' specifically for B2B vendor-client Data Processing Agreements (DPAs). Do NOT use 'generate_documents' for DPAs, as 'generate_documents' handles public website policies (Privacy, Terms, Cookies, EULA, AUP, Disclaimer, Return, Accessibility). Preconditions & side effects: Requires non-empty 'controller_name' and 'processor_name'. Stateless and read-only—does not require or mutate any registered site. Returns: JSON object with 'success', 'title', 'controller_name', 'processor_name', 'governing_law', 'sub_processors', 'markdown', 'word_count', and 'version' (or 'error').
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
get_consent_banner_codeGenerates developer-oriented Google Consent Mode v2 banner integration code with configurable 'gtm_mode' ('v2_basic' strict tag-blocking vs 'v2_advanced' cookieless behavioral mode…Reads text others write1 finding
Why it is in this group
- The name "get_consent_banner_code" says "get": a word for reading.
- The description's first verb is "generate": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe description's first sentence says "generate" and "html": it reads web pages, which anyone can write.
Findings
- Warn
The server marks "get_consent_banner_code" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "get_consent_banner_code" says "get": a word for reading.
Description, as the server wrote it Generates developer-oriented Google Consent Mode v2 banner integration code with configurable 'gtm_mode' ('v2_basic' strict tag-blocking vs 'v2_advanced' cookieless behavioral modeling with 'ads_data_redaction' and 'wait_for_update') and dynamic 'paperloo_consent_update' listener snippets across 'html', 'react', 'nextjs', and 'vue'. When to use vs. related tools: Choose 'get_consent_banner_code' over 'get_cookie_banner_script' when building custom frontend apps (including Vue 3) or when explicitly selecting Basic vs. Advanced Google Consent Mode v2 behavior. Choose 'get_cookie_banner_script' for CMS embeds (WordPress, Webflow, Shopify). Choose 'get_gtm_container_setup' for full Google Tag Manager container '<head>'/'<body>' snippets. Preconditions & side effects: 'siteId' must match a registered site in the active registry. Read-only operation. Returns: JSON object containing 'success', 'siteId', 'site_name', 'framework', 'gtm_mode', 'embed_code', 'gcm_default_state', 'consent_update_listener', and 'instructions' (or 'error' on failure).
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_cookie_banner_scriptGenerates a ready-to-deploy cookie consent banner embed snippet tailored to a target web framework or CMS ('html', 'react', 'nextjs', 'wordpress', 'webflow', 'shopify') with Google…Reads text others write1 finding
Why it is in this group
- The name "get_cookie_banner_script" says "get": a word for reading.
- The description's first verb is "generate": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe description's first sentence says "generate" and "web": it reads web pages, which anyone can write.
Findings
- Warn
The server marks "get_cookie_banner_script" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "get_cookie_banner_script" says "get": a word for reading.
Description, as the server wrote it Generates a ready-to-deploy cookie consent banner embed snippet tailored to a target web framework or CMS ('html', 'react', 'nextjs', 'wordpress', 'webflow', 'shopify') with Google Consent Mode v2 default 'denied' initialization. When to use vs. related tools: Call 'get_cookie_banner_script' when integrating into a CMS (WordPress PHP hook, Webflow head embed, Shopify theme.liquid) or standard React/Next.js/HTML app. Call 'get_consent_banner_code' instead if you need Vue 3 support, explicit selection between 'v2_basic' (blocking) vs 'v2_advanced' (cookieless pings) GCM v2 modes, or consent update event listeners. Call 'configure_cookie_banner' beforehand to customize banner styling. Preconditions & side effects: 'siteId' must exist in the active registry. Read-only code generation—does not mutate site state. Returns: JSON object with 'success', 'siteId', 'site_name', 'framework', 'embed_code', 'gcm_default_state', and 'instructions' (or 'success: false' and 'error' if not found).
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_gtm_container_setupGenerates ready-to-install Google Tag Manager '<head>' and '<body>' ('<noscript>') snippets pre-populated with Google Consent Mode v2 default signals and custom dataLayer consent t…1 finding
Why it is in this group
- The name "get_gtm_container_setup" says "get": a word for reading.
- The description's first verb is "generate": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
The server marks "get_gtm_container_setup" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "get_gtm_container_setup" says "get": a word for reading.
Description, as the server wrote it Generates ready-to-install Google Tag Manager '<head>' and '<body>' ('<noscript>') snippets pre-populated with Google Consent Mode v2 default signals and custom dataLayer consent trigger recipes for a registered site. When to use vs. related tools: Call 'get_gtm_container_setup' after 'configure_gtm_integration' (or with an explicit 'gtm_container_id' override) when installing GTM directly. Call 'get_cookie_banner_script' or 'get_consent_banner_code' to embed the Paperloo consent UI banner script itself. Preconditions & side effects: 'siteId' must exist in the active registry. Uses 'gtm_container_id' override if provided, otherwise reads the container ID and GCM v2 defaults stored on the site. Read-only operation. Returns: JSON object with 'success', 'siteId', 'gtm_container_id', 'head_snippet', 'body_snippet', 'consent_defaults', and 'consent_triggers' (or 'error' on failure).
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
scan_cookiesPerforms a live HTTP GET scan on a target website URL to inspect 'Set-Cookie' response headers and third-party tracking scripts in the HTML (such as Google Analytics 4, Google Ads,…Reads text others writeCan send data outNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
- outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
Description, as the server wrote it Performs a live HTTP GET scan on a target website URL to inspect 'Set-Cookie' response headers and third-party tracking scripts in the HTML (such as Google Analytics 4, Google Ads, Meta Pixel, TikTok, Hotjar, Clarity, LinkedIn, Stripe, HubSpot, Intercom, Cloudflare), returning a categorized inventory grouped into Necessary, Analytics, Marketing, and Preferences. When to use vs. related tools: Call 'scan_cookies' when you specifically want the categorized cookie and tracker inventory to populate a Cookie Policy or inspect third-party scripts. Call 'audit_site' instead when you also want security header checks, legal link verification, accessibility, AI Act checks, and an overall compliance score. Preconditions & side effects: Requires a reachable public HTTP(S) URL; no registry siteId or authentication needed. Read-only live HTTP inspection. Returns: JSON object containing 'success', 'reachable', 'url', 'total_cookies', 'scripts_detected', 'categorized_inventory' (grouped arrays), 'all_cookies', 'cookie_inventory', 'message', and optional 'error'.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
verify_complianceEvaluates a registered site's current compliance posture (score, grade, and active consent banner status) and issues a timestamped verification attestation hash, compliance status …1 finding
Why it is in this group
- The description's first verb is "evaluate": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
The server marks "verify_compliance" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":false,"openWorldHint":false}; The description's first verb is "evaluate": a word for a change.
Description, as the server wrote it Evaluates a registered site's current compliance posture (score, grade, and active consent banner status) and issues a timestamped verification attestation hash, compliance status ('VERIFIED_COMPLIANT' | 'CONDITIONALLY_COMPLIANT' | 'NON_COMPLIANT'), inline SVG trust badge markup, and HTML embed snippet. When to use vs. related tools: Call 'verify_compliance' when generating a trust seal or verifying status of a registered property already managed in Paperloo. Call 'audit_site' instead when you need to crawl a live external URL over HTTP. Preconditions & side effects: 'siteId' MUST match an existing site in the active registry (no fallback to default site). Read-only attestation generation. Returns: JSON object with 'success', 'siteId', 'site_name', 'compliance_score', 'compliance_grade', 'verification_status', 'verification_hash', 'verified_at', 'standards', 'badge_svg', and 'badge_embed' (or 'error' + 'available_sites').
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
Only reads 3Show 3 read-only tools
get_questionnaire_schemaReturns the structured compliance intake questionnaire schema (categorized sections, field keys, data types, labels, defaults, and option lists) scoped to the requested document ca…Reads private dataNo findings
Why it is in this group
- The name "get_questionnaire_schema" says "get": a word for reading.
What it can reach
- private-dataThe description's first sentence says "return" and "document": it reads documents.
Description, as the server wrote it Returns the structured compliance intake questionnaire schema (categorized sections, field keys, data types, labels, defaults, and option lists) scoped to the requested document category. When to use vs. related tools: Call 'get_questionnaire_schema' BEFORE 'generate_docs_questionnaire' when building dynamic intake forms or interviewing a user step-by-step to collect required legal facts. Call 'generate_documents' directly if you already hold the fields without needing question metadata. Preconditions & side effects: No required arguments; 'document_type' defaults to 'all'. Read-only metadata lookup. Returns: JSON object containing 'success: true', 'version', 'document_type', and scoped 'categories' array of question definitions (or 'success: false' and 'error' for unsupported document_type).
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_siteRetrieves the complete stored profile for a single monitored website—including cookie banner configuration, GTM Consent Mode v2 settings, attached legal policy Markdown documents, …Reads private dataReads text others writeNo findings
Why it is in this group
- The name "get_site" says "get": a word for reading.
What it can reach
- private-dataThe description's first sentence says "retrieve" and "document": it reads documents.
- untrusted-inputThe description's first sentence says "retrieve" and "website": it reads web pages, which anyone can write.
Description, as the server wrote it Retrieves the complete stored profile for a single monitored website—including cookie banner configuration, GTM Consent Mode v2 settings, attached legal policy Markdown documents, and ready-to-use HTML/GCM v2 embed snippets. When to use vs. related tools: Call 'get_site' when inspecting a single known property in full detail. Call 'list_sites' to browse or filter across all properties. Preconditions & side effects: 'siteId' must match an existing site ID or exact URL/hostname in the registry. Read-only lookup. Returns: JSON object containing 'success: true', full 'site' object, and 'embed_code' (or 'success: false', 'error', 'help', and 'available_sites' when not found).
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
list_sitesLists monitored website properties in the Paperloo compliance registry with status filtering ('all', 'active', 'compliant', 'needs_audit') and offset/limit pagination, returning su…Reads private dataReads text others writeNo findings
Why it is in this group
- The name "list_sites" says "list": a word for reading.
What it can reach
- private-dataThe description's first sentence says "list" and "document": it reads documents.
- untrusted-inputThe description's first sentence says "list" and "website": it reads web pages, which anyone can write.
Description, as the server wrote it Lists monitored website properties in the Paperloo compliance registry with status filtering ('all', 'active', 'compliant', 'needs_audit') and offset/limit pagination, returning summary compliance grades, banner readiness, GTM state, and document counts. When to use vs. related tools: Call 'list_sites' to discover valid 'siteId' identifiers before calling site-specific tools ('get_site', 'configure_cookie_banner', 'configure_gtm_integration', 'export_documents', 'delete_site'). Call 'get_site' afterward if you need a site's full nested cookie_banner, gtm, and document Markdown contents. Preconditions & side effects: No required parameters. Read-only registry query. Returns: JSON object with 'success', 'total_count', 'returned_count', 'offset', 'limit', 'filter_applied', and 'sites' array (or 'error' + 'supported_filters' if invalid filter/pagination arguments are supplied).
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
120 paths in this server alone from private data, through text someone else wrote, to a way out. Denying 3 private-data tools breaks every one.
- Reads private data3
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write8
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out5
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
{
"permissions": {
"deny": [
"mcp__paperloo__get_questionnaire_schema",
"mcp__paperloo__get_site",
"mcp__paperloo__list_sites"
]
}
}Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 19:13 UTC, unchanged since Nov 20, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 16
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- HighThe whole server
The endpoint served tools/list without credentials, and the list has 16 tools that change things (1 destructive, 15 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://paperloo.vercel.app/api/mcp: tools/list returned 19 tools to an anonymous client, including delete_site (destructive), audit_site (write), audit_accessibility (write), audit_ai_transparency (write), configure_cookie_banner (write) and 11 more
Posture changes
- Nov 20, 2026
- Tools that change things, listed without credentials: 15 to 16
- Nov 13, 2026
- HTTP status of an anonymous initialize: 500 to 200
- tools/list served without credentials: no to yes
- Tools that change things, listed without credentials: 0 to 15
- Protocol version: none to 2025-06-18
Findings
Matches of fixed checks, with the text they matched.
- Warnaudit_site
The server marks "audit_site" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":false,"openWorldHint":true}; The description's first verb is "execute": a word for a change.
The server marks "audit_ai_transparency" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":false,"openWorldHint":true}; The description's first verb is "evaluate": a word for a change.
The server marks "get_cookie_banner_script" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "get_cookie_banner_script" says "get": a word for reading.
The server marks "get_consent_banner_code" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "get_consent_banner_code" says "get": a word for reading.
The server marks "get_gtm_container_setup" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "get_gtm_container_setup" says "get": a word for reading.
- Warngenerate_dpa
The server marks "generate_dpa" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":false,"openWorldHint":false}; The name "generate_dpa" says "generate": a word for a change.
Show 1 more findingShow fewer
The server marks "verify_compliance" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":false,"openWorldHint":false}; The description's first verb is "evaluate": a word for a change.
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools16 added, 3 changed.+16 added~3 changedView diff
- Added:add_siteChanges things
- Added:audit_accessibilityChanges things
- Added:audit_ai_transparencyChanges things
- Added:configure_cookie_bannerChanges things
- Added:configure_gtm_integrationChanges things
- Added:delete_siteDeletes or cancels
- Added:export_documentsChanges things
- Added:generate_docs_questionnaireChanges things
- Added:generate_dpaChanges things
- Added:get_consent_banner_codeChanges things
- Added:get_cookie_banner_scriptChanges things
- Added:get_gtm_container_setupChanges things
- Added:get_questionnaire_schemaOnly reads
- Added:get_siteOnly reads
- Added:scan_cookiesChanges things
- Added:verify_complianceChanges things
- Changed:audit_siteChanges thingstitledescriptioninputSchemaannotations
- Changed:generate_documentsChanges thingstitledescriptioninputSchemaannotations
- Changed:list_sitesOnly readstitledescriptioninputSchemaannotations
PostureRemote posture changed. Tools that change things, listed without credentials: 15 -> 16.View diff
- Tools that change things, listed without credentials: 15 to 16
PostureRemote posture changed. HTTP status of an anonymous initialize: 500 -> 200; tools/list served without credentials: no -> yes; Tools that change things, listed without credentials: 0 -> 15 (and 1 more).View diff
- HTTP status of an anonymous initialize: 500 to 200
- tools/list served without credentials: no to yes
- Tools that change things, listed without credentials: 0 to 15
- Protocol version: none to 2025-06-18
Install
Pinned to version 1.0.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http paperloo https://paperloo.vercel.app/api/mcpclaude mcp add --transport http paperloo https://paperloo.vercel.app/api/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__paperloo__list_sites",
"mcp__paperloo__get_site",
"mcp__paperloo__get_questionnaire_schema"
],
"ask": [
"mcp__paperloo__audit_site",
"mcp__paperloo__audit_accessibility",
"mcp__paperloo__audit_ai_transparency",
"mcp__paperloo__configure_cookie_banner",
"mcp__paperloo__get_cookie_banner_script",
"mcp__paperloo__get_consent_banner_code",
"mcp__paperloo__configure_gtm_integration",
"mcp__paperloo__get_gtm_container_setup",
"mcp__paperloo__scan_cookies",
"mcp__paperloo__generate_documents",
"mcp__paperloo__generate_docs_questionnaire",
"mcp__paperloo__generate_dpa",
"mcp__paperloo__verify_compliance",
"mcp__paperloo__add_site",
"mcp__paperloo__export_documents"
],
"deny": [
"mcp__paperloo__delete_site"
]
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as paperloo. Review it before you use it.
Capability tags behind 10 rules
- mcp__paperloo__audit_site untrusted-input, outbound
- mcp__paperloo__audit_accessibility untrusted-input, outbound
- mcp__paperloo__audit_ai_transparency untrusted-input, outbound
- mcp__paperloo__get_cookie_banner_script untrusted-input
- mcp__paperloo__get_consent_banner_code untrusted-input
- mcp__paperloo__scan_cookies untrusted-input, outbound
- mcp__paperloo__list_sites private-data, untrusted-input
- mcp__paperloo__get_site private-data, untrusted-input
- mcp__paperloo__add_site outbound
- mcp__paperloo__get_questionnaire_schema private-data
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.github.yassinemohamedali/paperloo/verify?hash=ed1219224a091d454f26598dab83fcd5fe641d672ea8af9b9b9a2c04a9f60b68" | jq -e '.changed == false'Pinned hash ed1219224a09, from Nov 20, 2026, 19:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.yassinemohamedali/paperloo/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.yassinemohamedali/paperloo)Source: MCP Registry · repository. Synced Oct 21, 2026, 18:51 UTC.
Paperloo Compliance MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Paperloo Compliance MCP server safe?
- No scan can promise that. What its definitions show: 19 tools, 16 of which can change, send or delete something, and 7 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Paperloo Compliance MCP server delete data?
- Yes. 1 tool can delete, cancel or revoke something: delete_site.
Can the Paperloo Compliance MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the Paperloo Compliance MCP server have?
- 19 tools: 1 destructive, 15 write, 3 read. delete_site, audit_site, audit_accessibility, audit_ai_transparency, configure_cookie_banner, get_cookie_banner_script, get_consent_banner_code, configure_gtm_integration and 11 more.
Does the Paperloo Compliance MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Paperloo Compliance MCP server send data to outside services?
- 5 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): audit_site, audit_accessibility, audit_ai_transparency, scan_cookies and add_site.
Has the Paperloo Compliance MCP server changed its tools?
- Yes, once since Anlyon Radar started tracking it, most recently on Nov 20, 2026. Every change is on this page and in its Atom feed.