BulkSMS MCP by usefulapi
io.usefulapi/bulksmsusefulapi.iostreamable-httpv1.27.4Scanned
Read BulkSMS messages, replies, profile and webhooks; send SMS to up to 10 numbers.
8 tools: 2 can delete or cancel things and 6 only read.
- Reads private data · 4
- Reads text others write · 5
- Can send data out · 1
- No findings
The remote endpoint did not answer the last look. Remote posture
Anlyon alternative
2 of these tools change something. Run those as governed actions.
Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.
Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.
Import an OpenAPI spec →What the BulkSMS MCP by usefulapi can do
The BulkSMS MCP by usefulapi is published by usefulapi.io, a domain the MCP Registry verified. It has 8 tools. It can delete or cancel things (2 tools: bulksms_send_message and bulksms_block_number). 6 tools only read.
4 tools read private data (bulksms_get_profile, bulksms_list_messages, bulksms_get_message and 1 more); 5 tools bring in text other people can write (bulksms_get_profile, bulksms_list_messages, bulksms_get_message and 2 more); 1 tool can send data out of your system (bulksms_send_message). On its own it has all three parts of a prompt-injection exfiltration path: private data, text others write, and a way out.
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Last scanned Oct 25, 2026, version 1.27.4.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
8 tools
Deletes or cancels 2Claude Code: deny
bulksms_block_numberWRITE: 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…No findings
Why it is in this group
- The description's first verb is "write": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it 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.
Annotations the server declares
- title: Block a phone number
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: true
bulksms_send_messageWRITE: SENDS REAL SMS to real people and SPENDS CREDITS from the user's BulkSMS account; it cannot be undone or recalled.Reads text others writeCan send data outNo findings
Why it is in this group
- The name "bulksms_send_message" says "send": a word for sending, and what is sent cannot be taken back.
- The description says "cannot be undone".
- The input addresses people (input.to): what it sends cannot be taken back.
- The server marks it destructive (destructiveHint: true).
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
- outboundThe name "bulksms_send_message" says "send": it sends or publishes something to other people.
Description, as the server wrote it 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.
Annotations the server declares
- title: Send SMS
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: false
- openWorldHint: true
Only reads 6Show 6 read-only tools
bulksms_get_messageGet one sent or received message by its id: body, recipient, delivery status, number of parts and credit cost.Reads private dataReads text others writeNo findings
Why it is in this group
- The name "bulksms_get_message" says "get": a word for reading.
What it can reach
- private-dataThe name "bulksms_get_message" says "get" and "message": it reads messages.
- private-dataThe description's first sentence says "get" and "message": it reads messages.
- untrusted-inputThe name "bulksms_get_message" says "get" and "message": it reads messages, which other people can write.
- untrusted-inputThe description's first sentence says "get" and "message": it reads messages, which other people can write.
Description, as the server wrote it Get one sent or received message by its id: body, recipient, delivery status, number of parts and credit cost. BulkSMS REST: GET /messages/{id}.
Annotations the server declares
- title: Get message
- readOnlyHint: true
bulksms_get_profileShow 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 acc…Reads private dataReads text others writeNo findings
Why it is in this group
- The name "bulksms_get_profile" says "get": a word for reading.
What it can reach
- private-dataThe description's first sentence says "show" and "message": it reads messages.
- untrusted-inputThe description's first sentence says "show" and "message": it reads messages, which other people can write.
Description, as the server wrote it 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.
Annotations the server declares
- title: Get account profile and credits
- readOnlyHint: true
bulksms_list_blocked_numbersList phone numbers the account may not send to (added via the API, by a recipient replying STOP, or by BulkSMS).No findings
Why it is in this group
- The name "bulksms_list_blocked_numbers" says "list": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: List blocked numbers
- readOnlyHint: true
bulksms_list_messagesList sent (SENT) and received (RECEIVED) SMS messages, newest first by default.Reads private dataReads text others writeNo findings
Why it is in this group
- The name "bulksms_list_messages" says "list": a word for reading.
What it can reach
- private-dataThe name "bulksms_list_messages" says "list" and "message": it reads messages.
- private-dataThe description's first sentence says "list" and "message": it reads messages.
- untrusted-inputThe name "bulksms_list_messages" says "list" and "message": it reads messages, which other people can write.
- untrusted-inputThe description's first sentence says "list" and "message": it reads messages, which other people can write.
Description, as the server wrote it 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.
Annotations the server declares
- title: List messages
- readOnlyHint: true
bulksms_list_repliesList the received (RECEIVED) replies linked to a sent message id.Reads private dataReads text others writeNo findings
Why it is in this group
- The name "bulksms_list_replies" says "list": a word for reading.
What it can reach
- private-dataThe description's first sentence says "list" and "message": it reads messages.
- untrusted-inputThe name "bulksms_list_replies" says "list" and "reply": it reads comments, which other people can write.
- untrusted-inputThe description's first sentence says "list" and "reply": it reads comments, which other people can write.
Description, as the server wrote it 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.
Annotations the server declares
- title: List replies to a sent message
- readOnlyHint: true
bulksms_list_webhooksList the account's webhooks (name, trigger SENT/RECEIVED, active flag, invoke option).No findings
Why it is in this group
- The name "bulksms_list_webhooks" says "list": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: List webhooks
- readOnlyHint: true
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
20 paths in this server alone from private data, through text someone else wrote, to a way out. Denying 1 outbound tool breaks every one.
- Reads private data4
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write5
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out1
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
{
"permissions": {
"deny": [
"mcp__bulksms__bulksms_send_message"
]
}
}Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 19:33 UTC, unchanged since Oct 29, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- no
- HTTP status of an anonymous initialize
- not observed
- tools/list served without credentials
- no
- Tools that change things, listed without credentials
- 0
- Protocol version
- not observed
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
The probe stopped: The server redirected a POST to a different request.
Posture changes
- Oct 29, 2026
- Reachable: yes to no
- HTTP status of an anonymous initialize: 200 to none
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 2 to 0
- Protocol version: 2025-06-18 to none
- RFC 9728 protected resource metadata: https://bulksms.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
- Authorization servers: https://bulksms.usefulapi.io to none
- Dynamic client registration: yes to not observed
- Client ID metadata documents: no to not observed
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
PostureRemote posture changed. Reachable: yes -> no; HTTP status of an anonymous initialize: 200 -> none; tools/list served without credentials: yes -> no (and 6 more).View diff
- Reachable: yes to no
- HTTP status of an anonymous initialize: 200 to none
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 2 to 0
- Protocol version: 2025-06-18 to none
- RFC 9728 protected resource metadata: https://bulksms.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
- Authorization servers: https://bulksms.usefulapi.io to none
- Dynamic client registration: yes to not observed
- Client ID metadata documents: no to not observed
Install
Pinned to version 1.27.4. Values in angle brackets are yours to fill in.
claude mcp add --transport http bulksms https://bulksms.usefulapi.io/mcpclaude mcp add --transport http bulksms https://bulksms.usefulapi.io/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__bulksms__bulksms_get_profile",
"mcp__bulksms__bulksms_list_messages",
"mcp__bulksms__bulksms_get_message",
"mcp__bulksms__bulksms_list_replies",
"mcp__bulksms__bulksms_list_blocked_numbers",
"mcp__bulksms__bulksms_list_webhooks"
],
"ask": [],
"deny": [
"mcp__bulksms__bulksms_send_message",
"mcp__bulksms__bulksms_block_number"
]
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as bulksms. Review it before you use it.
Capability tags behind 5 rules
- mcp__bulksms__bulksms_get_profile private-data, untrusted-input
- mcp__bulksms__bulksms_list_messages private-data, untrusted-input
- mcp__bulksms__bulksms_get_message private-data, untrusted-input
- mcp__bulksms__bulksms_list_replies private-data, untrusted-input
- mcp__bulksms__bulksms_send_message untrusted-input, outbound
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.usefulapi/bulksms/verify?hash=35d38eccd2070b7fcd9a0a03bd451a272eb535a8470a480dd9c12b887753b49c" | jq -e '.changed == false'Pinned hash 35d38eccd207, from Oct 25, 2026, 23:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.usefulapi/bulksms/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.usefulapi/bulksms)Source: MCP Registry · repository. Synced Nov 18, 2026, 11:18 UTC.
BulkSMS MCP by usefulapi: questions and answers
Answered from the scan above, not from the publisher's description.
Is the BulkSMS MCP by usefulapi safe?
- No scan can promise that. What its definitions show: 8 tools, 2 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the BulkSMS MCP by usefulapi delete data?
- Yes. 2 tools can delete, cancel or revoke something: bulksms_send_message and bulksms_block_number.
Can the BulkSMS MCP by usefulapi do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the BulkSMS MCP by usefulapi have?
- 8 tools: 2 destructive, 6 read. bulksms_send_message, bulksms_block_number, bulksms_get_profile, bulksms_list_messages, bulksms_get_message, bulksms_list_replies, bulksms_list_blocked_numbers and bulksms_list_webhooks.
Does the BulkSMS MCP by usefulapi need sign-in or OAuth?
- Its remote endpoint did not answer the last anonymous look.
Does the BulkSMS MCP by usefulapi send data to outside services?
- 1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): bulksms_send_message.
Has the BulkSMS MCP by usefulapi changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Oct 25, 2026.