Ext Ops Panel
Open dashboard
Comparison

mozg-stake vs Obsidian Turbocharged

mozg-stake is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑23.

mozg-stake is a plugin bundle for AI coding tools published by mozg. No marketplace we read lists it any more. Obsidian Turbocharged is an MCP server published by The-40-Thieves. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-10-27. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.

Where each is published

Where each is published
Marketplacemozg-stakeObsidian Turbocharged
Community marketplace egorfedorov/mozg Removed on 2026-10-23
Version: 0.1.0
Forks (GitHub): 1
Stars (GitHub): 8
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.33.1
Downloads/month (npm): 4 317
Downloads/week (npm): 987
Forks (GitHub): 2
Stars (GitHub): 13
Not marked · First seen
npm registry (MCP servers) Not listed Listed
Version: 1.33.1
Downloads/month (npm): 4 317
Downloads/week (npm): 987
Forks (GitHub): 2
Stars (GitHub): 13
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

mozg-stake vs Obsidian Turbocharged
Factmozg-stakeno longer listed · Obsidian Turbocharged
Marketplaces that list it (differs)02
Stars (GitHub) (differs)813
Forks (GitHub) (differs)12
Last release (differs)Not published2026-10-14
Where it runs (differs)Installs as a plugin bundleOn your machine (obsidian-tc)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published2, secrets among them: 0
Parts of the bundle (differs)1Not a bundle
Licence (differs)Not statedAGPL-3.0-only
Repository (differs)github.com/egorfedorov/mozggithub.com/the-40-thieves/obsidian-tc
Changes in the last 7 days22
First seen (differs)2026-10-142026-10-11

Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.

What to use instead of mozg-stake

Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.

  • governance

    Engineering standards and code governance enforcement with parallel agent execution for code reviews, commits, and standards audits.

    by wrsmith108 · Plugin bundle

    Listed on: Claude Code: claude-plugins-community · Describes nearly the same job

  • secure-npm-package

    Set up a secure npm package release process — Trusted Publishing with staged publishes from GitHub Actions — and walk the user through the required npmjs.com and GitHub settings

    by evilmartians · Plugin bundle

    Listed on: Community GitHub marketplaces · Describes nearly the same job

  • dashclaw

    DashClaw governance, integration, and platform intelligence: guard checks, approvals, and audit trails for your agents.

    by DashClaw · Plugin bundle

    Listed on: Community GitHub marketplaces · Describes nearly the same job

  • copilot-plugin-development

    Create, migrate, audit, and validate flat GitHub Copilot plugins and marketplaces with direct component paths, canonical source ownership, dependency pinning, and isolated runtime…

    by Copilot Primitives Maintainers · Plugin bundle

    Listed on: Community GitHub marketplaces · Describes nearly the same job

  • ensembra

    Six specialist agents + scribe orchestrated through a 5-phase pipeline with Reuse-First cross-cutting policy. Built for solo developers.

    by HotRedMat · Plugin bundle

    Listed on: Claude Code: claude-plugins-community · Describes nearly the same job

  • git-github

    Git and GitHub conventions with a live GitHub Actions version check that resolves every uses: line from GitHub, plus a user-triggered /release workflow that bumps every version…

    by henkisdabro · Plugin bundle

    Listed on: Community GitHub marketplaces · Describes nearly the same job

Its card, with similar plugins by marketplace

What each says it does

mozg-stake

In its own words, on Community GitHub marketplaces:

Hands for the Stake Engine brain: upload bundles, run compliance checks, publish a release. Needs the stakecli binary.

Obsidian Turbocharged

In its own words, on Official MCP Registry:

Governed Obsidian vault access: hybrid retrieval, Markdown-native memory, HITL confirmations.

How to run each

mozg-stake

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

Obsidian Turbocharged As a local MCP server: npm package

Claude Code
claude mcp add --env "OBSIDIAN_TC_CONFIG=<YOUR_OBSIDIAN_TC_CONFIG>" --transport stdio obsidian-tc -- npx -y obsidian-tc

Requires: OBSIDIAN_TC_CONFIG

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

The marketplaces of mozg-stake publish no settings it asks for, so we do not compare settings.

What it can do: mozg-stake · What it can do: Obsidian Turbocharged · 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. Package data comes from the public npm registry (registry.npmjs.org). 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