Ext Ops Panel
Open dashboard
Comparison

Descope vs io.github.theluckystrike/leave

Descope is an MCP server published by descope-sample-apps. Marketplaces we read that list it: 1 (Docker MCP Catalog). io.github.theluckystrike/leave is an MCP server published by theluckystrike. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-16. 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
MarketplaceDescopeio.github.theluckystrike/leave
Docker MCP Catalog Listed
Version: sha256:554b2b490c18
Forks (GitHub): 7
Pulls (Docker Hub): 17 879
Stars (Docker Hub): 0
Stars (GitHub): 38
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.22.6
Forks (GitHub): 0
Stars (GitHub): 1
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

Descope vs io.github.theluckystrike/leave
FactDescopeio.github.theluckystrike/leave
Marketplaces that list it11
Stars (GitHub) (differs)38 (better)1 (worse)
Pulls (Docker Hub) (differs)17 879No figure on Docker Hub
Forks (GitHub) (differs)7 (better)0 (worse)
Last release (differs)Not published2026-10-14
Where it runs (differs)On your machine (mcp/descope)Remote server or your machine
Transport (differs)stdioStreamable HTTP, stdio
Tools it declares (differs)4Not published
Environment variables it asks for (differs)2, secrets among them: 11, secrets among them: 1
Licence (differs)MITNot stated
Repository (differs)github.com/descope-sample-apps/descope-mcp-servergithub.com/theluckystrike/mcp-servers
Changes in the last 7 days (differs)012
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

Descope

In its own words, on Docker MCP Catalog:

The Descope Model Context Protocol (MCP) server provides an interface to interact with Descope's Management APIs, enabling the search and retrieval of project-related information.

io.github.theluckystrike/leave

In its own words, on Official MCP Registry:

Employee leave and PTO requests: balances, approvals, calendars, and who-is-out summaries.

How to run each

Descope As a local MCP server: Docker image

Claude Code
claude mcp add --env "DESCOPE_MANAGEMENT_KEY=<YOUR_DESCOPE_MANAGEMENT_KEY>" --transport stdio descope -- docker run -i --rm -e DESCOPE_MANAGEMENT_KEY mcp/descope

Requires: DESCOPE_MANAGEMENT_KEY (secret)

io.github.theluckystrike/leave As a remote MCP server

Claude Code
claude mcp add --transport http leave https://mcp.zovo.one/mcp/leave --header "Authorization: Bearer <YOUR_TOKEN>"

Requires: MCP_LICENSE_KEY (secret), Authorization header

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

Only io.github.theluckystrike/leave has a remote endpoint we check. How we check endpoints

Tools each declares

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

Settings each asks for

Only Descope asks for

  • DESCOPE_MANAGEMENT_KEY (secret)
  • DESCOPE_PROJECT_ID

Only io.github.theluckystrike/leave asks for

  • MCP_LICENSE_KEY (secret)

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: Descope · What it can do: io.github.theluckystrike/leave · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. 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