Notify MCP Server

💬 MCP Server for notify to Weixin, Telegram, Bark, Lark, 飞书, 钉钉

MCP Servers Python Grade D Listed MIT
37.9/100
Rank #1096 of 1320
Compare Notify MCP Server

Thin or incomplete trust evidence. Review carefully before production use.

Open compare tool Suggest correction
Listing state
Listed
Evidence coverage
Grade B · 3/5 signals
Last push
2026-03-26 · 162d ago
Recent change
Rank +7

Is Notify MCP Server safe? Notify MCP Server scores 37.9/100 (Grade D), ranked #1096 of 1320 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 2.6/10; 12% of recent commits are signed; last pushed 2026-03-26. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in MCP Servers

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-09-04
Rank Moved
Rank dropped 19 spots (#1077 → #1096)
2026-09-03
Rank Moved
Rank dropped 56 spots (#1021 → #1077)
2026-09-02
Rank Moved
Rank dropped 49 spots (#972 → #1021)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 2.6/10. Tighten the weakest checks to improve public safety evidence.
Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.
Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.
Refresh maintenance signals The repo was last pushed 162 days ago. Fresh activity helps separate stable projects from stale ones.
15.5
Activity sub-score · out of 100
#627

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade D reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage B is separate — it grades how many independent signal types back the score (3 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-09-04 22:32 UTC · Repo last pushed 162 days ago

Rank Trend

2026-08-11 2026-09-04

Activity & Reach

Stars
28
Forks
7
Last Push
2026-03-26
162 days ago
Commits (4 wk)
0
Downloads (7d)
118
pypi
HN mentions (30d)
Open Issues
0
Rank Change
▼19
was #1077

Analysis

HVTrust Dimensions vs MCP Servers

37.9 / 100 · 100.0% confidence

Notify MCP Server MCP Servers average (778 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
3.9 / 25
5.7 below avg 9.6
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
2.6 below avg 13.4
Transparency50% declared license · 50% OSSF Scorecard
10.7 / 17
1.1 below avg 11.8
Maintenance60% last-push freshness · 40% commit activity
1.2 / 20
11.0 below avg 12.2
AdoptionLog-scaled stars · package downloads
6.3 / 20
in line with avg 6.3

Activity Inputs

15.5 / 100
StarsRepository reach
8.8 / 30
FreshnessLast push recency
2.5 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
4.2 / 20

Supply Chain Trust

Package Provenance
None
No package attestations found
OSSF Scorecard
2.6 / 10
OpenSSF Scorecard · scanned Sep 4, 2026
Signed Commits
12%
of last 100 commits verified
Binary-Artifacts 10
Branch-Protection 0
CI-Tests 0
CII-Best-Practices 0
Code-Review 0
Contributors 3
Dangerous-Workflow 10
Dependency-Update-Tool 0
Fuzzing 0
License 10
Maintained 0
Packaging 10
Pinned-Dependencies 0
SAST 0
Security-Policy 0
Signed-Releases -1
Token-Permissions 0
Vulnerabilities 0

Is Notify MCP Server safe?

Public trust evidence for Notify MCP Server is thin: several supply-chain signals are missing or weak. This does not mean the project is unsafe — it means an outside observer cannot easily verify the usual integrity checks. Treat with extra scrutiny.
Does Notify MCP Server publish package provenance?
No published build provenance is currently detected for Notify MCP Server. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Notify MCP Server have an OpenSSF Scorecard?
Notify MCP Server has an OpenSSF Scorecard score of 2.6/10. The Scorecard checks for branch protection, signed releases, dependency updates, fuzzing, code review, and other supply-chain hygiene items. See the full check breakdown on this page.
Is Notify MCP Server actively maintained?
Slowing down. Last push was 162 days ago — keep an eye on whether activity resumes.
What license does Notify MCP Server use?
Notify MCP Server ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Notify MCP Server's commits signed?
12% of the last 100 commits to Notify MCP Server are verified-signed (GPG, SSH, S/MIME, or GitHub's signing flow). Signed commits help confirm that code was authored by who the commit claims.

Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.

AI agent surface

MCP, providers, tool surface
Scored in HVTrust

These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →

MCP Server Support
high confidence
Implemented
Notify MCP Server appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
low confidence
None detected
No clear third-party provider dependency detected.
Credential signal: API keys or service config markers documented.
Tool / Plugin Surface
None detected
No clear plugin system or broad tool surface detected.
Detailed evidence is not shown in the public view.
Package Provenance Drift
high confidence
Match
Published package metadata matches the tracked repo
Detailed evidence is not shown in the public view.
  • MCP signal live
  • External deps live
  • Tool / plugin surface live
  • Package provenance drift live

Maintain Notify MCP Server?

For maintainers

HVTrust scores Notify MCP Server from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.

Reputation Timeline

Signal history
Rank 14Listed 1HVTrust 1Scorecard 1
2026-09-04
Rank Moved
Rank dropped 19 spots (#1077 → #1096)
2026-09-03
Rank Moved
Rank dropped 56 spots (#1021 → #1077)
2026-09-02
Rank Moved
Rank dropped 49 spots (#972 → #1021)
2026-09-01
Rank Moved
Rank dropped 47 spots (#925 → #972)
2026-08-31
Rank Moved
Rank dropped 31 spots (#894 → #925)
2026-08-30
Rank Moved
Rank dropped 42 spots (#852 → #894)
2026-08-29
Rank Moved
Rank dropped 45 spots (#807 → #852)
2026-08-28
Rank Moved
Rank dropped 24 spots (#783 → #807)
2026-08-27
Rank Moved
Rank dropped 26 spots (#757 → #783)
2026-08-26
Scorecard Added
OSSF Scorecard: 2.6/10
2026-08-26
Rank Moved
Rank rose 103 spots (#860 → #757)
2026-08-26
HVTrust Changed
HVTrust up 14.9pts (24.2 → 39.1)
2026-08-24
Rank Moved
Rank dropped 13 spots (#849 → #862)
2026-08-16
Rank Moved
Rank dropped 20 spots (#837 → #857)
2026-08-12
Rank Moved
Rank dropped 10 spots (#818 → #828)
2026-08-10
Rank Moved
Rank dropped 46 spots (#770 → #816)
2026-08-08
Newly Listed
First tracked at rank #780

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 37.9 Grade D
Markdown:
[![HVTrust](https://hvtracker.net/badge/notify-mcp-server.svg)](https://hvtracker.net/agents/notify-mcp-server)
HTML:
<a href="https://hvtracker.net/agents/notify-mcp-server"><img src="https://hvtracker.net/badge/notify-mcp-server.svg" alt="HVTrust"></a>

Other agents in MCP Servers

Data sources
GitHub REST API (repo, commits, stars, forks, license) · PyPI / pypistats (downloads, provenance) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON