Home / MCP registry index / io.usefulapi/voodoo-sms
Voodoo SMS MCP by usefulapi
io.usefulapi/voodoo-sms in the official MCP registry.
Endpoint https://voodoo-sms.usefulapi.io/mcp. Source: github.com/m190/usefulapi-mcp.
The registry describes it as: Read Voodoo SMS credits, reports, inbox and lists; send one SMS; manage the opt-out blacklist.
We read its 13 tools on 2026-10-21. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
voodoosms_get_credits voodoosms_list_delivery_reports voodoosms_list_scheduled_messages voodoosms_list_inbox voodoosms_list_numbers voodoosms_list_contact_lists voodoosms_get_contact_list voodoosms_list_blacklist voodoosms_send_sms voodoosms_cancel_scheduled_message voodoosms_add_to_blacklist voodoosms_create_contact_list voodoosms_update_contact_list
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/io-usefulapi-voodoo-sms)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.