RegSentry Website Tracking Inspector
com-regsentry-tracking-inspector declares 6 capabilities across 6 tools, with 1 critical issue.
Issues
6 of 6 tools declare no way for the customer to switch them off once granted. This applies to every tool because MCP has no field in which to declare a revocation mechanism; the product may provide one outside MCP that a manifest cannot show.
6 of 6 tools declare no expiry. This applies to every tool because MCP has no field in which to declare an expiry; the product may provide one outside MCP that a manifest cannot show.
6 of 6 tools declare no record of their actions that the customer can read. This applies to every tool because MCP has no field in which to declare an audit requirement; the product may provide one outside MCP that a manifest cannot show.
6 tools can read data and declare no limit.
Declared capabilities
| Tool | Read as | Basis |
|---|---|---|
inspect_site_tracking | read |
declared |
interpret_consent_evidence | read |
declared |
get_remediation_playbook | read |
declared |
inspect_runtime_consent | read |
declared |
compare_consent_observations | read |
declared |
export_consent_report | read |
declared |
Record history
| Recorded | Exposure | Source |
|---|---|---|
| 2026-10-11 | 5 | tools/list on https://regsentry.com/mcp, published in the official MCP registry as com.regsentry/tracking-inspector 1.0.0 |
tools/list response and it will be re-scored and dated.
Corrections are published alongside the original, not in place of it.