MCP.Market

FastMCP server that pages on-call via 100+ notification channels (Apprise wrappe MCP server

by adelaidasofia·io.github.adelaidasofia/paging-mcp·v0.1.0
No reviews yet

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

B73/100grade B
Write a reviewInstall
What users say
No reviews yet
Be the first
Safety scan
B73/100

full report

Adoption
New

0 stars

Reviews

Write one

Nobody has reviewed FastMCP server that pages on-call via 100+ notification channels (Apprise wrappe yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

FastMCP server that pages on-call via 100+ notification channels (Apprise wrappe tools

No tool declarations could be read from the package source. They show once the server is installed.

Public scan report

scanner v0.1.9 · 2026-09-27 · same rubric, same numbers if you re-run it

no findings
  • –Code scanpackage could not be scannedn/a
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitystatic API keys via environment variables6/15
  • Maintenancelast push 18 days ago15/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Overall 73/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How FastMCP server that pages on-call via 100+ notification channels (Apprise wrappe compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
73/100
higher than 40% of 48,273 servers

Install FastMCP server that pages on-call via 100+ notification channels (Apprise wrappe in Claude Code, Cursor or VS Code

The registry entry has no remote endpoint or installable package.

What the publisher says

From the FastMCP server that pages on-call via 100+ notification channels (Apprise wrappe repository's README, as published. We do not edit it. Read it on GitHub

paging-mcp

<!-- mycelium-badges:start -->

<!-- mycelium-badges:end -->

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.

Why this exists

If you're building anything that needs to wake a human up — a synthetic monitor on a B2B pipeline, a long-running batch job, a security alert — you want:

  1. Multiple channels in parallel so a single provider outage doesn't lose the page.
  2. Channels that actually fit your operator (WhatsApp for LatAm on-calls, ntfy for self-hosters, Pushover for personal phones, Twilio SMS for the cases where it still fits).
  3. Credentials redacted in tool responses so an agent reading the output doesn't leak them back into a transcript.
  4. One MCP your agent can call from anywhere (Claude Code, Codex, Cursor, etc.) without having to ship a new MCP per channel.

Apprise solves channels 1-2 in Python. This server makes it MCP-callable with redaction and channel filtering on top.

Install

Open Claude Code, paste:

/plugin marketplace add adelaidasofia/paging-mcp /plugin install paging-mcp@paging-mcp

Legacy install

git clone https://github.com/adelaidasofia/paging-mcp ~/.claude/paging-mcp
cd ~/.claude/paging-mcp
python3 -m venv .venv
.venv/bin/pip install -r requirements.txt

Configure

Set APPRISE_URLS to one or more Apprise URLs. Newline, semicolon, or comma separated:

export APPRISE_URLS="
ntfys://ntfy.sh/<your-secret-topic>
whapi+https://gate.whapi.cloud/messages/text?token=<TOKEN>&to=+57...
pover://<USER_KEY>@<APP_TOKEN>
mailto://user:pass@smtp.example.com/?to=alerts@example.com
"

Apprise URL examples by provider:

Full list: https://github.com/caronc/apprise/wiki

Register with Claude Code

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

FastMCP server that pages on-call via 100+ notification channels (Apprise wrappe: common questions

Is FastMCP server that pages on-call via 100+ notification channels (Apprise wrappe MCP server safe?
Mostly: it is graded B (73/100). Read the FastMCP server that pages on-call via 100+ notification channels (Apprise wrappe safety report
Does FastMCP server that pages on-call via 100+ notification channels (Apprise wrappe need an API key?
Yes. The registry entry asks for APPRISE_URLS.
Is FastMCP server that pages on-call via 100+ notification channels (Apprise wrappe maintained?
The last commit was 54 days ago (2026-09-09). The latest release is v0.1.0.
What can I use instead of FastMCP server that pages on-call via 100+ notification channels (Apprise wrappe?
Servers from other publishers that do the same job: OneUptime MCP server.

Alternatives to FastMCP server that pages on-call via 100+ notification channels (Apprise wrappe

Same job from other publishers: the closest match first, then the best rated.

  • OneUptime
    Manage incidents, alerts, monitors, status pages, on-call and telemetry in OneUptime.
    A

More from adelaidasofia →