Ext Ops Panel
Open dashboard
Comparison

Hunch — Engineering Memory + Change Gate vs Snipara Project Intelligence

Hunch — Engineering Memory + Change Gate is a plugin bundle for AI coding tools published by Dave Sheffer. Marketplaces we read that list it: 1 (Community GitHub marketplaces). Snipara Project Intelligence is an MCP server published by Snipara. 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
MarketplaceHunch — Engineering Memory + Change GateSnipara Project Intelligence
Community marketplace davesheffer/hunch Listed
Version: not stated
Forks (GitHub): 1
Stars (GitHub): 11
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.0
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

Hunch — Engineering Memory + Change Gate vs Snipara Project Intelligence
FactHunch — Engineering Memory + Change GateSnipara Project Intelligence
Marketplaces that list it11
Stars (GitHub) (differs)11 (better)0 (worse)
Forks (GitHub) (differs)1 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (hunch-exact)Remote server (api.snipara.com/mcp/%7Bproject_slug%7D)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)6Not a bundle
Licence (differs)Apache-2.0Not stated
Repository (differs)github.com/davesheffer/hunchgithub.com/snipara/snipara-examples
Changes in the last 7 days (differs)20
First seen (differs)2026-10-132026-10-11
Endpoint at the last check (differs)no remote endpoint we checknot checked yet

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

Hunch — Engineering Memory + Change Gate

In its own words, on Community GitHub marketplaces:

The hunch_* MCP tools (why, constraints, blast radius, merge verdict, capture) plus /hunch:capture, /hunch:heal, /hunch:why, /hunch:fix, /hunch:fragile. Requires Node 22.13+; launches the exact npm package `@davesheffer/hunch@1.17.0` per project.

Snipara Project Intelligence

In its own words, on Official MCP Registry:

Hosted MCP for source-backed project context, memory, code impact, and agent workflow continuity.

How to run each

Hunch — Engineering Memory + Change Gate As a Claude Code plugin

Claude Code
/plugin marketplace add davesheffer/hunch
/plugin install hunch@hunch

Snipara Project Intelligence

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

Requires: X-API-Key header

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: Hunch — Engineering Memory + Change Gate · What it can do: Snipara Project Intelligence · 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