insight-blueprint vs Scope Analytics
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). Scope Analytics is an MCP server published by wally827. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-24. 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 |  insight-blueprint | |
|---|---|---|
| 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.1.5 Downloads/month (PyPI): 338 Downloads/week (PyPI): 52 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 | insight-blueprint | Scope Analytics |
|---|---|---|
| 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) | Installs as a plugin bundle | On your machine (scope-analytics-mcp) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 2, secrets among them: 0 | 2, secrets among them: 1 |
| Parts of the bundle (differs) | 12 | Not a bundle |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/etoyama/insight-blueprint | Not stated |
| 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
insight-blueprint
Hypothesis-driven data analysis workflow and catalog MCP server
Scope Analytics
Install + query Scope analytics from an AI coding agent (Claude Code, Cursor, etc.).
How to run each
insight-blueprint As a Claude Code plugin
/plugin marketplace add anthropics/claude-plugins-community
/plugin install insight-blueprint@claude-communityScope Analytics As a local MCP server: PyPI package
claude mcp add --env "SCOPE_API_KEY=<YOUR_SCOPE_API_KEY>" --transport stdio scope-analytics-mcp -- uvx scope-analytics-mcpRequires: SCOPE_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_TIMEOUTPYTHONUNBUFFERED
Only Scope Analytics asks for
SCOPE_API_BASESCOPE_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: Scope 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 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.