Privacy Policy URL
REMOTE · WWW.PRIVACYPOLICYURL.COM
Hosted privacy policy URLs for apps, sites, stores and lead forms, created by an agent in one call
Available components
Last scanned (3 hours ago)
Scores higher than 58% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Documents and Files
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 1 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability72
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1241 tokens (~177/item across 7 items; 6 tools + 1 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management53
- Stability observed for 16 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage79
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 38% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “create_privacy_policy_url” rewrote its description, which is the text the model reads security
- Tool coverage: 43% → 38% ▼ functional
- Schema quality: 1032 → 1241 ▼ functional
- New tool “check_a2p_10dlc_documents” functional
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 24 Oct 26 −2
- The server rewrote its instructions, which are the text every model session reads security
- Tool coverage: 90% → 43% ▼ functional
- Schema quality: pass → fail ▼ functional
- New tool “generate_privacy_manifest” functional
- New tool “generate_store_privacy_labels” functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://www.privacypolicyurl.com/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.privacypolicyurl.com | CN=YR2,O=Let's Encrypt,C=US | 7 Sept 2026 | 6 Dec 2026 | RSA 2048 | SHA256-RSA | 6232f4bd168933b9c8d287e7efbc7a0c6c1 |
| SANs: *.privacypolicyurl.com | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of www.privacypolicyurl.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| privacypolicyurl.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
| content-security-policy | frame-ancestors 'none' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(), payment=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://www.privacypolicyurl.com/api/mcp | Verified | 200 | |
| http (plaintext) | http://www.privacypolicyurl.com/api/mcp | HTTPS enforced | 308 | https://www.privacypolicyurl.com/api/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_a2p_10dlc_documents Check A2P 10DLC documents before registering ~161
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.
| Name | Type | Req | Description |
|---|---|---|---|
| optInUrl | string | – | – |
| privacyUrl | string | yes | – |
| termsUrl | string | – | – |
No output schema declared.
No examples provided.
check_privacy_policy_url Check a privacy policy URL ~45
Confirm whether a hosted privacy policy is live. Returns status (active or not_found), liveUrl, and updatedAt when live.
| Name | Type | Req | Description |
|---|---|---|---|
| companySlug | string | yes | – |
No output schema declared.
No examples provided.
create_privacy_policy_url Create a hosted privacy policy URL ~282
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.
| Name | Type | Req | Description |
|---|---|---|---|
| caloppa | boolean | – | Include CalOPPA sections. |
| ccpa | boolean | – | Include CCPA/CPRA (California) sections. |
| companyName | string | yes | Business, app or site name as it should appear in the policy. |
| companySlug | string | – | URL slug (a-z, 0-9, hyphens). Defaults to a slug of companyName. |
| coppa | boolean | – | Include COPPA (children under 13) sections. |
| string | yes | Owner contact email. Receives the live link and manages the URL later. | |
| gdpr | boolean | – | Include GDPR (EU/UK) sections. |
| idempotencyKey | string | – | Your own retry key. Defaults to a hash of the other inputs. |
| resourceType | string | yes | What the policy covers. See list_resource_types for which are free. |
No output schema declared.
No examples provided.
generate_privacy_manifest Generate the app's PrivacyInfo.xcprivacy ~287
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).
| Name | Type | Req | Description |
|---|---|---|---|
| apiReasons | object | – | – |
| ownData | array | – | – |
| settings | object | – | – |
| staticSdks | array | – | – |
| tracking | object | – | – |
No output schema declared.
No examples provided.
generate_store_privacy_labels Generate App Store and Google Play privacy label answers ~208
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.
| Name | Type | Req | Description |
|---|---|---|---|
| deletionRequest | boolean | – | – |
| encryptedInTransit | boolean | – | – |
| ownData | array | – | – |
| platforms | array | yes | – |
| sdks | array | yes | – |
| settings | object | – | – |
No output schema declared.
No examples provided.
list_resource_types List resource types ~32
The resourceType values create_privacy_policy_url accepts, and which of them are hosted free. No side effects.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the Privacy Policy URL MCP server?
Privacy Policy URL is a hosted endpoint at https://www.privacypolicyurl.com/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · www.privacypolicyurl.com
claude mcp add --transport http com-privacypolicyurl-privacy-policy-url 'https://www.privacypolicyurl.com/api/mcp'
What is the Privacy Policy URL MCP server?
Privacy Policy URL is an MCP server listed in the public MCP registry as com.privacypolicyurl/privacy-policy-url. Hosted privacy policy URLs for apps, sites, stores and lead forms, created by an agent in one call. This page covers its hosted endpoint (https://www.privacypolicyurl.com/api/mcp).
Is the Privacy Policy URL MCP server safe to use?
Privacy Policy URL scores 72 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Privacy Policy URL MCP server expose?
Privacy Policy URL exposes 6 tools: create_privacy_policy_url, check_privacy_policy_url, generate_store_privacy_labels, check_a2p_10dlc_documents, generate_privacy_manifest, list_resource_types. Their descriptions and schemas cost roughly 1,015 tokens of context every time the server is loaded.
Does the Privacy Policy URL MCP server require authentication?
No. We connected to Privacy Policy URL without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Privacy Policy URL MCP server still maintained?
Privacy Policy URL is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.