Dev Tools & GitMCP Registryremote6 toolsD · 33

RegSentry Website Tracking Inspector MCP server

com.regsentry · Updated 1mo ago

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

At a glance

RegSentry Website Tracking Inspector is an MCP server in the Dev Tools & Git category. It is hosted remotely and connects over HTTP, and declares no required credentials. It exposes 6 tools, including inspect_site_tracking, interpret_consent_evidence and get_remediation_playbook. It scores D (33/100) on the MCP Skills Hub health score as of Oct 28, 2026.

Source

One-click install

VS Code VS Code Insiders Cursor

Opens your editor and pre-fills the config. Your editor will ask before adding it.

How to install RegSentry Website Tracking Inspector in your AI client

Setup for Claude Code, Claude Desktop, Cursor, Codex, Windsurf, Cline and VS Code — copy-paste ready.

How to install RegSentry Website Tracking Inspector in Claude CodeAnthropic's agentic CLI

Add the server

bash

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

2
Verify it's connected
bash
```
claude mcp list
```
Sharing it with your team?
Add `--scope project` to write it to .mcp.json in the repository root, which you can commit (with the secrets left as environment variables).
Use it in a session
Ask Claude to use the tools this server exposes (e.g. inspect_site_tracking, interpret_consent_evidence, get_remediation_playbook). It discovers them automatically.

How to install RegSentry Website Tracking Inspector in Claude DesktopDesktop app (MCP config)

Open your MCP config
macOS: ~/Library/Application Support/Claude/claude_desktop_config.json · Windows: %APPDATA%\Claude\claude_desktop_config.json

Add this server

json

{
  "mcpServers": {
    "tracking-inspector": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://regsentry.com/mcp"
      ]
    }
  }
}

Why the wrapper?
This is a remote (HTTP) server and Claude Desktop only launches local processes, so mcp-remote proxies the connection. It will open a browser window if the server needs OAuth.
Restart Claude Desktop
The tools appear under the 🔌 menu once the app reloads.

How to install RegSentry Website Tracking Inspector in CursorAI-first code editor

Create / edit .cursor/mcp.json in your project

json

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

Enable it
Cursor Settings → MCP → toggle the server on. Tools become available to the Composer/Agent.

How to install RegSentry Website Tracking Inspector in Codex CLIOpenAI coding agent

Add to ~/.codex/config.toml

toml

[mcp_servers.tracking-inspector]
command = "npx"
args = ["-y", "mcp-remote", "https://regsentry.com/mcp"]

Why the wrapper?
Codex runs MCP servers as local processes, so mcp-remote bridges this HTTP endpoint to stdio.
Run Codex
Codex loads MCP servers from config.toml on startup and exposes their tools to the agent.

How to install RegSentry Website Tracking Inspector in WindsurfCodeium's agentic IDE

Edit ~/.codeium/windsurf/mcp_config.json

json

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

Reload
Windsurf → Cascade → refresh MCP servers. Cascade can now call the tools.

How to install RegSentry Website Tracking Inspector in ClineVS Code autonomous agent

Open Cline → MCP Servers → Configure
Adds to cline_mcp_settings.json.

Add the server

json

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

How to install RegSentry Website Tracking Inspector in VS CodeCopilot / MCP support

Create .vscode/mcp.json

json

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

Start it
VS Code shows a ▶ Start action above the server entry. Agent mode (Copilot Chat) can then use the tools.

What tools does RegSentry Website Tracking Inspector expose? (6)

Read from the live server. Click any tool for its input schema.

inspect_site_trackingPerforms 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_evidenceDeterministically 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_playbookReturns 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_consentVisits 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. Blocks non-GET requests, forms, credentials and persistence; reports missing controls and incomplete runs explicitly. Changes only temporary browser consent state. Bounded observations are not proof of transmission, comp
compare_consent_observationsCompares 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_reportFormats 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.

What the code can do

This is a remote server — nothing is installed or run on your machine, so there is no local code to analyze. What it can reach is described above: your requests go to the provider's host.

Before you install

Signals gathered from the source repo and package registry — not a safety verdict.

What it can reach

Third-party hosted service — Your requests and any data in them are sent to regsentry.com.
No local execution — Nothing is installed or run on your machine.

No source repository — This registry entry does not link to a public repo, so its code cannot be reviewed before you install it.

Client compatibility

Claude Code: NativeClaude Desktop: Via mcp-remoteCursor: NativeCodex CLI: Via mcp-remoteWindsurf: NativeCline: NativeVS Code: Native

Health score

D · 33

Maintenance, adoption, transparency and packaging — not a safety audit. How this is calculated

Maintenance30%not measurable
No commit history available.
Adoption20%not measurable
No usage data available.
Transparency20%25%
1/4: ✗ public source repo, ✗ declared license, ✗ documentation, ✓ discoverable tool list.
Provenance15%0%
No source repository to trace the code back to.
Packaging15%75%
Remote endpoint; authentication requirements not declared.

Alternatives to RegSentry Website Tracking Inspector

Maintain RegSentry Website Tracking Inspector? Add a badge to your README

Shows its health grade, and links readers to install steps for every client.

markdown

[![RegSentry Website Tracking Inspector on MCP Skills Hub](https://mcp-skills-hub.vercel.app/badge/com-regsentry-tracking-inspector)](https://mcp-skills-hub.vercel.app/mcps/com-regsentry-tracking-inspector)

Catalog data refreshed Oct 28, 2026. Something wrong? Report it.