Apprise RMCP — Watchlist

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Follow-up value is specific to Rapprise notification dispatch and health checks: Do authenticated transports prevent unauthorised sends when one-off notification URLs are enabled?

Reviewed Oct 5, 2026 · Documentation review; complete setup workflow not independently tested

Best fit

Send Apprise notifications and manage configured notification targets through a Rust MCP/CLI server.

What we know

Apprise notifications over MCP and CLI with authenticated stdio and HTTP transports. This profile is based on verified official documentation where listed; unresolved operational details are explicitly marked.

Maintenance / activity evidence

@dinglebear/rapprise 0.3.0 published 2026-08-04T19:26:05.647Z

Tracking evidence observed Oct 5, 2026. These dated signals do not establish current maintenance. Reviewed enrichment confidence: medium.

Verification gaps / watch-outs

Installation and comprehensive security have not been independently audited.
Notification delivery and configured target management Writes: Send notification to configured services; Manage notification target configuration where supported.
Configuration-dependent Apprise credentials and HTTP authentication
Sensitive access: Notification payloads, Apprise destination credentials

Potential high-impact side effects: Send notification to configured services, Manage notification target configuration where supported.

Full authority, access and evidence limits are available in Review context and Access & risk.

All limitations / Review context

Do authenticated transports prevent unauthorised sends when one-off notification URLs are enabled?

The bounded review of the publisher's documented Rapprise notification dispatch and health checks and release notices identified no disclosed material condition preventing an accurately scoped public tracking entry. The resource's operational permissions remain uncertainty; this assessment does not certify installation safety.

Potential high-impact side effects: Send notification to configured services, Manage notification target configuration where supported.
Notification delivery and configured target management
Configuration-dependent Apprise credentials and HTTP authentication
Notifications may be forwarded to external Apprise target providers; HTTP deployments expose an additional trust boundary.
Reviewed write actions: Send notification to configured services; Manage notification target configuration where supported
Sensitive access: Notification payloads, Apprise destination credentials
Installation, client compatibility and comprehensive security have not been independently audited. Authentication and access depend on the configured services.
Runtime behavior, dependencies and undisclosed vulnerabilities were not independently audited.
Documented tool authority and any remote data handling must be checked before installation or use.
Tool inventory, client matrix and permissions completeness were not requirements for this Radar tracking review.
cost: plans, pay-per-call charges, and payment authorization details
The npm entry is a verified native-binary launcher rather than a separate server implementation
Delivery can contact real recipients
HTTP auth configuration is deployment-dependent
npm launcher downloads/verifies the Rust release binary; underlying implementation is dinglebear-ai/rapprise.

Original activity observations

@dinglebear/rapprise 0.3.0 published 2026-08-04T19:26:05.647Z

Technical identity

npm/@dinglebear/rapprise

Exact implementation source: https://www.npmjs.com/package/@dinglebear/rapprise ↗
Reviewed resource type: Gateway
Repository identity: dinglebear-ai/rapprise
Package identity: npm:@dinglebear/rapprise

Evidence & Sources

Evidence basis: Recorded source evidence
Setup runtime verification: Not independently runtime-tested by MCP100 for this setup workflow.

Reviewed Oct 5, 2026 · Latest source observation Oct 8, 2026

Package registry metadata ↗
@dinglebear/rapprise
Recorded package identity, distribution or download evidence.
GitHub repository ↗
dinglebear-ai/rapprise
Repository reference; implementation attribution is not established for every document.
Includes references whose attribution is not established.

Setup · Watchlist

Gateway setup

Publisher instructions.

Source evidence observed Oct 14, 2026.

Additional setup details required — see the specific gaps below.

Install / connect
Publisher instructions
Apprise notification gateway. Upstream Apprise API must run; APPRISE_TOKEN only if API requires bearer auth.
publisher install or stdio launch · Publisher instructions
npx -y @dinglebear/rapprise mcp
Configure / authenticate
MCP100 setup guide
Publisher: `npx -y @dinglebear/rapprise` with the documented MCP entry/subcommand; configure Apprise upstream before use.
Previously reviewed client configuration / prerequisites: Publisher: npx -y @dinglebear/rapprise health --json for local/upstream health, APPRISE_MCP_HOST=127.0.0.1 npx -y @dinglebear/rapprise serve for loopback HTTP; credentials and optional HTTP bearer auth differ from local stdio.
Check connection
Suggested check
`npx -y @dinglebear/rapprise health --json` is publisher read-only upstream preflight.
Remove / uninstall / revoke
MCP100 setup guide
For a Claude Code registration named `dinglebear-rapprise`, run `claude mcp remove dinglebear-rapprise`; otherwise remove the exact entry in the chosen MCP client settings and restart/reconnect. This client-host removal command is MCP100-composed from Claude Code lifecycle documentation, not a vendor-authored uninstall. With `npx`, a separate global package uninstall normally is unnecessary. Do not delete provider data or credentials by default.
Client unregister, package uninstall, data deletion, and OAuth/API token/wallet permissions are distinct.
Remove client registration · Claude Code only · MCP100 composed guide
claude mcp remove dinglebear-rapprise

Official Documentation & Sources

What it does

Apprise notifications over MCP and CLI with authenticated stdio and HTTP transports. This profile is based on verified official documentation where listed; unresolved operational details are explicitly marked.

Capability: Communication
Resource type: Gateway
Best fit: Send Apprise notifications and manage configured notification targets through a Rust MCP/CLI server.

Representative uses

Dispatch configured alert notifications
Inspect configured destinations and health
Run authenticated shared HTTP MCP

Limitations

The npm entry is a verified native-binary launcher rather than a separate server implementation
Delivery can contact real recipients
HTTP auth configuration is deployment-dependent
npm launcher downloads/verifies the Rust release binary; underlying implementation is dinglebear-ai/rapprise.

Reviewed access

Access & risk

Review the exact access boundary before connecting this MCP to accounts, credentials, or sensitive data.

Authentication: Configuration-dependent Apprise credentials and HTTP authentication
Permissions: Notification delivery and configured target management
Data handling: Notifications may be forwarded to external Apprise target providers; HTTP deployments expose an additional trust boundary.
Cost: Not documented in the reviewed sources
Risk and cautions: Potential high-impact side effects: Send notification to configured services, Manage notification target configuration where supported.

Access scope and cautions

Write actions: Send notification to configured services Manage notification target configuration where supported
Sensitive access: Notification payloads Apprise destination credentials
Risk level: high

FAQ

Based on reviewed evidence as of 2026-10-08. Watchlist tracking is not a recommendation or a security certification.

Which tasks are documented for this implementation?

The reviewed tasks include: Dispatch configured alert notifications; Inspect configured destinations and health; Run authenticated shared HTTP MCP.

What setup and authentication are documented?

Recorded installation/entrypoint step: npx -y @dinglebear/rapprise mcp. Recorded transport: stdio, streamable_http. Prerequisites: MCP-capable client. These are the documented setup details, not a claim that installation or client compatibility was independently tested. Authentication: Configuration-dependent Apprise credentials and HTTP authentication

Can it modify data or perform write operations?

Documented write actions include: Send notification to configured services; Manage notification target configuration where supported. Recorded permission boundary: Notification delivery and configured target management

What data-handling boundary should I consider?

Notifications may be forwarded to external Apprise target providers; HTTP deployments expose an additional trust boundary. Recorded sensitive-access context: Notification payloads; Apprise destination credentials.

What limitations and risks should I check before use?

Potential high-impact side effects: Send notification to configured services, Manage notification target configuration where supported. The npm entry is a verified native-binary launcher rather than a separate server implementation. Delivery can contact real recipients. HTTP auth configuration is deployment-dependent. npm launcher downloads/verifies the Rust release binary; underlying implementation is dinglebear-ai/rapprise. Runtime behavior, dependencies and undisclosed vulnerabilities were not independently audited. Documented tool authority and any remote data handling must be checked before installation or use.