Security & Testing
regsentry.com
An MCP server that inspects public websites for tracker markup and consent-compliance signals, grades consent evidence, and returns tracker-specific remediation playbooks.
ENDPOINT 1
https://regsentry.com/mcp
MCP server metadata
- Name
- regsentry
- Version
- 1.0.0
Use RegSentry only for authorized technical website-tracking inspection. Never describe its output as legal advice, a compliance certification, or proof of liability. Static site inspection must be followed by runtime verification before claiming tracker timing.
Known tools 3
inspect_site_trackingPerforms a bounded, non-persisting GET of an authorized public domain's homepage and reports tracker markup, consent setup signals, and runtime-verification gaps.
Inferred read-onlyinterpret_consent_evidenceDeterministically grades a redacted set of tracker-request observations by consent phase.
Inferred read-onlyget_remediation_playbookReturns deterministic, tracker-specific consent-gating guidance from RegSentry's maintained playbooks.
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.regsentry]
url = "https://regsentry.com/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"regsentry": {
"type": "http",
"url": "https://regsentry.com/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: regsentry
Remote MCP URL: https://regsentry.com/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": {
"regsentry": {
"url": "https://regsentry.com/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"regsentry": {
"type": "http",
"url": "https://regsentry.com/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "regsentry",
"transport": "streamable-http",
"url": "https://regsentry.com/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.