Ext Ops Panel
Open dashboard
Comparison

GitHits vs Claude Code Explorer MCP

GitHits is an MCP server published by githits.com. Marketplaces we read that list it: 3 (Official MCP Registry, Claude Code: claude-plugins-community, Community GitHub marketplaces). Claude Code Explorer MCP is an MCP server published by divu2025. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-17. 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
MarketplaceGitHitsClaude Code Explorer MCP
Official MCP Registry Listed
Version: 0.30.0
Downloads/month (npm): 11 168
Downloads/week (npm): 2 696
Forks (GitHub): 12
Stars (GitHub): 115
Not marked · First seen
Listed
Version: 1.1.0
Downloads/month (npm): 148
Downloads/week (npm): 32
Forks (GitHub): 3 663
Stars (GitHub): 3 395
Not marked · First seen
Claude Code: claude-plugins-community Listed
Version: 0.8.0
Forks (GitHub): 12
Stars (GitHub): 115
Not marked · First seen
Not listed

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

GitHits vs Claude Code Explorer MCP
FactGitHitsClaude Code Explorer MCP
Marketplaces that list it (differs)3 (better)1 (worse)
Stars (GitHub) (differs)115 (worse)3 395 (better)
Forks (GitHub) (differs)12 (worse)3 663 (better)
Last release (differs)2026-10-15Not published
Where it runs (differs)Remote server (mcp.githits.com)On your machine (@divyesh2000/codemaster)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)5Not a bundle
Licence (differs)Apache-2.0Not stated
Repository (differs)github.com/githits-com/githits-cligithub.com/codeaashu/claude-code
Changes in the last 7 days (differs)50
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Responded 4 days ago, requires a keyno remote endpoint we check

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

GitHits

In its own words, on Official MCP Registry:

Search public open-source code, documentation, metadata, vulnerabilities, changelogs, and examples.

Claude Code Explorer MCP

In its own words, on Official MCP Registry:

Explore the Claude Code CLI source — browse tools, commands, search code, and more.

How to run each

GitHits As a remote MCP server

Claude Code
claude mcp add --transport http githits https://mcp.githits.com

Claude Code Explorer MCP As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio codemaster -- npx -y @divyesh2000/codemaster

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

Only GitHits 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: GitHits · What it can do: Claude Code Explorer MCP · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. Data comes from public marketplace files in GitHub repositories of their authors. 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