mcp-registry/ai.dinglebear/rapprise
Also listed as github/dinglebear-ai/rapprise, glama/dinglebear-ai/apprise-rmcp
As of —, the Dinglebear Rapprise MCP server is unknown.
Apprise notifications over MCP and CLI with authenticated stdio and HTTP transports.
No hosted endpoint — run locally over stdio from the npm package `@dinglebear/rapprise` (e.g. `npx @dinglebear/rapprise`).
Compare: most reliable devops servers · most reliable other servers · most reliable communication servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of —, the Dinglebear Rapprise MCP server is unknown.
Dinglebear Rapprise MCP server advertises 5 tools, including health, help, notify, notify_url, status.
No hosted endpoint — run locally over stdio from the npm package `@dinglebear/rapprise` (e.g. `npx @dinglebear/rapprise`).
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.