Ext Ops Panel
Open dashboard
Comparison

ntfy-me-mcp vs tiltify-webhooks

ntfy-me-mcp is an MCP server published by gitmotion. Marketplaces we read that list it: 1 (npm registry (MCP servers)). tiltify-webhooks is a plugin bundle for AI coding tools published by Hookdeck. Marketplaces we read that list it: 1 (Community GitHub marketplaces). As of our marketplace pass on 2026-11-11. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
Marketplacentfy-me-mcptiltify-webhooks
npm registry (MCP servers) Listed
Version: 1.5.0
Downloads/month (npm): 995
Downloads/week (npm): 215
Forks (GitHub): 16
Stars (GitHub): 76
Not marked · First seen
Not listed
Community marketplace hookdeck/webhook-skills Not listed Listed
Version: not stated
Forks (GitHub): 16
Stars (GitHub): 101
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

ntfy-me-mcp vs tiltify-webhooks
Factntfy-me-mcptiltify-webhooks
Marketplaces that list it11
Stars (GitHub) (differs)76 (worse)101 (better)
Forks (GitHub)1616
Last releaseNot publishedNot published
Where it runs (differs)On your machine (ntfy-me-mcp)Installs as a plugin bundle
TransportNot statedNot stated
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Licence (differs)GPL-3.0MIT
Repository (differs)github.com/gitmotion/ntfy-me-mcpgithub.com/hookdeck/webhook-skills
Changes in the last 7 days (differs)02
First seen (differs)2026-10-122026-11-06

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

ntfy-me-mcp

In its own words, on npm registry (MCP servers):

An ntfy MCP server for sending ntfy notifications to your self-hosted ntfy server from AI Agents 📤 (supports secure token auth & more - use with npx or docker!)

tiltify-webhooks

In its own words, on Community GitHub marketplaces:

Receive and verify Tiltify webhooks. Use when setting up Tiltify webhook handlers, debugging X-Tiltify-Signature verification (base64 HMAC-SHA256 over "<X-Tiltify-Timestamp>.<raw body>"), or handling donation and fact events like public:direct:donation_updated and public:direct:fact_updated.

How to run each

ntfy-me-mcp

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

tiltify-webhooks As a Claude Code plugin

Claude Code
/plugin marketplace add hookdeck/webhook-skills
/plugin install tiltify-webhooks@webhook-skills

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

Neither one's marketplaces publish the settings it asks for.

What it can do: ntfy-me-mcp · What it can do: tiltify-webhooks · Compare two other plugins

Package data comes from the public npm registry (registry.npmjs.org). Data comes from public marketplace files in GitHub repositories of their authors. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built