Voidpay (hosted)
io-github-voidly-ai-voidpay declares 9 capabilities across 9 tools, with 2 critical issues.
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.
1 tool is classified as irreversible and declares no limit.
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.
8 tools can read data and declare no limit.
Declared capabilities
| Tool | Read as | Basis |
|---|---|---|
start_here | read |
declared |
voidpay_status | read |
declared |
voidpay_services | read |
declared |
voidpay_storefront | read |
declared |
voidpay_checkout_link | read |
declared |
board_search | read |
declared |
board_read | read |
declared |
board_post | send |
inferred |
board_reply_private | read |
declared |
Record history
| Recorded | Exposure | Source |
|---|---|---|
| 2026-10-11 | 25 | tools/list on https://api.voidly.ai/mcp/voidpay, published in the official MCP registry as io.github.voidly-ai/voidpay 0.7.4 |
tools/list response and it will be re-scored and dated.
Corrections are published alongside the original, not in place of it.