# RegSentry Website Tracking Inspector [Verified owner] [Health: Active]

**Category:** ⚖️ Legal  
**Repository:** https://regsentry.com/mcp-guide  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/regsentry-website-tracking-inspector

## Description
Inspect authorized static tracking signals and review supplied consent evidence.

## Tools
Capabilities this server exposes over MCP:

- **inspect_site_tracking** — Performs a bounded, non-persisting GET of an authorized public domain's homepage and reports tracker markup, consent setup signals, and runtime-verification gaps. It does not run JavaScript, submit forms, create a RegSentry record, or make a legal determination.
- **interpret_consent_evidence** — Deterministically grades a redacted set of tracker-request observations by consent phase. It computes from the supplied data only, stores nothing, and returns a technical—not legal—interpretation.
- **get_remediation_playbook** — Returns deterministic, tracker-specific consent-gating guidance from RegSentry's maintained playbooks. It does not change a website, contact a vendor, or verify that a fix was implemented.
- **inspect_runtime_consent** — Visits an authorized public homepage in three isolated browser sessions and records known tracker request attempts before consent and after exact reject-all or accept-all buttons. Uses temporary browser sessions, blocks non-GET requests, supplies no user credentials, and reports missing controls and incomplete runs. Page scripts and consent controls may make public GET requests, which can have remote effects. Bounded observations are not proof of transmission, compliance or a violation.
- **compare_consent_observations** — Compares two supplied RegSentry runtime snapshots of the same domain, phase by phase. Marks missing controls and incomplete observations unresolved. Reports newly observed or no-longer-observed tracker attempts without claiming causation, compliance or a verified fix. Stores nothing and makes no network requests.
- **export_consent_report** — Formats a supplied RegSentry runtime snapshot as a private plain-text report with its date, method, phase results and limitations. Returns file content without publishing, sharing, or storing it. Does not turn supplied evidence into a compliance certificate or legal opinion.

## Claude Desktop Quick Installation
No generated config for this server: it installs through its own setup steps.

The project's own setup steps (from https://regsentry.com/mcp-guide), copied verbatim. Run them in order; they are not an mcpServers config.

1. Add to Claude Code:

```sh
claude mcp add --transport http regsentry https://regsentry.com/mcp --header "Authorization: Bearer $REGSENTRY_API_KEY"
```

## Documentation

## What RegSentry Website Tracking Inspector does

RegSentry Website Tracking Inspector provides MCP tools for reviewing website tracking and consent behavior. It works with authorized public homepages, supplied tracker-request observations, and supplied RegSentry runtime snapshots. The results focus on technical evidence: tracker markup, consent setup signals, request attempts by consent phase, missing controls, incomplete observations, and runtime-verification gaps.

The server keeps its analysis bounded. Static inspection uses a non-persisting GET of a homepage. Runtime inspection uses isolated temporary browser sessions and records known tracker request attempts before consent and after exact reject-all or accept-all actions. Supplied evidence and snapshots are processed without storage.

## How it works

Use `inspect_site_tracking` for a static homepage review. It reports tracker markup and consent-related signals without running JavaScript or submitting forms. Use `inspect_runtime_consent` when browser behavior matters; it visits the authorized homepage in three isolated sessions and checks request attempts across pre-consent, reject-all, and accept-all phases.

For evidence already collected, `interpret_consent_evidence` deterministically grades redacted tracker-request observations by consent phase. `compare_consent_observations` compares two runtime snapshots for the same domain, identifying newly observed or no-longer-observed tracker attempts while leaving missing controls and incomplete observations unresolved.

## Tools and capabilities

- **Inspect static tracking:** Review homepage markup, consent setup signals, and runtime-verification gaps with `inspect_site_tracking`.
- **Inspect runtime consent:** Record known tracker request attempts around reject-all and accept-all controls with temporary browser sessions.
- **Interpret evidence:** Grade supplied, redacted observations by consent phase without making network requests.
- **Compare snapshots:** Identify differences between two supplied runtime observations without attributing causation or confirming a fix.
- **Get remediation guidance:** Retrieve deterministic tracker-specific consent-gating guidance from maintained RegSentry playbooks.
- **Export a report:** Format a supplied runtime snapshot as private plain-text content containing dates, methods, phase results, and limitations.

## Limitations and notes

Observations are bounded and are not proof of transmission, compliance, or a violation. Static inspection does not execute JavaScript, submit forms, or create a RegSentry record. Runtime inspection blocks non-GET requests and supplies no user credentials, but page scripts and consent controls may still make public GET requests with remote effects.

The remediation tool only returns guidance; it does not modify a website, contact a vendor, or verify that a change was implemented. Snapshot comparison does not make network requests and does not claim that observed differences were caused by a particular change. Exported reports are not published, shared, or stored by the tool, and they are not compliance certificates or legal opinions.

_Full upstream README: https://allmcps.com/mcp/regsentry-website-tracking-inspector/readme_