Apprise RMCP MCP server
Rust MCP server and CLI for Apprise notification fan-out across dozens of delivery backends.
2 stars
Reviews
Write oneNobody has reviewed Apprise RMCP yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Apprise RMCP 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-26 · same rubric, same numbers if you re-run it
- –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 0 days ago15/15
- Maintainer identitynamespace and repository owner differ; GitHub account older than a year6/10
Findings (1)
- highPackage apprise-rmcp not found on npm
code.package-missing
How Apprise RMCP compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 68/100
- higher than 30% of 48,255 servers
- GitHub stars
- 2
- more than 75% of 28,688 servers
Install Apprise RMCP in Claude Code, Cursor or VS Code
Runs npx -y apprise-rmcp on your machine. Read the scan report first; the gateway never runs local packages.
claude mcp add apprise-rmcp -- npx -y apprise-rmcp
What the publisher says
From the Apprise RMCP repository's README, as published. We do not edit it. Read it on GitHub
apprise-rmcp
Apprise notifications over MCP and CLI with authenticated stdio and HTTP transports.
It exposes one MCP tool, apprise, plus the rapprise CLI. Agents can send tagged notifications through a preconfigured Apprise server, run one-off Apprise URL sends, and check upstream health through stdio MCP, Streamable HTTP MCP, or direct shell commands.
30-second path: run npx -y @dinglebear/rapprise health --json -> start loopback HTTP with APPRISEMCPHOST=127.0.0.1 npx -y @dinglebear/rapprise serve -> call tools/call with {"action":"health"}.
Status: operational RMCP upstream-client server. Write-capable; notification sends are intentional side effects. HTTP MCP supports loopback dev mode, static bearer tokens, and Google OAuth through lab-auth.
Not for: replacing Apprise API, storing notification destinations in this repo, scheduling reminders, building a generic webhook relay, multi-tenant isolation, or passing upstream Apprise bearer tokens through MCP tool arguments.
Contents
- Naming
- Capabilities And Boundaries
- Install
- Quickstart
- Client Configuration
- Runtime Surfaces
- MCP Tool Reference
- CLI Reference
- Configuration
- Authentication
- Safety And Trust Model
- Architecture
Naming
The repo and npm package use the RMCP family name, while the shipped binary uses the short Rust CLI name rapprise.
Capabilities And Boundaries
- Send notifications through tags configured in the upstream Apprise API server.
- Send one-off notifications to Apprise URL schemas with notify_url.
- Check upstream Apprise API health.
- Expose the send_alert prompt for critical alert workflows.
- Provide setup and doctor commands for local plugin/runtime checks.
Install
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Apprise RMCP: common questions
- Is Apprise RMCP MCP server safe?
- With care: it is graded C, so read the findings first (68/100). Read the Apprise RMCP safety report
- How do I install Apprise RMCP?
- It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
- Does Apprise RMCP need an API key?
- Yes. The registry entry asks for
APPRISE_TOKEN. - Is Apprise RMCP maintained?
- The last commit was 39 days ago (2026-09-25). The latest release is v0.1.3.
- How does Apprise RMCP compare with other MCP servers?
- safety score 68/100 (higher than 30% of 48,255 servers); github stars 2 (more than 75% of 28,688 servers). Full comparison.