Ext Ops Panel
Open dashboard
Comparison

codescene-codehealth vs Repowise (Hosted)

codescene-codehealth is a plugin bundle for AI coding tools published by codescene-oss. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). Repowise (Hosted) is an MCP server published by repowise.dev. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-15. 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
Marketplacecodescene-codehealthRepowise (Hosted)
Claude Code: claude-plugins-community Listed
Version: 1.4.4
Forks (GitHub): 14
Stars (GitHub): 70
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.17.1
No figure published
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

codescene-codehealth vs Repowise (Hosted)
Factcodescene-codehealthRepowise (Hosted)
Marketplaces that list it11
Stars (GitHub) (differs)70No figure on GitHub
Forks (GitHub) (differs)14No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)On your machine (@codescene/codehealth-mcp)Remote server (api.repowise.dev/mcp/%7Bowner%7D/%7Brepo%7D)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)10Not a bundle
Licence (differs)Apache-2.0Not stated
Repository (differs)github.com/codescene-oss/codescene-mcp-serverNot stated
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 2 days ago

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

codescene-codehealth

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

A Claude Code plugin that provides CodeScene Code Health analysis tools and skills for reviewing, refactoring, and safeguarding code quality.

Repowise (Hosted)

In its own words, on Official MCP Registry:

Hosted codebase intelligence for repos indexed on repowise.dev — no local indexing needed.

How to run each

codescene-codehealth As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install codescene-codehealth@claude-community

Repowise (Hosted)

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

Requires: Authorization header

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only Repowise (Hosted) has a remote endpoint we check. How we check endpoints

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: codescene-codehealth · What it can do: Repowise (Hosted) · 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.

Where the data comes from: how the catalog is built