Voidmail (hosted)
io-github-voidly-ai-voidmail declares 7 capabilities across 7 tools, with 2 critical issues.
Issues
7 of 7 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.
2 tools are classified as irreversible and declare no limit.
7 of 7 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.
7 of 7 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.
5 tools can read data and declare no limit.
Declared capabilities
| Tool | Read as | Basis |
|---|---|---|
start_here | read |
declared |
voidmail_setup | read |
declared |
voidmail_sending_limits | read |
declared |
voidmail_list_inbox | read |
declared |
voidmail_read_email | send |
inferred |
voidmail_send_once | send |
inferred |
voidmail_send_status | read |
declared |
Record history
| Recorded | Exposure | Source |
|---|---|---|
| 2026-10-11 | 31 | tools/list on https://api.voidly.ai/mcp/mail, published in the official MCP registry as io.github.voidly-ai/voidmail 0.1.0 |
tools/list response and it will be re-scored and dated.
Corrections are published alongside the original, not in place of it.