Skip to content
ProtocolProbe
Explore

MCP servers › com.jointextkit › textkit

MCP server · registry snapshot 2026-10-30 · last tested 2026-10-30

textkit MCP server

Registry name com.jointextkit/textkit

by jointextkit.com · domain (the registry's namespace rule)repository owner on GitHub: textkithq (organization)Source ↗Website ↗

SMS for developers: send and receive texts, verify phones, and buy US and Canada numbers. — the publisher's description

4 of 4 record checks metRead-only · tools listed 2026-10-30version 1.0.2streamable HTTP152 tools

Summary

com.jointextkit/textkit is a remote MCP server listed in the official MCP registry at version 1.0.2, under the namespace of the domain jointextkit.com. Its linked repository is github.com/textkithq/textkit-mcp; GitHub reports its owner as textkithq, an organization. On 2026-10-30 ProtocolProbe connected to it in read-only mode and read its inventory: 152 tools, 0 resources and 4 prompts.

Record checks

4 of 4 record checks met · 4 do not apply · 1 not checked

  • met: Registry entry is active and says how to run it
  • met: Source repository link opens
  • met: Repository is not archived
  • met: Code pushed to the repository in the 90 days before our check
  • not checked: Repository publishes a security policy (SECURITY.md)
  • not applicable: Package names its licence with a standard (SPDX) identifier
  • not applicable: The version the registry lists can be installed and is not withdrawn
  • not applicable: npm package carries build provenance (attestation)
  • not applicable: No known critical or high advisory in the package or its dependencies
  • Not ranked by downloads: a remote server publishes no download figure
  • Not ranked by stars: 0 stars (ranked from 10)

From public records, not a safety rating. Each check with its reason · Is it safe to install?

Operate this server? Correct a fact · README badge · Run the checks yourself

Key facts

Runs
remote (hosted by the publisher)
Transport
streamable HTTP
Your own values
none declared (not a guarantee)
Sign-in
none needed to open a session
Repository
public
Tools
152
Last tested
2026-10-30

Tool list size

40,744 tokens on Claude Opus 5.5

Added to every request that loads this server's tools (152 tools). Counted with Anthropic's token counter on 2026-10-30, from the tool list we read on 2026-10-30. Median across 25,738 counted servers: 2,858 tokens. How it is counted

How a client gets in

Connects without signing in

Read from the server's public metadata on 2026-10-30 (mcp.jointextkit.com), in our read-only connection; no tool was called. It may have changed since. How it is read

Tool list at the three APIs

Not sent yet for this version (1.0.2).

Add to your client

Observed fact

This server accepted a session without any credential and lists 81 tools whose name or declaration suggests they change data (send_message, delete_message, redact_message, send_verification, check_verification and 76 more). That is our reading of the names; we did not call them. Source: our connection, 2026-10-30.

How fresh this is

Live-tested
yes, a real session (not a text-only review)
Last tested
2026-10-30
Mode
read-only (no tool calls)
Latest version
1.0.2, published 2026-10-30 (registry, as of the 2026-10-30 snapshot)
First listed version
2026-10-28 (earliest version still in the registry; older removed versions would be earlier)
Version history
3 versions listed, 2026-10-28 to 2026-10-30; 3 in the 90 days before the 2026-10-30 snapshot.
Most recent 3 versions
  • 1.0.2 · 2026-10-30
  • 1.0.1 · 2026-10-30
  • 1.0.0 · 2026-10-28
(versions still listed in the registry only)
Registry data
snapshot 2026-10-30
Package and repository
checked 2026-10-30
Engine
mcp-runtime-engine@0.1.0 · sdk@1.32.0

Dead or stale signals

None found in the records we hold

Looked for and not found: deprecated in the registry; repository link does not open; repository archived; no push in over 365 days. Does not apply: listed version cannot be installed or is withdrawn. Each line is a dated fact from a public record. It does not say whether the server still works, and a record can change after the date shown.

Changes since the last refresh

Version 1.0.0 (published 2026-10-28) → 1.0.2 (published 2026-10-30), between the registry lists of 2026-10-29 and 2026-10-30.

The publisher published no GitHub release note for this version: its repository publishes no GitHub releases.

Source: the official MCP Registry list on 2026-10-29 and on 2026-10-30; release notes from the GitHub Releases API, checked 2026-10-30.

What it is

What does this server offer?

Observed inventory
152tools
0resources
4prompts

None of its 152 tools are described as changing anything. For 152 the reading was uncertain, so no mark is shown.

  • send_messageon 98 other servers

    “Send one SMS from one of your numbers.”

    Publisher declares: read-only no · destructive yes · idempotent no · open-world yes

    13 inputs, 2 required
    • tostringrequired“Recipient's number in E.164”
    • fromstring“One of your numbers, or a sender pool id (pool_...): TextKit picks a pool member, the same one for each recipient every time.”
    • bodystringrequired“The message text”
    • customer_idstring“Optional.”
    • scheduled_atstring“Optional.”
    • categorystring“Optional.”
    • quiet_hoursstring“Optional.”
    • shorten_linksboolean“Optional.”
    • tagsarray“Optional.”
    • consentobject“Optional.”
    • mediaarray“Reserved for MMS; currently returns 400 mms_not_enabled.”
    • status_callbackstring“Optional.”
    • idempotency_keystring“Optional.”
  • get_messageon 24 other servers

    “Retrieve a message by its msg_...”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    1 input, 1 required
    • idstringrequired“Message id (msg_...)”
  • delete_messageon 12 other servers

    “Delete a finished message (delivered, failed or received) and every copy of its text, for a privacy request.”

    Publisher declares: read-only no · destructive yes · idempotent yes · open-world no

    1 input, 1 required
    • idstringrequired“Message id (msg_...)”
  • redact_message

    “Empty a finished message's text and media everywhere it is kept, keeping its status, price and timeline (redacted_at is set).”

    Publisher declares: read-only no · destructive yes · idempotent no · open-world no

    1 input, 1 required
    • idstringrequired“Message id (msg_...)”
  • list_messageson 44 other servers

    “List your messages, newest first.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    14 inputs
    • limitnumber“Max results (default 25, max 100)”
    • cursorstring“next_cursor from the previous page”
    • numberstring“Filter to messages to or from this number”
    • tostring“Exact destination number (E.164)”
    • fromstring“Exact sending number (E.164)”
    • statusstring“Only messages with this status”
    • blocked_reasonstring“Blocked messages with this reason.”
    • failure_codestring“Filter to messages that failed for this reason (the `failure.code` on a message)”
    • directionstring“outbound (sent) or inbound (received)”
    • created_afterstring“Inclusive.”
    • created_beforestring“Exclusive.”
    • customer_idstring“Filter to one customer's messages”
    • schedule_idstring“Filter to the occurrences of one recurring schedule (sch_...)”
    • tagstring“Filter to messages sent with this tag”
  • send_verification

    “Send a one-time verification code (OTP) to a phone number by text, or to an email address with channel "email".”

    Publisher declares: read-only no · destructive yes · idempotent no · open-world yes

    8 inputs
    • channelstring“How the code goes out.”
    • phonestring“The number to text the code to (channel `sms`).”
    • emailstring“The address to email the code to (channel `email`).”
    • app_namestring“Your product name, shown in the message”
    • user_ipstring“Optional.”
    • fromstring“Optional, channel `sms` only: send from a number you own instead of the TextKit pool”
    • customer_idstring“Optional: attribute the verification to one of your customers”
    • idempotency_keystring“Optional.”
  • check_verificationon 1 other server

    “Check a verification code submitted by a user, by the phone or email it went to.”

    Publisher declares: read-only no · destructive yes · idempotent no · open-world no

    3 inputs, 1 required
    • phonestring“The number the code was texted to.”
    • emailstring“The address the code was emailed to.”
    • codestringrequired“The code last sent”
  • fallback_verification

    “The text did not arrive: email a new code for the same pending verification (one id, one charge).”

    Publisher declares: read-only no · destructive yes · idempotent no · open-world yes

    4 inputs, 2 required
    • idstringrequired“Verification id (ver_...)”
    • emailstringrequired“The address to email the code to”
    • channelstring“The channel to fall back to.”
    • user_ipstring“Optional.”
  • list_numberson 5 other servers

    “List the phone numbers on your account.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    5 inputs
    • customer_idstring“Only this customer's numbers”
    • tagstring“Only numbers with this tag”
    • poolstring“Pool id”
    • modestring“test for sandbox numbers, live for real ones”
    • qstring“Matches digits of the number or its label”
  • request_short_code

    “Ask our team for a short code (or a toll-free number they set up).”

    Publisher declares: read-only no · destructive yes · idempotent no · open-world no

    4 inputs, 4 required
    • typestringrequired“short_code, or toll_free for a number our team sets up”
    • business_namestringrequired“The business the number is for”
    • monthly_volumestringrequired“Expected texts a month”
    • use_casestringrequired“What you will send, in a sentence or two.”
  • list_number_requests

    “Open short-code and toll-free requests.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    Takes no inputs.

  • search_available_numbers

    “Search purchasable numbers by area code (default 415).”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    1 input
    • area_codestring“Three-digit area code (default 415)”
Show 88 more tools
  • purchase_number

    “Buy a phone number for your account (free sandbox numbers with test keys).”

    Publisher declares: read-only no · destructive yes · idempotent no · open-world yes

    4 inputs, 1 required
    • phone_numberstringrequired“The number to buy, in E.164”
    • customer_idstring“Optional: assign the number to one of your customers”
    • registration_idstring“Optional (live numbers): the registration this number should send for.”
    • idempotency_keystring“Optional.”
  • release_numberon 1 other server

    “Release a number you own.”

    Publisher declares: read-only no · destructive yes · idempotent yes · open-world yes

    1 input, 1 required
    • phone_numberstringrequired“E.164 number you own”
  • lookup_phoneon 3 other servers

    “Look up line type (mobile, landline, VoIP) and carrier for any US/Canada number.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    1 input, 1 required
    • phonestringrequired“E.164 number”
  • simulate_inbound

    “Sandbox only: simulate an inbound SMS to one of your test numbers (emits message.received; STOP, START and HELP act as for real).”

    Publisher declares: read-only no · destructive yes · idempotent no · open-world yes

    3 inputs, 2 required
    • tostring“One of your sandbox numbers (never a live number).”
    • fromstringrequired“Who the simulated text comes from, in E.164”
    • bodystringrequired“The text of the simulated message”
  • list_eventson 111 other servers

    “List recent events (message.sent/delivered/failed/received, number.purchased/released, ...), newest first.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    3 inputs
    • limitnumber“Max results (default 25, max 100)”
    • cursorstring“next_cursor from the previous page”
    • typestring“Only events of this type, like message.delivered”
  • get_verificationon 11 other servers

    “Retrieve a verification by id: its status and attempts (never the code).”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    1 input, 1 required
    • idstringrequired“Verification id”
  • get_numberon 5 other servers

    “Retrieve one of your numbers: status, sender registration, tags, pools, customer.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    1 input, 1 required
    • phone_numberstringrequired“E.164 number you own”
  • bulk_purchase_numbers

    “Buy several numbers in one area code at once (e.g.”

    Publisher declares: read-only no · destructive yes · idempotent no · open-world yes

    5 inputs, 2 required
    • area_codestringrequired“Three-digit area code to buy in”
    • quantityintegerrequired“How many numbers to buy (1 to 50)”
    • pool_idstring“Add the new numbers to this pool”
    • tagsarray“Tags to put on the new numbers”
    • idempotency_keystring“Optional.”
  • link_number_to_registration

    “Attach a number to an approved 10DLC registration so it can send that registration's traffic.”

    Publisher declares: read-only no · destructive yes · idempotent no · open-world no

    2 inputs, 2 required
    • phone_numberstringrequired“E.164 number you own”
    • registration_idstringrequired“The approved registration to attach the number to (reg_...)”
  • assign_number_to_customer

    “Platforms: attribute a number (and its messages and usage) to one of your customers, or clear it with customer_id null.”

    Publisher declares: read-only no · destructive yes · idempotent no · open-world no

    2 inputs, 2 required
    • phone_numberstringrequired“E.164 number you own”
    • customer_idstringrequired“A customer id, or null to unassign”
  • bulk_update_numbers

    “Act on many numbers at once: tag, untag, label, add to or remove from a pool, or release.”

    Publisher declares: read-only no · destructive yes · idempotent no · open-world yes

    6 inputs, 2 required
    • idsarrayrequired“Numbers to act on, in E.164”
    • actionstringrequired“add_to_pool and remove_from_pool take pool_id, add_tags and remove_tags take tags, set_label takes label, release takes confirm”
    • pool_idstring“add_to_pool / remove_from_pool”
    • tagsarray“add_tags / remove_tags.”
    • labelstring“set_label; null clears”
    • confirmstring“release only”
  • export_numbers

    “Your numbers as CSV text.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    4 inputs
    • tagstring“Only numbers with this tag”
    • poolstring“Pool id”
    • modestring“test for sandbox numbers, live for real ones”
    • qstring“Matches digits of the number or its label”
  • list_number_pools

    “List sender pools.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    Takes no inputs.

  • create_number_pool

    “Create a sender pool from numbers you own.”

    Publisher declares: read-only no · destructive yes · idempotent no · open-world no

    3 inputs, 1 required
    • namestringrequired“Pool name”
    • descriptionstring“What the pool is for”
    • routingstring“How a recipient gets a number.”
  • get_number_pool

    “Retrieve a sender pool and its numbers.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    1 input, 1 required
    • idstringrequired“Pool id”
  • update_number_pool

    “Rename a sender pool or change its numbers.”

    Publisher declares: read-only no · destructive yes · idempotent no · open-world no

    4 inputs, 1 required
    • idstringrequired“Pool id”
    • namestring“Pool name”
    • descriptionstring“What the pool is for”
    • routingstring“How a recipient gets a number.”
  • delete_number_pool

    “Delete a sender pool.”

    Publisher declares: read-only no · destructive yes · idempotent yes · open-world no

    1 input, 1 required
    • idstringrequired“Pool id”
  • clone_number_pool

    “Copy a sender pool under a new name.”

    Publisher declares: read-only no · destructive yes · idempotent no · open-world no

    2 inputs, 1 required
    • idstringrequired“Pool id”
    • namestring“Name of the new pool”
  • import_contactson 4 other servers

    “Create or update up to 500 contacts per call, matched by phone_number.”

    Publisher declares: read-only no · destructive yes · idempotent no · open-world no

    6 inputs, 1 required
    • contactsarrayrequired“Contacts to create or update, up to 500 per call”
    • campaign_idstring“Applies to every opt_in row that does not name its own campaign_id”
    • dry_runboolean“true returns what would change and writes nothing”
    • check_line_typesboolean“dry_run only.”
    • import_idstring“From a previous response, to group several requests as one import.”
    • namestring“A label for the import (first request only).”
  • plan_import

    “Find out where an audience is and the ways to bring it in.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    1 input
    • sourcestring“Where the people are, in your words.”
  • upsert_contacton 1 other server

    “Create a contact, or update the existing one with the same phone_number.”

    Publisher declares: read-only no · destructive yes · idempotent no · open-world no

    12 inputs, 1 required
    • phone_numberstringrequired“E.164, US or Canada”
    • namestring“Display name.”
    • tagsarray“Labels that group contacts”
    • fieldsobject“Up to 20 string values (account id, plan, location...), usable in segments and as {{field:key}} merge fields”
    • notesstring“Free-text notes”
    • first_namestring“First name”
    • last_namestring“Last name”
    • emailstring“Email address”
    • companystring“Company name”
    • statestring“US state or Canadian province, usually a 2-letter code”
    • sourcestring“Where the contact came from.”
    • opt_inobject“Import only (POST /v1/contacts/import).”
  • list_contactson 25 other servers

    “List contacts, newest first.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    7 inputs
    • limitnumber“Max results (default 25, max 100)”
    • cursorstring“next_cursor from the previous page”
    • tagstring“Only contacts with this tag”
    • phone_numberstring“E.164”
    • segment_idstring“Only contacts in this segment”
    • list_idstring“Only contacts in this list”
    • qstring“Search text”
  • get_contacton 49 other servers

    “Retrieve a contact.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    1 input, 1 required
    • idstringrequired“Contact id”
  • update_contacton 15 other servers

    “Update a contact.”

    Publisher declares: read-only no · destructive yes · idempotent no · open-world no

    12 inputs, 1 required
    • idstringrequired“Contact id”
    • phone_numberstring“E.164, US or Canada”
    • namestring“Display name.”
    • tagsarray“Labels that group contacts”
    • fieldsobject“Up to 20 string values”
    • notesstring“Free-text notes.”
    • first_namestring“First name.”
    • last_namestring“Last name.”
    • emailstring“Email address.”
    • companystring“Company name.”
    • statestring“US state or Canadian province, usually a 2-letter code.”
    • sourcestring“Where the contact came from.”
  • delete_contacton 9 other servers

    “Delete a contact.”

    Publisher declares: read-only no · destructive yes · idempotent yes · open-world no

    1 input, 1 required
    • idstringrequired“Contact id”
  • bulk_update_contactson 1 other server

    “Add tags to, remove tags from, or delete many contacts by id.”

    Publisher declares: read-only no · destructive yes · idempotent no · open-world no

    3 inputs, 2 required
    • actionstringrequired“add_tags and remove_tags take tags, delete removes the contacts”
    • idsarrayrequired“Contact ids, up to 500”
    • tagsarray“Required for add_tags and remove_tags”
  • set_contact_topic

    “Subscribe a contact to a topic, or unsubscribe them (e.g.”

    Publisher declares: read-only no · destructive yes · idempotent yes · open-world no

    4 inputs, 3 required
    • idstringrequired“Contact id”
    • topicstringrequired“Topic id (see list_topics)”
    • subscribedbooleanrequired“true subscribes the contact to the topic, false unsubscribes them”
    • sourcestring“Where the change came from, e.g.”
  • create_liston 14 other servers

    “Create a list: a fixed group of contacts (Audience → Lists).”

    Publisher declares: read-only no · destructive yes · idempotent no · open-world no

    2 inputs
    • namestring“List name”
    • descriptionstring“What the list is for”
  • list_listson 15 other servers

    “List contact lists with their contact counts.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    Takes no inputs.

  • get_liston 20 other servers

    “Retrieve a list and its contact count.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    1 input, 1 required
    • idstringrequired“List id”
  • update_liston 5 other servers

    “Rename a list or change its description.”

    Publisher declares: read-only no · destructive yes · idempotent no · open-world no

    3 inputs, 1 required
    • idstringrequired“List id”
    • namestring“List name”
    • descriptionstring“What the list is for”
  • delete_liston 10 other servers

    “Delete a list (its contacts stay).”

    Publisher declares: read-only no · destructive yes · idempotent yes · open-world no

    1 input, 1 required
    • idstringrequired“List id”
  • list_list_contactson 1 other server

    “Page through a list's contacts, most recently added first.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    3 inputs, 1 required
    • idstringrequired“List id”
    • limitinteger“Max results (default 25, max 100)”
    • cursorstring“next_cursor from the previous page”
  • add_to_liston 4 other servers

    “Add contacts to a list by contact_ids and/or phone_numbers (up to 1,000; numbers must already be contacts).”

    Publisher declares: read-only no · destructive yes · idempotent no · open-world no

    3 inputs, 1 required
    • idstringrequired“List id”
    • contact_idsarray“Contact ids”
    • phone_numbersarray“Phone numbers in E.164, of existing contacts”
  • remove_from_liston 2 other servers

    “Remove contacts from a list (they stay contacts).”

    Publisher declares: read-only no · destructive yes · idempotent yes · open-world no

    3 inputs, 1 required
    • idstringrequired“List id”
    • contact_idsarray“Contact ids”
    • phone_numbersarray“Phone numbers in E.164, of existing contacts”
  • create_segmenton 11 other servers

    “Save an audience (a segment, a cohort): it appears in the console under Audience → Segments, and broadcasts can be sent to it.”

    Publisher declares: read-only no · destructive yes · idempotent no · open-world no

    4 inputs
    • namestring“Segment name”
    • descriptionstring“What the segment is for”
    • matchstring“all: a contact must match every rule.”
    • rulesarray“Up to 10 rules that decide who matches”
  • list_segmentson 13 other servers

    “List saved segments.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    Takes no inputs.

  • get_segmenton 7 other servers

    “Retrieve a segment and its rules.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    1 input, 1 required
    • idstringrequired“Segment id”
  • update_segmenton 9 other servers

    “Rename a segment or replace its rules.”

    Publisher declares: read-only no · destructive yes · idempotent no · open-world no

    5 inputs, 1 required
    • idstringrequired“Segment id”
    • namestring“Segment name”
    • descriptionstring“What the segment is for”
    • matchstring“all: a contact must match every rule.”
    • rulesarray“Up to 10 rules that decide who matches”
  • delete_segmenton 9 other servers

    “Delete a segment.”

    Publisher declares: read-only no · destructive yes · idempotent yes · open-world no

    1 input, 1 required
    • idstringrequired“Segment id”
  • query_audience

    “Count a cohort without saving anything (nothing appears in the console): run up to 10 segment rules now and get the counts (matched, opted out, eligible to text) and the first contacts.”

    Publisher declares: read-only no · destructive yes · idempotent no · open-world no

    4 inputs
    • matchstring“all: a contact must match every rule.”
    • rulesarray“Up to 10 rules that decide who matches”
    • topic_idstring“Topic id or name: eligible also removes contacts unsubscribed from it”
    • limitinteger“How many matching contacts to return”
  • preview_segmenton 1 other server

    “Count the contacts a segment matches right now and how many a broadcast would reach (opted-out contacts removed, and with topic_id those unsubscribed from it).”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    2 inputs, 1 required
    • idstringrequired“Segment id”
    • topic_idstring“Count only contacts subscribed to this topic”
  • list_topicson 59 other servers

    “List subscription topics.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    Takes no inputs.

  • create_topicon 11 other servers

    “Create a subscription topic, so people can opt out of one kind of message (e.g.”

    Publisher declares: read-only no · destructive yes · idempotent no · open-world no

    2 inputs, 1 required
    • namestringrequired“Topic name”
    • descriptionstring“What the topic covers”
  • create_templateon 21 other servers

    “Save a message template.”

    Publisher declares: read-only no · destructive yes · idempotent no · open-world no

    2 inputs, 2 required
    • namestringrequired“Template name”
    • bodystringrequired“The message text, with merge tags”
  • list_templateson 116 other servers

    “List message templates.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    Takes no inputs.

  • get_templateon 48 other servers

    “Retrieve a template.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    1 input, 1 required
    • idstringrequired“Template id”
  • update_templateon 18 other servers

    “Rename or edit a template.”

    Publisher declares: read-only no · destructive yes · idempotent no · open-world no

    3 inputs, 1 required
    • idstringrequired“Template id”
    • namestring“Template name”
    • bodystring“The message text, with merge tags”
  • delete_templateon 16 other servers

    “Delete a template.”

    Publisher declares: read-only no · destructive yes · idempotent yes · open-world no

    1 input, 1 required
    • idstringrequired“Template id”
  • recommend_message

    “Which text should we send?”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    15 inputs, 4 required
    • industrystringrequired“The sender's industry”
    • company_typestringrequired“Kind of business”
    • goalstring“The message type to write, or `any` to compare the types that fit `audience`”
    • audiencestring“Who gets it, in words, e.g.”
    • brandstringrequired“Business name as customers know it”
    • productstringrequired“What is being sold, as the customer would say it, e.g.”
    • offerstring“Optional, e.g.”
    • codestring“Optional promo code”
    • deadlinestring“Optional, e.g.”
    • linkstring“URL or merge field; default {{link}}”
    • first_nameboolean“Your contacts have first names, so candidates may use {{first_name}}”
    • first_messageboolean“The first text these people get from the number: the brand and opt-out line are added and counted”
    • candidatesstring“Your own drafts to score: a JSON array of up to 10 strings”
    • limitinteger“How many messages to return (default 5, max 20)”
    • use_historyboolean“false ranks on the case studies only”
  • send_batchon 1 other server

    “Send one message to many people (a broadcast or campaign): pick recipients by segment_id, tags, contact_ids, or an explicit recipients list.”

    Publisher declares: read-only no · destructive yes · idempotent no · open-world yes

    15 inputs, 1 required
    • fromstring“One of your numbers.”
    • bodystringrequired“The message text.”
    • namestring“A name for the broadcast”
    • recipientsarray“Explicit recipients, up to 10,000”
    • tagsarray“Send to contacts carrying any of these tags (instead of recipients).”
    • contact_idsarray“Send to these contacts, by id”
    • segment_idstring“Send to the contacts in this saved segment, evaluated when the batch is created (instead of recipients).”
    • list_idstring“Send to the contacts in this list, as it is when the batch is created (instead of recipients).”
    • categorystring“Optional.”
    • quiet_hoursstring“Optional.”
    • topic_idstring“Subscription topic.”
    • shorten_linksboolean“Optional.”
    • scheduled_atstring“Future ISO timestamp or epoch ms, up to 30 days out.”
    • dry_runboolean“Validate only: returns a BatchValidation and sends nothing.”
    • check_line_typesboolean“Reject landlines (first 500 unique numbers are checked).”
  • list_batcheson 4 other servers

    “List batches (broadcasts), newest first.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    3 inputs
    • limitnumber“Max results (default 25, max 100)”
    • cursorstring“next_cursor from the previous page”
    • statusstring“Only batches with this status”
  • get_batchon 8 other servers

    “Retrieve a batch with its progress counts.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    1 input, 1 required
    • idstringrequired“Batch id”
  • get_batch_results

    “Results of a batch: delivered, failed, pending, replies, opt-outs (stops), spend, and failures grouped by reason.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    1 input, 1 required
    • idstringrequired“Batch id”
  • list_batch_recipients

    “List a batch's recipients with each one's status.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    4 inputs, 1 required
    • idstringrequired“Batch id”
    • statusstring“Only recipients with this status”
    • limitnumber“Max results (default 25, max 100)”
    • cursorstring“next_cursor from the previous page”
  • pause_batch

    “Pause a sending or scheduled batch.”

    Publisher declares: read-only no · destructive yes · idempotent no · open-world no

    1 input, 1 required
    • idstringrequired“Batch id”
  • resume_batch

    “Resume a paused batch.”

    Publisher declares: read-only no · destructive yes · idempotent no · open-world yes

    1 input, 1 required
    • idstringrequired“Batch id”
  • cancel_batchon 2 other servers

    “Cancel a batch.”

    Publisher declares: read-only no · destructive yes · idempotent no · open-world no

    1 input, 1 required
    • idstringrequired“Batch id”
  • retry_batchon 1 other server

    “Retry a batch's failed recipients.”

    Publisher declares: read-only no · destructive yes · idempotent no · open-world yes

    1 input, 1 required
    • idstringrequired“Batch id”
  • track_eventon 2 other servers

    “Record something a customer did (e.g.”

    Publisher declares: read-only no · destructive yes · idempotent no · open-world yes

    5 inputs, 1 required
    • eventstringrequired“Letters, digits, and _ .”
    • user_idstring“Your id for the person.”
    • phonestring“The person's number in E.164”
    • propertiesobject“Up to 20 scalar values; usable as merge fields and in conditions.”
    • idempotency_keystring“Optional.”
  • plan_taskon 2 other servers

    “The questions behind anything a person does here, with this account's options for each: send a text, buy or release a number, register for 10DLC, verify a toll-free number, request a short code, veri…”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    1 input
    • taskstring“A task key (buy_number, register_10dlc, ...) or the person's own words ("buy a number").”
  • plan_campaignon 1 other server

    “Every input a send needs, as questions to ask the person, with this account's options for each.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    1 input
    • kindstring“automation (texts started by an event) or broadcast (one send to an audience).”
  • create_automationon 7 other servers

    “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.”

    Publisher declares: read-only no · destructive yes · idempotent no · open-world no

    5 inputs
    • namestring“Automation name”
    • fromstring“One of your numbers.”
    • topic_idstring“Skip recipients unsubscribed from this topic.”
    • triggerobject“What starts a run: an event, with optional filters”
    • stepsarray“Up to 20 steps, run in order”
  • list_automationson 14 other servers

    “List automations.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    Takes no inputs.

  • get_automationon 6 other servers

    “Retrieve an automation with its trigger and steps.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    1 input, 1 required
    • idstringrequired“Automation id”
  • update_automationon 5 other servers

    “Edit an automation (name, sender, trigger incl.”

    Publisher declares: read-only no · destructive yes · idempotent no · open-world no

    8 inputs, 1 required
    • idstringrequired“Automation id”
    • namestring“Automation name”
    • fromstring“One of your numbers.”
    • topic_idstring“Skip recipients unsubscribed from this topic.”
    • triggerobject“What starts a run: an event, with optional filters”
    • stepsarray“Replaces every step.”
    • stepobject“One of: send_sms {body, from?}; wait {seconds}; wait_for_event {event, timeout_seconds, on_received, on_timeout}; condition {check, on_met, on_not_met}; end.”
    • if_updated_atstring“The automation's `updated_at` as you read it.”
  • delete_automationon 4 other servers

    “Delete an automation.”

    Publisher declares: read-only no · destructive yes · idempotent yes · open-world no

    1 input, 1 required
    • idstringrequired“Automation id”
  • activate_automationon 1 other server

    “Turn an automation on, so tracked events start runs.”

    Publisher declares: read-only no · destructive yes · idempotent no · open-world yes

    1 input, 1 required
    • idstringrequired“Automation id”
  • pause_automationon 3 other servers

    “Pause an automation: no new runs start, and runs in progress wait where they are until it is activated again.”

    Publisher declares: read-only no · destructive yes · idempotent no · open-world no

    1 input, 1 required
    • idstringrequired“Automation id”
  • preview_automation

    “See an automation's texts exactly as they would go out, without sending: works on drafts.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    3 inputs, 1 required
    • idstringrequired“Automation id”
    • propertiesobject“Sample event properties for merge fields, e.g.”
    • tostring“E.164.”
  • test_automation

    “Text an automation's messages to your own verified phone or a verified recipient now, skipping waits and conditions, without activating it (drafts work).”

    Publisher declares: read-only no · destructive yes · idempotent no · open-world yes

    6 inputs, 2 required
    • idstringrequired“Automation id”
    • tostringrequired“E.164: your own verified phone or a verified recipient”
    • fromstring“Optional.”
    • propertiesobject“Sample event properties for merge fields”
    • stepsarray“Only these send_sms step ids.”
    • idempotency_keystring“Optional.”
  • list_automation_runson 2 other servers

    “List an automation's runs, newest first.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    3 inputs, 1 required
    • idstringrequired“Automation id”
    • limitnumber“Max results (default 25, max 100)”
    • cursorstring“next_cursor from the previous page”
  • get_automation_runon 1 other server

    “Retrieve one run with its step-by-step timeline.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    2 inputs, 2 required
    • idstringrequired“Automation id”
    • run_idstringrequired“Run id”
  • cancel_automation_run

    “Cancel a run in progress.”

    Publisher declares: read-only no · destructive yes · idempotent yes · open-world no

    2 inputs, 2 required
    • idstringrequired“Automation id”
    • run_idstringrequired“Run id”
  • get_topicon 26 other servers

    “Retrieve a topic.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    1 input, 1 required
    • idstringrequired“Topic id”
  • update_topicon 3 other servers

    “Rename or describe a topic.”

    Publisher declares: read-only no · destructive yes · idempotent no · open-world no

    3 inputs, 1 required
    • idstringrequired“Topic id”
    • namestring“Topic name”
    • descriptionstring“What the topic covers”
  • delete_topicon 3 other servers

    “Delete a topic you created (built-in topics stay).”

    Publisher declares: read-only no · destructive yes · idempotent yes · open-world no

    1 input, 1 required
    • idstringrequired“Topic id”
  • get_contact_topics

    “A contact's subscription to each topic.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    1 input, 1 required
    • idstringrequired“Contact id”
  • get_consent

    “Whether a number is opted in or out, per registration, with its full consent history and proof.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    1 input, 1 required
    • phonestringrequired“E.164 number”
  • set_consenton 2 other servers

    “Record an opt-in or opt-out from your own system (CRM, checkout, a form).”

    Publisher declares: read-only no · destructive yes · idempotent no · open-world no

    5 inputs, 2 required
    • phonestringrequired“E.164 number”
    • statusstringrequired“opted_in or opted_out”
    • notestring“A note kept on the consent record”
    • campaign_idstring“Only with opted_in: the registration the person opted in to.”
    • proofobject“Opt-in evidence (Messaging Policy 1.4).”
  • list_opt_outs

    “List opted-out numbers (the suppression list).”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    2 inputs
    • limitnumber“Max results (default 25, max 100)”
    • cursorstring“next_cursor from the previous page”
  • import_opt_outs

    “Bring a suppression list over from another provider or tool (up to 500 numbers per call), so people who opted out there are never texted here.”

    Publisher declares: read-only no · destructive yes · idempotent no · open-world no

    1 input, 1 required
    • phone_numbersarrayrequired“Opted-out numbers in E.164, up to 500 per call”
  • list_scheduled_messageson 2 other servers

    “List single messages scheduled for later and not yet sent.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    Takes no inputs.

  • get_scheduled_messageon 1 other server

    “Retrieve a pending scheduled message.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    1 input, 1 required
    • idstringrequired“Scheduled message id”
  • cancel_scheduled_message

    “Cancel a scheduled message before it sends.”

    Publisher declares: read-only no · destructive yes · idempotent yes · open-world no

    1 input, 1 required
    • idstringrequired“Scheduled message id”
  • create_scheduleon 14 other servers

    “Send the same text to one number every day, week or month at a local time (e.g.”

    Publisher declares: read-only no · destructive yes · idempotent no · open-world yes

    10 inputs, 3 required
    • tostringrequired“Recipient's number in E.164”
    • fromstring“One of your numbers.”
    • bodystringrequired“The text sent each time”
    • repeatobjectrequired“When it sends: how often, the local time and the time zone”
    • start_datestring“First local date it may run.”
    • end_datestring“Last local date it may run (inclusive).”
    • max_occurrencesinteger“The schedule completes after this many messages have been sent.”
    • categorystring“Optional.”
    • quiet_hoursstring“Optional.”
    • idempotency_keystring“Optional.”
  • list_scheduleson 20 other servers

    “List recurring schedules.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    Takes no inputs.

  • get_scheduleon 30 other servers

    “Retrieve a recurring schedule with its recent occurrences.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    1 input, 1 required
    • idstringrequired“Schedule id”

Each quoted sentence is the first sentence of the publisher’s own description. The kind of tool and the “changes data” mark are our AI model’s reading of that description, not something we tested: two differently worded runs had to agree, otherwise no label is shown, and nobody has checked them by hand. A tool without the “changes data” mark is described as only reading, searching or calculating, or the two runs did not agree. No tool was called. Read the publisher’s full description before relying on it. “Publisher declares” lists the hints the server itself sends with the tool (MCP annotations: read-only, destructive, idempotent, open-world); they are the publisher's claims, not checked by us. Inputs are the parameters in the tool's own input schema: name, declared type, whether it is required, and the first sentence of its description. The first 100 of 152 tools are listed. Read 2026-10-30.

How well are its tools described?

Features #4 and #5

How clearly this server's own tool descriptions say what a tool does, and how consistent its tool list is. The first part is an AI model's yes/no reading of each description; the second part is counted. We do not turn it into a grade.

Descriptions

AI reading of each description

No AI reading was available for this server's tools (the two runs did not agree, or the listing was not reviewed).

Counted from the listing

Parameters with a description
100% of 441
Tools with a description
100% of 152
Typical description length
125 characters

The tool set

Counted from the listing

Tools
152
Size of the list
about 31,795 tokens for an agent to load (characters ÷ 4)
Naming
152 of 152 names use snake_case

AI reading: easy to mix up

No pair found.

The AI items cover 0 of 152 tools: for a tool where two differently worded runs disagreed, that item is left out. They were not checked by hand, and no tool was called. “Easy to mix up” means two tools whose names or descriptions overlap without saying how they differ; the AI found none, comparing tools within groups of 40. We do not rate whether the tool set is complete or whether side effects are spelled out, because our AI reading of those was not reliable enough.

How do I add it to my client?

Config from the registry entry

From the remote endpoint (Streamable HTTP)

We connected to this URL on 2026-10-30 (a read-only session: no tool was called).

Add to CursorAn install link in the format Cursor documents, holding the Cursor config below.

Claude Desktop or claude.ai
Settings → Connectors → Add custom connector, then paste:
https://mcp.jointextkit.com/
Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json
{
  "mcpServers": {
    "textkit": {
      "url": "https://mcp.jointextkit.com/"
    }
  }
}
VS Code · .vscode/mcp.json
{
  "servers": {
    "textkit": {
      "type": "http",
      "url": "https://mcp.jointextkit.com/"
    }
  }
}
VS Code (command line) · Bash or zsh terminal (macOS, Linux)
code --add-mcp '{"name":"textkit","type":"http","url":"https://mcp.jointextkit.com/"}'
Claude Code
claude mcp add --transport http textkit https://mcp.jointextkit.com/
Cline · cline_mcp_settings.json (Cline CLI: ~/.cline/data/settings/; in the editor: MCP Servers → Configure → Configure MCP Servers)
{
  "mcpServers": {
    "textkit": {
      "type": "streamableHttp",
      "url": "https://mcp.jointextkit.com/",
      "disabled": false,
      "autoApprove": []
    }
  }
}
Gemini CLI · ~/.gemini/settings.json, or .gemini/settings.json in a project
{
  "mcpServers": {
    "textkit": {
      "httpUrl": "https://mcp.jointextkit.com/"
    }
  }
}
OpenAI Codex · ~/.codex/config.toml, or .codex/config.toml in a trusted project
[mcp_servers.textkit]
url = "https://mcp.jointextkit.com/"
Zed · Zed settings file (command: zed: open settings file)
{
  "context_servers": {
    "textkit": {
      "url": "https://mcp.jointextkit.com/"
    }
  }
}
Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+
npx @modelcontextprotocol/inspector@2.11.0 --server-url https://mcp.jointextkit.com/ --transport http
  • The server runs on the operator's infrastructure; it may ask you to sign in when you first connect.
  • Zed's docs we read on 2026-10-26 describe remote servers by URL and do not name the transport.
  • The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.

Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21; Cline, Gemini CLI, OpenAI Codex and Zed 2026-10-26). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.

Does the registry listing match what we found?

Feature #6

The registry checks an entry when it is published (each new version), and nothing re-checks it on a schedule. A difference below is about the listing, not a judgement of the publisher.

Registry saysWe foundResultSource · date
Remote endpoint mcp.jointextkit.com/Session openedmatchesour test · 2026-10-30
No credential declared as requiredOpened a session without any credentialmatchesour test · 2026-10-30
Repository github.com/textkithq/textkit-mcpOpens publiclymatchesapi.github.com · 2026-10-30

Who made it?

Feature #7 · lineage

Facts about the publisher. We do not turn them into a trust score.

Namespace
com.jointextkit
GitHub owner
an organization (textkithq)
Repository
github.com/textkithq/textkit-mcp
Stars
0
Repository age
0–30 days
Last push
0–30 days ago
Archived
no

Source: the registry entry and api.github.com · 2026-10-30.

Publish this server? Run these checks against it yourself before release, from your own machine: a server the command starts, or your own server at its URL after a one-time proof that you control it: npx protocolprobe-selftest.

Tool list changes

Our reads compared · no tool called

Hosted endpoint mcp.jointextkit.com

1 of 1 comparison between consecutive reads showed a change (2 reads, 2026-10-29 to 2026-10-30; versions 1.0.0 to 1.0.2).

Last change seen between our reads on 2026-10-29 (version 1.0.0) and 2026-10-30 (version 1.0.2).

Added (10):

create_linkget_integration_eventslist_conversionslist_linksplan_campaignplan_taskpreview_automationrecommend_messagerecord_conversiontest_automation

Changed (59) (25 shown):

add_to_list: input schemabulk_purchase_numbers: input schemabulk_update_contacts: input schemabulk_update_numbers: description, input schemaclone_number_pool: input schemaconnect_integration: description, input schemacreate_automation: description, input schemacreate_customer: input schemacreate_link_domain: description, input schemacreate_list: description, input schemacreate_number_pool: input schemacreate_schedule: input schemacreate_segment: input schemacreate_template: input schemacreate_topic: input schemacreate_webhook: input schemaexport_consent: input schemaexport_csv: input schemaexport_numbers: input schemaget_deliverability: input schemaimport_contacts: input schemaimport_opt_outs: input schemalink_number_to_registration: input schemalist_audit_logs: input schemalist_batch_recipients: input schema

and 34 more.

Compared from the tool lists our read-only connection recorded, separately for each hosted endpoint and each package: each tool's name, title, description, input schema and annotations (the order of keys and of tools is ignored). We see a list only when we read it: a change is shown between the two reads where we first saw it, and anything after 2026-10-30 is not known yet. No tool was called. How it is compared

Choosing

Record checks

Public records · not a safety rating

4 of 4 record checks met · 4 do not apply · 1 not checked

  • Not ranked by downloads: a remote server publishes no download figure
  • Not ranked by stars: 0 stars (ranked from 10)
  • MetRegistry entry is active and says how to run itActive, with a package or a remote address.
  • MetSource repository link opensThe linked GitHub repository is public.
  • MetRepository is not archivedNot archived.
  • MetCode pushed to the repository in the 90 days before our checkLast push 0-30 days before our check.
  • Not checkedRepository publishes a security policy (SECURITY.md)We did not read this repository's security policy.
  • Does not applyPackage names its licence with a standard (SPDX) identifierRemote server: it ships no package.
  • Does not applyThe version the registry lists can be installed and is not withdrawnRemote server: it ships no package.
  • Does not applynpm package carries build provenance (attestation)Remote server: it ships no package.
  • Does not applyNo known critical or high advisory in the package or its dependenciesRemote server: it ships no package.

Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-10-30. No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating, and the same rules apply to every server. How each check works · Leaderboards · How we stay neutral

Common questions about com.jointextkit/textkit

Answered from the data above

Who publishes com.jointextkit/textkit?

The registry ties the namespace com.jointextkit to the domain jointextkit.com; only its owner can publish under it. Its linked repository is github.com/textkithq/textkit-mcp; GitHub reports its owner as textkithq, an organization. These are facts from the registry and GitHub, not a rating.

Is com.jointextkit/textkit safe to install?

We do not rate servers as safe or unsafe. 4 of its 4 applicable record checks are met (facts from public records, each listed on this page). What the records show: Its source repository opens publicly. Its repository had a push in the last 90 days. These are facts with their sources on this page, not a safety guarantee, and we did not run its tools.

Does com.jointextkit/textkit need an API key or sign-in?

It opened a session without any credential on 2026-10-30. The registry entry declares no required credential; no declaration is not a guarantee.

Has com.jointextkit/textkit been security tested?

Partly. 5 of the 16 checks that apply to it were exercised. It accepted a session without any credential and lists tools whose names suggest they change data. We did not call them. ProtocolProbe publishes no security verdict for a named server.

Where is the source code of com.jointextkit/textkit?

In github.com/textkithq/textkit-mcp, which opens publicly.

Found this page useful?

Anonymous · no sign-in

A quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.

Compare with another server

Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.

Security testing

What did we test, and what did we leave out?

18 checks · features #1, #2

Open without sign-in

It accepted a session without any credential and lists tools whose names suggest they change data. We did not call them. No security score is given; a check we did not run is never counted as passed.

The 18 checks at a glanceour test · 2026-10-30
  1. Inventory: exercised
  2. Hidden instructions: exercised
  3. Real execution: not run · our policy
  4. Secret leak: not run · nothing to check it against
  5. Internal addresses: not run · our policy
  6. Unconfirmed changes: not run · our policy
  7. Bad input: not run · our policy
  8. Model requests: not run · nothing to check it against
  9. Sensitive questions: not run · nothing to check it against
  10. Folder boundary: not run · our policy
  11. Log leaks: not run · nothing to check it against
  12. Hidden content: exercised
  13. Fake assistant turns: exercised
  14. Token passthrough: not applicable
  15. Token audience: not applicable
  16. Sign-in redirect: not run · our policy
  17. Consent handling: not testable from outside
  18. Sign-in metadata: exercised

5 exercised11 not run (reason given)2 not applicable

Each check ends in exactly one state: exercised, not run (with the reason), or not applicable (with the reason). 5 of the 16 checks that apply to it were exercised. We do not publish security-check outcomes for named servers.

Exercised · 5
  • 1Inventory
    tool-list    Reads the declared tools, resources and prompts.exercised
  • 2Hidden instructions
    description-poisoning    Looks for hidden instructions in tool descriptions.exercised
  • 12Hidden content
    audience-hiding    Checks resources that hide content from the user.exercised
  • 13Fake assistant turns
    fake-assistant-turn    Checks prompts that pose as the assistant's own words.exercised
  • 18Sign-in metadata
    oauth-url-scheme    Checks the published sign-in metadata for unsafe URLs.exercised
Not run, with the reason · 11
  • 3Real execution
    real-execution    Calls a tool and checks what really happens.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 4Secret leak
    canary-leak    Plants a fake secret and checks whether it leaks.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 5Internal addresses
    ssrf    Checks whether a tool can be steered to internal addresses.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 6Unconfirmed changes
    write-without-confirmation    Checks whether tools that change data act without asking.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 7Bad input
    error-handling    Sends bad input and watches how the server answers.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 8Model requests
    sampling    Checks whether the server asks the client's model to act for it.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 9Sensitive questions
    elicitation-sensitive-data    Checks whether the server asks users for sensitive data.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 10Folder boundary
    root-boundary    Checks whether the server reaches outside the folders it was given.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 11Log leaks
    logging-side-channel    Checks whether log messages carry data they should not.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 16Sign-in redirect
    open-redirect    Checks the sign-in redirect for abuse.Testing the sign-in redirect means sending probes to the operator's sign-in service, which we do not do.not run · our policy
  • 17Consent handling
    confused-deputy    Checks consent handling when one service acts for another.Depends on the operator's own consent screen, which differs per server and cannot be tested from outside.not testable from outside
Does not apply to this server · 2
  • 14Token passthrough
    token-passthrough    Checks whether the server forwards a user's token to other services.The server opened a session without sign-in, so there is no token flow to check.not applicable
  • 15Token audience
    token-audience-validation    Checks whether tokens meant for another service are accepted.The server opened a session without sign-in, so there is no token flow to check.not applicable

Source: our own test, 2026-10-30, mcp-runtime-engine@0.1.0. Which checks count and why follows our published scoring model.

What happened during the test?

Feature #8

The steps in order, as the test record holds them.

  1. 0 msStarted a read-only session with the server's remote endpoint
  2. 1,704 msConnected after 0 redirects. No credential was sent or needed.
  3. Read the inventory: 152 tools, 0 resources, 4 prompts.
  4. 7,246 msFinished: 5 checks exercised.

Reference

How is it classified?

18 fields

One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.

TopicAI-classified
pending: added in a later update
listed 2026-10-30; not classified yet
Pricing modelAI-classified
pending: added in a later update
the website is not read yet
Programming language
not stated
GitHub detects no source language in this repository (docs-only or empty)
Hosting type
remote (hosted by the publisher)
registry · 2026-10-30
MCP capability
prompts, tools
our test · 2026-10-30
Transport
streamable HTTP
registry · 2026-10-30
Required credentials
none declared
registry · 2026-10-30 · no declaration is not a guarantee
Package registry
does not apply
remote-only server: no package is shipped, so there is no package registry
Freshness
0–30 days
registry updatedAt · 2026-10-30
Lifecycle status
active
registry · 2026-10-30
License class
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Integrity hash
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Signature / provenance
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Dependency advisories
does not apply
ships no package, so there are no dependencies to audit
Popularity
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Publisher signals
owner: an organization · repository age: 0–30 days · stars: 0–9
api.github.com · 2026-10-30
Maintenance
active
api.github.com · 2026-10-30
Environment
the publisher's infrastructure
where it runs, from the hosting type · 2026-10-30

“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.

Cite or correct this page

Sources and corrections

Suggested citation

ProtocolProbe. “com.jointextkit/textkit: MCP server record.” Data checked 2026-10-30. https://protocolprobe.com/mcp/servers/com.jointextkit/textkit

Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.

As JSON: this record in the API · API documentation.

Badge for your README

ProtocolProbe: 4 of 4 record checks met

[![ProtocolProbe](https://protocolprobe.com/api/v1/badge/com.jointextkit/textkit)](https://protocolprobe.com/mcp/servers/com.jointextkit/textkit)

It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.

Something wrong, or is this yours?

If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here.

Write to hello@protocolprobe.com · corrections log · methodology