Skip to content

Privacy Policy URL MCP server

com.privacypolicyurl/privacy-policy-urlprivacypolicyurl.comstreamable-httpv1.0.0Scanned

Hosted privacy policy URLs for apps, sites, stores and lead forms, created by an agent in one call

6 tools: 5 change things and 1 only read.

Tools: 0 delete, 0 irreversible, 5 write, 1 read.
  • Reads private data · 0
  • Reads text others write · 3
  • Can send data out · 0
  • 3 findings

Tools listed without sign-in. Remote posture

With Anlyon

5 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

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 Privacy Policy URL MCP server can do

The Privacy Policy URL MCP server is published by privacypolicyurl.com, a domain the MCP Registry verified. It has 6 tools. It can create or change data (5 tools: create_privacy_policy_url, check_privacy_policy_url, generate_store_privacy_labels, check_a2p_10dlc_documents and 1 more), but cannot delete data. 1 tool only reads.

3 tools bring in text other people can write (create_privacy_policy_url, check_a2p_10dlc_documents and list_resource_types).

The fixed checks matched 3 findings (annotation-conflict). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in, and its tools changed 2 times since Anlyon Radar first saw them.

Last scanned Nov 14, 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.

6 tools

Changes things 5Claude Code: ask
  • check_a2p_10dlc_documentsOpens a business's privacy policy, SMS terms and opt-in page (public https links) and checks what US carrier reviewers look for before approving an A2P 10DLC texting campaign: the …Reads text others write1 finding

    Why it is in this group

    • The description's first verb is "open": 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.

    Findings

    • Warn

      The server marks "check_a2p_10dlc_documents" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"idempotentHint":true,"openWorldHint":true}; The description's first verb is "open": a word for a change.

      What this check looks for
    Description, as the server wrote it
    Opens a business's privacy policy, SMS terms and opt-in page (public https links) and checks what US carrier reviewers look for before approving an A2P 10DLC texting campaign: the non-sharing statement and no wording that lets mobile data go to third parties (Twilio 30908, 30932), frequency, "Message and data rates may apply", STOP and HELP in the terms, and an opt-in that is never pre-ticked (30924). Returns verdict and pass/warn/fail checks per page. Pattern checks, not a carrier's decision; nothing is stored.

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: true
  • check_privacy_policy_urlConfirm whether a hosted privacy policy is live.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
    Confirm whether a hosted privacy policy is live. Returns status (active or not_found), liveUrl, and updatedAt when live.

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: false
  • create_privacy_policy_urlGenerate and host a privacy policy for a business, app, store or site and return its stable HTTPS URL.Reads text others writeNo findings

    Why it is in this group

    • The name "create_privacy_policy_url" says "create": a word for a change.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Generate and host a privacy policy for a business, app, store or site and return its stable HTTPS URL. Free resource types and Agent API key holders get liveUrl at once; other types get a Stripe Checkout link ($49/year) for a human to pay, plus the pendingUrl that goes live after payment. Repeating a call with the same inputs (or the same idempotencyKey) within 24 hours returns the first result.

    Annotations the server declares

    • readOnlyHint: false
    • idempotentHint: true
    • openWorldHint: true
  • generate_privacy_manifestApple privacy manifest for the app's own code: the data the app itself collects (ownData ids), its own tracking (with tracking domains), the required-reason APIs its code uses with…1 finding

    Why it is in this group

    • The name "generate_privacy_manifest" 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_privacy_manifest" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"idempotentHint":true,"openWorldHint":false}; The name "generate_privacy_manifest" says "generate": a word for a change.

      What this check looks for
    Description, as the server wrote it
    Apple privacy manifest for the app's own code: the data the app itself collects (ownData ids), its own tracking (with tracking domains), the required-reason APIs its code uses with Apple's reason codes, and optionally SDKs linked statically without their own manifest. SDKs with their own manifest are covered by theirs (Apple). Categories: NSPrivacyAccessedAPICategoryFileTimestamp (DDA9.1, C617.1, 3B52.1); NSPrivacyAccessedAPICategorySystemBootTime (35F9.1, 8FFB.1, 3D61.1); NSPrivacyAccessedAPICategoryDiskSpace (85F4.1, E174.1, 7D9E.1, B728.1); NSPrivacyAccessedAPICategoryActiveKeyboards (3EC4.1, 54BD.1); NSPrivacyAccessedAPICategoryUserDefaults (CA92.1, 1C8F.1, AC6B.1). Returns plist (XML), manifest (the same as JSON) and problems (empty when App Store Connect should accept it).

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: false
  • generate_store_privacy_labelsAnswers for Apple's App Privacy details and Google Play's Data safety form from the SDKs an app uses, their settings and the data the app collects itself.1 finding

    Why it is in this group

    • The name "generate_store_privacy_labels" 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_store_privacy_labels" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"idempotentHint":true,"openWorldHint":false}; The name "generate_store_privacy_labels" says "generate": a word for a change.

      What this check looks for
    Description, as the server wrote it
    Answers for Apple's App Privacy details and Google Play's Data safety form from the SDKs an app uses, their settings and the data the app collects itself. Every answer carries the vendor or store page it comes from. Settings are yes/no questions per SDK (ids like ga.user_id, app.iap); unknown ids are rejected. SDK ids: firebase-analytics, firebase-crashlytics, firebase-auth, firebase-messaging, admob, meta, revenuecat, onesignal, sentry, stripe, mixpanel, amplitude, google-sign-in, sign-in-with-apple, appsflyer. Returns wizardUrl, a privacy-policy wizard link with the same services and personal data filled in. A starting point to check, not legal advice.

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: false
Only reads 1Show 1 read-only tool
  • list_resource_typesThe resourceType values create_privacy_policy_url accepts, and which of them are hosted free.Reads text others writeNo findings

    Why it is in this group

    • The name "list_resource_types" says "list": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "url": it reads web pages, which anyone can write.
    Description, as the server wrote it
    The resourceType values create_privacy_policy_url accepts, and which of them are hosted free. No side effects.

    Annotations the server declares

    • readOnlyHint: true
    • 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.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write3
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

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.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:45 UTC, unchanged since Nov 6, 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
5
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
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 5 tools that change things (5 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://www.privacypolicyurl.com/api/mcp: tools/list returned 6 tools to an anonymous client, including create_privacy_policy_url (write), check_privacy_policy_url (write), generate_store_privacy_labels (write), check_a2p_10dlc_documents (write), generate_privacy_manifest (write)

    What this check looks for

Posture changes

  1. Nov 6, 2026
    • Tools that change things, listed without credentials: 4 to 5
  2. Oct 29, 2026
    • Tools that change things, listed without credentials: 2 to 4

Findings

Matches of fixed checks, with the text they matched.

3 warn
  • The server marks "generate_store_privacy_labels" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"idempotentHint":true,"openWorldHint":false}; The name "generate_store_privacy_labels" says "generate": a word for a change.

    What this check looks for
  • The server marks "check_a2p_10dlc_documents" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"idempotentHint":true,"openWorldHint":true}; The description's first verb is "open": a word for a change.

    What this check looks for
  • The server marks "generate_privacy_manifest" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"idempotentHint":true,"openWorldHint":false}; The name "generate_privacy_manifest" says "generate": a word for a change.

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools1 added, 1 changed.+1 added~1 changedView diff
  2. PostureRemote posture changed. Tools that change things, listed without credentials: 4 -> 5.View diff
    • Tools that change things, listed without credentials: 4 to 5
  3. Tools2 added, 2 changed.+2 added~2 changedView diff
  4. PostureRemote posture changed. Tools that change things, listed without credentials: 2 -> 4.View diff
    • Tools that change things, listed without credentials: 2 to 4

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http privacy-policy-url https://www.privacypolicyurl.com/api/mcp
claude mcp add --transport http privacy-policy-url https://www.privacypolicyurl.com/api/mcp

Run 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.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__privacy-policy-url__list_resource_types"
    ],
    "ask": [
      "mcp__privacy-policy-url__create_privacy_policy_url",
      "mcp__privacy-policy-url__check_privacy_policy_url",
      "mcp__privacy-policy-url__generate_store_privacy_labels",
      "mcp__privacy-policy-url__check_a2p_10dlc_documents",
      "mcp__privacy-policy-url__generate_privacy_manifest"
    ],
    "deny": []
  }
}

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 privacy-policy-url. Review it before you use it.

Capability tags behind 3 rules
  • mcp__privacy-policy-url__create_privacy_policy_url untrusted-input
  • mcp__privacy-policy-url__check_a2p_10dlc_documents untrusted-input
  • mcp__privacy-policy-url__list_resource_types untrusted-input

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/com.privacypolicyurl/privacy-policy-url/verify?hash=e126f3773cd8bc3a8bf511f6a80957bf65f8ad85815bd44e7c200febf58f7b80" | jq -e '.changed == false'

Pinned hash e126f3773cd8, from Nov 14, 2026, 02:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/com.privacypolicyurl/privacy-policy-url/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for com.privacypolicyurl/privacy-policy-url
[![Anlyon Radar](https://radar.anlyon.com/badge/com.privacypolicyurl/privacy-policy-url.svg)](https://radar.anlyon.com/servers/com.privacypolicyurl/privacy-policy-url)

Source: MCP Registry. Synced Oct 21, 2026, 18:00 UTC.

Privacy Policy URL MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Privacy Policy URL MCP server safe?

No scan can promise that. What its definitions show: 6 tools, 5 of which can change, send or delete something, and 3 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 Privacy Policy URL MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Privacy Policy URL 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 Privacy Policy URL MCP server have?

6 tools: 5 write, 1 read. create_privacy_policy_url, check_privacy_policy_url, generate_store_privacy_labels, check_a2p_10dlc_documents, generate_privacy_manifest and list_resource_types.

Does the Privacy Policy URL MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Privacy Policy URL MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Privacy Policy URL MCP server changed its tools?

Yes, 2 times since Anlyon Radar started tracking it, most recently on Nov 14, 2026. Every change is on this page and in its Atom feed.