Ext Ops Panel
Open dashboard
Comparison

agent-estimate vs Keypup Engineering Analytics

agent-estimate is a plugin bundle for AI coding tools published by haoranc. Marketplaces we read that list it: 2 (Claude Code: claude-plugins-community, Community GitHub marketplaces). 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-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

Where each is published
Marketplaceagent-estimateKeypup Engineering Analytics
Claude Code: claude-plugins-community Listed
Version: 0.7.4
Forks (GitHub): 1
Stars (GitHub): 6
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

agent-estimate vs Keypup Engineering Analytics
Factagent-estimateKeypup Engineering Analytics
Marketplaces that list it (differs)2 (better)1 (worse)
Stars (GitHub) (differs)6 (better)1 (worse)
Forks (GitHub) (differs)1 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleRemote server (hq.keypup.io/mcp)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)1Not a bundle
Licence (differs)Apache-2.0Not stated
Repository (differs)github.com/haoranc/agent-estimategithub.com/keypup-io/engineering-analytics-mcp-server
Changes in the last 7 days (differs)20
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 2 days 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

agent-estimate

In its own words, on Claude Code: claude-plugins-community:

Effort estimation for AI coding agents. PERT three-point estimation with METR reliability thresholds, modifier stacks (spec clarity, warm context, agent fit), and wave planning for multi-agent parallel execution. Supports single tasks, batch files, and GitHub issues.

Keypup Engineering Analytics

In its own words, on Official MCP Registry:

Generate answers & visualizations from your engineering data to track software development health.

How to run each

agent-estimate As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install agent-estimate@claude-community

Keypup Engineering Analytics As a remote MCP server

Claude Code
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: agent-estimate · What it can do: Keypup Engineering Analytics · Compare two other plugins

Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. 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.

Where the data comes from: how the catalog is built