BulkSMS MCP by usefulapi
io-usefulapi-bulksms declares 8 capabilities across 8 tools, with 2 critical issues.
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.
2 tools are classified as irreversible and declare no limit.
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.
6 tools can read data and declare no limit.
Declared capabilities
| Tool | Read as | Basis |
|---|---|---|
bulksms_get_profile | read |
declared |
bulksms_list_messages | read |
declared |
bulksms_get_message | read |
declared |
bulksms_list_replies | read |
declared |
bulksms_list_blocked_numbers | read |
declared |
bulksms_list_webhooks | read |
declared |
bulksms_send_message | destructive |
declared |
bulksms_block_number | destructive |
declared |
tools/list response and it will be re-scored and dated.
Corrections are published alongside the original, not in place of it.