dev.ezstat/ezstat-mcp-server vs Ecosystem Monitor
dev.ezstat/ezstat-mcp-server is an MCP server published by ezstat.dev. Marketplaces we read that list it: 1 (Official MCP Registry). Ecosystem Monitor is an MCP server published by memoryapi.org. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-14. 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 |  dev.ezstat/ezstat-mcp-server | |
|---|---|---|
| Official MCP Registry | Listed Version: 0.7.0 Downloads/month (npm): 214 Downloads/week (npm): 33 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Listed Version: 1.0.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
| Fact | dev.ezstat/ezstat-mcp-server | Ecosystem Monitor |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 0 | No figure on GitHub |
| Forks (GitHub) (differs) | 0 | No figure on GitHub |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (ezstat-mcp-server) | Remote server (monitor.memoryapi.org/mcp) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 2, secrets among them: 1 | Not published |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/clira-dev/ezstat-mcp-server | Not stated |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded less than an hour ago |
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
dev.ezstat/ezstat-mcp-server
Track and query EzStat metrics from Claude, Cursor, or any MCP agent. StatHat-compatible.
Ecosystem Monitor
Ecosystem monitoring: service status and x402 activity metrics
How to run each
dev.ezstat/ezstat-mcp-server As a local MCP server: npm package
claude mcp add --env "EZSTAT_API_KEY=<YOUR_EZSTAT_API_KEY>" --transport stdio ezstat-mcp-server -- npx -y ezstat-mcp-serverRequires: EZSTAT_API_KEY (secret)
Ecosystem Monitor As a remote MCP server
claude mcp add --transport http monitor https://monitor.memoryapi.org/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only Ecosystem Monitor 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
The marketplaces of Ecosystem Monitor publish no settings it asks for, so we do not compare settings.
What it can do: dev.ezstat/ezstat-mcp-server · What it can do: Ecosystem Monitor · 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.