McpStamp Leave Tracker
REMOTE · MCP.ZOVO.ONE · 2 COMPONENTS
Employee leave and PTO: requests, approvals, balances, who is out, and conflict checks.
Available components
Last scanned (3 hours ago)
Scores higher than 99% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Productivity and Notes
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 Security94
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- 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
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability85
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1131 tokens (~87/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 Management100
- No destabilizing schema changes in the last 30 days.Pass
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 14 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
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.
- 2 Nov 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: 79 → 87 ▼ functional
- Schema quality: excellent → good functional
- 21 Oct 26 0
- Stability: 0.97 → pass security
- 20 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Oct 26 +1
- Server version: 0.22.0 → 0.22.6 functional
- 15 Oct 26 +67
- Transport: unverified → pass ▲ security
- Injection markers: unverified → pass ▲ security
- Authorization: unverified → pass ▲ security
- Endpoint reachability: behind authorisation → reachable ▲ functional
- Stability: unverified → 0.80 ▲ functional
- Schema quality: unverified → 100 ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- 14 Oct 26 −66
- Endpoint reachability: reachable → behind authorisation ▼ security
- Tool safety: pass → unverified ▼ security
- Authorization: pass → unverified ▼ security
- Transport: pass → unverified ▼ security
- Stability: 0.73 → unverified ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Schema quality: 100 → unverified ▼ functional
- 12 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
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 5 Nov 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 | 31 Oct 2026 | 29 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 39e1adfa4eb6500e0e3d48868766e3e9 |
| 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 Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer realm="mcp.zovo.one", resource_metadata="https://mcp.zovo.one/.well-known/oauth-protected-resource/mcp/leave"
Bearer realm="mcp.zovo.one", resource_metadata="https://mcp.zovo.one/.well-known/oauth-protected-resource/mcp/leave"| Header | Value |
|---|---|
| strict-transport-security | max-age=15552000; includeSubDomains; preload |
| x-content-type-options | nosniff |
Protected resource metadata
| Document | https://mcp.zovo.one/.well-known/oauth-protected-resource/mcp/leave |
|---|---|
| Retrieved | Yes |
| Resource | https://mcp.zovo.one/mcp/leave |
| Authorisation server | https://mcp.zovo.one |
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.
How do I install the McpStamp Leave Tracker MCP server?
McpStamp Leave Tracker 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'
What is the McpStamp Leave Tracker MCP server?
McpStamp Leave Tracker is an MCP server listed in the public MCP registry as io.github.theluckystrike/leave. Employee leave and PTO: requests, approvals, balances, who is out, and conflict checks. This page covers its hosted endpoint (https://mcp.zovo.one/mcp/leave).
Is the McpStamp Leave Tracker MCP server safe to use?
McpStamp Leave Tracker scores 95 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 McpStamp Leave Tracker MCP server expose?
McpStamp Leave Tracker 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 McpStamp Leave Tracker MCP server require authentication?
Yes. McpStamp Leave Tracker 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 McpStamp Leave Tracker MCP server still maintained?
McpStamp Leave Tracker is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.