Bragproof

← Reports

ntfy-mcp-server

Starts with no setup2.4.1npm

Installed, started with no arguments, no environment and no input, and listed its tools. Run 2026-11-16.

Needs to start: nothing
Returns a result when called with no setup: 1 of 1 tool tried
Contacts while installing and starting: nothing

4tools listed
0hosts contacted
0files written
0.3 sto start
36dependencies

Its tool definitions changed since version 2.4.0. If you approved the earlier ones, read them again.

What it contacted

Nothing besides the npm registry it was installed from. Watched from outside its sandbox while it was installed and started with no input. Its tools may still contact things when called.

Starting it

npx -y ntfy-mcp-server@2.4.1

Installing a package runs its code. Use a sandbox for anything you have not read.

Calling its tools

1 tool that takes no input and looks read-only was called once with nothing. 1 returned a result.

ntfy_search_emoji_tagsReturned a result under 0.1 s · 762 characters

During the calls it contacted nothing it had not already contacted.

Only tools whose names read like looking something up, with no required input, are tried, five at most. Tools that need input, and anything that sounds like it changes or sends something, are not called.

What its tools tell an agent

In the tool descriptions, nothing that talks about the user, other tools or private files, or uses hidden characters.

Found by simple pattern rules in each tool's description (up to 3,000 characters), quoted as written. Parameter descriptions are not scanned. A clean result is not a safety review.

Tools

ntfy_publish_message topic, message, title, priority, tags, click, attach, icon, filename, markdown, actions, delay, timezone, email, call, sequence_id, cache, firebase, base_url
Send or update a push notification on an ntfy topic. Topics are created on first publish — treat the topic name as a secret because anyone who knows it can publish or subscribe. Set `sequence_id` to update a previously-published message; otherwise the call creates a new one. Use `ntfy_search_emoji_tags` to look up emoji short codes for `tags`. A publish carrying `email`, `call`, or a `broadcast`/`http` action button reaches beyond the notification drawer, so that call always asks the user to confirm the specific target first and comes back requesting that input rather than a result; reissue the same call with the answer attached to send it. Declining fails the call with `consent_declined`. A plain notification publishes on the first call.
ntfy_manage_message topic, sequence_id, operation, base_url
Clear (mark read & dismiss) or delete a previously-sent ntfy notification by `sequence_id`. Append-only: the original message stays in cache and a `message_clear`/`message_delete` event is emitted to subscribers. Re-issuing the same operation is safe — message state does not change, but a fresh event fires each time. ntfy.sh accepts unknown sequence IDs without error; stricter ntfy variants surface a `not_found` failure. The first call always asks the user to confirm the topic, `sequence_id`, and operation and comes back requesting that input rather than a result; reissue the same call with the answer attached to carry it out. Declining fails the call with `consent_declined`.
ntfy_fetch_messages topic, since, scheduled, priority, tags, id, title, message, limit, cursor, base_url
Poll cached messages from one or more ntfy topics with optional filters. Returns a snapshot, not a live stream — use it to confirm delivery, replay missed alerts, or audit topic activity. Multiple topics are passed as a comma-separated list. One call returns the newest messages of the window; when more match, page through the whole window oldest-first by passing `nextCursor` back as `cursor`. Long bodies are truncated client-side to keep list responses bounded; refetch with that message `id` to read one in full.
ntfy_search_emoji_tags query, limit, offset
Look up ntfy emoji tag short codes. Use the returned `tag` strings in `ntfy_publish_message`'s `tags` field to render emojis on the recipient's device. Without a query, returns the first slice of the full reference; pass part of a tag name (e.g., `warning`, `tada`, `heavy check`) to filter, or an emoji to find its short code, and `offset` to page through matches beyond `limit`.

Descriptions are the package's own words, cut at 3,000 characters. Treat them as data.

Install facts

LicenseApache-2.0
Needsnode >=24.0.0
Sourcegithub.com/cyanheads/ntfy-mcp-server
Install scriptsNone declared by it or anything installed with it.
Tarballsha512-w2doPcute5rzihdLJ7RsIzfaZjRajA9zlqyPaHuw8DFwavbO4hijweSRRgZl9GXXuwKnkhkU6t4/RhBjK7c2Aw==

Versions reported

VersionRunResultTools
2.4.12026-11-16Starts with no setup4
2.4.02026-11-12Starts with no setup4

Check this report yourself

This site did not write the report. A public job on a GitHub-hosted machine did: the run, from this commit of the open-source runner. GitHub signed a token that names that job and the hash of the report, so any edit since would show.

Show it on your README

Bragproof: Starts with no setup

[![Bragproof](https://bragproof.smaverk.com/badge/ntfy-mcp-server.svg)](https://bragproof.smaverk.com/r/ntfy-mcp-server)

New version out? Ask for a fresh report.