SimpleTexting MCP by usefulapi
REMOTE · SIMPLETEXTING.USEFULAPI.IO
Send SMS/MMS, manage contacts, and read campaigns, messages and media on SimpleTexting.
Available components
Last scanned (4 hours 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.
- 2 Nov 26 −62
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: pass → 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 +3
- Authorization: partial → pass ▲ security
- MCP protocol: fail → pass ▲ functional
- New prompt “check_segments_and_cost_of_a_text_before_sending” functional
- New prompt “find_an_mms_media_item” functional
- New prompt “look_up_or_update_a_contact” functional
- New prompt “review_recent_message_history” functional
- New prompt “review_sent_campaigns_and_their_recipients” functional
- New prompt “send_a_text_message_to_a_customer” functional
- MCP protocol version: 2025-06-18 → 2025-11-25 functional
- Server version: 1.31.0 → 1.33.0 functional
- Server version: 1.30.0 → 1.31.0 functional
- Server version: 1.29.2 → 1.30.0 functional
- 30 Oct 26 0
- Server version: 1.29.1 → 1.29.2 functional
- Server version: 1.29.0 → 1.29.1 functional
- 29 Oct 26 0
- Server version: 1.28.0 → 1.29.0 functional
- Server version: 1.27.0 → 1.28.0 functional
- 28 Oct 26 0
- Server version: 1.26.0 → 1.27.0 functional
- Server version: 1.25.0 → 1.26.0 functional
- 27 Oct 26 0
- Server version: 1.24.0 → 1.25.0 functional
- 25 Oct 26 0
- Server version: 1.23.0 → 1.24.0 functional
- Server version: 1.22.0 → 1.23.0 functional
- Server version: 1.21.3 → 1.22.0 functional
- Server version: 1.21.0 → 1.21.3 functional
- 24 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Server version: 1.20.0 → 1.21.0 functional
- Server version: 1.19.0 → 1.20.0 functional
- Server version: 1.17.0 → 1.19.0 functional
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://simpletexting.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 simpletexting.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://simpletexting.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/simpletexting/ |
| http (plaintext) | http://simpletexting.usefulapi.io/mcp | Inconclusive | 302 | http://simpletexting.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 →
simpletexting_evaluate_message Evaluate message ~100
DRY-RUN a message body to compute its segment count, whether it sends as SMS or MMS, and its estimated cost — WITHOUT sending anything. Safe and read-only. SimpleTexting REST: POST /messages/evaluate with JSON body {text, mode?}.
| Name | Type | Req | Description |
|---|---|---|---|
| mode | string | – | Optional send mode to evaluate against (e.g. AUTO | SMS | MMS). |
| text | string | yes | The message body to evaluate. |
No output schema declared.
No examples provided.
simpletexting_get_campaign Get campaign ~50
Get a single campaign by its id, including its message, recipients, and status. SimpleTexting REST: GET /campaigns/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| campaign_id | string | yes | Campaign id. |
No output schema declared.
No examples provided.
simpletexting_get_contact Get contact ~59
Get a single contact by its id or phone number, including profile fields, list memberships, and custom fields. SimpleTexting REST: GET /contacts/{contactIdOrNumber}.
| Name | Type | Req | Description |
|---|---|---|---|
| contact | string | yes | Contact id or phone number. |
No output schema declared.
No examples provided.
simpletexting_get_media Get media ~53
Get a single media item (MMS asset) by its id, including its URL and metadata. SimpleTexting REST: GET /media/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| media_id | string | yes | Media item id. |
No output schema declared.
No examples provided.
simpletexting_get_message Get message ~51
Get a single message by its id, including its text, direction, status, and timestamps. SimpleTexting REST: GET /messages/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| message_id | string | yes | Message id. |
No output schema declared.
No examples provided.
simpletexting_list_campaigns List campaigns ~180
List the account's campaigns as a paged collection, optionally filtered by sending number, state, list, and start-date range. Note: only immediate campaigns are returned — scheduled/recurring campaigns are NOT included. SimpleTexting REST: GET /campaigns.
| Name | Type | Req | Description |
|---|---|---|---|
| accountPhone | string | – | Filter by the sending account phone number. |
| listNameOrId | string | – | Filter by recipient list name or id. |
| page | integer | – | Zero-based page number. |
| size | integer | – | Page size (1-100). |
| startDateFrom | string | – | Filter to campaigns starting on/after this date. |
| startDateTo | string | – | Filter to campaigns starting on/before this date. |
| state | string | – | Filter by campaign state (e.g. SENT | SCHEDULED | DRAFT). |
No output schema declared.
No examples provided.
simpletexting_list_contacts List contacts ~101
List the account's contacts as a paged collection, optionally filtered by a `since` cursor and sort `direction`. SimpleTexting REST: GET /contacts.
| Name | Type | Req | Description |
|---|---|---|---|
| direction | string | – | Sort direction (e.g. ASC | DESC). |
| page | integer | – | Zero-based page number. |
| since | string | – | Return contacts created/updated since this cursor or timestamp. |
| size | integer | – | Page size (1-100). |
No output schema declared.
No examples provided.
simpletexting_list_media List media ~61
List the account's media items (MMS assets) as a paged collection. SimpleTexting REST: GET /media.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | Zero-based page number. |
| size | integer | – | Page size (1-100). |
No output schema declared.
No examples provided.
simpletexting_list_messages List messages ~62
List the account's messages as a paged collection (inbound + outbound message history). SimpleTexting REST: GET /messages.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | Zero-based page number. |
| size | integer | – | Page size (1-100). |
No output schema declared.
No examples provided.
simpletexting_send_message Send message ~185
SENDS A REAL SMS or MMS to a recipient — this MODIFIES live data and consumes message credits. Provide only the optional fields you need. SimpleTexting REST: POST /messages with JSON body {contactPhone, text, accountPhone?, mode?, subject?, fallbackText?, mediaItems?}.
| Name | Type | Req | Description |
|---|---|---|---|
| accountPhone | string | – | Sending account phone number — omit to use the account default. |
| contactPhone | string | yes | Recipient phone number (E.164 or national format). |
| fallbackText | string | – | Fallback text if MMS cannot be delivered. |
| mediaItems | array | – | Media URLs or media ids to attach (makes it an MMS). |
| mode | string | – | Send mode: AUTO | SMS | MMS | MMS_PREFERRED. |
| subject | string | – | MMS subject line. |
| text | string | yes | Message body to send. |
No output schema declared.
No examples provided.
simpletexting_update_contact Update contact ~181
UPDATES a live contact — its profile fields, list memberships, and custom fields. This MODIFIES live data. Provide only the fields you want to change. SimpleTexting REST: PUT /contacts/{contactIdOrNumber}.
| Name | Type | Req | Description |
|---|---|---|---|
| birthday | string | – | Contact birthday (YYYY-MM-DD). |
| comment | string | – | Free-text note on the contact. |
| contact | string | yes | Contact id or phone number to update. |
| contactPhone | string | – | New phone number for the contact. |
| customFields | object | – | Custom field values, as a map of field name → value. |
| string | – | Contact email address. | |
| firstName | string | – | Contact first name. |
| lastName | string | – | Contact last name. |
| listIds | array | – | List ids or names to assign the contact to. |
No output schema declared.
No examples provided.
How do I install the SimpleTexting MCP by usefulapi server?
SimpleTexting MCP by usefulapi is a hosted endpoint at https://simpletexting.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 · simpletexting.usefulapi.io
claude mcp add --transport http io-usefulapi-simpletexting 'https://simpletexting.usefulapi.io/mcp'
What is the SimpleTexting MCP by usefulapi server?
SimpleTexting MCP by usefulapi is listed in the public MCP registry as io.usefulapi/simpletexting. Send SMS/MMS, manage contacts, and read campaigns, messages and media on SimpleTexting. This page covers its hosted endpoint (https://simpletexting.usefulapi.io/mcp).
Is the SimpleTexting MCP by usefulapi server safe to use?
SimpleTexting 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 SimpleTexting MCP by usefulapi server expose?
SimpleTexting MCP by usefulapi exposes 11 tools: simpletexting_list_contacts, simpletexting_get_contact, simpletexting_list_campaigns, simpletexting_get_campaign, simpletexting_list_messages, and 6 more. Their descriptions and schemas cost roughly 1,083 tokens of context every time the server is loaded.
Does the SimpleTexting MCP by usefulapi server require authentication?
Its publisher declares no required credentials for SimpleTexting 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 SimpleTexting MCP by usefulapi server still maintained?
SimpleTexting 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.