B
Warning
89/100
3 days ago

Notify

Multi-platform notification delivery supporting WeChat, Telegram, DingTalk, Bark, Lark, Feishu, and more

aahl/mcp-notify· pypi: mcp-notify· 4.3K installs· listed on pulsemcp

Warning. Serious findings were identified. Review the full report before connecting. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we verified

Code Verified⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every pushwhy connect →

Who stands behind it

aahl

Source: PulseMCP · also listed on modelscope

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

Install from

M8ven verifies MCPs across every public registry — install directly from whichever one you prefer.

// key findings
🚨
Secret credentials may flow to a network call
8 flows detected: HASS_MOBILE_KEY, DINGTALK_BOT_KEY, BARK_DEVICE_KEY. We can’t prove the destination matches the brand the credential belongs to.
🔐
You'll be asked for 9 credentials: HASS_ACCESS_TOKEN, HASS_MOBILE_KEY, DINGTALK_BOT_KEY, LARK_BOT_KEY, BARK_DEVICE_KEY, PUSH_PLUS_TOKEN, TELEGRAM_BOT_TOKEN, WEWORK_BOT_KEY, WEWORK_APP_SECRET
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// environment variables
To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.
configTRANSPORT
configHASS_BASE_URLHome Assistant 地址,默认: http://homeassistant.local:8123
🔐 secretHASS_ACCESS_TOKENHome Assistant 长效令牌
🔐 secretHASS_MOBILE_KEYHome Assistant 移动设备key (如: mobile_app_your_iphone),也可在提示词指定
🔐 secretDINGTALK_BOT_KEY钉钉群机器人access_token
configDINGTALK_BASE_URL钉钉API地址,默认: https://oapi.dingtalk.com
🔐 secretLARK_BOT_KEYLark群机器人key,也可以在提示词指定
configLARK_BASE_URLLark API地址,默认: https://open.larksuite.com
configFEISHU_BASE_URL飞书API地址,默认: https://open.feishu.cn
🔐 secretBARK_DEVICE_KEY默认Bark设备key,也可以在提示词指定
configBARK_BASE_URLBark API地址,默认: https://api.day.app
configNTFY_BASE_URLNtfy API地址,默认: https://ntfy.sh
configNTFY_DEFAULT_TOPIC默认Ntfy订阅主题,也可以在提示词指定
🔐 secretPUSH_PLUS_TOKEN默认PushPlus令牌,也可以在提示词指定
configPUSH_PLUS_BASE_URLPushPlus API地址,默认: http://www.pushplus.plus
configTELEGRAM_DEFAULT_CHATTelegram 默认会话ID,也可以在提示词指定
🔐 secretTELEGRAM_BOT_TOKENTelegram 机器人令牌
configTELEGRAM_BASE_URLTelegram API反代理地址,默认: https://api.telegram.org
🔐 secretWEWORK_BOT_KEY"": "your-wework-bot-key"
configWEWORK_APP_AGENTID企业微信应用的ID,默认: 1000002
configWEWORK_APP_CORPID企业微信所属的企业ID
🔐 secretWEWORK_APP_SECRET企业微信应用的凭证密钥
configWEWORK_APP_TOUSER企业微信默认接收人ID,也可以在提示词指定,默认: @all
configWEWORK_BASE_URL企业微信API反代理地址,用于可信IP,默认: https://qyapi.weixin.qq.com
Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.
deployPORT
// quality suggestions

Tool annotations

No tools have read-only/destructive annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

21/21 tools missing one or more hints — ha_send_mobile (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); ding_send_text (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); lark_send_text (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +18 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

Tests exist

No test files found

Add tests that exercise each declared tool.

Secrets stay with their owner

4 secret/sensitive values flow into network calls (WEWORK_BOT_KEY → dynamic, WEWORK_BOT_KEY → dynamic) (4 other flows matched canonical API hosts)

Audit where credentials are sent. A NOTION_TOKEN should only reach api.notion.com — never a third-party host.

Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.

// full audit trail
The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// improvement guidance — verified publishers only
We have 4 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Verified](https://m8ven.ai/badge/mcp/mcp-notify-1fx806?variant=verified)](https://m8ven.ai/mcp/mcp-notify-1fx806)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: 669dcc53d848fc1a5607a8ba524babf30e1a73e7
code hash: 4822661a078df966e84c400e30ac061aa8f750d4ec3450323b0238571e212f12
verified: 8/16/2026, 11:02:56 AM
view raw JSON →
Check MCPs from inside your assistant
Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check
check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern
How to add it →Free · no account needed · works in any MCP client