io.github.aahl/mcp-notify

MCPcommunity
v0.1.11io.github.aahlUnknownUpdated 6mo agoGitHub

MCP Server for notify to Weixin, Telegram, Bark, Lark, Feishu, DingTalk

提供消息推送的 MCP (Model Context Protocol) 服务器，支持企业微信、钉钉、Telegram、Bark、Lark、飞书、Home Assistant 需要通过OAuth授权或Smithery key 添加到 Cherry Studio []( 添加到 Claude Code, 执行命令: 添加到 OpenAI CodeX, 执行命令: : 企业微信群机器人默认key，也可以在提示词指定 : 企业微信默认接收人ID，也可以在提示词指定，默认: : 企业微信API反代理地址，用于可信IP，默认: : 飞书群机器人key，也可以在提示词指定 : Lark群机器人key，也可以在提示词指定 : Telegram 默认会话ID，也可以在提示词指定 : Telegram API反代理地址，默认: : Home Assistant 地址，默认: : Home…

Works in
ClaudeCursorCopilotGemini

Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
28GitHub stars
7Forks
6mo agoLast update
Package
Authorio.github.aahl
LicenseUnknown
Version0.1.11
Sourcemcp-registry
GitHubaahl/mcp-notify
SBOMCycloneDX 1.6 ↓
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/20
→ Publisher: run `forge publish` from the package repo to claim ownership
—Ed25519 publish signature+0/5
→ Included automatically when the publisher runs `forge publish`
—Domain verification+0/5
→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
—npm Trusted Publishing (Sigstore)+0/5
→ Publish from GitHub Actions with --provenance so the attestation binds this package to this repo
—npm maintainer match+0/5
→ Earned once your identity is verified above and that login is an npm maintainer of this package
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
DependenciesNot audited
Tool surface—
Security scan✓ Cleanv0.1.11 · 3mo agoHow well does this scan work?
EvalsNone
IndexedJun 13, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

No tool declarations found in the source3mo ago

Forge read 0 source files from the published package tarball and matched no MCP tool registrations. Extraction is pattern-based over shipped source: a server that builds its tool list at runtime, or that ships only bundled or minified code, registers nothing this can see. Treat it as “not detected”, not as “exposes none”.

About

提供消息推送的 MCP (Model Context Protocol) 服务器，支持企业微信、钉钉、Telegram、Bark、Lark、飞书、Home Assistant 需要通过OAuth授权或Smithery key 添加到 Cherry Studio []( 添加到 Claude Code, 执行命令: 添加到 OpenAI CodeX, 执行命令: : 企业微信群机器人默认key，也可以在提示词指定 : 企业微信默认接收人ID，也可以在提示词指定，默认: : 企业微信API反代理地址，用于可信IP，默认: : 飞书群机器人key，也可以在提示词指定 : Lark群机器人key，也可以在提示词指定 : Telegram 默认会话ID，也可以在提示词指定 : Telegram API反代理地址，默认: : Home Assistant 地址，默认: : Home Assistant 长效令牌 : Home Assistant 移动设备key (如: mobileappyouriphone)，也可在提示词指定 : 默认Bark设备key，也可以在提示词指定 :…

Keywords
mcp
Alternatives
Comparing tool surfaces…

No dependency coverage

Forge's dependency resolver reads npm metadata only, so this PyPI package has no resolved tree. That is a gap in coverage, not a clean bill of health.