Home / MCP registry index / com.jointextkit/textkit

TextKit

com.jointextkit/textkit in the official MCP registry. Endpoint https://mcp.jointextkit.com/. Source: github.com/textkithq/textkit-mcp.

The registry describes it as: SMS for developers: send and receive texts, verify phones, and buy US and Canada numbers.

We read its 152 tools on 2026-10-31. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.

A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.

Connect it

The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:

Claude Code

claude mcp add --transport http textkit https://mcp.jointextkit.com/

Cursor: ~/.cursor/mcp.json

{
  "mcpServers": {
    "textkit": {
      "url": "https://mcp.jointextkit.com/"
    }
  }
}

VS Code

code --add-mcp '{"name":"textkit","type":"http","url":"https://mcp.jointextkit.com/"}'

Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which.

Let Claude Code check servers as it adds them

With the free lazaretto-guard plugin installed, when Claude Code adds a server for you or writes one into an MCP config, the plugin reads the server's tools first and asks you if one of our rules matches. Install it, restart Claude Code, then ask it to run the command above.

Install lazaretto-guard

claude plugin marketplace add jamesdfinance-dev/lazaretto-plugins
claude plugin install lazaretto-guard@lazaretto-plugins

Tools it advertises

send_message get_message delete_message redact_message list_messages send_verification check_verification fallback_verification list_numbers request_short_code list_number_requests search_available_numbers purchase_number release_number lookup_phone simulate_inbound list_events get_verification get_number bulk_purchase_numbers link_number_to_registration assign_number_to_customer bulk_update_numbers export_numbers list_number_pools create_number_pool get_number_pool update_number_pool delete_number_pool clone_number_pool import_contacts plan_import upsert_contact list_contacts get_contact update_contact delete_contact bulk_update_contacts set_contact_topic create_list list_lists get_list update_list delete_list list_list_contacts add_to_list remove_from_list create_segment list_segments get_segment update_segment delete_segment query_audience preview_segment list_topics create_topic create_template list_templates get_template update_template and 92 more

Tool changes

We compare every full read of this server with the one before. No change in what its tools say has been seen since we started keeping this record on 2026-10-30.

Fingerprint of its tools at our last full read (2026-10-31): f8da05d9d1e6bbf0. A client can hash the tools it is served the same way and compare; the full value and a hash per tool are in this page as JSON.

Run this server? Show the check in your README

The badge reflects the latest weekly read:

Markdown

[![MCP tool check](https://lazaretto.dev/mcp-registry/com-jointextkit-textkit/badge.svg)](https://lazaretto.dev/mcp-registry/com-jointextkit-textkit)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.