Cursor Data Compliance Classifier MCP validate_data_safety_lite
How to: Cursor Data Compliance Classifier MCP validate_data_safety_lite
Add Data Compliance Classifier MCP to Cursor
-
01
Open ~/.cursor/mcp.json and merge this in. Keep any servers already there.
{
"mcpServers": {
"data-compliance-mcp": {
"url": "https://data-compliance-mcp-production.up.railway.app"
}
}
}-
02
Save the file and restart Cursor.
-
03
Ask for something validate_data_safety_lite does. Cursor lists the server's tools on connect and calls validate_data_safety_lite itself — you do not invoke it by name.
-
04
If nothing happens, check the server is running and that Data Compliance Classifier MCP's identifier in your config matches the one above exactly.
Use .cursor/mcp.json in a project root instead to scope it to that project. Cursor merges both. Cursor docs
Set these first
Data Compliance Classifier MCP will not start until these are set, so validate_data_safety_lite never becomes available.
-
ANTHROPIC_API_KEY -
ABUSEIPDB_API_KEY
Same tool, other clients
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.