dpdp-compliance MCP server
io.openproof/dpdp-complianceopenproof.iostreamable-httpv1.1.0Scanned
India DPDP Act facts, current pricing and a public-site compliance scan. No login needed.
5 tools: 5 change things.
- Reads private data · 0
- Reads text others write · 1
- Can send data out · 1
- 1 finding
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.
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 dpdp-compliance MCP server can do
The dpdp-compliance MCP server is published by openproof.io, a domain the MCP Registry verified. It has 5 tools. It can create or change data (5 tools: dpdp_key_dates, dpdp_obligations, dpdp_penalty_ceilings, openproof_pricing and 1 more), but cannot delete data. None of its tools only reads.
1 tool brings in text other people can write (scan_site); 1 tool can send data out of your system (scan_site).
The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 18, 2026, version 1.1.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.
5 tools
Changes things 5Claude Code: ask
dpdp_key_datesKey dates under the India DPDP Rules, 2025: when the Rules were notified and when each group of obligations begins (Consent Managers, Data Fiduciary duties, penalties).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 Key dates under the India DPDP Rules, 2025: when the Rules were notified and when each group of obligations begins (Consent Managers, Data Fiduciary duties, penalties). Includes the confidence and review status of each.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: false
dpdp_obligationsLook up DPDP Act sections and Rules by topic (for example: breach, consent, grievance, children, processor contract, erasure, security safeguards, transfers).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 Look up DPDP Act sections and Rules by topic (for example: breach, consent, grievance, children, processor contract, erasure, security safeguards, transfers). Returns matching summaries with confidence and review status.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: false
dpdp_penalty_ceilingsThe maximum penalties in the Schedule to the DPDP Act and the factors the Data Protection Board considers.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 The maximum penalties in the Schedule to the DPDP Act and the factors the Data Protection Board considers. These are ceilings, not an estimate of what any business would pay.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: false
openproof_pricingOpenProof's current public plans: the three annual tiers with price in INR before taxes, what each includes and its limits, and the free trial length.1 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.
Findings
- Warn
The server marks "openproof_pricing" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"openWorldHint":false}; The description's first verb is "open": a word for a change.
Description, as the server wrote it OpenProof's current public plans: the three annual tiers with price in INR before taxes, what each includes and its limits, and the free trial length. Read live from the same source as the pricing page.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: false
scan_siteRun OpenProof's website scan on one public web address and return the DPDP-related signals found: consent banner and cookies before consent, third-party trackers, privacy-policy pr…Reads text others writeCan send data outNo findings
Why it is in this group
- The description's first verb is "run": 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.
- 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 Run OpenProof's website scan on one public web address and return the DPDP-related signals found: consent banner and cookies before consent, third-party trackers, privacy-policy presence and content signals, signup-form consent checkbox, sensitive-field collection and TLS. It reads only the public page, honours site-owner opt-outs, and is an automated surface check, not an audit or legal advice. Limited to a few scans per hour per client. Send it as its own request, not inside a batch.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
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.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write1
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out1
- 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.
Looked at Nov 20, 2026, 19:13 UTC, unchanged since Oct 22, 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.
What this check looks forMatched text
https://api.openproof.io/mcp: tools/list returned 5 tools to an anonymous client, including dpdp_key_dates (write), dpdp_obligations (write), dpdp_penalty_ceilings (write), openproof_pricing (write), scan_site (write)
Findings
Matches of fixed checks, with the text they matched.
The server marks "openproof_pricing" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"openWorldHint":false}; The description's first verb is "open": a word for a change.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.1.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http dpdp-compliance https://api.openproof.io/mcpclaude mcp add --transport http dpdp-compliance https://api.openproof.io/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": [],
"ask": [
"mcp__dpdp-compliance__dpdp_key_dates",
"mcp__dpdp-compliance__dpdp_obligations",
"mcp__dpdp-compliance__dpdp_penalty_ceilings",
"mcp__dpdp-compliance__openproof_pricing",
"mcp__dpdp-compliance__scan_site"
],
"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 dpdp-compliance. Review it before you use it.
Capability tags behind 1 rule
- mcp__dpdp-compliance__scan_site untrusted-input, outbound
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.openproof/dpdp-compliance/verify?hash=1b3725efb6e98948d3a5fc048c8611ca1e6ede8cb6e40e545fff5f0622d09253" | jq -e '.changed == false'Pinned hash 1b3725efb6e9, from Nov 18, 2026, 13:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.openproof/dpdp-compliance/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.openproof/dpdp-compliance)Source: MCP Registry. Synced Oct 21, 2026, 18:52 UTC.
dpdp-compliance MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the dpdp-compliance MCP server safe?
- No scan can promise that. What its definitions show: 5 tools, 5 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the dpdp-compliance MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the dpdp-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 dpdp-compliance MCP server have?
- 5 tools: 5 write. dpdp_key_dates, dpdp_obligations, dpdp_penalty_ceilings, openproof_pricing and scan_site.
Does the dpdp-compliance MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the dpdp-compliance MCP server send data to outside services?
- 1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): scan_site.
Has the dpdp-compliance MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 18, 2026.