io.usefulapi/text-em-all
REMOTE · TEXT-EM-ALL.USEFULAPI.IO · SCANNED OCT 4
Send and track Text-Em-All broadcasts, texts and contact lists.
Available components
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 Security89
- 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 is enforced; there's no plaintext access path. View diagnostics → Pass
- 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 & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability69
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 2297 tokens (~164/item across 14 items; 14 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 Management13
- Stability observed for 4 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
How do I install the io.usefulapi/text-em-all MCP server?
io.usefulapi/text-em-all is a hosted endpoint at https://text-em-all.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 · text-em-all.usefulapi.io
claude mcp add --transport http io-usefulapi-text-em-all 'https://text-em-all.usefulapi.io/mcp'
{
"mcpServers": {
"io-usefulapi-text-em-all": {
"url": "https://text-em-all.usefulapi.io/mcp"
}
}
} {
"servers": {
"io-usefulapi-text-em-all": {
"type": "http",
"url": "https://text-em-all.usefulapi.io/mcp"
}
}
} [mcp_servers.io-usefulapi-text-em-all] url = "https://text-em-all.usefulapi.io/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"io-usefulapi-text-em-all": {
"type": "remote",
"url": "https://text-em-all.usefulapi.io/mcp",
"enabled": true
}
}
} openclaw mcp add io-usefulapi-text-em-all --url 'https://text-em-all.usefulapi.io/mcp' --transport streamable-http
mcp_servers:
io-usefulapi-text-em-all:
url: "https://text-em-all.usefulapi.io/mcp" {
"McpServers": {
"io-usefulapi-text-em-all": {
"Transport": "http",
"Url": "https://text-em-all.usefulapi.io/mcp"
}
}
} assistant mcp add io-usefulapi-text-em-all -t streamable-http -u 'https://text-em-all.usefulapi.io/mcp'
{
"mcpServers": {
"io-usefulapi-text-em-all": {
"type": "http",
"url": "https://text-em-all.usefulapi.io/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 3 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.
- 2 Oct 26 +3
- Authorization: fail → pass ▲ security
- Server version: 1.3.0 → 1.5.1 functional
- 1 Oct 26 +2
- Authorization: pass → fail ▼ security
- HTTPS: unverified → pass ▲ security
- Stability: unverified → 0.03 ▲ functional
- Server version: 1.0.0 → 1.3.0 functional
- 30 Sept 26 +52
- Authorization: unverified → pass ▲ security
- Injection markers: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- First check of Judged manipulation: pass security
- First check of Authorization: partial security
- MCP protocol: unverified → fail ▼ functional
- Tool coverage: unverified → 100 ▲ functional
- First check of Schema quality: fail functional
- First check of Schema quality: excellent functional
- First check of Schema quality: fail functional
- First check of Destructive annotations: 100 functional
- First check of Tool coverage: 100 functional
- 29 Sept 26 18
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 4 Oct 2026 · Probed https://text-em-all.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 text-em-all.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 | 200 |
WWW-Authenticate challenge Bearer realm="OAuth", resource_metadata="https://text-em-all.usefulapi.io/.well-known/oauth-protected-resource/mcp"
Bearer realm="OAuth", resource_metadata="https://text-em-all.usefulapi.io/.well-known/oauth-protected-resource/mcp"Protected resource metadata
| Document | https://text-em-all.usefulapi.io/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://text-em-all.usefulapi.io/mcp |
| Authorisation server | https://text-em-all.usefulapi.io |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://text-em-all.usefulapi.io/mcp | Verified | 200 | |
| http (plaintext) | http://text-em-all.usefulapi.io/mcp | HTTPS enforced | 301 | https://text-em-all.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 →
add_account_user Add an account user ~179
MUTATES Text-Em-All data: adds a new user to your account (a master user can do this). Text-Em-All API: POST /v1/account/users. Provide the user's fields via `fields` using the API's PascalCase names (e.g. UserName, FirstName, LastName, EmailAddress, Permissions). Returns the created user.
| Name | Type | Req | Description |
|---|---|---|---|
| fields | object | – | Additional documented Text-Em-All fields to send verbatim in the JSON write body, using the API's PascalCase names (e.g. CallerID, TextNumberID, Lists, RetryTimes). Merged OVER the typed fields above. |
| firstName | string | – | First name (FirstName). |
| lastName | string | – | Last name (LastName). |
| userName | string | – | The new user's login username (UserName). |
No output schema declared.
No examples provided.
create_broadcast Send a broadcast ~355
MUTATES Text-Em-All data AND SENDS MESSAGES (spends account credits): creates + sends a broadcast to the given contacts. Text-Em-All API: POST /v1/broadcasts. Set broadcastType to 'SMS' (a text broadcast — provide textMessage) or 'Announcement' (a voice broadcast — provide voiceText for text-to-speech, or a pre-recorded AudioID via `fields.Audio`). Contacts is a list of { primaryPhone, firstName?, lastName?, notes? }. Extra documented fields (CallerID, TextNumberID, Lists, RetryTimes, CallThrottle, MaxMessageLength, StartDate, CheckCallingWindow) go through `fields` (PascalCase). Returns the created broadcast.
| Name | Type | Req | Description |
|---|---|---|---|
| broadcastName | string | yes | A name/label for this broadcast (BroadcastName). Required. |
| broadcastType | string | yes | 'SMS' for a text broadcast, 'Announcement' for a voice broadcast. Required. |
| contacts | array | yes | Recipients (each needs primaryPhone). Required. |
| fields | object | – | Additional documented Text-Em-All fields to send verbatim in the JSON write body, using the API's PascalCase names (e.g. CallerID, TextNumberID, Lists, RetryTimes). Merged OVER the typed fields above. |
| primaryPhoneNumbersOnly | boolean | – | Only send to each contact's primary phone number (PrimaryPhoneNumbersOnly, default true). |
| textMessage | string | – | The text body for an SMS broadcast (TextMessage). Required when broadcastType='SMS'. |
| voiceText | string | – | Text-to-speech message for an Announcement broadcast (mapped to Audio.TextToSpeech=true + Audio.Text). |
No output schema declared.
No examples provided.
create_draft_broadcast Create a draft broadcast ~172
MUTATES Text-Em-All data (creates a DRAFT — does NOT send anything): stages a broadcast with the given contacts and returns a single-sign-on URL to finish + send it in the Text-Em-All UI. Safer than create_broadcast when a human should review before sending. Text-Em-All API: POST /v1/draftbroadcasts. Returns { SingleSignOnUrl, ... }.
| Name | Type | Req | Description |
|---|---|---|---|
| contacts | array | yes | Contacts to pre-populate on the draft broadcast (each needs primaryPhone). Required. |
| fields | object | – | Additional documented Text-Em-All fields to send verbatim in the JSON write body, using the API's PascalCase names (e.g. CallerID, TextNumberID, Lists, RetryTimes). Merged OVER the typed fields above. |
No output schema declared.
No examples provided.
get_account Get account settings ~57
Fetch your Text-Em-All account settings — company/billing info plus credit balances (AvailableCallUnits, CallBalance) used for sending. Text-Em-All API: GET /v1/account. Use this first to confirm your credentials work.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_authorization_token Get a user authorization token ~118
Exchange a Text-Em-All account username + PIN/password for that user's authorization token (the value you set as TEXTEMALL_AUTH_TOKEN). Text-Em-All API: POST /v1/user/login. Signed with your App/Secret key only (no user token yet). Returns { AuthToken }. Use this once to bootstrap; store the token in config thereafter.
| Name | Type | Req | Description |
|---|---|---|---|
| password | string | yes | The Text-Em-All website login PIN/password. Required. |
| username | string | yes | The Text-Em-All website login username. Required. |
No output schema declared.
No examples provided.
get_broadcast Get a broadcast ~50
Fetch a single broadcast by id, including its status and summary. Text-Em-All API: GET /v1/broadcasts/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string|number | yes | The BroadcastID. |
No output schema declared.
No examples provided.
get_broadcast_details Get broadcast delivery details ~57
Fetch per-contact delivery details/results for a broadcast (who was reached, delivery status). Text-Em-All API: GET /v1/broadcasts/{id}/details.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string|number | yes | The BroadcastID. |
No output schema declared.
No examples provided.
get_conversations_sso_url Get a single-sign-on conversations URL ~134
Generate a single-sign-on URL to the Text-Em-All conversations UI (open in a browser/iframe). Optionally scope it to one conversation thread by passing a toll-free textNumber + the other phoneNumber. Text-Em-All API: POST /v1/singlesignon/conversations. Returns { Url }. No account data is changed.
| Name | Type | Req | Description |
|---|---|---|---|
| phoneNumber | string | – | A phone number that has a conversation with the text number, e.g. 9725551212. |
| textNumber | string | – | A toll-free text number on the account, e.g. 18885551234. |
No output schema declared.
No examples provided.
list_broadcasts List broadcasts ~243
List broadcasts (text + voice campaigns) as a paged Feed { Size, Items:[...], Previous, Next }. Text-Em-All API: GET /v1/broadcasts. Filter with equals-style `params` (e.g. BroadcastStatus=Complete) and order with `sortby`. For date-range operators (StartDate~gte~2024-01-01) use the textemall_request escape hatch.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | 1-based page number (Feed `page`). |
| pagesize | integer | – | Number of items per page (Feed `pagesize`, default 10). |
| params | object | – | Additional documented equals-style query filters to send verbatim (e.g. BroadcastStatus=Completed). For range operators (Field~gte~value etc.) use the textemall_request escape hatch. Merged with pagi… |
| sortby | string | – | Comma-separated fields to sort by; prefix a field with '-' for descending (e.g. '-StartDate,CreatedDate'). |
| takesize | integer | – | How many items to return (Feed `takesize`; defaults to pagesize). |
No output schema declared.
No examples provided.
list_lists List contact lists ~184
List saved contact lists (groups you can broadcast to) as a Feed; each List has a ListID/ListName. Text-Em-All API: GET /v1/lists. NOTE: inferred from the API's List model — if your account/endpoint differs, use the textemall_request escape hatch.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | 1-based page number (Feed `page`). |
| pagesize | integer | – | Number of items per page (Feed `pagesize`, default 10). |
| params | object | – | Additional documented equals-style query filters to send verbatim (e.g. BroadcastStatus=Completed). For range operators (Field~gte~value etc.) use the textemall_request escape hatch. Merged with pagi… |
| takesize | integer | – | How many items to return (Feed `takesize`; defaults to pagesize). |
No output schema declared.
No examples provided.
list_text_numbers List text numbers ~176
List the toll-free text (SMS) numbers on your account as a Feed. Each TextNumber has a TextNumberID you need to send a 1:1 conversation text (see send_text_message). Text-Em-All API: GET /v1/textnumbers.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | 1-based page number (Feed `page`). |
| pagesize | integer | – | Number of items per page (Feed `pagesize`, default 10). |
| params | object | – | Additional documented equals-style query filters to send verbatim (e.g. BroadcastStatus=Completed). For range operators (Field~gte~value etc.) use the textemall_request escape hatch. Merged with pagi… |
| takesize | integer | – | How many items to return (Feed `takesize`; defaults to pagesize). |
No output schema declared.
No examples provided.
send_text_message Send a conversation text ~257
MUTATES Text-Em-All data AND SENDS A TEXT (spends credits): sends a 1:1 conversation text message immediately from one of your toll-free text numbers to a single contact. Text-Em-All API: POST /v1/conversations. You need a textNumberId (from list_text_numbers). Returns the conversation.
| Name | Type | Req | Description |
|---|---|---|---|
| fields | object | – | Additional documented Text-Em-All fields to send verbatim in the JSON write body, using the API's PascalCase names (e.g. CallerID, TextNumberID, Lists, RetryTimes). Merged OVER the typed fields above. |
| firstName | string | – | Recipient first name (Contact.FirstName). |
| lastName | string | – | Recipient last name (Contact.LastName). |
| message | string | yes | The text message body. Required. |
| phoneNumber | string | yes | The recipient's phone number (e.g. 9725551212). Required. |
| textNumberId | string|number | yes | The TextNumberID of the toll-free number to send from (see list_text_numbers). Required. |
| truncateIfExceedsLimit | boolean | – | Truncate the message if it exceeds the length limit (TruncateIfExceedsLimit). |
No output schema declared.
No examples provided.
textemall_request Raw read request ~129
Power-user escape hatch: GET any Text-Em-All API path not wrapped by a dedicated tool. READ-ONLY — only GET is allowed. Pass the FULL API path after the origin, starting with a slash, INCLUDING any query string, e.g. "/v1/broadcasts?StartDate~gte~2024-01-01&sortby=-StartDate" or "/v1/textnumbers". Returns the parsed JSON.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | Full API path after the origin, starting with "/", e.g. "/v1/broadcasts?pagesize=50". |
No output schema declared.
No examples provided.
update_account_user Update an account user ~186
MUTATES Text-Em-All data: updates an existing account user. Text-Em-All API: PUT /v1/account/users/{user_id}. Provide the fields to change via `fields` (PascalCase, e.g. FirstName, LastName, EmailAddress, Permissions). The user_id is never sent in the body. Returns the updated user.
| Name | Type | Req | Description |
|---|---|---|---|
| fields | object | – | Additional documented Text-Em-All fields to send verbatim in the JSON write body, using the API's PascalCase names (e.g. CallerID, TextNumberID, Lists, RetryTimes). Merged OVER the typed fields above. |
| firstName | string | – | New first name (FirstName). |
| lastName | string | – | New last name (LastName). |
| user_id | string|number | yes | The id of the user to update (path only). Required. |
No output schema declared.
No examples provided.
What is the io.usefulapi/text-em-all MCP server?
io.usefulapi/text-em-all is an MCP server listed in the public MCP registry as io.usefulapi/text-em-all. Send and track Text-Em-All broadcasts, texts and contact lists. This page covers its hosted endpoint (https://text-em-all.usefulapi.io/mcp).
Is the io.usefulapi/text-em-all MCP server safe to use?
io.usefulapi/text-em-all scores 76 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 io.usefulapi/text-em-all MCP server expose?
io.usefulapi/text-em-all exposes 14 tools: get_account, list_broadcasts, get_broadcast, get_broadcast_details, list_text_numbers, and 9 more. Their descriptions and schemas cost roughly 2,297 tokens of context every time the server is loaded.
Does the io.usefulapi/text-em-all MCP server require authentication?
Yes. io.usefulapi/text-em-all 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 io.usefulapi/text-em-all MCP server still maintained?
io.usefulapi/text-em-all is still listed as active in the MCP registry. We last reached this channel on 4 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.