# io.github.theluckystrike/leave (remote · mcp.zovo.one)

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

- Trust score: 79/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-21

## Components

- remote · `mcp.zovo.one`: 79/100 (this document), [markdown](https://verifymcp.io/servers/theluckystrike-leave/mcp-leave.md), [page](https://verifymcp.io/servers/theluckystrike-leave/mcp-leave)

## Channel facts

- Endpoint: `https://mcp.zovo.one/mcp/leave`
- Transports: `streamable-http`
- Auth: `required`
- Version: `0.22.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-21.

- **Endpoint Security**: 89/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 86/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 1039 tokens (~79/item across 13 items; 12 tools + 1 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 12 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 13 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

**Unverified: 1 category.** A category scored 0 because we could not verify it: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

## Install

### How do I install the io.github.theluckystrike/leave MCP server?

io.github.theluckystrike/leave is a hosted endpoint at https://mcp.zovo.one/mcp/leave, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http theluckystrike-leave 'https://mcp.zovo.one/mcp/leave'
```

### Cursor

```json
{
  "mcpServers": {
    "theluckystrike-leave": {
      "url": "https://mcp.zovo.one/mcp/leave"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "theluckystrike-leave": {
      "type": "http",
      "url": "https://mcp.zovo.one/mcp/leave"
    }
  }
}
```

### Codex

```toml
[mcp_servers.theluckystrike-leave]
url = "https://mcp.zovo.one/mcp/leave"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "theluckystrike-leave": {
      "type": "remote",
      "url": "https://mcp.zovo.one/mcp/leave",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add theluckystrike-leave --url 'https://mcp.zovo.one/mcp/leave' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  theluckystrike-leave:
    url: "https://mcp.zovo.one/mcp/leave"
```

### Netclaw

```json
{
  "McpServers": {
    "theluckystrike-leave": {
      "Transport": "http",
      "Url": "https://mcp.zovo.one/mcp/leave"
    }
  }
}
```

### Vellum

```bash
assistant mcp add theluckystrike-leave -t streamable-http -u 'https://mcp.zovo.one/mcp/leave'
```

### Other

```json
{
  "mcpServers": {
    "theluckystrike-leave": {
      "type": "http",
      "url": "https://mcp.zovo.one/mcp/leave"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-21 (score 79, +54)

- [security regression] Authorization: unverified → fail
- [security improvement] Injection markers: unverified → pass
- [security improvement] Transport: fail → pass
- [security] First check of Judged manipulation: pass
- [functional improvement] Tool coverage: unverified → 100
- [functional improvement] Schema quality: unverified → 100
- [functional improvement] MCP protocol: unverified → pass
- [functional] First check of Schema quality: fail
- [functional] First check of Schema quality: excellent
- [functional] First check of Destructive annotations: pass
- [functional] First check of Schema quality: pass
- [functional] First check of Tool coverage: 100

### 2026-09-20 (score 25)

First indexed and scored.

## MCP tools (12)

### `leave_employee_add` (~124 tokens)

Add an employee

Add an employee to the leave tracker and return their EMP-NNNN id. Give their annual paid-leave allowance in whole days and any days carried over from last year. Balances charge approved plus pending leave against allowance + carried-over. Free tier: unlimited.

Input parameters:

- `annualAllowance` (integer, required): Annual paid leave allowance in whole days
- `carriedOver` (integer): Days carried over from last year (default 0)
- `email` (string): Work email, for calendar lookup
- `name` (string, required): Full name, e.g. Taylor Wren

### `leave_request` (~166 tokens)

Request leave

Create a leave or PTO request and return its LV-NNNN id. type is vacation, sick, unpaid or parental. start and end are inclusive YYYY-MM-DD dates; halfDay charges half a day for the whole span. A pending request is refussed if it would overlap another approved or pending request of the same employee. Free tier: unlimited requests.

Input parameters:

- `employee` (string, required): The employee id or name
- `end` (string, required): Last day off, YYYY-MM-DD, inclusive
- `halfDay` (boolean): Half-day charge for the whole span (default false)
- `reason` (string): Why, shown in reports and calendar
- `start` (string, required): First day off, YYYY-MM-DD, inclusive
- `type` (string, required): Kind of leave

### `leave_approve` (~63 tokens)

Approve leave

Approve a pending leave request by id. Also used to re-open a rejected one. Nothing to approve on an already-approved request.

Input parameters:

- `comment` (string): Approval note
- `request` (string, required): The request id (e.g. LV-0001).

### `leave_reject` (~76 tokens)

Reject leave

Reject or cancel a leave request by id. A pending or approved request becomes rejected; a rejected one can be reopened via leave_approve. Use leave_cancel (via reject with reason) for voluntary withdrawal.

Input parameters:

- `reason` (string): Why
- `request` (string, required): The request id (e.g. LV-0001).

### `leave_balance` (~56 tokens)

Leave balance

Show one employee's leave balance: allowance + carried-over, minus approved and pending, as whole days plus a possible half day. Remaining is rounded down to whole days on the report.

Input parameters:

- `employee` (string, required): Employee id or name

### `leave_out_range` (~84 tokens)

Who is out?

Who is out in a date range: start and end are inclusive YYYY-MM-DD. Each employee appears once per day; pending requests count as a plan. Use for coverage, calendars and absence summaries. Free tier: unlimited.

Input parameters:

- `end` (string, required): Last day, YYYY-MM-DD, inclusive
- `start` (string, required): First day, YYYY-MM-DD, inclusive

### `leave_list` (~57 tokens)

List employees or requests

List all employees, or all leave requests (optionally filtered by employee and/or status). Omit the filter to list requests.

Input parameters:

- `employee` (string): Filter requests to one employee
- `status` (string): Filter requests by status

### `leave_import` (~104 tokens)

Bulk import requests (Pro)

Pro. Bulk-create leave requests from a CSV/TSV. First row is a header: employee,type,start,end,halfDay,status,reason. status may be omitted (defaults to pending) or be approved/rejected. Each request is still checked for overlap conflicts; a conflicting row is reported, not applied. watermark-free, full CRUD.

Input parameters:

- `csv` (string, required): CSV text, newline-separated, first row header: employee,type,start,end,halfDay,status,reason

### `leave_export_ics` (~59 tokens)

Export calendar (Pro)

Pro. Export all APPROVED leave as an .ics calendar (RFC5545). Returns the calendar text; pass path to also write it to a local file. watermark-free.

Input parameters:

- `path` (string): Local .ics file to write

### `license_status` (~55 tokens)

License status

Report this endpoint's licence state for your token as JSON: the product, the tier free or pro, why it is not Pro, and the checkout URL. Call it to explain a free-tier refusal. No arguments, nothing changes.

### `license_activate` (~76 tokens)

Activate license

Turn Pro on for this connection with key, an MCPL1.<payload>.<signature> issued at checkout for this server or the bundle. Data under your token stays; a wrong or expired key changes nothing. license_status confirms it.

Input parameters:

- `key` (string, required): License key from checkout, MCPL1.<payload>.<signature>

### `leave_cancel` (~69 tokens)

Cancel leave

Cancel a pending or approved request by id, keeping its record with status cancelled. Differs from leave_reject in intent (voluntary withdrawal). Nothing happened if already cancelled.

Input parameters:

- `reason` (string): Why
- `request` (string, required): The request id (e.g. LV-0001).

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/theluckystrike-leave/mcp-leave#diagnostics

## Score history

- 2026-09-21: 79
- 2026-09-20: 25

## Common questions

### What is the io.github.theluckystrike/leave MCP server?

io.github.theluckystrike/leave is an MCP server listed in the public MCP registry as io.github.theluckystrike/leave. Employee leave and PTO requests: balances, approvals, calendars, and who-is-out summaries. This page covers its hosted endpoint (https://mcp.zovo.one/mcp/leave).

### Is the io.github.theluckystrike/leave MCP server safe to use?

io.github.theluckystrike/leave scores 79 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the io.github.theluckystrike/leave MCP server expose?

io.github.theluckystrike/leave exposes 12 tools: leave_employee_add, leave_request, leave_approve, leave_reject, leave_balance, and 7 more. Their descriptions and schemas cost roughly 989 tokens of context every time the server is loaded.

### Does the io.github.theluckystrike/leave MCP server require authentication?

Yes. io.github.theluckystrike/leave asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

### Is the io.github.theluckystrike/leave MCP server still maintained?

io.github.theluckystrike/leave is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://mcp.zovo.one/mcp/leave
- Authorisation metadata: https://mcp.zovo.one/.well-known/oauth-protected-resource/mcp/leave
- Repository: https://github.com/theluckystrike/mcp-servers
- Website: https://mcp.zovo.one/s/leave
- Changelog RSS feed: https://verifymcp.io/servers/theluckystrike-leave/mcp-leave.xml
- Changelog JSON feed: https://verifymcp.io/servers/theluckystrike-leave/mcp-leave.json
- HTML version of this page: https://verifymcp.io/servers/theluckystrike-leave/mcp-leave