Ext Ops Panel
Open dashboard
Comparison

Securenote.link vs three.ws Notifications

Securenote.link is an MCP server published by jackalterman. Marketplaces we read that list it: 1 (Docker MCP Catalog). three.ws Notifications is an MCP server published by nirholas. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-15. 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
MarketplaceSecurenote.linkthree.ws Notifications
Docker MCP Catalog Listed
Version: sha256:b3aff281c846
Forks (GitHub): 0
Pulls (Docker Hub): 37 135
Stars (Docker Hub): 2
Stars (GitHub): 1
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.1.4
Downloads/month (npm): 208
Downloads/week (npm): 46
Forks (GitHub): 64
Stars (GitHub): 237
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

Securenote.link vs three.ws Notifications
FactSecurenote.linkthree.ws Notifications
Marketplaces that list it11
Stars (GitHub) (differs)1 (worse)237 (better)
Pulls (Docker Hub) (differs)37 135No figure on Docker Hub
Forks (GitHub) (differs)0 (worse)64 (better)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/securenote-link-mcp-server)On your machine (@three-ws/notifications-mcp)
Transportstdiostdio
Tools it declares (differs)3Not published
Environment variables it asks for (differs)Not published3, secrets among them: 1
LicenceNot statedNot stated
Repository (differs)github.com/jackalterman/securenote-link-mcp-servergithub.com/nirholas/three.ws
Changes in the last 7 days00
First seen2026-10-112026-10-11

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

Securenote.link

In its own words, on Docker MCP Catalog:

SecureNote.link MCP Server - allowing AI agents to securely share sensitive information through end-to-end encrypted notes.

three.ws Notifications

In its own words, on Official MCP Registry:

Read the inbox, mark items read, manage delivery preferences, and register Web Push devices.

How to run each

Securenote.link As a local MCP server: Docker image

Claude Code
claude mcp add --transport stdio securenote-link-mcp-server -- docker run -i --rm mcp/securenote-link-mcp-server

three.ws Notifications As a local MCP server: npm package

Claude Code
claude mcp add --env "THREE_WS_API_KEY=<YOUR_THREE_WS_API_KEY>" --transport stdio notifications-mcp -- npx -y @three-ws/notifications-mcp

Requires: THREE_WS_API_KEY (secret)

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

Tools each declares

The marketplaces of three.ws Notifications publish no list of tools, so we do not compare tools.

Settings each asks for

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

What it can do: Securenote.link · What it can do: three.ws Notifications · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. 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