# BulkSMS MCP by usefulapi (remote · bulksms.usefulapi.io)

Read BulkSMS messages, replies, profile and webhooks; send SMS to up to 10 numbers.

- Trust score: 65/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-18

## Components

- remote · `bulksms.usefulapi.io`: 65/100 (this document), [markdown](https://verifymcp.io/servers/io-usefulapi-bulksms/bulksms.md), [page](https://verifymcp.io/servers/io-usefulapi-bulksms/bulksms)

## Channel facts

- Endpoint: `https://bulksms.usefulapi.io/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-18.

- **Endpoint Security**: 78/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
  - The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents.
- **Transport & Reachability**: 0/100
  - Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly.
- **Schema Quality & AI Usability**: 81/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 20/100
  - Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add --transport http io-usefulapi-bulksms 'https://bulksms.usefulapi.io/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "io-usefulapi-bulksms": {
      "url": "https://bulksms.usefulapi.io/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "io-usefulapi-bulksms": {
      "type": "http",
      "url": "https://bulksms.usefulapi.io/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.io-usefulapi-bulksms]
url = "https://bulksms.usefulapi.io/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-usefulapi-bulksms": {
      "type": "remote",
      "url": "https://bulksms.usefulapi.io/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add io-usefulapi-bulksms --url 'https://bulksms.usefulapi.io/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  io-usefulapi-bulksms:
    url: "https://bulksms.usefulapi.io/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "io-usefulapi-bulksms": {
      "Transport": "http",
      "Url": "https://bulksms.usefulapi.io/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add io-usefulapi-bulksms -t streamable-http -u 'https://bulksms.usefulapi.io/mcp'
```

### Other

```json
{
  "mcpServers": {
    "io-usefulapi-bulksms": {
      "type": "http",
      "url": "https://bulksms.usefulapi.io/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-17 (score 65, +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.

### 2026-10-15 (score 64, +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.

### 2026-10-14 (score 63, +2)

- [security] The server rewrote its instructions, which are the text every model session reads
- [functional] 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

### 2026-10-13 (score 61, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-12 (score 60)

First indexed and scored.

## MCP tools (8)

### `bulksms_get_profile` (~66 tokens)

Get account profile and credits

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.

### `bulksms_list_messages` (~346 tokens)

List messages

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.

Input parameters:

- `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).

### `bulksms_get_message` (~63 tokens)

Get message

Get one sent or received message by its id: body, recipient, delivery status, number of parts and credit cost. BulkSMS REST: GET /messages/{id}.

Input parameters:

- `message_id` (string, required): The message id (from list_messages or send_message).

### `bulksms_list_replies` (~79 tokens)

List replies to a sent message

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.

Input parameters:

- `message_id` (string, required): The id of the SENT message.

### `bulksms_list_blocked_numbers` (~99 tokens)

List blocked numbers

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.

Input parameters:

- `limit` (integer): Maximum records, default 100.
- `min_id` (integer): Only records with id >= min_id (default 0).

### `bulksms_list_webhooks` (~74 tokens)

List webhooks

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.

### `bulksms_send_message` (~408 tokens)

Send SMS

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.

Input parameters:

- `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, required): 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, required): 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.

### `bulksms_block_number` (~110 tokens)

Block a phone number

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.

Input parameters:

- `phone_number` (string, required): The number in international format, e.g. +447700900000 or 447700900000.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/io-usefulapi-bulksms/bulksms#diagnostics

## Score history

- 2026-10-18: 65
- 2026-10-17: 65
- 2026-10-16: 64
- 2026-10-15: 64
- 2026-10-14: 63
- 2026-10-13: 61
- 2026-10-12: 60

## Common questions

### 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.

## Links

- Remote endpoint: https://bulksms.usefulapi.io/mcp
- Repository: https://github.com/m190/usefulapi-mcp
- Website: https://usefulapi.io/bulksms/
- Changelog RSS feed: https://verifymcp.io/servers/io-usefulapi-bulksms/bulksms.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-usefulapi-bulksms/bulksms.json
- HTML version of this page: https://verifymcp.io/servers/io-usefulapi-bulksms/bulksms