io.github.theluckystrike/leave
REMOTE · MCP.ZOVO.ONE · SCANNED SEP 21
Employee leave and PTO requests: balances, approvals, calendars, and who-is-out summaries.
Available components
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. How we score → Why this is hard to score →
Endpoint Security89
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability86
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 1039 tokens (~79/item across 13 items; 12 tools + 1 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 12 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 13 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
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.
remote · mcp.zovo.one
claude mcp add --transport http theluckystrike-leave 'https://mcp.zovo.one/mcp/leave'
{
"mcpServers": {
"theluckystrike-leave": {
"url": "https://mcp.zovo.one/mcp/leave"
}
}
} {
"servers": {
"theluckystrike-leave": {
"type": "http",
"url": "https://mcp.zovo.one/mcp/leave"
}
}
} [mcp_servers.theluckystrike-leave] url = "https://mcp.zovo.one/mcp/leave"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"theluckystrike-leave": {
"type": "remote",
"url": "https://mcp.zovo.one/mcp/leave",
"enabled": true
}
}
} openclaw mcp add theluckystrike-leave --url 'https://mcp.zovo.one/mcp/leave' --transport streamable-http
mcp_servers:
theluckystrike-leave:
url: "https://mcp.zovo.one/mcp/leave" {
"McpServers": {
"theluckystrike-leave": {
"Transport": "http",
"Url": "https://mcp.zovo.one/mcp/leave"
}
}
} assistant mcp add theluckystrike-leave -t streamable-http -u 'https://mcp.zovo.one/mcp/leave'
{
"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.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 21 Sept 26 +54
- Authorization: unverified → fail ▼ security
- Injection markers: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- First check of Judged manipulation: pass security
- Tool coverage: unverified → 100 ▲ functional
- Schema quality: unverified → 100 ▲ functional
- 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 functional
- 20 Sept 26 25
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Sept 2026 · Probed https://mcp.zovo.one/mcp/leave
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=zovo.one | CN=WE1,O=Google Trust Services,C=US | 2 Sept 2026 | 1 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | ef74739bd6e575bb13db69661e215324 |
| SANs: zovo.one, mcp.zovo.one, *.mcp.zovo.one | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.zovo.one. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| one. | present | 64939 | 8 | Verified |
| zovo.one. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Challenged, unverified
The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.
| Result | Challenged, unverified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer realm="mcp.zovo.one", error="invalid_token"
Bearer realm="mcp.zovo.one", error="invalid_token"| Header | Value |
|---|---|
| strict-transport-security | max-age=15552000; includeSubDomains; preload |
| x-content-type-options | nosniff |
Protected resource metadata
| Retrieved | No |
|---|---|
| Problem | no_resource_metadata |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.zovo.one/mcp/leave | Verified | 200 | |
| http (plaintext) | http://mcp.zovo.one/mcp/leave | HTTPS enforced | 301 | https://mcp.zovo.one/mcp/leave |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
leave_approve Approve leave ~63
Approve a pending leave request by id. Also used to re-open a rejected one. Nothing to approve on an already-approved request.
| Name | Type | Req | Description |
|---|---|---|---|
| comment | string | – | Approval note |
| request | string | yes | The request id (e.g. LV-0001). |
No output schema declared.
No examples provided.
leave_balance Leave balance ~56
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.
| Name | Type | Req | Description |
|---|---|---|---|
| employee | string | yes | Employee id or name |
No output schema declared.
No examples provided.
leave_cancel Cancel leave ~69
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.
| Name | Type | Req | Description |
|---|---|---|---|
| reason | string | – | Why |
| request | string | yes | The request id (e.g. LV-0001). |
No output schema declared.
No examples provided.
leave_employee_add Add an employee ~124
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.
| Name | Type | Req | Description |
|---|---|---|---|
| annualAllowance | integer | yes | Annual paid leave allowance in whole days |
| carriedOver | integer | – | Days carried over from last year (default 0) |
| string | – | Work email, for calendar lookup | |
| name | string | yes | Full name, e.g. Taylor Wren |
No output schema declared.
No examples provided.
leave_export_ics Export calendar (Pro) ~59
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.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | – | Local .ics file to write |
No output schema declared.
No examples provided.
leave_import Bulk import requests (Pro) ~104
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.
| Name | Type | Req | Description |
|---|---|---|---|
| csv | string | yes | CSV text, newline-separated, first row header: employee,type,start,end,halfDay,status,reason |
No output schema declared.
No examples provided.
leave_list List employees or requests ~57
List all employees, or all leave requests (optionally filtered by employee and/or status). Omit the filter to list requests.
| Name | Type | Req | Description |
|---|---|---|---|
| employee | string | – | Filter requests to one employee |
| status | string | – | Filter requests by status |
No output schema declared.
No examples provided.
leave_out_range Who is out? ~84
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.
| Name | Type | Req | Description |
|---|---|---|---|
| end | string | yes | Last day, YYYY-MM-DD, inclusive |
| start | string | yes | First day, YYYY-MM-DD, inclusive |
No output schema declared.
No examples provided.
leave_reject Reject leave ~76
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.
| Name | Type | Req | Description |
|---|---|---|---|
| reason | string | – | Why |
| request | string | yes | The request id (e.g. LV-0001). |
No output schema declared.
No examples provided.
leave_request Request leave ~166
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.
| Name | Type | Req | Description |
|---|---|---|---|
| employee | string | yes | The employee id or name |
| end | string | yes | 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 | yes | First day off, YYYY-MM-DD, inclusive |
| type | string | yes | Kind of leave |
No output schema declared.
No examples provided.
license_activate Activate license ~76
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.
| Name | Type | Req | Description |
|---|---|---|---|
| key | string | yes | License key from checkout, MCPL1.<payload>.<signature> |
No output schema declared.
No examples provided.
license_status License status ~55
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
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.