RegSentry Website Tracking Inspector

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.