Ext Ops Panel
Open dashboard
Comparison

ntfy-me-mcp vs Nodle IoT Dashboard

ntfy-me-mcp is an MCP server published by gitmotion. Marketplaces we read that list it: 1 (npm registry (MCP servers)). Nodle IoT Dashboard is an MCP server published by nodle.com. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-08. 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-mcpNodle IoT Dashboard
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
Official MCP Registry Not listed Listed
Version: 0.1.0
No figure published
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 Nodle IoT Dashboard
Factntfy-me-mcpNodle IoT Dashboard
Marketplaces that list it11
Stars (GitHub) (differs)76No figure on GitHub
Forks (GitHub) (differs)16No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)On your machine (ntfy-me-mcp)Remote server (dashboard.nodle.com/api/mcp)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Licence (differs)GPL-3.0Not stated
Repository (differs)github.com/gitmotion/ntfy-me-mcpNot stated
Changes in the last 7 days (differs)02
First seen (differs)2026-10-122026-11-04
Endpoint at the last check (differs)no remote endpoint we checkResponded 20 h ago, requires authentication

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!)

Nodle IoT Dashboard

In its own words, on Official MCP Registry:

Fleets, devices, detections and webhooks on the Nodle Bluetooth Low Energy network.

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.

Nodle IoT Dashboard As a remote MCP server

Claude Code
claude mcp add --transport http iot-dashboard https://dashboard.nodle.com/api/mcp

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

Only Nodle IoT Dashboard has a remote endpoint we check. How we check endpoints

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: Nodle IoT Dashboard · Compare two other plugins

Package data comes from the public npm registry (registry.npmjs.org). Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. 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