io.usefulapi/simpletexting

REMOTE · SIMPLETEXTING.USEFULAPI.IO · SCANNED AUG 3

Send SMS/MMS, manage contacts, and read campaigns, messages and media on SimpleTexting.

Available components

+4 this week 72 72 Trust /100

Trust breakdown (6 categories)

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 →

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 not yet verified: we couldn't determine whether a plaintext access path exists. 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 & Reachability100

Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass

Schema Quality & AI Usability73

AI-judged instruction clarity (good).Pass
Tool/resource definitions use about 1083 tokens (~98/item across 11 items; 11 tools + 0 resources), lean.Pass
Usage-examples check failed: none of the tools include examples. See how to fix → Fail

Stability & Change Management23

Stability observed for 7 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

Capabilities60

Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

remote · simpletexting.usefulapi.io

Claude Codex opencode OpenClaw Hermes Other

# add to Claude Code

claude mcp add --transport http io-usefulapi-simpletexting https://simpletexting.usefulapi.io/mcp

# ~/.codex/config.toml

[mcp_servers.io-usefulapi-simpletexting]
url = "https://simpletexting.usefulapi.io/mcp"

// opencode.json

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

# add to OpenClaw

openclaw mcp add io-usefulapi-simpletexting --url https://simpletexting.usefulapi.io/mcp --transport streamable-http

# ~/.hermes/config.yaml

mcp_servers:
  io-usefulapi-simpletexting:
    url: "https://simpletexting.usefulapi.io/mcp"

// mcp.json

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

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

Changelog

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 Aug 26 +1

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
31 Jul 26 +3
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
30 Jul 26 −2
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
29 Jul 26 +1

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
28 Jul 26 +1
- Stability: unverified → 0.03 ▲ functional
27 Jul 26 +56
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
26 Jul 26 12

First indexed and scored.

Show 6 earlier entries Hide earlier entries

Diagnostics

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 3 Aug 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	19 Jul 2026	17 Oct 2026	ECDSA 256	ECDSA-SHA256	10a8f8f8521a82cd0e71bedbb6bc83d0
SANs: usefulapi.io, simpletexting.usefulapi.io, *.simpletexting.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

DNSSEC insecure

Validation of simpletexting.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://simpletexting.usefulapi.io/.well-known/oauth-protected-resource/mcp", error="invalid_token", error_description="Missing or invalid access token"

Bearer realm="OAuth", resource_metadata="https://simpletexting.usefulapi.io/.well-known/oauth-protected-resource/mcp", error="invalid_token", error_description="Missing or invalid access token"

Protected resource metadata

Document	https://simpletexting.usefulapi.io/.well-known/oauth-protected-resource/mcp
Retrieved	Yes
Resource	https://simpletexting.usefulapi.io/mcp
Authorisation server	https://simpletexting.usefulapi.io

Transports 2 probes

Transport	URL	Outcome	Status	Location
streamable-http	https://simpletexting.usefulapi.io/mcp	Verified	200
http (plaintext)	http://simpletexting.usefulapi.io/mcp	Inconclusive	401

MCP tools — 11 exposed · ~1,083 tokens

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.

Tool Tokens

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?}.

Input Output Examples

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

Input Output Examples

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

Input Output Examples

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

Input Output Examples

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

Input Output Examples

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.

Input Output Examples

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.

Input Output Examples

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.

Input Output Examples

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.

Input Output Examples

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?}.

Input Output Examples

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

Input Output Examples

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

On this page

Handy links

Scoring key

80+ high trust
60–79 medium
below 60 low

How we score

Score history · last 30 days

26 Jul 3 Aug

Day	Score
26 Jul	12
27 Jul	68
28 Jul	69
29 Jul	70
30 Jul	68
31 Jul	71
1 Aug	71
2 Aug	72
3 Aug	72