TextKit
REMOTE · MCP.JOINTEXTKIT.COM
SMS for developers: send and receive texts, verify phones, and buy US and Canada numbers.
Available components
Last scanned (2 hours ago)
Scores higher than 85% 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 Security97
- 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
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
- 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 Usability81
- 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 15326 tokens (~100/item across 152 items; 152 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 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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 21 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 153 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities40
- Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28. See how to fix → Fail
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.
- 4 Nov 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.
- 3 Nov 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “create_automation” rewrote its description, which is the text the model reads security
- Tool “plan_campaign” rewrote its description, which is the text the model reads security
- Tool “preview_automation” rewrote its description, which is the text the model reads security
- Tool “send_batch” rewrote its description, which is the text the model reads security
- Tool “send_message” rewrote its description, which is the text the model reads security
- Schema quality: pass → fail ▼ functional
- Server version: 1.0.0+5ba17e9f → 1.0.0+69219112 functional
- “send_batch” added an optional parameter “send_at_local” cosmetic
- “create_schedule” reworded the description of “quiet_hours” cosmetic
- “preview_automation” reworded the description of “to” cosmetic
- “send_batch” reworded the description of “quiet_hours” cosmetic
- “send_message” reworded the description of “quiet_hours” cosmetic
- “send_message” reworded the description of “scheduled_at” cosmetic
- “send_message” reworded the description of “shorten_links” cosmetic
- “update_automation” reworded the description of “step” cosmetic
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “list_toll_free_verifications” rewrote its description, which is the text the model reads security
- Server version: 1.0.0+51517bf4 → 1.0.0+5ba17e9f functional
- 31 Oct 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- New tool “create_link”, which the server declares destructive security
- New tool “record_conversion”, which the server declares destructive security
- Tool “activate_automation” rewrote its description, which is the text the model reads security
- Tool “create_automation” rewrote its description, which is the text the model reads security
- Tool “create_link_domain” rewrote its description, which is the text the model reads security
- Tool “list_link_domains” rewrote its description, which is the text the model reads security
- Tool “send_batch” rewrote its description, which is the text the model reads security
- Tool “update_automation” rewrote its description, which is the text the model reads security
- Server version: 1.0.0+795e87c1 → 1.0.0+51517bf4 functional
- New tool “list_conversions” functional
- New tool “list_links” functional
- “create_automation” added an optional parameter “category” cosmetic
- “update_automation” added an optional parameter “category” cosmetic
- “create_automation” reworded the description of “from” cosmetic
- “send_batch” reworded the description of “from” cosmetic
- “send_message” reworded the description of “shorten_links” cosmetic
- “update_automation” reworded the description of “from” cosmetic
- 30 Oct 26 +1
We did not load change detail this far back for this component, so this day may have recorded more than is shown.
- Tool “create_list” rewrote its description, which is the text the model reads security
- Tool “bulk_update_numbers” rewrote its description, which is the text the model reads security
- Tool “send_batch” rewrote its description, which is the text the model reads security
- Tool “connect_integration” rewrote its description, which is the text the model reads security
- Tool “create_automation” rewrote its description, which is the text the model reads security
- Tool “create_segment” rewrote its description, which is the text the model reads security
- Tool “list_link_domains” rewrote its description, which is the text the model reads security
- Tool “plan_import” rewrote its description, which is the text the model reads security
- Tool “preview_segment” rewrote its description, which is the text the model reads security
- Tool “update_automation” rewrote its description, which is the text the model reads security
- Tool “update_integration” rewrote its description, which is the text the model reads security
- Schema quality: 80 → 97 ▼ functional
- Schema quality: 80 → 90 ▼ functional
- Tool coverage: 67% → 100% ▲ functional
- Stability: unverified → 0.03 ▲ functional
- Server version: 1.0.0+e2ccd528 → 1.0.0+795e87c1 functional
- Server version: 1.0.0+8daf0c1f → 1.0.0+e2ccd528 functional
- New tool “get_integration_events” functional
- “send_batch” added an optional parameter “shorten_links” cosmetic
- “connect_integration” added an optional parameter “eventTriggers” cosmetic
- “update_automation” added an optional parameter “if_updated_at” cosmetic
- “update_automation” added an optional parameter “step” cosmetic
- “update_integration” added an optional parameter “eventTriggers” cosmetic
- “add_to_list” reworded the description of “contact_ids” cosmetic
- “add_to_list” reworded the description of “phone_numbers” cosmetic
- “bulk_purchase_numbers” reworded the description of “area_code” cosmetic
- “bulk_purchase_numbers” reworded the description of “quantity” cosmetic
- “bulk_purchase_numbers” reworded the description of “tags” cosmetic
- “bulk_update_contacts” reworded the description of “action” cosmetic
- “bulk_update_contacts” reworded the description of “ids” cosmetic
- “bulk_update_numbers” reworded the description of “action” cosmetic
- “bulk_update_numbers” reworded the description of “ids” cosmetic
- “clone_number_pool” reworded the description of “name” cosmetic
- “connect_integration” reworded the description of “provider” cosmetic
- “connect_integration” reworded the description of “sfObject” cosmetic
- “create_automation” reworded the description of “name” cosmetic
- “create_automation” reworded the description of “steps” cosmetic
- “create_automation” reworded the description of “trigger” cosmetic
- “create_customer” reworded the description of “name” cosmetic
- “create_link_domain” reworded the description of “domain” cosmetic
- “create_list” reworded the description of “description” cosmetic
- “create_list” reworded the description of “name” cosmetic
- “create_number_pool” reworded the description of “description” cosmetic
- “create_number_pool” reworded the description of “name” cosmetic
- “create_schedule” reworded the description of “body” cosmetic
- “create_schedule” reworded the description of “repeat” cosmetic
- “create_schedule” reworded the description of “to” cosmetic
- “create_segment” reworded the description of “description” cosmetic
- “create_segment” reworded the description of “match” cosmetic
- “create_segment” reworded the description of “name” cosmetic
- “create_segment” reworded the description of “rules” cosmetic
- “create_template” reworded the description of “body” cosmetic
- “create_template” reworded the description of “name” cosmetic
- “create_topic” reworded the description of “description” cosmetic
- “create_topic” reworded the description of “name” cosmetic
- “create_webhook” reworded the description of “description” cosmetic
- “create_webhook” reworded the description of “url” cosmetic
- “export_consent” reworded the description of “type” cosmetic
- “export_numbers” reworded the description of “mode” cosmetic
- “export_numbers” reworded the description of “pool” cosmetic
- “export_numbers” reworded the description of “q” cosmetic
- “export_numbers” reworded the description of “tag” cosmetic
- “get_deliverability” reworded the description of “group_by” cosmetic
- “import_contacts” reworded the description of “contacts” cosmetic
- “import_contacts” reworded the description of “dry_run” cosmetic
- “import_opt_outs” reworded the description of “phone_numbers” cosmetic
- “link_number_to_registration” reworded the description of “registration_id” cosmetic
- “list_audit_logs” reworded the description of “cursor” cosmetic
- “list_audit_logs” reworded the description of “limit” cosmetic
- “list_batch_recipients” reworded the description of “status” cosmetic
- “list_batches” reworded the description of “status” cosmetic
- “list_contacts” reworded the description of “list_id” cosmetic
- “list_contacts” reworded the description of “segment_id” cosmetic
- “list_contacts” reworded the description of “tag” cosmetic
- “list_customers” reworded the description of “cursor” cosmetic
- “list_customers” reworded the description of “limit” cosmetic
- “list_events” reworded the description of “type” cosmetic
- “list_list_contacts” reworded the description of “cursor” cosmetic
- “list_list_contacts” reworded the description of “limit” cosmetic
- “list_messages” reworded the description of “direction” cosmetic
- “list_messages” reworded the description of “status” cosmetic
- “list_numbers” reworded the description of “mode” cosmetic
- “list_numbers” reworded the description of “tag” cosmetic
- “list_toll_free_verifications” reworded the description of “limit” cosmetic
- “list_toll_free_verifications” reworded the description of “status” cosmetic
- “purchase_number” reworded the description of “phone_number” cosmetic
- “query_audience” reworded the description of “match” cosmetic
- “query_audience” reworded the description of “rules” cosmetic
- “recommend_message” reworded the description of “limit” cosmetic
- “remove_from_list” reworded the description of “contact_ids” cosmetic
- “remove_from_list” reworded the description of “phone_numbers” cosmetic
- “replay_event” reworded the description of “endpoint_id” cosmetic
- “request_short_code” reworded the description of “business_name” cosmetic
- “request_short_code” reworded the description of “monthly_volume” cosmetic
- “request_short_code” reworded the description of “type” cosmetic
- “search_available_numbers” reworded the description of “area_code” cosmetic
- “send_batch” reworded the description of “body” cosmetic
- “send_batch” reworded the description of “contact_ids” cosmetic
- “send_batch” reworded the description of “name” cosmetic
- “send_batch” reworded the description of “recipients” cosmetic
- “send_message” reworded the description of “body” cosmetic
- “send_message” reworded the description of “to” cosmetic
- “set_consent” reworded the description of “note” cosmetic
- “set_consent” reworded the description of “status” cosmetic
- “set_contact_topic” reworded the description of “subscribed” cosmetic
- “set_spend_limit” reworded the description of “alert_thresholds” cosmetic
- “simulate_inbound” reworded the description of “body” cosmetic
- “simulate_inbound” reworded the description of “from” cosmetic
- “track_event” reworded the description of “phone” cosmetic
- “track_event” reworded the description of “user_id” cosmetic
- “update_automation” reworded the description of “name” cosmetic
- “update_automation” reworded the description of “trigger” cosmetic
- “update_contact” reworded the description of “company” cosmetic
- “update_contact” reworded the description of “email” cosmetic
- “update_contact” reworded the description of “first_name” cosmetic
- “update_contact” reworded the description of “last_name” cosmetic
- “update_contact” reworded the description of “name” cosmetic
- “update_contact” reworded the description of “notes” cosmetic
- “update_contact” reworded the description of “source” cosmetic
- “update_contact” reworded the description of “state” cosmetic
- “update_contact” reworded the description of “tags” cosmetic
- “update_customer” reworded the description of “name” cosmetic
- “update_integration” reworded the description of “accessToken” cosmetic
- “update_integration” reworded the description of “apiKey” cosmetic
- “update_integration” reworded the description of “consentEvent” cosmetic
- “update_integration” reworded the description of “consentField” cosmetic
- “update_integration” reworded the description of “name” cosmetic
- “update_integration” reworded the description of “phoneEvent” cosmetic
- “update_integration” reworded the description of “phoneEventProperty” cosmetic
- “update_integration” reworded the description of “phoneField” cosmetic
- “update_integration” reworded the description of “secret” cosmetic
- “update_integration” reworded the description of “secretKey” cosmetic
- “update_integration” reworded the description of “sourceId” cosmetic
- “update_integration” reworded the description of “status” cosmetic
- “update_integration” reworded the description of “username” cosmetic
- “update_list” reworded the description of “description” cosmetic
- “update_list” reworded the description of “name” cosmetic
- “update_number_pool” reworded the description of “description” cosmetic
- “update_number_pool” reworded the description of “name” cosmetic
- “update_segment” reworded the description of “description” cosmetic
- “update_segment” reworded the description of “match” cosmetic
- “update_segment” reworded the description of “name” cosmetic
- “update_segment” reworded the description of “rules” cosmetic
- “update_template” reworded the description of “body” cosmetic
- “update_template” reworded the description of “name” cosmetic
- “update_topic” reworded the description of “description” cosmetic
- “update_topic” reworded the description of “name” cosmetic
- “update_webhook” reworded the description of “description” cosmetic
- “update_webhook” reworded the description of “events” cosmetic
- “update_webhook” reworded the description of “url” cosmetic
- “upsert_contact” reworded the description of “company” cosmetic
- “upsert_contact” reworded the description of “email” cosmetic
- “upsert_contact” reworded the description of “first_name” cosmetic
- “upsert_contact” reworded the description of “last_name” cosmetic
- “upsert_contact” reworded the description of “notes” cosmetic
- “upsert_contact” reworded the description of “state” cosmetic
- “upsert_contact” reworded the description of “tags” cosmetic
- “send_message” reworded the description of “shorten_links” cosmetic
- “update_automation” reworded the description of “steps” cosmetic
- 29 Oct 26 78
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 5 Nov 2026 · Probed https://mcp.jointextkit.com
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.jointextkit.com | CN=YR2,O=Let's Encrypt,C=US | 28 Oct 2026 | 26 Jan 2027 | RSA 2048 | SHA256-RSA | 6c53f993074f2fbf171fd6c8255fb6b6916 |
| SANs: mcp.jointextkit.com | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of mcp.jointextkit.com. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| jointextkit.com. | present | 54022 | 8 | Verified |
| mcp.jointextkit.com. | Verified address RRset verified with the apex keys |
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 resource_metadata="https://mcp.jointextkit.com/.well-known/oauth-protected-resource"
Bearer resource_metadata="https://mcp.jointextkit.com/.well-known/oauth-protected-resource"| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains; preload |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | origin-when-cross-origin |
| permissions-policy | accelerometer=(), browsing-topics=(), camera=(), display-capture=(), geolocation=(), gyroscope=(), hid=(), magnetometer=(), microphone=(), midi=(), payment=(), serial=(), usb=(), clipboard-write=(self) |
Protected resource metadata
| Document | https://mcp.jointextkit.com/.well-known/oauth-protected-resource |
|---|---|
| Retrieved | Yes |
| Resource | https://mcp.jointextkit.com |
| Authorisation server | https://jointextkit.com |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.jointextkit.com | Verified | 200 | |
| http (plaintext) | http://mcp.jointextkit.com | HTTPS enforced | 308 | https://mcp.jointextkit.com/ |
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 →
activate_automation Activate automation ~72
Turn an automation on, so tracked events start runs. With a live number it texts real people. With no `from`, a number approved for its `category` must exist or `issues` says what is missing; `sender` shows the numbers it will use.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Automation id |
No output schema declared.
No examples provided.
add_to_list Add to list ~72
Add contacts to a list by contact_ids and/or phone_numbers (up to 1,000; numbers must already be contacts).
| Name | Type | Req | Description |
|---|---|---|---|
| contact_ids | array | – | Contact ids |
| id | string | yes | List id |
| phone_numbers | array | – | Phone numbers in E.164, of existing contacts |
No output schema declared.
No examples provided.
assign_number_to_customer Assign number to customer ~67
Platforms: attribute a number (and its messages and usage) to one of your customers, or clear it with customer_id null.
| Name | Type | Req | Description |
|---|---|---|---|
| customer_id | string | yes | A customer id, or null to unassign |
| phone_number | string | yes | E.164 number you own |
No output schema declared.
No examples provided.
bulk_purchase_numbers Bulk purchase numbers ~157
Buy several numbers in one area code at once (e.g. for a sender pool). Live numbers are billed monthly each.
| Name | Type | Req | Description |
|---|---|---|---|
| area_code | string | yes | Three-digit area code to buy in |
| idempotency_key | string | – | Optional. Retries are already safe: the same call with the same inputs within 10 minutes is done once and answers with the first result. Pass your own key to dedupe across a longer gap, or a new one… |
| pool_id | string | – | Add the new numbers to this pool |
| quantity | integer | yes | How many numbers to buy (1 to 50) |
| tags | array | – | Tags to put on the new numbers |
No output schema declared.
No examples provided.
bulk_update_contacts Bulk update contacts ~71
Add tags to, remove tags from, or delete many contacts by id.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | add_tags and remove_tags take tags, delete removes the contacts |
| ids | array | yes | Contact ids, up to 500 |
| tags | array | – | Required for add_tags and remove_tags |
No output schema declared.
No examples provided.
bulk_update_numbers Bulk update numbers ~149
Act on many numbers at once: tag, untag, label, add to or remove from a pool, or release. Releasing cannot be undone.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | add_to_pool and remove_from_pool take pool_id, add_tags and remove_tags take tags, set_label takes label, release takes confirm |
| confirm | string | – | release only |
| ids | array | yes | Numbers to act on, in E.164 |
| label | string | – | set_label; null clears |
| pool_id | string | – | add_to_pool / remove_from_pool |
| tags | array | – | add_tags / remove_tags. Lowercased; up to 20 per number. |
No output schema declared.
No examples provided.
cancel_automation_run Cancel automation run ~35
Cancel a run in progress.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Automation id |
| run_id | string | yes | Run id |
No output schema declared.
No examples provided.
cancel_batch Cancel batch ~27
Cancel a batch. Messages already sent stay sent.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Batch id |
No output schema declared.
No examples provided.
cancel_scheduled_message Cancel scheduled message ~28
Cancel a scheduled message before it sends.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Scheduled message id |
No output schema declared.
No examples provided.
check_verification Check verification ~124
Check a verification code submitted by a user, by the phone or email it went to. Returns {verified, status, channel, charged}. Billed only when verified is true.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | The code last sent |
| string | – | The address the code was emailed to. After a fallback, check by `email`: the code proves the address, not the phone, and a check by `phone` answers 409 `invalid_state`. | |
| phone | string | – | The number the code was texted to. Send this or `email`. |
No output schema declared.
No examples provided.
clone_number_pool Clone number pool ~39
Copy a sender pool under a new name.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Pool id |
| name | string | – | Name of the new pool |
No output schema declared.
No examples provided.
connect_integration Connect integration ~734
Connect a tool so its people sync in as contacts, in a list of their own, every 6 hours: Mixpanel (projectId, username, secret = a service account; sourceId = cohort id), Amplitude (apiKey, secretKey, sourceId), HubSpot (accessToken), Shopify (shopDomain, accessToken), Salesforce, or a webhook. Takes the event or property that shows people agreed to texts (consentEvent / consentField) and the property that holds their phone (phoneField). Credentials are proved with one read, sealed, and never returned. Mixpanel also takes eventTriggers, which turn Mixpanel events into TextKit events that start, end or branch automations; `warnings` names mapped events with no volume in 7 days.
| Name | Type | Req | Description |
|---|---|---|---|
| accessToken | string | – | HubSpot private app token, or Shopify Admin API access token. |
| apiKey | string | – | Amplitude API key. |
| clientId | string | – | Salesforce consumer key, or Shopify client id. |
| clientSecret | string | – | Salesforce consumer secret, or Shopify client secret. |
| consentEvent | string | – | Mixpanel / Amplitude: the opt-in event the cohort is built on (e.g. SMS Opt In). Everyone in the cohort is recorded as opted in, from that event. |
| consentField | string | – | The tool's property that records SMS consent (e.g. sms_opt_in). |
| eventTriggers | array | – | Mixpanel (with a service account): events to turn into TextKit events within about 10 minutes, so automations start, wait and branch on them. Each entry is a TextKit event name and the Mixpanel event… |
| instanceUrl | string | – | Salesforce My Domain URL. |
| mode | string | – | Mixpanel / Amplitude: pull with credentials every 6 hours (default when credentials are sent), or push: no credentials, the tool's cohort sync posts to the ingest URL. |
| name | string | – | What to call it (default: the tool and its source). |
| phoneEvent | string | – | Mixpanel: an event that carries the number when profiles do not (e.g. Verification Check Success). A member with no phone on the profile gets it from their latest such event. |
| phoneEventProperty | string | – | Mixpanel: that event's property holding the number (default phone). |
| phoneField | string | – | The tool's property holding the mobile number, when not the usual one ($phone, phone, mobilephone). |
| projectId | string | – | Mixpanel project id. |
| provider | string | yes | The tool to connect |
| region | string | – | Mixpanel / Amplitude data residency. |
| secret | string | – | Mixpanel service account secret. |
| secretKey | string | – | Amplitude secret key. |
| sfObject | string | – | Salesforce: the object to sync |
| shopDomain | string | – | Shopify store, like acme.myshopify.com. |
| sourceId | string | – | Mixpanel or Amplitude cohort id; HubSpot list id; Salesforce campaign id; a Shopify customer search. Blank = everyone (HubSpot, Shopify, Salesforce). |
| username | string | – | Mixpanel service account username. |
No output schema declared.
No examples provided.
create_api_key Create api key ~121
Create an API key for an app you are building, to store as a secret in its environment (for example TEXTKIT_API_KEY) so the app can send texts itself. Same mode (test or live) as this connection; optional scopes limit it. The secret is returned once; the account owner is emailed.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | What the key is for, e.g. "Booking app" |
| scopes | array | – | Limit the key to these scopes (see /docs/authentication). Omit for full access (full-access callers only). |
No output schema declared.
No examples provided.
create_automation Create automation ~399
Create a triggered text flow (as a draft): when trigger.event is tracked, run steps such as send_sms, wait, wait_for_event, and condition branches. Example: on cart_abandoned, wait 3600s, then if checkout_completed was not received send a reminder. A send_sms step with send_time: "optimal_user_time" and max_wait_seconds (60 to 86400, required) waits for the hour that person usually replies or clicks, 10am their time with no history, inside quiet hours: recommend it for marketing and lifecycle texts, leave it off anything time-sensitive, and it is refused for one-time codes and order or shipping texts. For events that repeat, trigger.cooldown_seconds stops the same person starting it again for that long. Merge fields like {{plan}} fill from the trigger event's properties; `issues` names any no tracked event carries. Leave out `from` and TextKit picks a number approved for `category` (marketing, transactional for alerts, otp for codes) when it sends; `sender` shows the numbers, and `issues` says so when none is approved yet. Pass `from` only to pin a number. Drafts send nothing until activated.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | What it sends: marketing, alerts (transactional) or codes (otp). With no `from`, TextKit picks a number approved for this. Falls back to a built-in topic. |
| from | string | – | One of your numbers, to pin the flow to it. Leave it out and TextKit picks a number approved for `category`. A sandbox number makes it a sandbox flow. |
| name | string | – | Automation name |
| steps | array | – | Up to 20 steps, run in order |
| topic_id | string | – | Skip recipients unsubscribed from this topic. |
| trigger | object | – | What starts a run: an event, with optional filters |
No output schema declared.
No examples provided.
create_customer Create customer ~65
Platforms sending for other businesses: create a customer to attribute numbers, messages and usage to.
| Name | Type | Req | Description |
|---|---|---|---|
| external_id | string | – | Your id for them; unique per account |
| metadata | object | – | Up to 50 string values |
| name | string | – | The customer's name |
No output schema declared.
No examples provided.
create_link Create link ~106
Make a tracked short link to copy into a text, ad, email or anywhere else: returns short_url. The same url again returns the same link. Suggest this whenever someone wants to know whether a link gets clicked or leads to sales. A link inside a text needs only shorten_links: true on the send.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | – | Optional. Your name for it. |
| url | string | yes | Where the link goes. Public shorteners and look-alike domains are refused. |
No output schema declared.
No examples provided.
create_link_domain Create link domain ~77
Add a subdomain of the user's own (links.example.com) for short links. Returns two DNS records (CNAME and TXT) the user adds at their DNS host; then verify the domain. Optional: without one, tracked links use our domain.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | A subdomain you own, like links.example.com |
No output schema declared.
No examples provided.
create_list Create list ~57
Create a list: a fixed group of contacts (Audience → Lists). Membership is set by hand, unlike a segment, which follows rules.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | What the list is for |
| name | string | – | List name |
No output schema declared.
No examples provided.
create_number_pool Create number pool ~88
Create a sender pool from numbers you own.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | What the pool is for |
| name | string | yes | Pool name |
| routing | string | – | How a recipient gets a number. sticky: the same member every time. local: a member in the recipient's area code, else one in their time zone, else any; still the same one each time. |
No output schema declared.
No examples provided.
create_schedule Create schedule ~354
Send the same text to one number every day, week or month at a local time (e.g. a weekly reminder). Every occurrence runs the usual send checks.
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | yes | The text sent each time |
| category | string | – | Optional. It can make each occurrence stricter (`marketing`), never looser: the sending number's registration and the wording decide ([which messages are marketing](/docs/compliance-checks#which-mess… |
| end_date | string | – | Last local date it may run (inclusive). |
| from | string | – | One of your numbers. Optional when the account has exactly one number for the key's mode. |
| idempotency_key | string | – | Optional. Retries are already safe: the same call with the same inputs within 10 minutes is done once and answers with the first result. Pass your own key to dedupe across a longer gap, or a new one… |
| max_occurrences | integer | – | The schedule completes after this many messages have been sent. |
| quiet_hours | string | – | Optional. What to do with a message in the recipient's quiet hours: `block` refuses it (403 quiet_hours), `defer` holds it until their next 9:00am. Omitted: an occurrence in quiet hours is held until… |
| repeat | object | yes | When it sends: how often, the local time and the time zone |
| start_date | string | – | First local date it may run. Defaults to today. |
| to | string | yes | Recipient's number in E.164 |
No output schema declared.
No examples provided.
create_segment Create segment ~229
Save an audience (a segment, a cohort): it appears in the console under Audience → Segments, and broadcasts can be sent to it. Everyone who can be texted: one rule, status is subscribed. Contacts matching all (or any) of up to 10 rules. Attributes: tags, contact fields, custom fields (field = "field", key = the name), opt-in status, topic, import, created_at. Behaviour: last_message_at, last_reply_at, batch (key = batch id; value included, sent, failed, skipped or replied) and event (key = a tracked event name). Times take an ISO date or a window like 7d. It is evaluated live each time it is used, so a batch or list sent to it reaches whoever matches then.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | What the segment is for |
| match | string | – | all: a contact must match every rule. any: at least one rule |
| name | string | – | Segment name |
| rules | array | – | Up to 10 rules that decide who matches |
No output schema declared.
No examples provided.
create_template Create template ~61
Save a message template. Merge tags: {{first_name}}, {{name}}, {{phone}}, {{field:<custom>}}, and per-recipient variables.
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | yes | The message text, with merge tags |
| name | string | yes | Template name |
No output schema declared.
No examples provided.
create_topic Create topic ~53
Create a subscription topic, so people can opt out of one kind of message (e.g. promotions) and keep others.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | What the topic covers |
| name | string | yes | Topic name |
No output schema declared.
No examples provided.
create_webhook Create webhook ~165
Send events (message.received, message.delivered, message.opted_out, ...) to a URL: your app, a CRM, an automation tool. Returns the signing secret once.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | A note on what the endpoint is for |
| events | – | – | Event types to receive. Omit, or send "*" or [], for every event. An unknown type is a 400. |
| numbers | array | – | Optional. Only events about these of your numbers (E.164): message events by their from/to, number events by phone_number. Events about no number (batches, credits, registrations) go only to endpoint… |
| url | string | yes | The https URL that receives the events |
No output schema declared.
No examples provided.
delete_automation Delete automation ~22
Delete an automation.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Automation id |
No output schema declared.
No examples provided.
delete_contact Delete contact ~35
Delete a contact. Messages, consent records, and topic preferences for the number are kept.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Contact id |
No output schema declared.
No examples provided.
delete_customer Delete customer ~21
Delete a customer.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Customer id |
No output schema declared.
No examples provided.
delete_link_domain Delete link domain ~35
Remove a branded link domain. Every short link already sent on it stops working.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Link domain id |
No output schema declared.
No examples provided.
delete_list Delete list ~25
Delete a list (its contacts stay).
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | List id |
No output schema declared.
No examples provided.
delete_message Delete message ~56
Delete a finished message (delivered, failed or received) and every copy of its text, for a privacy request. Opt-out records and billing are kept. Cannot be undone.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Message id (msg_...) |
No output schema declared.
No examples provided.
delete_number_pool Delete number pool ~28
Delete a sender pool. Its numbers are kept.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Pool id |
No output schema declared.
No examples provided.
delete_schedule Delete schedule ~22
Delete a recurring schedule.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Schedule id |
No output schema declared.
No examples provided.
delete_segment Delete segment ~26
Delete a segment. Contacts are not touched.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Segment id |
No output schema declared.
No examples provided.
delete_template Delete template ~21
Delete a template.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Template id |
No output schema declared.
No examples provided.
delete_topic Delete topic ~28
Delete a topic you created (built-in topics stay).
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Topic id |
No output schema declared.
No examples provided.
delete_webhook Delete webhook ~25
Delete a webhook endpoint.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Webhook endpoint id |
No output schema declared.
No examples provided.
disconnect_integration Disconnect integration ~37
Disconnect a tool: its credentials and its list are deleted; the contacts stay with their consent.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Integration id |
No output schema declared.
No examples provided.
export_consent Export consent ~50
The suppression list, or the full consent ledger with opt-in proof, as CSV text.
| Name | Type | Req | Description |
|---|---|---|---|
| type | string | – | suppressions: the opted-out numbers. ledger: every consent record, with proof |
No output schema declared.
No examples provided.
export_csv Export csv ~464
Export as CSV text for analysis: messages, deliveries, events, opt_outs, webhook_deliveries, usage, usage_monthly, audit_log or credit_history. At most 50,000 rows; narrow the date range with from and to.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | – | audit_log: one action, or a group prefix with a trailing dot (team.) |
| actor | string | – | audit_log: actor id or part of the actor email |
| batch | string | – | messages, deliveries: batch id (bc_...) |
| blocked_reason | string | – | messages, deliveries: blocked messages with this reason |
| created_after | string | – | audit_log: same as on GET /audit-logs (from is accepted too) |
| created_before | string | – | audit_log: same as on GET /audit-logs (to is accepted too) |
| customer_id | string | – | messages, deliveries |
| direction | string | – | messages |
| endpoint_id | string | – | webhook_deliveries (default: all endpoints) |
| failure_code | string | – | messages, deliveries: failed for this reason (the `failure.code` on a message) |
| from | string | – | ISO date/time or epoch ms (messages, deliveries, events, webhook_deliveries) |
| from_number | string | – | messages, deliveries: exact sender (E.164) |
| kind | string | yes | messages, deliveries, events, opt_outs, webhook_deliveries, usage, usage_monthly, audit_log or credit_history |
| months | integer | – | usage: daily rows for the last N months |
| number | string | – | messages, deliveries: digits matched against either side |
| ok | boolean | – | webhook_deliveries |
| q | string | – | messages: body/failure text; events: id/payload text |
| status | string | – | messages, deliveries |
| target_type | string | – | audit_log |
| to | string | – | Inclusive; a bare date means the end of that day (UTC) |
| to_number | string | – | messages, deliveries: exact recipient (E.164). `to`/`from` are the date range here. |
| type | string | – | events, webhook_deliveries |
No output schema declared.
No examples provided.
export_numbers Export numbers ~66
Your numbers as CSV text.
| Name | Type | Req | Description |
|---|---|---|---|
| mode | string | – | test for sandbox numbers, live for real ones |
| pool | string | – | Pool id |
| q | string | – | Matches digits of the number or its label |
| tag | string | – | Only numbers with this tag |
No output schema declared.
No examples provided.
fallback_verification Fallback verification ~131
The text did not arrive: email a new code for the same pending verification (one id, one charge). The emailed code replaces the texted one and is checked by the email address, which it proves (not the phone). Once per verification.
| Name | Type | Req | Description |
|---|---|---|---|
| channel | string | – | The channel to fall back to. Only `email` today. |
| string | yes | The address to email the code to | |
| id | string | yes | Verification id (ver_...) |
| user_ip | string | – | Optional. Your end user's IP address, counted in the same per-IP limit as POST /verify. |
No output schema declared.
No examples provided.
forget_identity Forget identity ~42
Privacy erasure: forget the phone number linked to a user_id, so its tracked events stop reaching automations.
| Name | Type | Req | Description |
|---|---|---|---|
| user_id | string | yes | Your user id |
No output schema declared.
No examples provided.
get_automation Get automation ~27
Retrieve an automation with its trigger and steps.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Automation id |
No output schema declared.
No examples provided.
get_automation_run Get automation run ~39
Retrieve one run with its step-by-step timeline.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Automation id |
| run_id | string | yes | Run id |
No output schema declared.
No examples provided.
get_balance Get balance ~18
Prepaid credit balance and auto-recharge setting.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_batch Get batch ~25
Retrieve a batch with its progress counts.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Batch id |
No output schema declared.
No examples provided.
get_batch_results Get batch results ~45
Results of a batch: delivered, failed, pending, replies, opt-outs (stops), spend, and failures grouped by reason.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Batch id |
No output schema declared.
No examples provided.
get_consent Get consent ~40
Whether a number is opted in or out, per registration, with its full consent history and proof.
| Name | Type | Req | Description |
|---|---|---|---|
| phone | string | yes | E.164 number |
No output schema declared.
No examples provided.
get_contact Get contact ~21
Retrieve a contact.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Contact id |
No output schema declared.
No examples provided.
get_contact_topics Get contact topics ~26
A contact's subscription to each topic.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Contact id |
No output schema declared.
No examples provided.
How do I install the TextKit MCP server?
TextKit is a hosted endpoint at https://mcp.jointextkit.com/, 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 · mcp.jointextkit.com
claude mcp add --transport http com-jointextkit-textkit 'https://mcp.jointextkit.com/'
What is the TextKit MCP server?
TextKit is an MCP server listed in the public MCP registry as com.jointextkit/textkit. SMS for developers: send and receive texts, verify phones, and buy US and Canada numbers. This page covers its hosted endpoint (https://mcp.jointextkit.com).
Is the TextKit MCP server safe to use?
TextKit scores 82 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 TextKit MCP server expose?
TextKit exposes 152 tools: send_message, get_message, delete_message, redact_message, list_messages, and 147 more. Their descriptions and schemas cost roughly 14,609 tokens of context every time the server is loaded.
Does the TextKit MCP server require authentication?
Yes. TextKit 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 TextKit MCP server still maintained?
TextKit 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.