Ext Ops Panel
Open dashboard
Comparison

Glif vs Notify Sound

Glif is an MCP server published by glif.app. Marketplaces we read that list it: 3 (Official MCP Registry, Docker MCP Catalog, Community GitHub marketplaces). Notify Sound is an MCP server published by botmonster. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-28. 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
MarketplaceGlifNotify Sound
Official MCP Registry Listed
Version: 1.0.1
Forks (GitHub): 32
Stars (GitHub): 216
Not marked · First seen
Listed
Version: 1.0.0
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Docker MCP Catalog Listed
Version: sha256:3f93ddceeb99
Forks (GitHub): 32
Pulls (Docker Hub): 20 025
Stars (Docker Hub): 2
Stars (GitHub): 216
Not marked · First seen
Not listed

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

Glif vs Notify Sound
FactGlifNotify Sound
Marketplaces that list it (differs)3 (better)1 (worse)
Stars (GitHub) (differs)216 (better)0 (worse)
Pulls (Docker Hub) (differs)20 025No figure on Docker Hub
Forks (GitHub) (differs)32 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)Remote server or your machineRemote server (notifysound.com/mcp)
Transport (differs)Streamable HTTP, stdioStreamable HTTP
Tools it declares (differs)10Not published
Environment variables it asks for (differs)3, secrets among them: 1Not published
Parts of the bundle (differs)11Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/glifxyz/glif-mcp-servergithub.com/botmonster/notify-sound
Changes in the last 7 days (differs)02
First seen (differs)2026-10-112026-10-22
Endpoint at the last check (differs)Responded 5 days agonot checked yet

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

Glif

In its own words, on Official MCP Registry:

Generate images, video, and audio with Glif's media-generation agent

Notify Sound

In its own words, on Official MCP Registry:

Design notification sounds from layered tones and get an editor link to play and download.

How to run each

Glif As a remote MCP server

Claude Code
claude mcp add --transport http glif https://glif.app/api/mcp

Notify Sound As a remote MCP server

Claude Code
claude mcp add --transport http notify-sound https://notifysound.com/mcp

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

Only Glif has a remote endpoint we check. How we check endpoints

Tools each declares

The marketplaces of Notify Sound publish no list of tools, so we do not compare tools.

Settings each asks for

The marketplaces of Notify Sound publish no settings it asks for, so we do not compare settings.

What it can do: Glif · What it can do: Notify Sound · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. 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