RegSentry Website Tracking Inspector MCP Server

by regsentry Your server? Claim it

answering

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

Inspect a public site's tracking signals, grade consent evidence, and get remediation playbooks.

Uptime history 31 hours of history

31 hours agonow

100.0%

Uptime 24h

91 of 91 checks

Tools

read from the server

327 ms

Response time

average over 24h

open, no key

Access

streamable-http

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 9 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

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "tracking-inspector": {
      "url": "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

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

Available tools 3

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

inspect

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

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	262 ms	9 min ago

Alternatives to RegSentry Website Tracking Inspector

same job, measured the same way

Woo Revenue Incident Graph

by tytutueh13-sudo

Check WooCommerce checkout-change risk using public evidence and privacy-safe store signals.

4 tools answering

Devops Status MCP Server

by cyanheads

Vendor status pages, TLS cert inspection, DNS propagation checks, and incident-response playbooks.

245 installs/wk 7 tools answering

FluxProof

by equinoxaifinance-rgb

Evidence-bearing public webpage monitoring with hashes, diffs, signed webhooks, REST, and MCP.

5 tools answering

Website Change Monitor

by blyck

Monitor public pages and JSON endpoints after agents disconnect, with polling and webhooks.

answering

Changeflow

by stevebutterworth

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

26 installs/wk local only

AI Incident Law

by snapsynapse

Public-record corpus of AI litigation, regulation, and enforcement, anchored to EveryAILaw.

77 installs/wk local only

Perceptdot Sentry

by perceptdot

AI agent vision for Sentry error tracking — with ROI measurement. perceptdot.com

29 installs/wk local only

COS Monitor

by internexio

Scores website pages for communication quality, tracks regressions, surfaces a fix queue.

13 tools answering

RegSentry Website Tracking Inspector — questions

Answers built from our own checks of this server.

What can RegSentry Website Tracking Inspector do?

It exposes 3 tools, read directly from the server on our last check. Among them: get_remediation_playbook, 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 327 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 with the file path 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 3 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 327 ms on average, which is faster than 50% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.