three.ws Alerts vs OpenPulsechain Analytics
three.ws Alerts is an MCP server published by nirholas. Marketplaces we read that list it: 1 (Official MCP Registry). OpenPulsechain Analytics is an MCP server published by openpulsechain. 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
| Marketplace |  three.ws Alerts |  OpenPulsechain Analytics |
|---|---|---|
| Official MCP Registry | Listed Version: 0.1.3 Downloads/month (npm): 199 Downloads/week (npm): 50 Forks (GitHub): 64 Stars (GitHub): 237 Not marked · First seen |
Listed Version: 2.1.0 Downloads/month (npm): 215 Downloads/week (npm): 38 Forks (GitHub): 1 Stars (GitHub): 3 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 | three.ws Alerts | OpenPulsechain Analytics |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 237 (better) | 3 (worse) |
| Forks (GitHub) (differs) | 64 (better) | 1 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (@three-ws/alerts-mcp) | On your machine (@openpulsechain/mcp-server) |
| Transport | stdio | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 3, secrets among them: 1 | 1, secrets among them: 1 |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/nirholas/three.ws | github.com/openpulsechain/public |
| Changes in the last 7 days | 0 | 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
three.ws Alerts
Create, update, and delete pump.fun alert rules and read fired-alert history across channels.
OpenPulsechain Analytics
PulseChain analytics: 28 tools — safety scores, signals, whale alerts, pair analytics, AML.
How to run each
three.ws Alerts As a local MCP server: npm package
claude mcp add --env "THREE_WS_SESSION=<YOUR_THREE_WS_SESSION>" --transport stdio alerts-mcp -- npx -y @three-ws/alerts-mcpRequires: THREE_WS_SESSION (secret)
OpenPulsechain Analytics As a local MCP server: npm package
claude mcp add --env "OPENPULSECHAIN_API_KEY=<YOUR_OPENPULSECHAIN_API_KEY>" --transport stdio analytics -- npx -y @openpulsechain/mcp-serverRequires: OPENPULSECHAIN_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 three.ws Alerts asks for
THREE_WS_BASETHREE_WS_SESSION (secret)THREE_WS_TIMEOUT_MS
Only OpenPulsechain Analytics asks for
OPENPULSECHAIN_API_KEY (secret)
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: three.ws Alerts · What it can do: OpenPulsechain Analytics · Compare two other plugins
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.