DPOLens
REMOTE · MCP.DPOLENS.COM
Privacy law your AI assistant can cite: the exact clause and its version. GDPR and UAE PDPL today.
Available components
Last scanned (1 hour ago)
Scores higher than 76% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Health and Science
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 Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- 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 Usability77
- 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 878 tokens (~219/item across 4 items; 4 tools + 0 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 Management47
- Stability observed for 14 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (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 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +5
- HTTPS: unverified → pass ▲ security
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 +1
- Server version: 0.1.0 → 0.2.0 functional
- 29 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Server version: 0.1.0rc3 → 0.1.0 functional
- 28 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 24 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
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://mcp.dpolens.com/
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=dpolens.com | CN=WE1,O=Google Trust Services,C=US | 21 Oct 2026 | 19 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 417cae8610f35625133e92e08de2285c |
| SANs: dpolens.com, *.dpolens.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.dpolens.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| dpolens.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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.dpolens.com/ | Verified | 200 | |
| http (plaintext) | http://mcp.dpolens.com/ | HTTPS enforced | 301 | https://mcp.dpolens.com/ |
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 →
get_clause Read one clause ~155
Read one clause by its key, with where it sits and what sits beneath it. Use it when a search result points at another clause, or when you need the whole of an article rather than the part that matched. The call is recorded, with the key that was read rather than a question.
| Name | Type | Req | Description |
|---|---|---|---|
| as_of | – | – | Read the clause as it stood on this date |
| key | string | yes | A canonical key, such as gdpr:art-17:para-1 |
| lang | string | – | Which language to prefer, as a two letter code |
| whole_subtree | boolean | – | Also return this clause and everything beneath it in reading order, which is what you want for a whole article |
| Name | Type | Req | Description |
|---|---|---|---|
| children | array | yes | The clauses directly beneath this one |
| clause | – | yes | – |
| cross_references | array | yes | Keys this clause's own words point at |
| formerly | – | – | Set when this key named a different rule in the policy's version before |
| now | – | – | For a policy's clause read in a version that is no longer in force, where the same rule is in the version in force. A policy's keys follow its printed numbers, so the rule may have another key now |
| subtree | array | – | This clause and everything beneath it in reading order, when asked for |
No examples provided.
get_document Read one document's outline ~81
Read one document and its top level structure, without the text. The outline is where to find a clause key when you know roughly where to look. Read the words with get_clause. The call is recorded.
| Name | Type | Req | Description |
|---|---|---|---|
| as_of | – | – | Read the document as it stood on this date |
| slug | string | yes | The document's slug, such as gdpr |
| Name | Type | Req | Description |
|---|---|---|---|
| document | – | yes | – |
| outline | array | yes | – |
No examples provided.
list_documents List what can be cited ~62
List the laws this community version can cite, and which version of each is in force.
| Name | Type | Req | Description |
|---|---|---|---|
| as_of | – | – | List the documents in force on this date |
| limit | integer | – | How many to return |
| offset | integer | – | Skip this many first |
| Name | Type | Req | Description |
|---|---|---|---|
| documents | array | yes | – |
| total | integer | yes | How many documents are in force, ignoring limit and offset |
No examples provided.
search_policies Search the law ~219
Search the privacy law this community version holds. Call this before writing or changing code that collects, stores, logs, shares or deletes personal data, and before answering a question about what the law requires. What comes back is the clause itself, word for word, with the key, document and version to cite it by. Questions asked here are kept 30 days, with nothing about who asked.
| Name | Type | Req | Description |
|---|---|---|---|
| as_of | – | – | Read the documents as they stood on this date |
| include_explanatory | boolean | – | Include text that explains without obliging, such as a GDPR recital |
| lang | – | – | The language of the question, en or ar. Leave it out to have it read from the letters the question is written in |
| laws | – | – | Only these of the laws this organisation has selected, by slug, such as gdpr or uae-pdpl. Leave it out to search all of them |
| limit | integer | – | How many clauses to return |
| query | string | yes | The question, in words |
| Name | Type | Req | Description |
|---|---|---|---|
| results | array | yes | – |
| searched | string | yes | What was searched, and as of when |
No examples provided.
How do I install the DPOLens MCP server?
DPOLens is a hosted endpoint at https://mcp.dpolens.com/, 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 · mcp.dpolens.com
claude mcp add --transport http com-dpolens-dpolens 'https://mcp.dpolens.com/'
What is the DPOLens MCP server?
DPOLens is an MCP server listed in the public MCP registry as com.dpolens/dpolens. Privacy law your AI assistant can cite: the exact clause and its version. GDPR and UAE PDPL today. This page covers its hosted endpoint (https://mcp.dpolens.com/).
Is the DPOLens MCP server safe to use?
DPOLens scores 78 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 DPOLens MCP server expose?
DPOLens exposes 4 tools: search_policies, get_clause, list_documents, get_document. Their descriptions and schemas cost roughly 517 tokens of context every time the server is loaded.
Does the DPOLens MCP server require authentication?
No. We connected to DPOLens without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the DPOLens MCP server still maintained?
DPOLens 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.