Ext Ops Panel
Open dashboard
Comparison

io.github.layergen/eodly-mcp vs io.github.theluckystrike/leave

io.github.layergen/eodly-mcp is an MCP server published by layergen. Marketplaces we read that list it: 1 (Official MCP Registry). 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-26. 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.layergen/eodly-mcpio.github.theluckystrike/leave
Official MCP Registry Listed
Version: 0.2.2
Downloads/month (npm): 339
Downloads/week (npm): 31
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Listed
Version: 0.22.6
Forks (GitHub): 0
Stars (GitHub): 2
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.layergen/eodly-mcp vs io.github.theluckystrike/leave
Factio.github.layergen/eodly-mcpio.github.theluckystrike/leave
Marketplaces that list it11
Stars (GitHub) (differs)0 (worse)2 (better)
Forks (GitHub)00
Last release (differs)Not published2026-10-14
Where it runs (differs)Remote server (eodly.io/mcp)Remote server or your machine
Transport (differs)Streamable HTTPStreamable HTTP, stdio
Tools it declaresNot publishedNot published
Environment variables it asks for1, secrets among them: 11, secrets among them: 1
LicenceNot statedNot stated
Repository (differs)github.com/layergen/eodly-mcpgithub.com/theluckystrike/mcp-servers
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Responded 6 days agoNot responding since 2026-10-25

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.layergen/eodly-mcp

In its own words, on Official MCP Registry:

Read your team's end-of-day reports and roster from Eodly. Sign in with OAuth or use an API key.

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

io.github.layergen/eodly-mcp As a remote MCP server

Claude Code
claude mcp add --transport http eodly-mcp https://eodly.io/mcp

Requires: EODLY_API_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 the endpoint of io.github.layergen/eodly-mcp responded at the last daily 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

Only io.github.layergen/eodly-mcp asks for

  • EODLY_API_KEY (secret)

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: io.github.layergen/eodly-mcp · What it can do: io.github.theluckystrike/leave · Compare two other plugins

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