Voodoo SMS MCP by usefulapi
REMOTE · VOODOO-SMS.USEFULAPI.IO
Read Voodoo SMS credits, reports, inbox and lists; send one SMS; manage the opt-out blacklist.
Available components
Last scanned (3 hours ago)
Scores higher than 47% of remote servers
Reachable. Last reached 17 Oct 2026.
Category Communication
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security78
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- HTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability0
- Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability80
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 2095 tokens (~161/item across 13 items; 13 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management17
- Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 14 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 16 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Oct 26 +3
- The server rewrote its instructions, which are the text every model session reads security
- The server now declares the “prompts” capability functional
- First check of Schema quality: 100 functional
- New prompt “getting_started” functional
- Server version: 1.0.0 → 1.1.0 functional
- 13 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 12 Oct 26 60
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 17 Oct 2026 · Probed https://voodoo-sms.usefulapi.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=usefulapi.io | CN=WE1,O=Google Trust Services,C=US | 13 Sept 2026 | 12 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | d9be3287b0fde9630e825ba1f79bff3f |
| SANs: usefulapi.io, *.usefulapi.io | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of voodoo-sms.usefulapi.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 57355 | 8 | Verified |
| usefulapi.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 302 |
WWW-Authenticate challenge Bearer realm="OAuth", resource_metadata="https://voodoo-sms.usefulapi.io/.well-known/oauth-protected-resource/mcp"
Bearer realm="OAuth", resource_metadata="https://voodoo-sms.usefulapi.io/.well-known/oauth-protected-resource/mcp"Protected resource metadata
| Document | https://voodoo-sms.usefulapi.io/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://voodoo-sms.usefulapi.io/mcp |
| Authorisation server | https://voodoo-sms.usefulapi.io |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://voodoo-sms.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/voodoo-sms/ |
| http (plaintext) | http://voodoo-sms.usefulapi.io/mcp | Inconclusive | 302 | http://voodoo-sms.usefulapi.io/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
voodoosms_add_to_blacklist Add a number to the blacklist ~106
WRITE: adds one number to the account's opt-out blacklist; from then on no SMS is sent to it (sends to it fail with error 20). Use it for a recipient who asked to stop. This tool cannot remove a number again. Voodoo SMS REST: POST /blacklist.
| Name | Type | Req | Description |
|---|---|---|---|
| number | string | yes | Phone number in international format with the country code and no leading 0, e.g. 447700900123. |
No output schema declared.
No examples provided.
voodoosms_cancel_scheduled_message Cancel a scheduled SMS ~91
WRITE: cancels one SMS that was scheduled through the send API, so it will not be sent. A message that has already gone out cannot be cancelled. Whether credits are refunded for a cancelled message is not documented by the vendor. Voodoo SMS REST: DELETE /schedule/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | yes | The scheduled message id (id from list_scheduled_messages). |
No output schema declared.
No examples provided.
voodoosms_create_contact_list Create a contact list ~120
WRITE: creates a new contact list with up to 500 contacts (the list name must be unique, at most 32 characters). It does not send anything. Voodoo SMS REST: POST /contacts.
| Name | Type | Req | Description |
|---|---|---|---|
| contacts | array | yes | Contacts to put in the list: [{number, dynamic_data?}]. |
| country | integer | – | Default country calling code for the list (default 44). |
| description | string | – | Optional description. |
| name | string | yes | Unique list name, at most 32 characters. |
No output schema declared.
No examples provided.
voodoosms_get_contact_list Get contacts in a list ~105
Get one contact list including its contacts (id, number, status, dynamic_data, created_at). Voodoo SMS REST: GET /contacts?contact_list_id=.
| Name | Type | Req | Description |
|---|---|---|---|
| contact_list_id | integer | yes | The contact list id (id from list_contact_lists). |
| limit | integer | – | Number of contacts to return (default 100, max 5000). |
| skip | integer | – | Where to start the returned results (default 0). |
No output schema declared.
No examples provided.
voodoosms_get_credits Get credit balance ~52
Get the SMS credit balance of the account. One credit pays for one 160-character SMS part (153 characters per part in a long message). Voodoo SMS REST: GET /credits.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
voodoosms_list_blacklist List blacklisted numbers ~179
List the numbers on the account's opt-out blacklist (no SMS is ever sent to them), or look up one number (`{empty: true}` means it is not on the list). Returns an empty result when the blacklist is empty. Voodoo SMS REST: GET /blacklist.
| Name | Type | Req | Description |
|---|---|---|---|
| end | string | – | Newest date a number was added. |
| limit | integer | – | Number of entries to return (default 25, max 1000). |
| number | string | – | Look up a single number (international format, e.g. 447700900123). |
| skip | integer | – | Where to start the returned results (default 0). |
| sort | string | – | Sort by id, ASC or DESC (default DESC). |
| start | string | – | Oldest date a number was added. |
No output schema declared.
No examples provided.
voodoosms_list_contact_lists List contact lists ~94
List the account's contact lists (id, name, status, size, created/updated times) without their contacts. Returns an empty result if there are none. Voodoo SMS REST: GET /contacts.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Number of lists to return (default 100, max 5000). |
| skip | integer | – | Where to start the returned results (default 0). |
No output schema declared.
No examples provided.
voodoosms_list_delivery_reports List delivery reports ~266
List delivery reports of sent messages (message_id, sender_id, to, sent_at, delivered_at, price, status), optionally filtered. Use it to check whether a message was delivered. Dates accept a UNIX timestamp, ISO 8601 (2026-10-01T09:00:00+00:00) or plain English ('yesterday', '2 weeks'). Voodoo SMS REST: GET /report.
| Name | Type | Req | Description |
|---|---|---|---|
| delivered_at | string | – | Only messages delivered at this date/time. |
| end | string | – | End of the date range to filter on. |
| external_reference | string | – | The external_reference used when sending. |
| limit | integer | – | Number of reports to return (default 25, max 1000). |
| message_id | string | – | The messages[].id returned when the SMS was sent. |
| sender_id | string | – | The sender id the messages were sent with. |
| sent_at | string | – | Only messages sent at this date/time. |
| start | string | – | Start of the date range to filter on. |
| status | string | – | Only messages with this status. |
| to | string | – | Only messages sent to this number (international format, e.g. 447700900123). |
No output schema declared.
No examples provided.
voodoosms_list_inbox List received SMS ~220
List SMS received on the account's Virtual Mobile Numbers (replies and keyword messages). Needs a purchased number; an empty inbox returns an empty result. Dates accept a UNIX timestamp, ISO 8601 or plain English. Voodoo SMS REST: GET /inbox.
| Name | Type | Req | Description |
|---|---|---|---|
| end | string | – | Newest date of the messages to return. |
| from | string | – | The number the message came from (international format). |
| keyword | string | – | The keyword (first word of the message). |
| limit | integer | – | Number of messages to return (default 25, max 1000). |
| reference | string | – | The external_reference of the original outgoing message. |
| skip | integer | – | Where to start the returned results (default 0). |
| sort | string | – | Sort by id, ASC or DESC (default DESC). |
| start | string | – | Oldest date of the messages to return. |
| to | string | – | The number the message was sent to: your virtual number (international format). |
No output schema declared.
No examples provided.
voodoosms_list_numbers List virtual mobile numbers ~50
List the Virtual Mobile Numbers (VMNs) the account has purchased, used to receive SMS. Returns an empty result if there are none. Voodoo SMS REST: GET /numbers.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
voodoosms_list_scheduled_messages List scheduled messages ~53
List SMS that were scheduled through the send API and are still waiting to go out (messages scheduled in the portal's Web SMS are not shown). Voodoo SMS REST: GET /schedule.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
voodoosms_send_sms Send an SMS to one recipient ~422
WRITE: SENDS A REAL SMS to ONE recipient and USES THE ACCOUNT'S CREDITS (1 credit per message part, charged whether or not it is delivered; it cannot be undone). `sandbox` is required: true validates and prices the message without sending or charging, false sends it for real. Optional `schedule` queues it for later (cancel with cancel_scheduled_message). Do not retry after an error or timeout without checking list_delivery_reports / list_scheduled_messages, or the recipient may get it twice. One recipient per call; there is no bulk or list send. Voodoo SMS REST: POST /sendsms.
| Name | Type | Req | Description |
|---|---|---|---|
| country_code | integer | – | Country calling code of the recipient (e.g. 44), when `to` has no country code. |
| external_reference | string | – | Your own reference for this SMS (e.g. an order number); shown in reports. |
| from | string | yes | Sender id shown to the recipient: 4 to 11 letters/digits or a number of up to 15 digits. |
| msg | string | yes | The message text. 160 characters per part (153 in a long message), 70 (67) if it has emoji or other non-GSM characters; maximum 918 (402 with Unicode). |
| sandbox | boolean | yes | REQUIRED. true = validate and price the message only: nothing is sent and no credits are used. false = really send the SMS and use credits. Use true first unless the user clearly asked to send now. |
| schedule | string | – | Send later: a UNIX timestamp, ISO 8601 (2026-12-25T09:00:00+00:00) or plain English ('2 weeks'). Must be in the future. |
| timezone | string | – | Timezone for `schedule` (default UTC). |
| to | string | yes | ONE recipient number: international format with the country code and no leading 0 (447700900123), or a national number if country_code is given. |
No output schema declared.
No examples provided.
voodoosms_update_contact_list Rename a contact list or add contacts ~120
WRITE: renames a contact list and/or adds up to 500 contacts to it (existing contacts are not removed). Adding dynamic data needs a list created as dynamic. It does not send anything. Voodoo SMS REST: PUT /contacts/{contact_list_id}.
| Name | Type | Req | Description |
|---|---|---|---|
| contact_list_id | integer | yes | The contact list id (id from list_contact_lists). |
| contacts | array | – | Contacts to add: [{number, dynamic_data?}]. |
| name | string | – | New list name, at most 32 characters. |
No output schema declared.
No examples provided.
How do I install the Voodoo SMS MCP by usefulapi server?
Voodoo SMS MCP by usefulapi is a hosted endpoint at https://voodoo-sms.usefulapi.io/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · voodoo-sms.usefulapi.io
claude mcp add --transport http io-usefulapi-voodoo-sms 'https://voodoo-sms.usefulapi.io/mcp'
What is the Voodoo SMS MCP by usefulapi server?
Voodoo SMS MCP by usefulapi is listed in the public MCP registry as io.usefulapi/voodoo-sms. Read Voodoo SMS credits, reports, inbox and lists; send one SMS; manage the opt-out blacklist. This page covers its hosted endpoint (https://voodoo-sms.usefulapi.io/mcp).
Is the Voodoo SMS MCP by usefulapi server safe to use?
Voodoo SMS MCP by usefulapi scores 64 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Voodoo SMS MCP by usefulapi server expose?
Voodoo SMS MCP by usefulapi exposes 13 tools: voodoosms_get_credits, voodoosms_list_delivery_reports, voodoosms_list_scheduled_messages, voodoosms_list_inbox, voodoosms_list_numbers, and 8 more. Their descriptions and schemas cost roughly 1,878 tokens of context every time the server is loaded.
Does the Voodoo SMS MCP by usefulapi server require authentication?
Yes. Voodoo SMS MCP by usefulapi asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the Voodoo SMS MCP by usefulapi server still maintained?
Voodoo SMS MCP by usefulapi is still listed as active in the MCP registry. We last reached this channel on 17 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.