RegSentry

npx add-mcp 'https://regsentry.com/mcp'

Website tracking answers inside your AI workspace.

Connect RegSentry to OpenAI or Claude to inspect an authorized public homepage, interpret redacted consent evidence, and get tracker-specific remediation guidance.

https://regsentry.com/mcp Public · read only

Protocol: Streamable HTTP · Authentication: none · The inspection tool requires an explicit ownership or authorization attestation.

Inspect site tracking

Reads one public homepage with a bounded GET and reports static tracker and consent signals. It does not run JavaScript or persist a scan.

Interpret consent evidence

Grades caller-supplied, redacted request observations by consent phase without making a network request or storing the evidence.

Get a remediation playbook

Returns deterministic consent-gating guidance for a named tracker from RegSentry's maintained playbooks.

Connect from OpenAI

1. Open the app or connector management area available to your OpenAI workspace.
2. Add a remote MCP server and enter https://regsentry.com/mcp.
3. Review the three read-only tools, then enable the connection for your workspace or test conversation.
4. Try: “Inspect the tracking setup on my authorized domain example.com.”

OpenAI plan, role, and review requirements can affect which connector controls are visible.

Connect from Claude

1. Open the custom connector settings available to your Claude workspace.
2. Add a remote connector using https://regsentry.com/mcp.
3. Confirm the tool list and use the connector in a new conversation.
4. Try: “Give me RegSentry's remediation playbook for Microsoft Clarity.”

Tool boundary

Behavior	What RegSentry MCP does
External access	Only the authorized inspection tool fetches the caller's public domain over HTTPS.
Customer data	No account, subscription, database, evidence-file, or internal RegSentry record access.
State changes	No form submissions, emails, website mutations, scans saved to RegSentry, or background jobs.
Legal meaning	Technical observations and remediation guidance only—not legal advice, compliance certification, or proof of liability.

Example prompts

Inspect the tracking and consent setup on my authorized domain example.com.

I observed Hotjar before consent and FullStory after rejection. Grade this evidence.

Which detected trackers still require browser verification?