io.github.adelaidasofia/paging-mcp

MCPcommunity
v0.1.0io.github.adelaidasofiaUnknownUpdated 1mo agoGitHub

FastMCP server that pages on-call via 100+ notification channels (Apprise wrapper)

FastMCP server that pages on-call via 100+ notification channels. Built on top of Apprise, which speaks WhatsApp, ntfy, Pushover, Telegram, Discord, Slack, Signal, Matrix, Gotify, mailto, Twilio SMS, AWS SNS, and dozens more. The point is provider independence. Wire one MCP, configure as many channels as you want, get redundant paging without rewriting integration code every time you swap a…

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
1mo agoLast update
Package
Authorio.github.adelaidasofia
LicenseUnknown
Version0.1.0
Sourcemcp-registry
GitHubadelaidasofia/paging-mcp
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/25
→ Publisher: run `forge publish` from the package repo to claim ownership
—Ed25519 publish signature+0/10
→ 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>" }
—CVE scan · not run+0/30
→ Not yet scanned — package must be on npm
✓Static analysis · clean+20/20
—npm provenance (Sigstore)+0/5
→ Publish from GitHub Actions with the --provenance flag
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 · 19d ago
EvalsNone
IndexedJun 13, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts — it cannot prove the absence of malicious code.

About

FastMCP server that pages on-call via 100+ notification channels. Built on top of Apprise, which speaks WhatsApp, ntfy, Pushover, Telegram, Discord, Slack, Signal, Matrix, Gotify, mailto, Twilio SMS, AWS SNS, and dozens more. The point is provider independence. Wire one MCP, configure as many channels as you want, get redundant paging without rewriting integration code every time you swap a vendor. If you're building anything that needs to wake a human up — a synthetic monitor on a B2B…

Keywords
mcp