📄️ ATCP (Option 200)
ATCP is a predecessor of GMCP and is commonly used to provide supplemental information or hints to the client by the server (and for the server to query capabilities and information from the client).
📄️ GMCP (Option 201)
Source: Mudhalla
📄️ MCCP2 (Option 86)
Source: The MUD Client Protocol (MCP)
📄️ MCCP3 (Option 87)
Source: The MUD Client Protocol (MCP)
📄️ MCP
Source: The MUD Client Protocol (MCP)
📄️ MCP2
Source: The MUD Client Protocol, Version 2.1
📄️ MMCP
Source: Mudhalla
📄️ MMP
MMP (working name) is a specification for MUDs to make room data available to client and/or users for the creation of maps.
📄️ MNES (Option 39)
Allows a client to inform the server of it's capabilities.
📄️ MPCP (Option 202)
MPCP is a draft secure authentication mechanism between proxies and MUD servers
📄️ MSDP (Option 69)
Source: Mudhalla
📄️ MSLP
Source: Mudhalla
📄️ MSP (90)
Source: Zuggsoft
📄️ MSSP (Option 70)
Source: Mudhalla
📄️ MTTS (Option 24)
MUD servers often want to know the various capabilities of a Mud Client. While various methods exist there is no consistent nor guaranteed way to do so.
📄️ MXP (Option 91)
Version History
📄️ Portal MIP
(Messaging Information Protocol)
📄️ Pueblo
Pueblo.gif Pueblo/UE is a multimedia MUD/MUSH/MOO/MUX (MU*) client for Windows 95, 98, NT, ME, 2000, and XP. You can also use it as a regular Telnet client for line-based applications.
📄️ RIPscrip
This is not really a protocol invented for MUD. Instead it was invented for bulletin board systems and also used in a few MUD servers. Nowadays there are no clients in use that support this protocol.
📄️ ZMP (Option 93)
Source: Discworld