com.tamperlens/mcp
com-tamperlens-mcp declares 5 capabilities across 5 tools, with 1 critical issue.
Issues
5 of 5 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.
5 of 5 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.
5 of 5 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.
3 tools can modify data and declare no limit.
2 tools can read data and declare no limit.
Declared capabilities
| Tool | Read as | Basis |
|---|---|---|
inspect_document | write |
assumed |
triage_document | write |
assumed |
check_redaction | read |
inferred |
compare_documents | read |
inferred |
inspect_case | write |
assumed |
Record history
| Recorded | Exposure | Source |
|---|---|---|
| 2026-10-13 | 20 | tools/list answered by the npm package tamperlens-mcp@1.42.0 (published to npm as tamperlens-mcp, listed in the official MCP registry as com.tamperlens/mcp 1.42.0), run in an isolated container with no network access and placeholder credentials |
| 2026-10-11 | 15 | tools/list answered by the npm package tamperlens-mcp@1.36.0 (published to npm as tamperlens-mcp, listed in the official MCP registry as com.tamperlens/mcp 1.36.0), run in an isolated container with no network access and placeholder credentials |
tools/list response and it will be re-scored and dated.
Corrections are published alongside the original, not in place of it.