HeatPulse
cc-heatpulse-heatpulse declares 8 capabilities across 8 tools, with 1 critical issue.
Issues
8 of 8 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.
8 of 8 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.
8 of 8 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.
2 tools can modify data and declare no limit.
6 tools can read data and declare no limit.
Declared capabilities
| Tool | Read as | Basis |
|---|---|---|
search_news | read |
inferred |
get_event | read |
inferred |
related_stories | write |
assumed |
daily_digest | write |
assumed |
list_topics | read |
inferred |
llm_leaderboard | read |
inferred |
route_intent | read |
inferred |
list_datasets | read |
inferred |
Record history
| Recorded | Exposure | Source |
|---|---|---|
| 2026-10-11 | 21 | tools/list on https://heatpulse.cc/mcp, published in the official MCP registry as cc.heatpulse/heatpulse 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.