POTATO MUSHCLIENT  [client]
A cross-platform Tcl/Tk client written for MUSH players. Good encoding support,
and a documentation set that says nothing at all about most protocols.
https://www.potatomushclient.com/
Runs on: Windows, Linux, macOS

Capabilities
  Read off each project's own documentation, not measured by us — a client has
  no handshake for us to observe. "unknown" means we looked and did not
  establish it. It never means no.

  screen reader    unknown
  TLS              yes
      https://github.com/potatomushclient/potato/wiki/ConfigureWorldsBasics
  UTF-8            yes
      https://github.com/potatomushclient/potato/wiki/Features
  MCCP             unknown
  GMCP             unknown
  MSDP             unknown
  ATCP             unknown
  MXP              unknown
  MSP              unknown
  scripting        yes
      https://github.com/potatomushclient/potato/wiki/FAQs

  7 of 10 rows are unknown: we did not find the project's own documentation
  saying either way. A short honest table beats a long guessed one.

Potato is a Tcl/Tk client built for MUSH play — multiple worlds, spawn windows,
and a set of defaults that assume you are typing poses rather than combat
commands. It runs on Windows, Linux and macOS from the same source, with the
macOS builds usually a version or two behind.

It negotiates character encoding and speaks full Unicode, which for the MUSH
side of the hobby is the capability that matters most in practice.

Note one documented limitation: it supports connecting to a port that is SSL
from the start, and its own configuration page says STARTTLS-style negotiated
SSL is not supported.

WHY SIX ROWS SAY UNKNOWN

We searched the project's home page, its downloads page, all 103 of its wiki
help files and its entire source tree for GMCP, MSDP, MCCP, MXP, MSP and ATCP.
There is no documented statement about any of them. There is code that touches
some of them, and this section does not turn code into a capability claim — a
table that says "yes" on the strength of a constant in a header is making a
promise the project never made.

The screen-reader row is the same answer reached the same way: a
case-insensitive sweep for "screen reader", "text-to-speech", NVDA, JAWS,
VoiceOver, "accessibility", "visually impaired" and "blind" across everything
the project publishes returned nothing at all. That is not a finding about the
software.

See also
  BeipMU — /reference/clients/beipmu
  MUSHclient — /reference/clients/mushclient
  You want collaborative roleplay — /reference/collaborative-roleplay