PeerPush
com-peerpush-peerpush declares 9 capabilities across 9 tools, with 1 critical issue.
Issues
9 of 9 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.
9 of 9 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.
9 of 9 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.
8 tools can read data and declare no limit.
Declared capabilities
| Tool | Read as | Basis |
|---|---|---|
peerpush_find_alternative | read |
declared |
peerpush_find_product | read |
declared |
peerpush_compare | read |
declared |
peerpush_product_details | read |
declared |
peerpush_trending | read |
declared |
peerpush_discover | read |
declared |
peerpush_deals | read |
declared |
peerpush_new_launches | read |
declared |
peerpush_create_product | write |
inferred |
Record history
| Recorded | Exposure | Source |
|---|---|---|
| 2026-10-11 | 19 | tools/list on https://peerpush.com/api/mcp, published in the official MCP registry as com.peerpush/peerpush 1.4.0 |
tools/list response and it will be re-scored and dated.
Corrections are published alongside the original, not in place of it.