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.

TextKit

REMOTE · MCP.JOINTEXTKIT.COM

SMS for developers: send and receive texts, verify phones, and buy US and Canada numbers.

Available components

remote · mcp.jointextkit.com 82
+4 this week 82 Trust /100

Last scanned (5 hours ago)

Scores higher than 85% of remote servers

Reachable. Last reached 5 Nov 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 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
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
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

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.

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

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 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. DS published 19718 13 Verified
jointextkit.com. DS published 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/
MCP tools · 152 exposed · ~14,609 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
verify_link_domain ~45

Check a link domain's DNS records now. When both are found it is turned on (active) at once.

NameTypeReqDescription
idstringyesLink domain id (ld_...)

No output schema declared.

No examples provided.

wait_for_events ~68

Wait up to 25 seconds for the next events after a cursor (a reply, a delivery receipt), then return them.

NameTypeReqDescription
cursorstring–The `cursor` of the previous response. Omit on the first call.
timeoutinteger–Seconds to hold the request.

No output schema declared.

No examples provided.

Install

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

# add to Claude Code
claude mcp add --transport http com-jointextkit-textkit 'https://mcp.jointextkit.com/'
Common questions

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.

What did VerifyMCP test on the TextKit MCP server?

VerifyMCP ran 13 checks on TextKit, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.