# SlickText MCP by usefulapi (remote · slicktext.usefulapi.io)

Read SlickText contacts, lists, campaigns, analytics and inbox; create and update contacts.

- Trust score: 65/100 (medium)
- Change this week: +6
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-17

## Components

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

## Channel facts

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

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

- **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**: 80/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 3396 tokens (~141/item across 24 items; 24 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 93/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 80% 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.
  - We read all 24 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 25 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 SlickText MCP by usefulapi server?

SlickText MCP by usefulapi is a hosted endpoint at https://slicktext.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-slicktext 'https://slicktext.usefulapi.io/mcp'
```

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

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

### Netclaw

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

### Vellum

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

### Other

```json
{
  "mcpServers": {
    "io-usefulapi-slicktext": {
      "type": "http",
      "url": "https://slicktext.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 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 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 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-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.4.0 → 1.5.0

### 2026-10-13 (score 61, +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-11 (score 60, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-10 (score 59)

First indexed and scored.

## MCP tools (24)

### `slicktext_get_brand` (~61 tokens)

Get the brand

Get the SlickText brand this API key belongs to: brand_id, name, website, sending-number registration details, opt-in / double-opt-in messages, inbox settings and the message credit limit. Every other tool works within this brand. GET /brands.

### `slicktext_get_credit_usage` (~48 tokens)

Get message credit usage

Message credits for the current billing period: total_credits (subscription + rollover + purchased), credits_used, credits_available and the credit limit. GET /brands/{brand_id}/usage.

### `slicktext_list_contacts` (~198 tokens)

List contacts

List the brand's contacts (subscribers) with name, mobile_number, email, opt_in_status, source, custom_fields and dates. Filters are exact, case-sensitive matches (SlickText has no partial search). Paged: returns count, has_more and next_offset. GET /brands/{brand_id}/contacts.

Input parameters:

- `custom_fields` (object): Exact-match filters on custom fields, keyed by internal_name (see slicktext_list_custom_fields), e.g. {"favorite_color": "blue"}.
- `first_name` (string): Exact first name (case-sensitive).
- `last_name` (string): Exact last name (case-sensitive).
- `limit` (integer): Results per page (1-100, default 25).
- `offset` (integer): Number of results to skip (default 0). Use next_offset from the previous page.
- `opt_in_status` (string): Only contacts with this opt-in status.

### `slicktext_find_contact` (~157 tokens)

Find a contact by phone or email

Find contacts by mobile number or email address (exact match). A 10-digit US number is matched as +1XXXXXXXXXX, the way SlickText stores numbers. Use it before creating a contact to avoid duplicates. GET /brands/{brand_id}/contacts?mobile_number=… or ?email=….

Input parameters:

- `email` (string): Exact email address (case-sensitive, as stored).
- `limit` (integer): Results per page (1-100, default 25).
- `mobile_number` (string): Mobile number, e.g. +16155553338 or (615) 555-3338.
- `offset` (integer): Number of results to skip (default 0). Use next_offset from the previous page.

### `slicktext_get_contact` (~68 tokens)

Get a contact

Get one contact by id: name, mobile_number, email, birthdate, address, opt_in_status, source, custom_fields, time zone and dates. GET /brands/{brand_id}/contacts/{id}.

Input parameters:

- `contact_id` (integer, required): The contact id (a positive integer).

### `slicktext_list_custom_fields` (~90 tokens)

List custom fields

List the brand's contact custom fields: name, internal_name (the key used in contact filters and writes), data_type and description. GET /brands/{brand_id}/custom-fields.

Input parameters:

- `limit` (integer): Results per page (1-100, default 25).
- `offset` (integer): Number of results to skip (default 0). Use next_offset from the previous page.

### `slicktext_list_lists` (~96 tokens)

List contact lists

List the brand's contact lists (contact_list_id, name, description, created). Optional exact name filter. GET /brands/{brand_id}/lists.

Input parameters:

- `limit` (integer): Results per page (1-100, default 25).
- `name` (string): Exact list name (case-sensitive).
- `offset` (integer): Number of results to skip (default 0). Use next_offset from the previous page.

### `slicktext_get_list` (~70 tokens)

Get a contact list

Get one contact list by id plus its contact count (all statuses: subscribed, not subscribed, unsubscribed, blocked). GET /brands/{brand_id}/lists/{id} and /lists/{id}/contacts/count.

Input parameters:

- `list_id` (integer, required): The contact list id (a positive integer).

### `slicktext_list_list_contacts` (~108 tokens)

List contacts in a list

List the contacts in one contact list (paged). GET /brands/{brand_id}/lists/{id}/contacts.

Input parameters:

- `limit` (integer): Results per page (1-100, default 25).
- `list_id` (integer, required): The contact list id (a positive integer).
- `offset` (integer): Number of results to skip (default 0). Use next_offset from the previous page.
- `opt_in_status` (string): Only contacts with this opt-in status.

### `slicktext_list_segments` (~79 tokens)

List segments

List the brand's segments (rule-based contact groups: segment_id, name, description). GET /brands/{brand_id}/segments.

Input parameters:

- `limit` (integer): Results per page (1-100, default 25).
- `offset` (integer): Number of results to skip (default 0). Use next_offset from the previous page.

### `slicktext_list_segment_contacts` (~92 tokens)

List contacts in a segment

List the contacts that currently match one segment (paged). GET /brands/{brand_id}/segments/{id}/contacts.

Input parameters:

- `limit` (integer): Results per page (1-100, default 25).
- `offset` (integer): Number of results to skip (default 0). Use next_offset from the previous page.
- `segment_id` (integer, required): The segment id (a positive integer).

### `slicktext_list_campaigns` (~128 tokens)

List campaigns

List the brand's SMS/MMS campaigns: name, body, status (e.g. draft, scheduled, queued, sent), scheduled/started/finished times, completion_percentage and audience (lists/segments and size). GET /brands/{brand_id}/campaigns.

Input parameters:

- `limit` (integer): Results per page (1-100, default 25).
- `offset` (integer): Number of results to skip (default 0). Use next_offset from the previous page.
- `status` (string): Exact status, e.g. "sent", "scheduled", "draft".

### `slicktext_get_campaign` (~57 tokens)

Get a campaign

Get one campaign by id: body, media_url, status, audience_size, schedule and completion. GET /brands/{brand_id}/campaigns/{id}.

Input parameters:

- `campaign_id` (integer, required): The campaign id (a positive integer).

### `slicktext_get_campaign_stats` (~96 tokens)

Get campaign performance

Performance of one campaign: contacts reached, clicks, click_rate, unique clicks, unsubscribes, unsubscribe_rate, orders, revenue, average order value, revenue per message, plus the campaign, its audiences and links. GET /brands/{brand_id}/analytics/campaigns/{id}.

Input parameters:

- `campaign_id` (integer, required): The campaign id (a positive integer).
- `group` (string): Group the results by source.

### `slicktext_get_analytics` (~312 tokens)

Get brand analytics

Brand-level analytics. metric: contacts (current totals), contact_growth, contact_add_delete_events, opt_in_status_events, campaigns, messages (messages sent), message_credits, inbox_users (assignments, closures, response times per user), inbox_tags. Optional group (allowed per metric — contacts: source|opt_in_status; contact_growth/campaigns: contact_source; contact_add_delete_events: contact_source|type; opt_in_status_events: contact_source|contact_unsubscribe_source|opt_in_status; messages: source|status|direction|weekday; message_credits: source|status), a start/end range, frequency (hour/day/month/year) and compare (YoY, QoQ, MoM, WoW, DoD, PoP). GET /brands/{brand_id}/analytics/….

Input parameters:

- `compare` (string): Compare with the previous period.
- `end` (string): Range end, YYYY-MM-DD (= end of that day) or YYYY-MM-DD HH:MM[:SS] (SlickText's format, no time zone (passed through as is)).
- `frequency` (string): Bucket size of the time series.
- `group` (string): Group results by this field (allowed values depend on metric; see description).
- `metric` (string, required): Which analytics report.
- `start` (string): Range start, YYYY-MM-DD or YYYY-MM-DD HH:MM[:SS] (SlickText's format, no time zone (passed through as is)).

### `slicktext_list_keywords` (~105 tokens)

List keywords

List the brand's text-to-join keywords (word, description, active, auto-response and opt-in messages, double opt-in). GET /brands/{brand_id}/keywords.

Input parameters:

- `active` (boolean): true = only active keywords, false = only inactive.
- `limit` (integer): Results per page (1-100, default 25).
- `offset` (integer): Number of results to skip (default 0). Use next_offset from the previous page.

### `slicktext_get_keyword` (~56 tokens)

Get a keyword

Get one keyword by id, including the contact_list_ids that people who text it are added to. GET /brands/{brand_id}/keywords/{id}.

Input parameters:

- `keyword_id` (integer, required): The keyword id (a positive integer).

### `slicktext_list_messages` (~256 tokens)

List messages

List individual SMS/MMS messages sent and received by the brand: to, from, body, direction, source (Campaign, Keyword, InboxThread, API …), status (delivered, undelivered …), credits and the contact. Filters are exact matches; use to/from with a phone number to read one contact's history, or source=InboxThread with source_id = a conversation id. GET /brands/{brand_id}/messages.

Input parameters:

- `direction` (string)
- `from` (string): Sender number (incoming messages: the contact; outgoing: your number).
- `limit` (integer): Results per page (1-100, default 25).
- `offset` (integer): Number of results to skip (default 0). Use next_offset from the previous page.
- `source` (string): Exact source, e.g. "Campaign", "Keyword", "InboxThread", "API".
- `source_id` (string): Id of the source (a campaign id, a conversation id …).
- `status` (string): Exact status, e.g. "delivered", "undelivered".
- `to` (string): Recipient number (outgoing messages: the contact; incoming: your number).

### `slicktext_list_conversations` (~122 tokens)

List inbox conversations

List two-way inbox conversations: status (open, pending, closed), the contact, the last message and its direction/time, assigned user, tags and unread state. GET /brands/{brand_id}/inbox-threads.

Input parameters:

- `assigned_to_user_id` (integer): Only conversations assigned to this user id.
- `limit` (integer): Results per page (1-100, default 25).
- `offset` (integer): Number of results to skip (default 0). Use next_offset from the previous page.
- `status` (string)

### `slicktext_get_conversation` (~103 tokens)

Get an inbox conversation

Get the content of one inbox conversation by its id (the _id from slicktext_list_conversations). For the message-by-message history also call slicktext_list_messages with source=InboxThread and source_id=<conversation id>. GET /brands/{brand_id}/inbox-threads/{id}/content.

Input parameters:

- `conversation_id` (string, required): The conversation _id, e.g. 6744a2ba587c8f2cf4028786.

### `slicktext_list_inbox_tags` (~85 tokens)

List inbox tags

List the inbox tags used to label conversations (inbox_tag_id, name, color, description). GET /brands/{brand_id}/inbox-tags.

Input parameters:

- `limit` (integer): Results per page (1-100, default 25).
- `offset` (integer): Number of results to skip (default 0). Use next_offset from the previous page.

### `slicktext_create_contact` (~368 tokens)

Create a contact

WRITE: add a contact to the brand. By default the contact is created as 'not subscribed' and gets no text. Set opt_in_status='subscribed' ONLY for people who gave explicit permission to receive texts (SlickText has a zero-tolerance policy for unsolicited texts). force_double_opt_in=true makes SlickText SEND A REAL SMS to the number asking the person to confirm. Check slicktext_find_contact first to avoid duplicates. WARNING: SlickText workflows can trigger on this event (Contact Created / Contact Field Changed / Contact Added to List) and may immediately SEND REAL TEXTS or take other actions configured in the brand's workflows. POST /brands/{brand_id}/contacts.

Input parameters:

- `address` (string)
- `birthdate` (string): Birthday, YYYY-MM-DD.
- `city` (string)
- `country` (string)
- `custom_fields` (object): Custom field values keyed by the field's internal_name (see slicktext_list_custom_fields), e.g. {"favorite_color": "blue"}.
- `email` (string)
- `first_name` (string)
- `force_double_opt_in` (boolean): true = SlickText texts the number a double opt-in confirmation (a real SMS).
- `language` (string): Primary language code, e.g. "en".
- `last_name` (string)
- `mobile_number` (string, required): Mobile number (required), e.g. +16155553338 or (615) 555-3338.
- `opt_in_status` (string): Default 'not subscribed'. 'subscribed' only with the person's explicit consent.
- `state` (string)
- `timezone` (string): Contact time zone (SlickText accepts these four).
- `zip` (string)

### `slicktext_update_contact` (~298 tokens)

Update a contact

WRITE: change fields of an existing contact (only the fields you pass are sent). opt_in_status can mark a contact unsubscribed or blocked; set it to 'subscribed' ONLY when the person explicitly agreed to receive texts. WARNING: SlickText workflows can trigger on this event (Contact Created / Contact Field Changed / Contact Added to List) and may immediately SEND REAL TEXTS or take other actions configured in the brand's workflows. PUT /brands/{brand_id}/contacts/{id}.

Input parameters:

- `address` (string)
- `birthdate` (string): Birthday, YYYY-MM-DD.
- `city` (string)
- `contact_id` (integer, required): The contact id (a positive integer).
- `country` (string)
- `custom_fields` (object): Custom field values keyed by the field's internal_name (see slicktext_list_custom_fields), e.g. {"favorite_color": "blue"}.
- `email` (string)
- `first_name` (string)
- `language` (string): Primary language code, e.g. "en".
- `last_name` (string)
- `mobile_number` (string): New mobile number.
- `opt_in_status` (string): New opt-in status. 'subscribed' only with the person's explicit consent.
- `state` (string)
- `timezone` (string): Contact time zone (SlickText accepts these four).
- `zip` (string)

### `slicktext_add_contact_to_lists` (~134 tokens)

Add a contact to lists

WRITE: add one contact to one or more contact lists (it does not change the contact's opt-in status; lists are also campaign audiences). Returns SlickText's count of memberships added. WARNING: SlickText workflows can trigger on this event (Contact Created / Contact Field Changed / Contact Added to List) and may immediately SEND REAL TEXTS or take other actions configured in the brand's workflows. POST /brands/{brand_id}/lists/contacts.

Input parameters:

- `contact_id` (integer, required): The contact id (a positive integer).
- `list_ids` (array, required): Contact list ids (from slicktext_list_lists).

## Diagnostics

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

## Score history

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

## Common questions

### What is the SlickText MCP by usefulapi server?

SlickText MCP by usefulapi is listed in the public MCP registry as io.usefulapi/slicktext. Read SlickText contacts, lists, campaigns, analytics and inbox; create and update contacts. This page covers its hosted endpoint (https://slicktext.usefulapi.io/mcp).

### Is the SlickText MCP by usefulapi server safe to use?

SlickText 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 SlickText MCP by usefulapi server expose?

SlickText MCP by usefulapi exposes 24 tools: slicktext_get_brand, slicktext_get_credit_usage, slicktext_list_contacts, slicktext_find_contact, slicktext_get_contact, and 19 more. Their descriptions and schemas cost roughly 3,187 tokens of context every time the server is loaded.

### Does the SlickText MCP by usefulapi server require authentication?

Yes. SlickText 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 SlickText MCP by usefulapi server still maintained?

SlickText MCP by usefulapi is still listed as active in the MCP registry. We last reached this channel on 17 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://slicktext.usefulapi.io/mcp
- Repository: https://github.com/m190/usefulapi-mcp
- Website: https://usefulapi.io/slicktext/
- Changelog RSS feed: https://verifymcp.io/servers/io-usefulapi-slicktext/slicktext.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-usefulapi-slicktext/slicktext.json
- HTML version of this page: https://verifymcp.io/servers/io-usefulapi-slicktext/slicktext