Ext Ops Panel
Open dashboard
Comparison

GitHub vs spendtron

GitHub is an MCP server published by github. Marketplaces we read that list it: 2 (Official MCP Registry, Docker MCP Catalog). spendtron is an MCP server published by swantron. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-12. 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
MarketplaceGitHubspendtron
Official MCP Registry Listed
Version: 2.0.2
Forks (GitHub): 5 134
Stars (GitHub): 33 552
Not marked · First seen
Listed
Version: 1.1.0
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Docker MCP Catalog Listed
Version: sha256:ffced0d76e77
Forks (GitHub): 5 134
Stars (GitHub): 33 552
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

GitHub vs spendtron
FactGitHubspendtron
Marketplaces that list it (differs)2 (better)1 (worse)
Stars (GitHub) (differs)33 552 (better)0 (worse)
Forks (GitHub) (differs)5 134 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)Remote server or your machineRemote server (spendtron.com/mcp)
Transport (differs)Streamable HTTP, stdioStreamable HTTP
Tools it declares (differs)40Not published
Environment variables it asks for (differs)1, secrets among them: 1Not published
Licence (differs)MITNot stated
Repository (differs)github.com/github/github-mcp-servergithub.com/swantron/spendtron
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last checknot checked yetnot 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

GitHub

In its own words, on Official MCP Registry:

Connect AI assistants to GitHub - manage repos, issues, PRs, and workflows through natural language.

spendtron

In its own words, on Official MCP Registry:

Finds the GitHub Actions workflow eating your CI bill and suggests fix diffs, verified against runs.

How to run each

GitHub As a local MCP server: Docker image

Claude Code
claude mcp add --env "GITHUB_PERSONAL_ACCESS_TOKEN=<YOUR_GITHUB_PERSONAL_ACCESS_TOKEN>" --transport stdio github-official -- docker run -i --rm -e GITHUB_PERSONAL_ACCESS_TOKEN ghcr.io/github/github-mcp-server

Requires: GITHUB_PERSONAL_ACCESS_TOKEN (secret)

spendtron

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

The marketplaces of spendtron publish no list of tools, so we do not compare tools.

Settings each asks for

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

What it can do: GitHub · What it can do: spendtron · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. 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