Ext Ops Panel
Open dashboard
Comparison

Sectionsight vs io.github.sudomichael/gizmoanalytics

Sectionsight is a plugin bundle for AI coding tools published by Majny. Marketplaces we read that list it: 1 (Community GitHub marketplaces). io.github.sudomichael/gizmoanalytics is an MCP server published by sudomichael. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-23. 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
MarketplaceSectionsightio.github.sudomichael/gizmoanalytics
Community marketplace davepoon/buildwithclaude Listed
Version: 0.4.0
Forks (GitHub): 0
Stars (GitHub): 1
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.1.5
Downloads/month (npm): 122
Downloads/week (npm): 20
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

Sectionsight vs io.github.sudomichael/gizmoanalytics
FactSectionsightio.github.sudomichael/gizmoanalytics
Marketplaces that list it11
Stars (GitHub) (differs)1No figure on GitHub
Forks (GitHub) (differs)0No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleOn your machine (gizmoanalytics-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)MITNot stated
Repository (differs)github.com/majny/sectionsightgithub.com/sudomichael/analyticsautopilot
Changes in the last 7 days00
First seen (differs)2026-10-152026-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

Sectionsight

In its own words, on Community GitHub marketplaces:

Sets up cookieless, privacy-first website analytics in your own site: time per page section, scroll, goals and 404s from a small tracker and a same-origin collector, an optional consent banner, PostHog session replay only after consent, one Slack or e-mail line per notable visit, a weekly digest, and health alerts. A Playwright check then proves the privacy claims: nothing stored before consent, no e-mail or token from the URL in any report, private pages silent.

io.github.sudomichael/gizmoanalytics

In its own words, on Official MCP Registry:

Cookieless analytics for AI coding agents. Install in one prompt, 28 tools, OAuth onboarding.

How to run each

Sectionsight As a Claude Code plugin

Claude Code
/plugin marketplace add davepoon/buildwithclaude
/plugin install sectionsight@buildwithclaude

io.github.sudomichael/gizmoanalytics

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

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

Neither one's marketplaces publish the settings it asks for.

What it can do: Sectionsight · What it can do: io.github.sudomichael/gizmoanalytics · 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.

Where the data comes from: how the catalog is built