Player-session MUD protocol
MSSP
MUD Server Status Protocol
Widely used
Documented current use
Publishes machine-readable server metadata such as name, player count, uptime, codebase, URLs, and supported capabilities.
Protocol overview
- First seen
- 2009
- Present-day status
- Widely used
- In use today?
- Yes, with documented current use.
- Legacy?
- No.
- Layer
- Player-session MUD protocol
- Transport
- Telnet option 70 with VAR/VAL records
- Telnet option
- 70
- Research validated
Current use and fit
Actively used by crawlers and directories, including MUDVerse, and supported by current engines and clients.
Implementation essentials
- Offer WILL MSSP and send the status record after the peer accepts.
- Keep NAME, PLAYERS, and UPTIME accurate and update dynamic fields at collection time.
- Advertise only capabilities the listener actually supports.
Compatibility and safety notes
- Do not cache dynamic fields indefinitely.
- MSSP values are public metadata, not an authentication channel.
Original specifications and sources
- MUDhalla full specification Primary
- MUD Standards preservation Preservation
- MUDVerse MSSP implementation guide Local
Where an original site has disappeared, a preservation archive is linked and identified as such. MUDVerse does not claim authorship of the original protocol.