pareto-analysis vs Keypup Engineering Analytics
pareto-analysis is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑28.
pareto-analysis is a plugin bundle for AI coding tools published by dunnock. No marketplace we read lists it any more. Keypup Engineering Analytics is an MCP server published by keypup.io. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-28. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.
Where each is published
| Marketplace |  Keypup Engineering Analytics | |
|---|---|---|
| Community marketplace ddunnock/claude-plugins | Removed on 2026-10-28 Version: 1.0.2 Forks (GitHub): 7 Stars (GitHub): 14 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.0.1 Forks (GitHub): 0 Stars (GitHub): 1 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 | pareto-analysisno longer listed · | Keypup Engineering Analytics |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 1 |
| Stars (GitHub) (differs) | 14 | 1 |
| Forks (GitHub) (differs) | 7 | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | Remote server (hq.keypup.io/mcp) |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/ddunnock/claude-plugins | github.com/keypup-io/engineering-analytics-mcp-server |
| Changes in the last 7 days (differs) | 2 | 0 |
| First seen (differs) | 2026-10-15 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Not responding since 2026-10-24 |
Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.
What to use instead of pareto-analysis
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Institutional-grade Business Analysis skills for Claude. Methodology-grade outputs grounded in BABOK and real delivery experience. Includes four plugins: Capability Mapping (MECE…
-
Apply 20+ classical decision-making frameworks (cost-benefit, pre-mortem, MCDA, decision tree, reversibility, regret minimization, OODA, Eisenhower, SWOT, second-order…
-
Data & analytics skills: Metrics Framework, SQL Query Explainer, Dashboard Brief, Chart Data Extractor, Cohort Analysis, Data Pipeline Spec, A/B Test Readout, Metric Tree Builder…
-
A statistical analyst in your AI chat: bring data and a question, get a citable, re-runnable report.
-
The full AI Analyst skill system for data analysis in Claude Cowork: decision framing, data profiling, validated analysis, visualization, and a working-folder memory that learns…
-
Choose a prioritization framework based on stage, team context, and stakeholder needs.
What each says it does
pareto-analysis
Conduct Pareto Analysis (80/20 Rule) to identify vital few causes driving majority of problems. Generates Pareto charts and prioritization reports.
Keypup Engineering Analytics
Generate answers & visualizations from your engineering data to track software development health.
How to run each
pareto-analysis
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Keypup Engineering Analytics As a remote MCP server
claude mcp add --transport http engineering-analytics https://hq.keypup.io/mcp --header "Authorization: Bearer <YOUR_TOKEN>"Requires: Authorization header
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only Keypup Engineering Analytics 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
Neither one's marketplaces publish the settings it asks for.
What it can do: pareto-analysis · What it can do: Keypup Engineering Analytics · Compare two other plugins
Data comes from public marketplace files in GitHub repositories of their authors. 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.