Ext Ops Panel
Open dashboard
Comparison

io.github.CloudCorpRecords/greenlight vs GitHub

io.github.CloudCorpRecords/greenlight is an MCP server published by CloudCorpRecords. Marketplaces we read that list it: 1 (Official MCP Registry). GitHub is an MCP server published by github. Marketplaces we read that list it: 3 (Official MCP Registry, Docker MCP Catalog, Community GitHub marketplaces). As of our marketplace pass on 2026-11-08. 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
Marketplaceio.github.CloudCorpRecords/greenlightGitHub
Official MCP Registry Listed
Version: 0.26.0
Downloads/month (npm): 7 967
Downloads/week (npm): 854
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Listed
Version: 2.1.0
Forks (GitHub): 5 308
Stars (GitHub): 34 320
Not marked · First seen
Docker MCP Catalog Not listed Listed
Version: sha256:f6056fc10bff
Forks (GitHub): 5 308
Stars (GitHub): 34 320
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

io.github.CloudCorpRecords/greenlight vs GitHub
Factio.github.CloudCorpRecords/greenlightGitHub
Marketplaces that list it (differs)1 (worse)3 (better)
Stars (GitHub) (differs)0 (worse)34 320 (better)
Forks (GitHub) (differs)0 (worse)5 308 (better)
Last release (differs)2026-11-05 (better)2026-11-04 (worse)
Where it runs (differs)On your machine (@reneturcios/greenlight)Remote server or your machine
Transport (differs)stdioStreamable HTTP, stdio
Tools it declares (differs)Not published40
Environment variables it asks for (differs)Not published1, secrets among them: 1
Licence (differs)Not statedMIT
Repository (differs)github.com/cloudcorprecords/greenlightgithub.com/github/github-mcp-server
Changes in the last 7 days (differs)13
First seen (differs)2026-10-162026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 12 h ago, requires authentication

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

io.github.CloudCorpRecords/greenlight

In its own words, on Official MCP Registry:

Pre-flight checks for open-source contributions: is this GitHub issue actually landable?

GitHub

In its own words, on Official MCP Registry:

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

How to run each

io.github.CloudCorpRecords/greenlight As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio greenlight -- npx -y @reneturcios/greenlight mcp

GitHub As a remote MCP server

Claude Code
claude mcp add --transport http github-mcp-server https://api.githubcopilot.com/mcp/ --header "Authorization: Bearer <YOUR_TOKEN>"

Requires: Authorization header

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

Only GitHub has a remote endpoint we check. How we check endpoints

Tools each declares

The marketplaces of io.github.CloudCorpRecords/greenlight publish no list of tools, so we do not compare tools.

Settings each asks for

The marketplaces of io.github.CloudCorpRecords/greenlight publish no settings it asks for, so we do not compare settings.

What it can do: io.github.CloudCorpRecords/greenlight · What it can do: GitHub · 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. 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