RegSentry Website Tracking Inspector MCP server
com.regsentry/tracking-inspectorregsentry.comstreamable-httpv2.0.0Scanned
Inspect authorized website tracking, compare consent observations, and get remediation guidance.
6 tools: 2 change things and 4 only read.
- Reads private data · 0
- Reads text others write · 2
- Can send data out · 0
- 1 finding
Tools listed without sign-in. Remote posture
With Anlyon
2 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the RegSentry Website Tracking Inspector MCP server can do
The RegSentry Website Tracking Inspector MCP server is published by regsentry.com, a domain the MCP Registry verified. It has 6 tools. It can create or change data (2 tools: interpret_consent_evidence and export_consent_report), but cannot delete data. 4 tools only read.
2 tools bring in text other people can write (inspect_site_tracking and inspect_runtime_consent).
The fixed checks matched 1 finding (credentials-mention). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.
Last scanned Nov 11, 2026, version 2.0.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
6 tools
Changes things 2Claude Code: ask
export_consent_reportFormats a supplied RegSentry runtime snapshot as a private plain-text report with its date, method, phase results and limitations.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
- idempotentHint: true
- title: Export a technical consent report
interpret_consent_evidenceDeterministically grades a redacted set of tracker-request observations by consent phase.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
- idempotentHint: true
- title: Interpret consent evidence
Only reads 4Show 4 read-only tools
compare_consent_observationsCompares two supplied RegSentry runtime snapshots of the same domain, phase by phase.No findings
Why it is in this group
- The name "compare_consent_observations" says "compare": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
- idempotentHint: true
- title: Compare consent observations
get_remediation_playbookReturns deterministic, tracker-specific consent-gating guidance from RegSentry's maintained playbooks.No findings
Why it is in this group
- The name "get_remediation_playbook" says "get": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
- idempotentHint: true
- title: Get tracker remediation playbook
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.Reads text others write1 finding
Why it is in this group
- The name "inspect_runtime_consent" says "inspect": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
- untrusted-inputThe description's first sentence says "browser": it reads web pages, which anyone can write.
Findings
- Info
The description mentions "credentials".
What this check looks forMatched text
description: "...ocks non-GET requests, supplies no user credentials, and reports missing controls and incom..."
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: true
- idempotentHint: true
- title: Observe runtime consent choices
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.Reads text others writeNo findings
Why it is in this group
- The name "inspect_site_tracking" says "inspect": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: true
- idempotentHint: true
- title: Inspect site tracking setup
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write2
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:45 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 2
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 2 tools that change things (2 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://regsentry.com/mcp: tools/list returned 6 tools to an anonymous client, including interpret_consent_evidence (write), export_consent_report (write)
Findings
Matches of fixed checks, with the text they matched.
The description mentions "credentials".
What this check looks forMatched text
description: "...ocks non-GET requests, supplies no user credentials, and reports missing controls and incom..."
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools6 changed.~6 changedView diff
- Changed:compare_consent_observationsOnly readsannotations
- Changed:export_consent_reportChanges thingsannotations
- Changed:get_remediation_playbookOnly readsannotations
- Changed:inspect_runtime_consentOnly readsdescriptionannotations
- Changed:inspect_site_trackingOnly readsannotations
- Changed:interpret_consent_evidenceChanges thingsannotations
Install
Pinned to version 2.0.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http tracking-inspector https://regsentry.com/mcpclaude mcp add --transport http tracking-inspector https://regsentry.com/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__tracking-inspector__inspect_site_tracking",
"mcp__tracking-inspector__get_remediation_playbook",
"mcp__tracking-inspector__inspect_runtime_consent",
"mcp__tracking-inspector__compare_consent_observations"
],
"ask": [
"mcp__tracking-inspector__interpret_consent_evidence",
"mcp__tracking-inspector__export_consent_report"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as tracking-inspector. Review it before you use it.
Capability tags behind 2 rules
- mcp__tracking-inspector__inspect_site_tracking untrusted-input
- mcp__tracking-inspector__inspect_runtime_consent untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/com.regsentry/tracking-inspector/verify?hash=100e47e2c228be284e3a7bf33dbae808c119ad91a11d842077170a39eb0fd540" | jq -e '.changed == false'Pinned hash 100e47e2c228, from Nov 11, 2026, 06:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.regsentry/tracking-inspector/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.regsentry/tracking-inspector)Source: MCP Registry. Synced Oct 29, 2026, 19:17 UTC.
RegSentry Website Tracking Inspector MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the RegSentry Website Tracking Inspector MCP server safe?
- No scan can promise that. What its definitions show: 6 tools, 2 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the RegSentry Website Tracking Inspector MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the RegSentry Website Tracking Inspector MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the RegSentry Website Tracking Inspector MCP server have?
- 6 tools: 2 write, 4 read. interpret_consent_evidence, export_consent_report, inspect_site_tracking, get_remediation_playbook, inspect_runtime_consent and compare_consent_observations.
Does the RegSentry Website Tracking Inspector MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the RegSentry Website Tracking Inspector MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the RegSentry Website Tracking Inspector MCP server changed its tools?
- Yes, once since Anlyon Radar started tracking it, most recently on Nov 11, 2026. Every change is on this page and in its Atom feed.