Security reports may cover the public documentation and examples in this repository, or the production MCP endpoint at https://singlinkbot.com/mcp/connect. Only the latest published version is supported.

Do not open a public issue for authentication bypasses, cross-account or cross-group access, exposed credentials, injection, personal data, or other exploitable findings. Use the private security-reporting channel listed on the canonical SingLinkBot contact page. Include the affected endpoint, minimal reproduction steps, impact, and safe evidence. Do not include another user's data.

We will acknowledge a complete report, investigate it, and coordinate disclosure. Avoid destructive testing, denial of service, automated high-volume scanning, accessing data that is not yours, or changing production records.

• Never commit MCP access tokens, GitHub tokens, Telegram bot tokens, cookies, .env files, database URLs, logs, exports, or user/group identifiers.
• Examples must use placeholders such as slmcp_live_REPLACE_ME.
• MCP credentials must be sent only to https://singlinkbot.com/mcp/connect.
• Revoke and replace any credential that may have been disclosed.

Authenticated management operations are evaluated against the authenticated SingLink account, granted scopes, and an allow-list of group identifiers. Client-supplied userId, ownerId, or impersonation-style fields must never be treated as authorization.