io.github.rmzlb/notifyd

MCPcommunityunreachable
v0.4.0io.github.rmzlbUnknownUpdated 19d agoGitHub

Operate a self-hosted notifyd instance: digest, jobs, retries, suppressions, projects, test sends.

Endpoint healthunreachable
checked 9 days ago · never seen reachable
0% of the last 3 checks reached this endpoint
Works in
ClaudeCursorCopilotChatGPTGemini

Inferred from the transports this listing declares (streamable-http). 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 →
12GitHub stars
1Forks
19d agoLast update
Needs 3 credentials before it runs
  • DATABASE_URLAPI keyrequired

    PostgreSQL connection string

  • JWT_SECRETAPI keyrequired

    Secret for subscriber tokens

  • ADMIN_API_KEYAPI keyrequired

    Operator key; also the Bearer token for /mcp

Declared by the author in the official MCP registry. Forge does not store, broker, or ever see these values — the config below is scaffolded with placeholders you fill in locally.

Package
Authorio.github.rmzlb
LicenseUnknown
Version0.4.0
Sourcemcp-registry
GitHubrmzlb/notifyd
SBOMCycloneDX 1.6 ↓
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/30
→ Publisher: run `forge publish` from the repo to claim ownership
—Domain verification+0/10
→ Not currently available for this listing type — the domain-verification check only runs for npm-backed packages today, so this row cannot be earned here yet regardless of what's hosted at the domain.
✓Prompt-injection scan · clean+30/30
✓Obfuscation / exfil scan · 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✓ CleanvHEAD · 28d agoHow well does this scan work?
EvalsNone
IndexedSep 7, 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 source28d ago

Forge read 10 source files from the repository archive 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

Operate a self-hosted notifyd instance: digest, jobs, retries, suppressions, projects, test sends.

Keywords
mcp
Alternatives
Comparing tool surfaces…

No dependency coverage

This entry publishes no npm package, so Forge has no dependency tree for it. That is a gap in coverage — not a statement that it has no dependencies.