MCP.Market

ntfy MCP server

by ni-c·io.github.ni-c/ntfy-mcp·v0.3.0
No reviews yet

Publish ntfy notifications, read the message cache, and manage users and topic access

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

full report

Adoption
Growing

0 stars45 downloads/wk

Reviews

Write one

Nobody has reviewed ntfy yet.

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

ntfy tools (13, 5 write)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • check_topic_access

    Reports whether the configured credentials may SUBSCRIBE to each

  • create_userwrite action

    Creates a non-admin account on a self-hosted instance. Requires an

  • delete_messageswrite action

    Deletes notifications and cancels scheduled ones that have not been

  • delete_userwrite action

    Removes an account and every access grant attached to it. Requires

  • get_account

    Identity, role, tier, limits and current usage of the configured

  • get_message

    Fetches a single cached message in full, including the untruncated

  • get_server_info

    Health, capabilities and usage of the ntfy instance. Health, config

  • list_messages

    Polls the cached messages of one or more topics, oldest first.

  • list_users

    Every account on the instance with its per-topic grants — the

  • manage_user_access

    Sets or removes an account's access to a topic or topic pattern.

  • mark_messages_read

    Clears notifications on subscribers' devices. The messages stay in

  • publish_messagewrite action

    Sends a notification to one or more topics.

  • update_messagewrite action

    Replaces the content of a notification already published, so

Public scan report

scanner v0.1.10 · 2026-10-15 · same rubric, same numbers if you re-run it

no findings
  • Code scan29 source files scanned25/25
  • –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 identityregistry namespace matches repository owner; GitHub account older than a year8/10
Overall 83/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How ntfy compares

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

Safety score
83/100
higher than 65% of 48,255 servers
Tools
13
the typical server has 7
Tools that change things
38%
typical: 0%. Fewer write tools means less an agent can break
Downloads a week
45
more than 37% of 12,191 servers with a package

What its tools let an agent do: 7 read · 1 create · 2 change · 2 delete · 1 send or post

Install ntfy in Claude Code, Cursor or VS Code

Runs npx -y @ni-c/ntfy-mcp on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add ntfy-mcp -- npx -y @ni-c/ntfy-mcp
Add to Cursor

What the publisher says

From the ntfy repository's README, as published. We do not edit it. Read it on GitHub

ntfy-mcp

<!-- badges: start -->

<!-- badges: end -->

A Model Context Protocol (MCP) server for ntfy, the pub-sub notification service that sends push messages to your phone with an HTTP request and nothing else.

Lets MCP clients like Claude Code, Claude Desktop or Codex send you notifications, read back what was sent, revise a notification in place while a job runs, and — with an admin account — create accounts and grant or revoke their access to topics, which otherwise means the ntfy command line on the server.

Thirteen tools is the ceiling, not the floor: NTFYALLOWTOOLS=essential registers a curated six instead, and a model picks the right tool far more reliably from six than from thirteen — see choosing which tools load.

<!-- is resolved against the colour scheme of the page showing it, so GitHub picks the variant that matches its own theme toggle. npm strips and when it sanitises the README and keeps the , which is why that fallback brings its own dark card instead of relying on a media query.

The URLs must stay absolute: a relative path is simply invisible on npm. -->

<!-- Recorded with vhs from docs/demo.tape against a throwaway ntfy container, so it reproduces without touching a real instance — see the header of that file. -->

What makes it different

A progress report stays one notification. The id publishmessage returns is also the notification's sequence id, and updatemessage replaces its content in place — subscribers watch one notification change from "building" to "deployed" instead of collecting five.

NTFYTOPICS is the fence.** On ntfy a topic name is a bearer credential: knowing it is often the whole of the access control. One variable names the topics this server may touch and supplies the default when a tool omits one, so the name stays out of the tool arguments and out of the model's context.

Requirements

Shortened. The full README is on GitHub.

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

ntfy: common questions

Is ntfy MCP server safe?
Mostly: it is graded B (83/100). Read the ntfy safety report
How do I install ntfy?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does ntfy need an API key?
Yes. The registry entry asks for NTFY_TOKEN, NTFY_PASSWORD.
Is ntfy maintained?
The last commit was 20 days ago (2026-10-15). The latest release is v0.3.0.
How does ntfy compare with other MCP servers?
safety score 83/100 (higher than 65% of 48,255 servers); tools 13 (the typical server has 7); tools that change things 38% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.

More from ni-c →