RegSentry Website Tracking Inspector MCP Server

by regsentry Your server? Claim it

answering

RegSentry Website Tracking Inspector is answering right now. Last checked 14 min ago. It exposes 6 tools.

Inspect authorized website tracking, compare consent observations, and get remediation guidance.

Uptime history 48 days of history · worst day 7%

48 days agonow

100.0%

Uptime 24h

91 of 91 checks

Tools

read from the server

353 ms

Response time

average over 24h

open, no key

Access

streamable-http

What changed 6

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 21 October 2026. No other catalogue keeps this.

29 Oct a tool description was rewritten inspect_runtime_consent

28 Oct a tool changed version

21 Oct 3 tools appeared compare_consent_observations, export_consent_report, inspect_runtime_consent

21 Oct a tool changed version

Nothing serious here today

Today is the operative word: we check RegSentry Website Tracking Inspector every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 14 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add tracking-inspector --transport http https://regsentry.com/mcp

Settings → Connectors → Add custom connector, then paste this address

https://regsentry.com/mcp

~/.codex/config.toml

[mcp_servers.tracking-inspector]
url = "https://regsentry.com/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "tracking-inspector": {
      "url": "https://regsentry.com/mcp"
    }
  }
}

.vscode/mcp.json

{
  "servers": {
    "tracking-inspector": {
      "type": "http",
      "url": "https://regsentry.com/mcp"
    }
  }
}

Available tools 6

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

inspect

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.

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.

compare

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

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.

interpret

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.

remediation

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.

Endpoints

URL	Transport	State	Latency	Checked
https://regsentry.com/mcp	streamable-http	answering	318 ms	14 min ago

Alternatives to RegSentry Website Tracking Inspector

same job, measured the same way

Agent Observability

by blueskylineassets

Agent observability: structured logging, cost tracking, and compliance audit trails

50 installs/wk local only

UK Source Intelligence

by pages-uk-source-intelligence

Inspect GOV.UK guidance, check quotations, and monitor recorded HMRC changes. Free agent trial.

12 tools answering

Changeflow

by stevebutterworth

AI-powered web monitoring. Track any website, get structured change intelligence.

45 installs/wk local only

Author iTag

by author-tag

GPS trackers, phones and QR tags: locations, trips, alerts and vehicle controls with user consent.

answering

mcp-trace-inspector

by abhishekash

Read local agent-run JSONL traces through MCP for failures, approvals, and run comparisons.

4 installs/wk local only

Nws Weather MCP Server

by cyanheads

Get US weather forecasts, active alerts, and current observations.

311 installs/wk 10 tools answering

ChangeDetection.io MCP Server

by rusty4444

MCP server for ChangeDetection.io website monitoring and change history.

141 installs/wk local only

SpanHound

by abhishekash

Capture local agent traces and inspect failures, approvals, and run comparisons.

161 installs/wk local only

RegSentry Website Tracking Inspector — questions

Answers built from our own checks of this server.

What can RegSentry Website Tracking Inspector do?

It exposes 6 tools, read directly from the server on our last check. Among them: compare_consent_observations, export_consent_report, get_remediation_playbook, inspect_runtime_consent, inspect_site_tracking, interpret_consent_evidence. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is RegSentry Website Tracking Inspector working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 353 ms. The bar chart above shows every period we have measured.

How do I connect RegSentry Website Tracking Inspector?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does RegSentry Website Tracking Inspector need an API key?

No. RegSentry Website Tracking Inspector completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 6 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is RegSentry Website Tracking Inspector?

It answers our handshake in 353 ms on average, which is faster than 39% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.