Security Release v1.1.23

This might be a "breaking" release of your workflows as it disables unfurling behavior by-default.

You may enable it back a) in full or b) (recommended) for specified hosts using new env variable SLACK_MCP_ADD_MESSAGE_UNFURLING. The following values are valid:

• Fully disabled: (empty, no whitespace), no, 0 or false
• Fully enabled: yes, 1 or true
• RECOMMENDED - Specified hosts: google.com,github.com,...

• Unfurling by @korotovsky in #69

Full Changelog: v1.1.22...v1.1.23

What's Changed in v1.1.22

• Fix: Redirect console logs to stderr for stdio transport compatibility by @clement-izard in #65
• Send fake TLS handshake to avoid fingerprinting detection by @korotovsky in #66

For Slack Enterprise Grid has been developed a new layer of "anti-protection". In case you are getting instant log-outs then make sure:

1. set SLACK_MCP_USER_AGENT environment variable to match your browser's User-Agent string from where you extracted xoxc and xoxd
2. enable SLACK_MCP_CUSTOM_TLS to enable custom TLS-handshakes to start to look like a real browser.