# Zovo PTO Accrual Calculator (remote · pto-accrual.zovo.one)

PTO balance and accrual ledger

- Trust score: 78/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

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

## Channel facts

- Endpoint: `https://pto-accrual.zovo.one/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.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-11-21.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - 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**: 65/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 3069 tokens (~1023/item across 3 items; 2 tools + 1 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 43/100
  - Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **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.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 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.
  - Supports UI / widget rendering.

## Install

### How do I install the Zovo PTO Accrual Calculator MCP server?

Zovo PTO Accrual Calculator is a hosted endpoint at https://pto-accrual.zovo.one/mcp, 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-pto-accrual 'https://pto-accrual.zovo.one/mcp'
```

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

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

### Netclaw

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

### Vellum

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

### Other

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

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-11-21 (score 78, +1)

No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-19 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-17 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-14 (score 75, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-12 (score 74, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-10 (score 73, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-09 (score 72, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-08 (score 72)

First indexed and scored.

## MCP tools (2)

### `calculate_pto_balance` (~1540 tokens)

Calculate PTO balance

Use this when someone asks how much PTO they have, wants a PTO accrual calculator or vacation accrual calculator, or needs an employee's PTO, vacation or sick leave balance from an accrual policy. Give the accrual rule as accrual_amount + accrual_unit (hours, days, weeks) + accrual_per (year, month, week, pay_period, hour_worked), e.g. 2 weeks a year = 2, weeks, year; 1 hour per 30 worked = 0.0333, hours, hour_worked; use accrual_rate text only as a fallback. Takes the policy (per hour worked like 1 h per 30, hours per pay period with weekly/biweekly/semimonthly/monthly pay, or a yearly amount front-loaded or accrued evenly), tenure tiers, hire date, max balance, annual cap, carryover limit and reset date, waiting period, hours worked, and time taken (dates, hours or ranges; future dates are planned). Returns the balance as of a date (default today, US Eastern), available hours, a dated ledger with accrued, used, capped and forfeited hours, upcoming accruals, a year-end projection with hours to use before the reset, and PDF, Excel and CSV files. Does not give legal advice, check state law compliance, compute PTO payout in money, or connect to payroll. For several employees use calculate_team_pto_balances.

Input parameters:

- `accrual_amount`: Preferred way to give the rule: the amount earned, e.g. 15 (with accrual_unit days, accrual_per year), 4.62 (hours per pay_period) or 0.0333 (hours per hour_worked).
- `accrual_method`: How PTO is earned: per_hour_worked (e.g. 1 h per 30 h worked), per_pay_period (fixed hours each paycheck, e.g. 4.62 h), annual_front_loaded (whole year granted at once on the reset date), annual_accr…
- `accrual_per`: How often accrual_amount is earned: year, month, week, pay_period, or hour_worked. Required for hours; days or weeks without it are read as per year.
- `accrual_rate`: Fallback only, when you cannot fill accrual_amount/accrual_unit/accrual_per: the rule as text with a number, unit and period, e.g. "1 per 30", "4.62 hours per paycheck", "15 days a year". Hours witho…
- `accrual_unit`: Unit of accrual_amount: hours (default), days, or weeks (weeks = days_per_week x hours_per_day).
- `annual_accrual_cap`: Most hours that can be earned in one accrual year, e.g. 48.
- `annual_days`: Days of PTO per year, e.g. 15. Converted with hours_per_day (default 8).
- `annual_hours`: Hours of PTO per year, e.g. 120. Use instead of annual_days.
- `as_of_date`: Date to report the balance on, e.g. 2026-10-26. Default: today in US Eastern time.
- `carryover_limit`: Hours that may roll over at the reset date, e.g. 40. 0 = use it or lose it. Leave out for unlimited rollover.
- `days_per_week`: Workdays per week, default 5. Converts weeks of PTO to hours.
- `employee_name`: Optional name for the ledger header, e.g. Dana Kim.
- `first_year`: For annual_front_loaded: prorated (default, first grant prorated by days left in the year) or full.
- `hire_date`: Hire (start) date, e.g. 2024-03-04. Used for tenure tiers, the waiting period and the first partial pay period.
- `hours_per_day`: Hours in one PTO day, default 8, e.g. 7.5.
- `hours_per_week`: Standard hours per week, default 40, e.g. 30 for part time. Used when hours worked are not given.
- `hours_used`: Total PTO hours used without dates, e.g. 40 for "I used 40 hours this year". Subtracted on the as-of date. Use time_taken when dates are known.
- `hours_worked`: Actual hours worked per pay period for per_hour_worked, e.g. [{"date":"2026-01-09","hours":72}] or "2026-01-09: 72, 2026-01-23: 80". Periods not listed use the standard hours.
- `hours_worked_per_period`: Hours worked in each pay period, for per_hour_worked when it differs from the standard (40 h/week), e.g. 64.
- `max_balance`: Maximum balance (accrual stops at this cap until hours are used), in hours, e.g. 240, or "30 days".
- `pay_date`: Any real payday for weekly or biweekly pay, e.g. 2026-01-09, so accruals land on the right Fridays. Default: the first Friday on or after the ledger start.
- `pay_frequency`: Pay schedule: weekly, biweekly (default, every two weeks), semimonthly (15th and last day), or monthly.
- `reset_date`: When the accrual year resets (carryover is applied), e.g. "01-01" (default January 1), "July 1", or "anniversary" (hire anniversary), or "none".
- `starting_balance`: Known balance on starting_balance_date, in hours, e.g. 32.5 (from a pay stub), or "4 days".
- `starting_balance_date`: Date of the starting balance, e.g. 2026-01-01. Default: the start of the current accrual year (or the hire date if later).
- `state`: Optional US state, e.g. CA, for an informational note on state paid sick leave accrual rules.
- `tenure_tiers`: Tenure tiers (years of service), as text "0-2: 10 days, 3-5: 15 days, 6+: 20 days" or a list [{"from_year":0,"annual_days":10},{"from_year":3,"annual_days":15}]. "years 3-5" starts at the 3rd work an…
- `time_taken`: PTO used or planned, as a list [{"date":"2026-03-02","hours":8}] or text "2026-03-02 8h, 2026-07-06 to 2026-07-10, Dec 24 4h". Future dates count as planned time off in the projection.
- `waiting_period`: Waiting period after hire before PTO can be used, e.g. "90 days" or "3 months".
- `waiting_period_rule`: accrue_but_locked (default: hours accrue from hire but cannot be used until the waiting period ends) or no_accrual (nothing accrues during the waiting period).

Output parameters:

- `as_of` (string)
- `as_of_label` (string)
- `as_of_source` (string)
- `assumptions` (array)
- `available_hours` (number)
- `balance_days` (number)
- `balance_hours` (number)
- `downloads` (object)
- `employee` (string|null)
- `kind` (string)
- `ledger_preview` (array)
- `ledger_rows_total` (number)
- `ledger_start` (string)
- `notes` (array)
- `policy` (object)
- `projection` (object)
- `tier` (object)
- `upcoming` (array)
- `warnings` (array)
- `year_to_date` (object)

### `calculate_team_pto_balances` (~1353 tokens)

Calculate team PTO balances

Use this when an owner or HR person wants PTO balances for a team: one PTO, vacation or sick leave balance per employee from one accrual policy (accrual_amount + accrual_unit + accrual_per, e.g. 15, days, year) and a list of employees (typed, pasted CSV, or an attached CSV/Excel file with name, hire date, starting balance, hours used). Applies the same policy options as calculate_pto_balance (per hour worked, per pay period, annual front-loaded or accrued, tenure tiers, caps, carryover and reset, waiting period). Returns each person's balance, hours used this year, year-end projection and hours at risk at the reset, team totals, and PDF, Excel (with each person's ledger) and CSV files. Does not give legal advice, process payroll, or compute PTO payout in money. For one person's dated ledger use calculate_pto_balance.

Input parameters:

- `accrual_amount`: Preferred way to give the rule: the amount earned, e.g. 15 (with accrual_unit days, accrual_per year), 4.62 (hours per pay_period) or 0.0333 (hours per hour_worked).
- `accrual_method`: How PTO is earned: per_hour_worked (e.g. 1 h per 30 h worked), per_pay_period (fixed hours each paycheck, e.g. 4.62 h), annual_front_loaded (whole year granted at once on the reset date), annual_accr…
- `accrual_per`: How often accrual_amount is earned: year, month, week, pay_period, or hour_worked. Required for hours; days or weeks without it are read as per year.
- `accrual_rate`: Fallback only, when you cannot fill accrual_amount/accrual_unit/accrual_per: the rule as text with a number, unit and period, e.g. "1 per 30", "4.62 hours per paycheck", "15 days a year". Hours witho…
- `accrual_unit`: Unit of accrual_amount: hours (default), days, or weeks (weeks = days_per_week x hours_per_day).
- `annual_accrual_cap`: Most hours that can be earned in one accrual year, e.g. 48.
- `annual_days`: Days of PTO per year, e.g. 15. Converted with hours_per_day (default 8).
- `annual_hours`: Hours of PTO per year, e.g. 120. Use instead of annual_days.
- `as_of_date`: Date to report the balance on, e.g. 2026-10-26. Default: today in US Eastern time.
- `carryover_limit`: Hours that may roll over at the reset date, e.g. 40. 0 = use it or lose it. Leave out for unlimited rollover.
- `days_per_week`: Workdays per week, default 5. Converts weeks of PTO to hours.
- `employees`: The team: a list of employees, or CSV text with a header such as "name,hire_date,starting_balance,used_hours" and one row per person. Up to 500.
- `employees_file` (object): Optional CSV or Excel (.xlsx) file of employees with columns like name, hire date, starting balance, hours used, e.g. team-pto.csv.
- `first_year`: For annual_front_loaded: prorated (default, first grant prorated by days left in the year) or full.
- `hire_date`: Hire (start) date, e.g. 2024-03-04. Used for tenure tiers, the waiting period and the first partial pay period.
- `hours_per_day`: Hours in one PTO day, default 8, e.g. 7.5.
- `hours_per_week`: Standard hours per week, default 40, e.g. 30 for part time. Used when hours worked are not given.
- `hours_worked`: Actual hours worked per pay period for per_hour_worked, e.g. [{"date":"2026-01-09","hours":72}] or "2026-01-09: 72, 2026-01-23: 80". Periods not listed use the standard hours.
- `hours_worked_per_period`: Hours worked in each pay period, for per_hour_worked when it differs from the standard (40 h/week), e.g. 64.
- `max_balance`: Maximum balance (accrual stops at this cap until hours are used), in hours, e.g. 240, or "30 days".
- `pay_date`: Any real payday for weekly or biweekly pay, e.g. 2026-01-09, so accruals land on the right Fridays. Default: the first Friday on or after the ledger start.
- `pay_frequency`: Pay schedule: weekly, biweekly (default, every two weeks), semimonthly (15th and last day), or monthly.
- `reset_date`: When the accrual year resets (carryover is applied), e.g. "01-01" (default January 1), "July 1", or "anniversary" (hire anniversary), or "none".
- `starting_balance`: Known balance on starting_balance_date, in hours, e.g. 32.5 (from a pay stub), or "4 days".
- `starting_balance_date`: Date of the starting balance, e.g. 2026-01-01. Default: the start of the current accrual year (or the hire date if later).
- `tenure_tiers`: Tenure tiers (years of service), as text "0-2: 10 days, 3-5: 15 days, 6+: 20 days" or a list [{"from_year":0,"annual_days":10},{"from_year":3,"annual_days":15}]. "years 3-5" starts at the 3rd work an…
- `waiting_period`: Waiting period after hire before PTO can be used, e.g. "90 days" or "3 months".
- `waiting_period_rule`: accrue_but_locked (default: hours accrue from hire but cannot be used until the waiting period ends) or no_accrual (nothing accrues during the waiting period).

Output parameters:

- `as_of` (string)
- `as_of_label` (string)
- `as_of_source` (string)
- `assumptions` (array)
- `downloads` (object)
- `employees` (array)
- `employees_total` (number)
- `kind` (string)
- `notes` (array)
- `policy` (object)
- `projection_through` (string)
- `reset_date` (string|null)
- `source_file`
- `totals` (object)
- `warnings` (array)

## Diagnostics

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

## Score history

- 2026-11-21: 78
- 2026-11-20: 77
- 2026-11-19: 77
- 2026-11-18: 76
- 2026-11-17: 76
- 2026-11-16: 75
- 2026-11-15: 75
- 2026-11-14: 75
- 2026-11-13: 74
- 2026-11-12: 74
- 2026-11-11: 73
- 2026-11-10: 73
- 2026-11-09: 72
- 2026-11-08: 72

## Common questions

### What is the Zovo PTO Accrual Calculator MCP server?

Zovo PTO Accrual Calculator is an MCP server listed in the public MCP registry as io.github.theluckystrike/pto-accrual. PTO balance and accrual ledger. This page covers its hosted endpoint (https://pto-accrual.zovo.one/mcp).

### Is the Zovo PTO Accrual Calculator MCP server safe to use?

Zovo PTO Accrual Calculator scores 78 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 Zovo PTO Accrual Calculator MCP server expose?

Zovo PTO Accrual Calculator exposes 2 tools: calculate_pto_balance, calculate_team_pto_balances. Their descriptions and schemas cost roughly 2,893 tokens of context every time the server is loaded.

### Does the Zovo PTO Accrual Calculator MCP server require authentication?

No. We connected to Zovo PTO Accrual Calculator without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Zovo PTO Accrual Calculator MCP server still maintained?

Zovo PTO Accrual Calculator is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the Zovo PTO Accrual Calculator MCP server?

VerifyMCP ran 14 checks on Zovo PTO Accrual Calculator, covering TLS certificate, Authorization, HTTPS, HSTS header and 10 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://pto-accrual.zovo.one/mcp
- Website: https://pto-accrual.zovo.one/
- Changelog RSS feed: https://verifymcp.io/servers/theluckystrike-pto-accrual/pto-accrual.xml
- Changelog JSON feed: https://verifymcp.io/servers/theluckystrike-pto-accrual/pto-accrual/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/theluckystrike-pto-accrual/pto-accrual.json
- HTML version of this page: https://verifymcp.io/servers/theluckystrike-pto-accrual/pto-accrual
