BulkSMS MCP by usefulapi
REMOTE · BULKSMS.USEFULAPI.IO
Read BulkSMS messages, replies, profile and webhooks; send SMS to up to 10 numbers.
Available components
Last scanned (5 hours ago)
Scores higher than 47% of remote servers
Reachable. Last reached 18 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 Usability81
- 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 1456 tokens (~182/item across 8 items; 8 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 Management20
- Stability observed for 6 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 9 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.
- 17 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Oct 26 +2
- 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 +1
- 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 18 Oct 2026 · Probed https://bulksms.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 bulksms.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://bulksms.usefulapi.io/.well-known/oauth-protected-resource/mcp"
Bearer realm="OAuth", resource_metadata="https://bulksms.usefulapi.io/.well-known/oauth-protected-resource/mcp"Protected resource metadata
| Document | https://bulksms.usefulapi.io/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://bulksms.usefulapi.io/mcp |
| Authorisation server | https://bulksms.usefulapi.io |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://bulksms.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/bulksms/ |
| http (plaintext) | http://bulksms.usefulapi.io/mcp | Inconclusive | 302 | http://bulksms.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 →
bulksms_block_number Block a phone number ~110
WRITE: adds ONE phone number to the account's blocked list, so that no further messages are sent to it (a send to a blocked number fails with FAILED.BLOCKED and still costs credits). This API has no way to remove a block again: do it only when the user asks for it. BulkSMS REST: POST /blocked-numbers.
| Name | Type | Req | Description |
|---|---|---|---|
| phone_number | string | yes | The number in international format, e.g. +447700900000 or 447700900000. |
No output schema declared.
No examples provided.
bulksms_get_message Get message ~63
Get one sent or received message by its id: body, recipient, delivery status, number of parts and credit cost. BulkSMS REST: GET /messages/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| message_id | string | yes | The message id (from list_messages or send_message). |
No output schema declared.
No examples provided.
bulksms_get_profile Get account profile and credits ~66
Show the BulkSMS account: username, credit balance, credit limit, whether credit transfer is allowed, the daily message quota (size and remaining today) and the sender ids this account may use. Company and billing details are left out. BulkSMS REST: GET /profile.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
bulksms_list_blocked_numbers List blocked numbers ~99
List phone numbers the account may not send to (added via the API, by a recipient replying STOP, or by BulkSMS). To page, pass min_id = the largest id of the previous page + 1. BulkSMS REST: GET /blocked-numbers.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum records, default 100. |
| min_id | integer | – | Only records with id >= min_id (default 0). |
No output schema declared.
No examples provided.
bulksms_list_messages List messages ~346
List sent (SENT) and received (RECEIVED) SMS messages, newest first by default. BulkSMS limits the window to the last 7 days unless submission_date_from is given. To page newest-first, pass before_id = the smallest id of the previous page; with sort_order ASCENDING pass after_id = the largest id of the previous page. REST: GET /messages with a `filter` built from the arguments.
| Name | Type | Req | Description |
|---|---|---|---|
| after_id | string | – | Only messages with an id higher than this (newer), for paging with sort_order ASCENDING: pass the largest id of the previous page. |
| before_id | string | – | Only messages with an id lower than this (older), for paging. |
| limit | integer | – | Maximum number of messages, default 50. The API may return fewer even if more exist: page with before_id. |
| sort_order | string | – | Default DESCENDING (newest first). |
| status_id | string | – | Filter by full status id, e.g. FAILED.BLOCKED or FAILED.EXPIRED. |
| status_type | string | – | Filter by delivery status type. |
| submission_date_from | string | – | Only messages submitted at or after this time, ISO 8601 with offset, e.g. 2026-10-01T00:00:00Z. |
| submission_id | string | – | Only messages of this submission (the submission.id of a sent message). |
| type | string | – | SENT = outgoing (MT), RECEIVED = incoming replies (MO). |
| user_supplied_id | string | – | The userSuppliedId you set when sending (SENT messages only). |
No output schema declared.
No examples provided.
bulksms_list_replies List replies to a sent message ~79
List the received (RECEIVED) replies linked to a sent message id. Only messages sent with a REPLIABLE sender have linked replies. An empty list means none or an unknown id. BulkSMS REST: GET /messages/{id}/relatedReceivedMessages.
| Name | Type | Req | Description |
|---|---|---|---|
| message_id | string | yes | The id of the SENT message. |
No output schema declared.
No examples provided.
bulksms_list_webhooks List webhooks ~74
List the account's webhooks (name, trigger SENT/RECEIVED, active flag, invoke option). Only the host of each webhook URL is shown: the path and query can hold a secret. Read-only: webhooks are not changed by this server. BulkSMS REST: GET /webhooks.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
bulksms_send_message Send SMS ~408
WRITE: SENDS REAL SMS to real people and SPENDS CREDITS from the user's BulkSMS account; it cannot be undone or recalled. One message text to 1 to 10 phone numbers in international format (e.g. +447700900000). Cost = credits per message part x number of parts x number of recipients (about 1 credit per 160-character GSM part to a standard-route destination; the exact cost depends on the destination and appears as creditCost on the sent messages afterwards). Messages longer than one part are concatenated up to max_parts parts (default 3). Non-GSM characters (emoji, accents outside GSM 03.38) are replaced by "?" unless auto_unicode is true, which sends Unicode (shorter parts, more credits). Messages to blocked numbers still cost credits. Only send what the user explicitly asked for, confirm the text and recipients first. No groups, no scheduling. Texts containing BulkSMS template placeholders such as {F0###}, {fn###} or {sn###} are rejected (they would merge contact data). BulkSMS REST: POST /messages.
| Name | Type | Req | Description |
|---|---|---|---|
| auto_unicode | boolean | – | If true, a text with characters outside GSM 03.38 is sent as Unicode instead of having them replaced by '?'. Default false. |
| body | string | yes | The message text. |
| from | string | – | Optional sender id: an allowed international number or a short alphanumeric name (see get_profile originAddresses). Omit to use the account default. |
| max_parts | integer | – | Cap on concatenated parts (and so on cost per recipient). Default 3. |
| to | array | yes | 1 to 10 recipient numbers in international format with country code, e.g. +447700900000 or 27831234567. |
| user_supplied_id | string | – | Your own reference (max 20 characters) stored on the messages, usable as a filter in list_messages. |
No output schema declared.
No examples provided.
How do I install the BulkSMS MCP by usefulapi server?
BulkSMS MCP by usefulapi is a hosted endpoint at https://bulksms.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 · bulksms.usefulapi.io
claude mcp add --transport http io-usefulapi-bulksms 'https://bulksms.usefulapi.io/mcp'
What is the BulkSMS MCP by usefulapi server?
BulkSMS MCP by usefulapi is listed in the public MCP registry as io.usefulapi/bulksms. Read BulkSMS messages, replies, profile and webhooks; send SMS to up to 10 numbers. This page covers its hosted endpoint (https://bulksms.usefulapi.io/mcp).
Is the BulkSMS MCP by usefulapi server safe to use?
BulkSMS MCP by usefulapi scores 65 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 BulkSMS MCP by usefulapi server expose?
BulkSMS MCP by usefulapi exposes 8 tools: bulksms_get_profile, bulksms_list_messages, bulksms_get_message, bulksms_list_replies, bulksms_list_blocked_numbers, and 3 more. Their descriptions and schemas cost roughly 1,245 tokens of context every time the server is loaded.
Does the BulkSMS MCP by usefulapi server require authentication?
Yes. BulkSMS 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 BulkSMS MCP by usefulapi server still maintained?
BulkSMS MCP by usefulapi is still listed as active in the MCP registry. We last reached this channel on 18 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.