Ext Ops Panel
Open dashboard
Comparison

insight-blueprint vs io.github.hmamut39/tewip

insight-blueprint is a plugin bundle for AI coding tools published by etoyama. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). io.github.hmamut39/tewip is an MCP server published by hmamut39. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-28. 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
Marketplaceinsight-blueprintio.github.hmamut39/tewip
Claude Code: claude-plugins-community Listed
Version: 0.6.0
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.70.16
Downloads/month (npm): 18 139
Downloads/week (npm): 7 853
Forks (GitHub): 0
Stars (GitHub): 0
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

insight-blueprint vs io.github.hmamut39/tewip
Factinsight-blueprintio.github.hmamut39/tewip
Marketplaces that list it11
Stars (GitHub)00
Forks (GitHub)00
Last release (differs)Not published2026-10-19
Where it runs (differs)Installs as a plugin bundleOn your machine (tewip-ai)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)2, secrets among them: 01, secrets among them: 1
Parts of the bundle (differs)12Not a bundle
LicenceMITMIT
Repository (differs)github.com/etoyama/insight-blueprintgithub.com/hmamut39/tewip
Changes in the last 7 days00
First seen2026-10-112026-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

insight-blueprint

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

Hypothesis-driven data analysis workflow and catalog MCP server

io.github.hmamut39/tewip

In its own words, on Official MCP Registry:

Proves software work: triages failing tests, checks whether a test can fail, and reads migrations.

How to run each

insight-blueprint As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install insight-blueprint@claude-community

io.github.hmamut39/tewip As a local MCP server: npm package

Claude Code
claude mcp add --env "OPENAI_API_KEY=<YOUR_OPENAI_API_KEY>" --transport stdio tewip -- npx -y tewip-ai mcp

Requires: OPENAI_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 insight-blueprint asks for

  • MCP_TIMEOUT
  • PYTHONUNBUFFERED

Only io.github.hmamut39/tewip asks for

  • OPENAI_API_KEY (secret)

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: insight-blueprint · What it can do: io.github.hmamut39/tewip · 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 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.

Where the data comes from: how the catalog is built