SMS Everyone MCP by usefulapi
REMOTE · SMS-EVERYONE.USEFULAPI.IO
Send confirmed SMS, check credits, delivery and replies, and manage opt-outs with SMS Everyone.
Available components
Last scanned (1 hour ago)
Scores higher than 4% of remote servers
Reachable. Last reached 5 Nov 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 Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- 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
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 Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
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.
- 1 Nov 26 −48
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: 0.07 → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Authorization: pass → unverified ▼ security
- Schema quality: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 31 Oct 26 +4
- Authorization: partial → pass ▲ security
- MCP protocol: fail → pass ▲ functional
- New prompt “check_credits_before_sending” functional
- New prompt “follow_campaign_progress_and_delivery” functional
- New prompt “record_customer_opt_outs” functional
- New prompt “review_recent_customer_replies” functional
- New prompt “send_a_confirmed_reminder_or_alert” functional
- MCP protocol version: 2025-06-18 → 2025-11-25 functional
- Server version: 1.2.0 → 1.4.0 functional
- Server version: 1.1.0 → 1.2.0 functional
- Server version: 1.0.2 → 1.1.0 functional
- 30 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- Server version: 1.0.1 → 1.0.2 functional
- Server version: 1.0.0 → 1.0.1 functional
- 29 Oct 26 62
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 5 Nov 2026 · Probed https://sms-everyone.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 sms-everyone.usefulapi.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 38690 | 8 | Verified |
| usefulapi.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|---|
| HTTP status | 302 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://sms-everyone.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/sms-everyone/ |
| http (plaintext) | http://sms-everyone.usefulapi.io/mcp | Inconclusive | 302 | http://sms-everyone.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 →
smseveryone_add_optouts Opt numbers out ~115
WRITE: adds 1 to 25 phone numbers to the account's optout database, so no later campaign is sent to them. This server cannot opt a number back in. Do it only when the user asks. SMS Everyone REST: POST /api/optouts with Action add.
| Name | Type | Req | Description |
|---|---|---|---|
| confirm | boolean | yes | Must be true only after the user confirms this exact write and its affected recipients/campaign. |
| numbers | array | yes | Numbers in international format, e.g. 61400123456. |
No output schema declared.
No examples provided.
smseveryone_cancel_campaign Cancel a scheduled campaign ~107
WRITE: deletes a scheduled SMS campaign so it is not sent. Only works before the campaign start time (afterwards SMS Everyone refuses it with an error code). It cannot be undone. SMS Everyone REST: POST /api/campaign with Action delete.
| Name | Type | Req | Description |
|---|---|---|---|
| campaign_id | integer | yes | The CampaignId SMS Everyone returned when the message was sent or scheduled. |
| confirm | boolean | yes | Must be true only after the user confirms this exact write and its affected recipients/campaign. |
No output schema declared.
No examples provided.
smseveryone_get_account Get account settings and credits ~55
Show the SMS Everyone account: user id, remaining SMS credits, whether unicode (emoji, non-English text) is enabled and whether international messaging is allowed. SMS Everyone REST: POST /api/RetrieveUserSettings.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
smseveryone_get_campaign_status Get campaign status ~64
Show whether a sent or scheduled campaign is Scheduled, Running, Paused or Deleted. SMS Everyone REST: POST /api/campaign with Action status.
| Name | Type | Req | Description |
|---|---|---|---|
| campaign_id | integer | yes | The CampaignId SMS Everyone returned when the message was sent or scheduled. |
No output schema declared.
No examples provided.
smseveryone_get_contact_list Get the numbers in a contact list ~115
Show the mobile numbers stored in one list. The API returns the whole list; this tool shows the first `limit` numbers and the total count. SMS Everyone REST: POST /api/crm with Action details.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Show at most this many numbers, default 200. |
| list_id | integer | yes | The CrmId from list_contact_lists. |
| offset | integer | – | Skip this many entries (for paging: use next_offset of the previous result). Default 0. |
No output schema declared.
No examples provided.
smseveryone_get_delivery_status Get delivery status ~187
Delivery receipts of a campaign: one entry per destination with a timestamp, a DeliveryReceiptStatusId and a carrier code. Pass destination to see one number only. An empty list means no receipt has arrived yet (carriers can take up to 24 hours) or the campaign id is not on this account. SMS Everyone asks for no more than one request per minute in production. SMS Everyone REST: POST /api/DRStatus.
| Name | Type | Req | Description |
|---|---|---|---|
| campaign_id | integer | yes | The CampaignId SMS Everyone returned when the message was sent or scheduled. |
| destination | string | – | Optional single phone number in international format, e.g. 61400123456. |
| limit | integer | – | Show at most this many destinations, default 500. |
| offset | integer | – | Skip this many entries (for paging: use next_offset of the previous result). Default 0. |
No output schema declared.
No examples provided.
smseveryone_list_contact_lists List contact lists ~93
List the stored lists (CRM groups) of mobile numbers: list id (CrmId), description and number count. SMS Everyone REST: POST /api/crm with Action list.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Show at most this many lists, default 500. |
| offset | integer | – | Skip this many entries (for paging: use next_offset of the previous result). Default 0. |
No output schema declared.
No examples provided.
smseveryone_list_optouts List opted-out numbers ~115
List phone numbers in the account's optout database (messages to them are never sent): number, date added, reason. The API returns the whole list; this tool shows the first `limit` entries and the total. SMS Everyone REST: POST /api/optouts with Action list.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Show at most this many entries, default 200. |
| offset | integer | – | Skip this many entries (for paging: use next_offset of the previous result). Default 0. |
No output schema declared.
No examples provided.
smseveryone_list_replies List SMS replies ~273
List SMS replies received on the account: received time, the sender's number (Originator), the account number it was sent to (Recipient), the text and a reference id. Always asks for a time window (the last `days` days, 1 to 7, counted back to 12am yesterday for 1, or a date range of at most 30 days), which leaves the replies available for later calls. Default: days 1. Production polling is limited to once per minute per account through this MCP; five minutes is recommended. SMS Everyone REST: POST /api/replies.
| Name | Type | Req | Description |
|---|---|---|---|
| date_end | string | – | End date, YYYY-MM-DD (default: today). Needs date_start. |
| date_start | string | – | Start date, YYYY-MM-DD. |
| days | integer | – | The last N days, 1 to 7 (1 = back to 12am yesterday in the account's time zone). Default 1. Ignored when date_start is given. For longer periods use date_start/date_end (up to 30 days). |
| limit | integer | – | Show at most this many replies, default 100. |
| offset | integer | – | Skip this many entries (for paging: use next_offset of the previous result). Default 0. |
No output schema declared.
No examples provided.
smseveryone_pause_campaign Pause a campaign ~130
WRITE: pauses a scheduled campaign (or one that is sending; SMS Everyone sends over 1000 messages a second, so a running campaign usually finishes first). A campaign scheduled in the past cannot be paused. This server has no way to resume it: the user must do that in SMS Everyone. SMS Everyone REST: POST /api/campaign with Action pause.
| Name | Type | Req | Description |
|---|---|---|---|
| campaign_id | integer | yes | The CampaignId SMS Everyone returned when the message was sent or scheduled. |
| confirm | boolean | yes | Must be true only after the user confirms this exact write and its affected recipients/campaign. |
No output schema declared.
No examples provided.
smseveryone_send_sms Send SMS ~424
WRITE: SENDS REAL SMS to real people and SPENDS CREDITS from the user's SMS Everyone account; a sent message cannot be recalled (a campaign scheduled for later can be cancelled with cancel_campaign). One message text to 1 to 25 phone numbers in international format without "+" (e.g. 61400123456 for Australia, 6421123456 for New Zealand). Cost = credits per part x number of parts x recipients: a text is 160 characters per part (153 when longer), and one emoji or non-English character makes it unicode: 70 characters per part (67 when longer), more credits. Numbers on the account's optout list are skipped. The originator is where the message appears to come from and must be one registered with SMS Everyone for the account (an Australian alphanumeric sender must be ACMA registered). Optional time_scheduled (YYYYMMDDHHmm in the account's time zone; a time in the past sends at once). Only send what the user explicitly asked for; confirm the text, recipients and sender first. No stored lists, no bulk. SMS Everyone REST: POST /api/campaign with Action create.
| Name | Type | Req | Description |
|---|---|---|---|
| confirm | boolean | yes | Must be true only after the user confirms this exact write and its affected recipients/campaign. |
| destinations | array | yes | 1 to 25 recipient numbers in international format with country code, no leading 0, e.g. 61400123456. |
| message | string | yes | The message text (long texts are split into several parts and cost more). |
| originator | string | yes | Sender: the registered originator exactly as SMS Everyone gave it (a mobile number without +, a 4 to 6 digit short code, or a registered alphanumeric name; names are case sensitive). |
| time_scheduled | string | – | Optional send time YYYYMMDDHHmm in the account's time zone, e.g. 203507301300 = 30 July 2035, 1pm. Omit to send now. |
No output schema declared.
No examples provided.
How do I install the SMS Everyone MCP by usefulapi server?
SMS Everyone MCP by usefulapi is a hosted endpoint at https://sms-everyone.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 · sms-everyone.usefulapi.io
claude mcp add --transport http io-usefulapi-sms-everyone 'https://sms-everyone.usefulapi.io/mcp'
What is the SMS Everyone MCP by usefulapi server?
SMS Everyone MCP by usefulapi is listed in the public MCP registry as io.usefulapi/sms-everyone. Send confirmed SMS, check credits, delivery and replies, and manage opt-outs with SMS Everyone. This page covers its hosted endpoint (https://sms-everyone.usefulapi.io/mcp).
Is the SMS Everyone MCP by usefulapi server safe to use?
SMS Everyone MCP by usefulapi scores 18 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 SMS Everyone MCP by usefulapi server expose?
SMS Everyone MCP by usefulapi exposes 11 tools: smseveryone_get_account, smseveryone_get_campaign_status, smseveryone_get_delivery_status, smseveryone_list_replies, smseveryone_list_optouts, and 6 more. Their descriptions and schemas cost roughly 1,678 tokens of context every time the server is loaded.
Does the SMS Everyone MCP by usefulapi server require authentication?
Its publisher declares no required credentials for SMS Everyone MCP by usefulapi. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the SMS Everyone MCP by usefulapi server still maintained?
SMS Everyone MCP by usefulapi is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.