Skip to content
RegSentry logo

RegSentry MCP server

Which servers in the official MCP registry are RegSentry's own, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-25

← Back to RegSentry

Whose server it is
  • Registry namecom.regsentry/tracking-inspectorverified in the MCP registry

The registry name sits under regsentry.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-25
  • Stateanswerschecked 2026-10-25
  • Tools6
  • Server calls itselfregsentry
  • Server version1.1.0
  • Protocol version2025-06-18

On 2026-10-25 the server answered initialize and tools/list without a sign-in. First answer in 54 ms.

Should an agent connect itNot proven either way yet
  • Its tools do every use case we checked: Scan websites for tracking pixels and session replay tools; See when trackers load before visitors consent.
  • Checked on 2 of the 7 days it takes to judge reliability.

Once connected

  • For "Scan websites for tracking pixels and session replay tools", the likely first call is inspect_site_tracking.
  • Parameters are untyped or undescribed in 5 of 6 tools: check arguments before calling.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

Measured dailydaily checks: 2, the first on 2026-10-25
  • INITE MCP scoreafter a weeka score needs 7 daily checks: 2 so far
  • What an agent can do with it2 of 2 use cases
  • Answeredmeasuring2 of the 7 daily checks it takes to print a share
  • Median first answer99 ms
  • Space in an agent's context≈ 2,155 tokensthe definitions of all its tools (6), which an agent carries on every turn
  • Tool definitionsB · 86 of 100
  • Typed results6 of 6 toolsdeclared outputSchema: results come typed, read once
  • Parameters without a description: in 5 of 6

What an agent can do with it

  • can do · Scan websites for tracking pixels and session replay tools
  • can do · See when trackers load before visitors consent
  • not sure · Verify fixes for detected trackers on their site

Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?

Worth a look

None of the five warning signs in these definitions.

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (30%), doing the product's job (25%), definitions (20%), context (10%) and use (15%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

Tools it offers6 tools · read 2026-10-25
  • 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…

  • 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. Blocks non-GET requests, forms, credentials and…

  • 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…

  • 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…

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

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

Add it

Claude Code, in a terminal

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

Add to CursorAdd to VS Code

claude.ai, ChatGPT and other clients: add https://regsentry.com/mcp as a custom connector in the settings.

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.