Pulse Verity
io-github-pulsebet-pulse-verity 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 |
|---|---|---|
get_index_price | read |
declared |
get_index_batch | read |
declared |
list_index_assets | read |
declared |
get_recorded_print | read |
declared |
verify_print | read |
declared |
get_account_status | read |
declared |
get_index_history | read |
declared |
get_upgrade_options | read |
declared |
submit_verity_feedback | write |
inferred |
Record history
| Recorded | Exposure | Source |
|---|---|---|
| 2026-10-13 | 14 | tools/list answered by the npm package pulse-verity@1.3.1 (published to npm as pulse-verity, listed in the official MCP registry as io.github.PulseBet/pulse-verity 1.3.1), 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.