Ext Ops Panel
Open dashboard
Comparison

light-mcp vs io.github.QoreNext-IT/qorenext-mcp

light-mcp is a plugin bundle for AI coding tools published by light-space. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). io.github.QoreNext-IT/qorenext-mcp is an MCP server published by QoreNext-IT. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-21. 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
Marketplacelight-mcpio.github.QoreNext-IT/qorenext-mcp
Claude Code: claude-plugins-community Listed
Version: 34ee2f6
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.1
Forks (GitHub): 0
Stars (GitHub): 0
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

light-mcp vs io.github.QoreNext-IT/qorenext-mcp
Factlight-mcpio.github.QoreNext-IT/qorenext-mcp
Marketplaces that list it11
Stars (GitHub)00
Forks (GitHub)00
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleRemote server (mcp.qorenext.com/mcp)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
LicenceNot statedNot stated
Repository (differs)github.com/light-space/light-mcpgithub.com/qorenext-it/qorenextmcp
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkAnswered with HTTP 404 (18 h 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

light-mcp

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

Light's MCP integration lets you use AI tools to query your financial data, search invoices, look up vendors, and run reports, without switching context.

io.github.QoreNext-IT/qorenext-mcp

In its own words, on Official MCP Registry:

Company hierarchy analysis and address verification via MCP

How to run each

light-mcp As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install light-mcp@claude-community

io.github.QoreNext-IT/qorenext-mcp As a remote MCP server

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

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

Only io.github.QoreNext-IT/qorenext-mcp 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: light-mcp · What it can do: io.github.QoreNext-IT/qorenext-mcp · 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