io.github.PetShopBros/lowdown-proxy
io-github-petshopbros-lowdown-proxy declares 4 capabilities across 4 tools, with 1 critical issue.
Issues
4 of 4 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.
4 of 4 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.
4 of 4 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.
1 tool can modify data and declares no limit.
3 tools can read data and declare no limit.
Declared capabilities
| Tool | Read as | Basis |
|---|---|---|
get_lowdown | read |
inferred |
record_interaction | write |
assumed |
compare_tools | read |
inferred |
get_node_stats | read |
inferred |
Record history
| Recorded | Exposure | Source |
|---|---|---|
| 2026-10-15 | 11 | tools/list answered by the npm package lowdown-proxy@0.1.17 (published to npm as lowdown-proxy, listed in the official MCP registry as io.github.PetShopBros/lowdown-proxy 0.1.17), run in an isolated container with no network access and no credentials |
| 2026-10-13 | 11 | tools/list answered by the npm package lowdown-proxy@0.1.16 (published to npm as lowdown-proxy, listed in the official MCP registry as io.github.PetShopBros/lowdown-proxy 0.1.16), run in an isolated container with no network access and no credentials |
tools/list response and it will be re-scored and dated.
Corrections are published alongside the original, not in place of it.