Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Textline MCP by usefulapi

REMOTE · TEXTLINE.USEFULAPI.IO

Read Textline conversations, contacts and reports; send a text, add notes, resolve or transfer.

+5 this week 66 Trust /100

Last scanned (2 hours ago)

Scores higher than 56% of remote servers

Reachable. Last reached 18 Oct 2026.

Category Communication

Trust breakdown (7 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 → Why this is hard to score →

Endpoint Security78
Transport & Reachability0
Schema Quality & AI Usability83
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 2710 tokens (~117/item across 23 items; 23 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 Management27
  • Stability observed for 8 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 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 24 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
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.

  • 17 Oct 26 +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.

  • 15 Oct 26 +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.

  • 14 Oct 26 +2
    • The server rewrote its instructions, which are the text every model session reads security
    • 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 functional
  • 12 Oct 26 +1
    • Stability: unverified → 0.07 ▲ functional
  • 10 Oct 26 61

    First indexed and scored.

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 18 Oct 2026 · Probed https://textline.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 textline.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 302

WWW-Authenticate challenge Bearer realm="OAuth", resource_metadata="https://textline.usefulapi.io/.well-known/oauth-protected-resource/mcp"

Bearer realm="OAuth", resource_metadata="https://textline.usefulapi.io/.well-known/oauth-protected-resource/mcp"

Protected resource metadata

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

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://textline.usefulapi.io/mcp Redirected 302 https://usefulapi.io/textline/
http (plaintext) http://textline.usefulapi.io/mcp Inconclusive 302 http://textline.usefulapi.io/mcp
MCP tools · 23 exposed · ~2,503 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. 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 →

Tool Tokens
textline_add_whisper ~158

WRITE: add an internal whisper (a note only your agents see, never sent to the customer) to a conversation, by conversation_uuid or phone_number. POST /api/conversation/{uuid}.json or POST /api/conversations.json with a whisper.

NameTypeReqDescription
bodystringyesThe note text (visible to agents only).
conversation_uuidstring–The conversation UUID (pass this OR phone_number).
group_uuidstring–With phone_number only: the department to use. Default: the first department.
phone_numberstring–The contact's phone number (pass this OR conversation_uuid); opens the conversation if there is none.
resolveboolean–Resolve the conversation after adding the note.

No output schema declared.

No examples provided.

textline_create_customer ~112

WRITE: add a contact (customer) to the Textline address book. Sends nothing to the contact. POST /api/customers.json.

NameTypeReqDescription
emailstring–Email address.
namestring–Full name.
notesstring–Notes on the contact (replaces the existing notes).
phone_numberstringyesThe contact's phone number.
tagsarray–Tags, e.g. ['VIP', 'new_lead'] (underscores instead of spaces).

No output schema declared.

No examples provided.

textline_get_agent ~59

Retrieve one agent (user) by UUID or email: name, permission level, availability (on_call) and departments. GET /api/users.json.

NameTypeReqDescription
emailstring–Agent email.
user_uuidstring–Agent UUID.

No output schema declared.

No examples provided.

textline_get_conversation ~140

Retrieve one conversation and its posts (messages in and out, internal whispers, resolve/transfer events), newest page first. Page with page/page_size or with before_uuid/after_uuid (a post uuid). GET /api/conversation/{uuid}.json.

NameTypeReqDescription
after_uuidstring–Only posts after this post uuid (exclusive).
before_uuidstring–Only posts before this post uuid (exclusive).
conversation_uuidstringyesConversation UUID.
pageinteger–Page number, 0-based (default 0).
page_sizeinteger–Results per page (default 30, max 50).

No output schema declared.

No examples provided.

textline_get_conversation_by_phone ~166

Retrieve the conversation with a phone number (in a department) and its posts (messages). GET /api/conversations.json?phone_number=….

NameTypeReqDescription
after_uuidstring–Only posts after this post uuid (exclusive).
before_uuidstring–Only posts before this post uuid (exclusive).
group_uuidstring–Department (group) UUID from textline_list_departments. Default: the first department.
pageinteger–Page number, 0-based (default 0).
page_sizeinteger–Results per page (default 30, max 50).
phone_numberstringyesThe contact's phone number, e.g. +14155550123 or (415) 555-0123.

No output schema declared.

No examples provided.

textline_get_customer ~45

Retrieve one contact (customer) from the address book by UUID. GET /api/customer/{uuid}.json.

NameTypeReqDescription
customer_uuidstringyesContact (customer) UUID.

No output schema declared.

No examples provided.

textline_get_customer_by_phone ~50

Retrieve one contact (customer) from the address book by phone number. GET /api/customers.json?phone_number=….

NameTypeReqDescription
phone_numberstringyesThe contact's phone number.

No output schema declared.

No examples provided.

textline_get_organization ~57

Retrieve the organization (account) name, optionally with its departments and agents. GET /api/organization.json.

NameTypeReqDescription
include_groupsboolean–Include the departments.
include_usersboolean–Include the agents (users).

No output schema declared.

No examples provided.

textline_list_agents ~47

List the agents (users) in the organization: name, email, UUID, permission level, availability and department UUIDs. GET /api/organization.json?include_users=1.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

textline_list_conversations ~126

List conversations (one per contact) in a department of the Textline shared inbox, with the contact and resolved status. Optional keyword search. GET /api/conversations.json.

NameTypeReqDescription
group_uuidstring–Department (group) UUID from textline_list_departments. Default: the first department.
pageinteger–Page number, 0-based (default 0).
page_sizeinteger–Results per page (default 30, max 50).
querystring–Keyword to search conversations on (name, phone, message text).

No output schema declared.

No examples provided.

textline_list_custom_fields ~45

List the address book's custom fields (name, data type, UUID). Use the UUIDs with textline_update_customer. GET /api/address_book/custom_fields.json.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

textline_list_customers ~105

List or search contacts (customers) in the Textline address book: name, phone, email, tags, notes, custom fields, consent and reachability. GET /api/customers.json.

NameTypeReqDescription
pageinteger–Page number, 0-based (default 0).
page_sizeinteger–Results per page (default 30, max 50).
querystring–Keyword to search on (name, phone, email, tag).

No output schema declared.

No examples provided.

textline_list_departments ~56

List the departments (groups / inbox phone lines) the token's agent can see: name, UUID, phone number, type (sms, facebook, smart_sms) and member agent UUIDs. GET /api/groups.json.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

textline_list_dispositions ~60

List the dispositions (resolution reasons) set up in the account, optionally for one department. Use a UUID with textline_resolve_conversation. GET /api/dispositions.json.

NameTypeReqDescription
group_uuidstring–Only dispositions of this department.

No output schema declared.

No examples provided.

textline_list_saved_searches ~41

List the address book's saved searches (contact segments) with name, description and UUID. GET /api/address_book/saved_searches.json.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

textline_list_survey_responses ~93

List the responses to one survey (ratings, follow-up text, contact, tags). Default: the last 30 days. GET /api/survey/{uuid}/responses.json.

NameTypeReqDescription
end_datestring–Last day, YYYY-MM-DD.
start_datestring–First day, YYYY-MM-DD.
survey_uuidstringyesSurvey UUID from textline_list_surveys.

No output schema declared.

No examples provided.

textline_list_surveys ~36

List surveys (NPS, CSAT, custom) with their type and UUID. GET /api/surveys.json.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

textline_report_conversations ~322

Reporting API: list a department's conversations filtered by created/updated time, resolved, archived or blocked, with total_records. To get the next page pass the returned next.search_uuid, next.page and next.page_size exactly (the same filters are kept). Then use textline_report_posts per conversation. GET /api/reporting/conversations.json.

NameTypeReqDescription
archivedboolean–Only archived (true) or unarchived (false) contacts. Default: both.
blockedboolean–Only blocked (true) or unblocked (false) contacts. Default: both.
created_afterstring–Created after this ISO date-time (with timezone).
created_beforestring–Created before this ISO date-time (with timezone).
group_uuidstring–Department UUID (required unless search_uuid is given).
pageinteger–Page number, 0-based (default 0).
page_sizeinteger–Results per page (default 30, max 30).
resolvedboolean–Only resolved (true) or unresolved (false) conversations.
search_uuidstring–Continue an earlier result set: next.search_uuid from a previous call (with next.page and next.page_size).
sort_bystring–Sort field (default created_at).
sort_orderstring–Sort order (default desc).
updated_afterstring–Updated after this ISO date-time (with timezone).
updated_beforestring–Updated before this ISO date-time (with timezone).

No output schema declared.

No examples provided.

textline_report_posts ~197

Reporting API: list all posts (messages, whispers) of one conversation with creator, thread, first-response flags, filtered by created time, with total_records. To get the next page pass the returned next.search_uuid, next.page and next.page_size exactly. GET /api/reporting/conversation/{uuid}/posts.json.

NameTypeReqDescription
conversation_uuidstringyesConversation UUID.
created_afterstring–Created after this ISO date-time (with timezone).
created_beforestring–Created before this ISO date-time (with timezone).
pageinteger–Page number, 0-based (default 0).
page_sizeinteger–Results per page (default 30, max 30).
search_uuidstring–Continue an earlier result set: next.search_uuid from a previous call (with next.page and next.page_size).
sort_orderstring–Sort order (default desc).

No output schema declared.

No examples provided.

textline_resolve_conversation ~75

WRITE: mark a conversation resolved (closed), optionally with a disposition from textline_list_dispositions. Nothing is sent to the customer. POST /api/conversation/{uuid}/resolve.json.

NameTypeReqDescription
conversation_uuidstringyesConversation UUID.
disposition_uuidstring–Disposition (resolution reason) UUID.

No output schema declared.

No examples provided.

textline_send_message ~205

SENDS A REAL SMS/MMS to ONE contact from your Textline number — the customer receives it immediately and it cannot be unsent; it consumes message credits. Address it by conversation_uuid or by phone_number (+ optional department). Confirm the recipient and text with the user first. One recipient per call; no bulk sends. POST /api/conversation/{uuid}.json or POST /api/conversations.json.

NameTypeReqDescription
attachment_urlsarray–Public https URLs of files to attach (makes it an MMS).
bodystringyesThe message text the customer will receive.
conversation_uuidstring–The conversation UUID (pass this OR phone_number).
group_uuidstring–With phone_number only: the department to use. Default: the first department.
phone_numberstring–The contact's phone number (pass this OR conversation_uuid); opens the conversation if there is none.
resolveboolean–Resolve the conversation after sending.

No output schema declared.

No examples provided.

textline_transfer_conversation ~92

WRITE: assign a conversation to another agent of the same department, by agent UUID or email (one of them). Nothing is sent to the customer. POST /api/conversation/{uuid}/transfer.json.

NameTypeReqDescription
assigneestring–The agent's email.
conversation_uuidstringyesConversation UUID.
user_uuidstring–The agent's UUID (from textline_list_agents).

No output schema declared.

No examples provided.

textline_update_customer ~216

WRITE: update a contact's name, email, notes, tags (add, remove or replace) or custom fields (by custom-field UUID from textline_list_custom_fields). Overwrites the fields you pass; sends nothing to the contact. PUT /api/customer/{uuid}.json.

NameTypeReqDescription
custom_fieldsobject–Custom field values keyed by custom-field UUID, e.g. {"c43a1766-47e1-4c9c-a2cc-36bf424fcbc0": "Gold"}.
customer_uuidstringyesContact (customer) UUID.
emailstring–Email address.
namestring–Full name.
notesstring–Notes on the contact (replaces the existing notes).
tagsarray–Tags, e.g. ['VIP', 'new_lead'] (underscores instead of spaces).
tags_handlingstring–How to apply tags: add, remove or replace (Textline's default if omitted).

No output schema declared.

No examples provided.

Install

How do I install the Textline MCP by usefulapi server?

Textline MCP by usefulapi is a hosted endpoint at https://textline.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 · textline.usefulapi.io

# add to Claude Code
claude mcp add --transport http io-usefulapi-textline 'https://textline.usefulapi.io/mcp'
Common questions

What is the Textline MCP by usefulapi server?

Textline MCP by usefulapi is listed in the public MCP registry as io.usefulapi/textline. Read Textline conversations, contacts and reports; send a text, add notes, resolve or transfer. This page covers its hosted endpoint (https://textline.usefulapi.io/mcp).

Is the Textline MCP by usefulapi server safe to use?

Textline MCP by usefulapi scores 66 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 Textline MCP by usefulapi server expose?

Textline MCP by usefulapi exposes 23 tools: textline_list_conversations, textline_get_conversation, textline_get_conversation_by_phone, textline_list_customers, textline_get_customer, and 18 more. Their descriptions and schemas cost roughly 2,503 tokens of context every time the server is loaded.

Does the Textline MCP by usefulapi server require authentication?

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

Textline MCP by usefulapi is still listed as active in the MCP registry. We last reached this channel on 18 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.