Telegram Notification Mcp — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited Telegram Notification Mcp (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
A minimal Telegram notification MCP server using only native Node.js APIs.
Add the Telegram notification MCP server using the claude mcp add command:
claude mcp add --transport stdio telegram-notification --scope user \
--env TELEGRAM_BOT_TOKEN=YOUR_BOT_TOKEN \
--env TELEGRAM_CHAT_ID=YOUR_CHAT_ID \
-- npx -y telegram-notification-mcpReplace YOUR_BOT_TOKEN and YOUR_CHAT_ID with your actual Telegram bot token and chat ID.
If you prefer to configure manually, add to your MCP configuration (e.g., ~/.cursor/mcp.json or Claude Desktop settings):
{
"mcpServers": {
"telegram-notification": {
"command": "npx",
"args": ["telegram-notification-mcp@latest"],
"env": {
"TELEGRAM_BOT_TOKEN": "YOUR_TELEGRAM_BOT_TOKEN",
"TELEGRAM_CHAT_ID": "YOUR_TELEGRAM_CHAT_ID"
}
}
}
}For local development, use an absolute path:
{
"mcpServers": {
"telegram-notification": {
"command": "node",
"args": ["/absolute/path/to/telegram-notification-mcp/index.js"],
"env": {
"TELEGRAM_BOT_TOKEN": "YOUR_TELEGRAM_BOT_TOKEN",
"TELEGRAM_CHAT_ID": "YOUR_TELEGRAM_CHAT_ID"
}
}
}
}Send a notification message to Telegram.
Parameters:
message (string, required): The message to sendExample:
{
"method": "tools/call",
"params": {
"name": "send_notification",
"arguments": {
"message": "Hello, World!"
}
}
}~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.