Model Context Protocol moderate risk

Ntfy Me

ntfy-me-mcp sends real-time notifications to devices via the ntfy service, supporting public and self-hosted instances with token authentication and markdown formatting.

Connections & Capabilities

Connects To

GitHubDocker

Capabilities

write

Quickstart

Install

npm install -g ntfy-me-mcp

Config

{
  "ntfy-me-mcp": {
    "command": "npx",
    "args": ["ntfy-me-mcp"],
    "env": {
      "NTFY_TOPIC": "your-topic-name"
    }
  }
}

Exposed MCP Tools (2)

moderate

ntfy_me

Sends a notification to a specified ntfy topic with customizable title, message, and priority.

Sends notifications, which could be abused if the topic is not properly secured.

safe

ntfy_me_fetch

Retrieves messages from a specified ntfy topic, allowing filtering based on various parameters.

Read-only access to messages on the ntfy topic.

Safety Assessment

ntfy-me-mcp is relatively safe when configured with strong authentication and used with a properly secured ntfy server. Risks increase if tokens are stored insecurely or if the ntfy topic is publicly accessible. Using VS Code inputs for secure token handling is the recommended approach.

Uses environment variables for configuration, reducing hardcoded secrets.
Supports token-based authentication for protected topics.
Provides options for secure token handling using VS Code inputs.
Can be run in a Docker container, providing some isolation.

Requires network access to send notifications.
Improperly secured ntfy server could lead to information disclosure.
Direct token configuration (Option 1) is less secure.
If the ntfy topic is not properly secured, unauthorized users could send notifications.