Security & Testing
deid.pro
Provides DeID.pro de-identification capabilities, output formats, documentation, and privacy architecture details, emphasizing local processing boundaries and data never sent to a server.
ENDPOINT 1
https://deid.pro/mcp
MCP server metadata
- Name
- deid-pro-metadata
- Version
- 0.6.30
Known tools 2
get_deid_capabilitiesReturns DeID.pro formats, outputs, documentation, and local-processing boundaries.
Inferred read-onlyget_privacy_architectureExplains where DeID.pro processing occurs and which data is never sent to a server.
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.deid-pro-metadata]
url = "https://deid.pro/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"deid-pro-metadata": {
"type": "http",
"url": "https://deid.pro/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: deid-pro-metadata
Remote MCP URL: https://deid.pro/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"deid-pro-metadata": {
"url": "https://deid.pro/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"deid-pro-metadata": {
"type": "http",
"url": "https://deid.pro/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "deid-pro-metadata",
"transport": "streamable-http",
"url": "https://deid.pro/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.