Heimdall vs three.ws Notifications
Heimdall is an MCP server published by erayendes. Marketplaces we read that list it: 2 (Official MCP Registry, Community GitHub marketplaces). 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-24. 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
| Marketplace |  Heimdall |  three.ws Notifications |
|---|---|---|
| Official MCP Registry | Listed Version: 2.7.1 Downloads/month (npm): 2 205 Downloads/week (npm): 466 Forks (GitHub): 6 Stars (GitHub): 53 Not marked · First seen |
Listed Version: 0.1.4 Downloads/month (npm): 172 Downloads/week (npm): 40 Forks (GitHub): 68 Stars (GitHub): 249 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
| Fact | Heimdall | three.ws Notifications |
|---|---|---|
| Marketplaces that list it (differs) | 2 (better) | 1 (worse) |
| Stars (GitHub) (differs) | 53 (worse) | 249 (better) |
| Forks (GitHub) (differs) | 6 (worse) | 68 (better) |
| Last release (differs) | 2026-10-16 | Not published |
| Where it runs (differs) | On your machine (@erayendes/asc-mcp) | On your machine (@three-ws/notifications-mcp) |
| Transport | stdio | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 5, secrets among them: 1 | 3, secrets among them: 1 |
| Parts of the bundle (differs) | 1 | Not a bundle |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/erayendes/app-store-connect-mcp | github.com/nirholas/three.ws |
| Changes in the last 7 days (differs) | 1 | 0 |
| First seen | 2026-10-11 | 2026-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
Heimdall
Every App Store Connect + StoreKit 2 endpoint. 902 tools in 13 profiles, narrow to 27.
three.ws Notifications
Read the inbox, mark items read, manage delivery preferences, and register Web Push devices.
How to run each
Heimdall As a local MCP server: npm package
claude mcp add --env "ASC_PRIVATE_KEY=<YOUR_ASC_PRIVATE_KEY>" --transport stdio asc-mcp -- npx -y @erayendes/asc-mcpRequires: ASC_PRIVATE_KEY (secret)
three.ws Notifications As a local MCP server: npm package
claude mcp add --env "THREE_WS_API_KEY=<YOUR_THREE_WS_API_KEY>" --transport stdio notifications-mcp -- npx -y @three-ws/notifications-mcpRequires: 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
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Only Heimdall asks for
ASC_BUNDLE_IDASC_ISSUER_IDASC_KEY_IDASC_PRIVATE_KEY (secret)ASC_PRIVATE_KEY_PATH
Only three.ws Notifications asks for
THREE_WS_API_KEY (secret)THREE_WS_BASETHREE_WS_TIMEOUT_MS
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: Heimdall · What it can do: three.ws Notifications · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. 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.