# Zovo Chore Chart (remote · chore-chart.zovo.one)

Make a printable chore chart and a fair chore rotation schedule for kids, a family or roommates.

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

## Components

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

## Channel facts

- Endpoint: `https://chore-chart.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**: 71/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 880 tokens (~293/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 Chore Chart MCP server?

Zovo Chore Chart is a hosted endpoint at https://chore-chart.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-chore-chart 'https://chore-chart.zovo.one/mcp'
```

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

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

### Netclaw

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

### Vellum

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

### Other

```json
{
  "mcpServers": {
    "theluckystrike-chore-chart": {
      "type": "http",
      "url": "https://chore-chart.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 79, +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 78, +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-16 (score 77, +1)

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

### 2026-11-14 (score 76, +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 75, +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 74, +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 73, 0)

- [functional improvement] Stability: unverified → 0.03

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

First indexed and scored.

## MCP tools (2)

### `generate_chore_chart` (~570 tokens)

Generate chore chart

Use this when the user wants a chore chart, chore chart for kids, roommate chore schedule, chore rotation or reward chart: a fair weekly rotation of chores between people (as even weekly points as possible, chores moving between people each week, rules like "Sam cannot do dishes" and minimum ages respected), with points per person and the spread, a printable PDF (one week per page, standard or kids style with a star/sticker column) and an .ics file with one weekly summary per person. Does not split one chore between people on different days, does not track completion, and does not send reminders.

Input parameters:

- `age_appropriate` (string|number|boolean|null): yes to apply default minimum ages to chores without one (mowing and cooking 12+, bathroom and laundry 8+, dishes, vacuum and trash 6+); needs ages in people. Default no.
- `chores` (required): The chores, one per line or comma separated, with optional frequency (daily, weekly, weekdays, Mon Thu, twice a week), points or difficulty (2 points, easy/medium/hard), everyone, and a minimum age (…
- `layout` (string|number|boolean|null): people (default: a row per person with their chores each day) or chores (a row per chore with the assigned person), e.g. chores.
- `paper` (string|number|boolean|null): letter (default) or A4, e.g. A4.
- `people` (required): Who shares the chores, with optional ages, e.g. "Sam (9), Mia (6), Leo (12)" or ["Ana","Ben","Chris"] or [{"name":"Sam","age":9}].
- `rules`: Optional rules, e.g. "Sam cannot do dishes", "no mowing for Mia", "Leo: no laundry".
- `start_date` (string|number|boolean|null): First day of week 1, e.g. 2026-11-02 or Nov 2. Default: the coming Monday. The chart's weeks start on this weekday.
- `style` (string|number|boolean|null): standard (default) or kids (larger boxes and a star/sticker column), e.g. kids.
- `title`: Heading on the chart, e.g. Family chore chart. Default: Chore chart.
- `weeks` (string|number|boolean|null): How many weeks to plan, 1 to 12, e.g. 4 (default 4).

Output parameters:

- `assumptions` (array)
- `chores` (array)
- `downloads` (object)
- `fairness` (object)
- `kind` (string)
- `layout` (string)
- `paper` (string)
- `people` (array)
- `rules_applied` (array)
- `style` (string)
- `summary` (string)
- `title` (string)
- `warnings` (array)
- `weeks` (array)

### `generate_habit_tracker` (~232 tokens)

Generate habit tracker

Use this when the user wants a habit tracker printable: a one-page grid of habits x days of a month with checkboxes (or stars in kids style), optional goal per habit, as a PDF. Does not track progress, send reminders or analyse habits.

Input parameters:

- `habits` (required): The habits to track, one per line or comma separated, optional goal in brackets, e.g. "Drink water (8 glasses)\nRead 20 minutes\nNo phone after 10pm" or ["Exercise","Journal"].
- `month` (string|number|boolean|null): Month to print, e.g. November 2026, 2026-11, Nov, or next month. Default: the current month (New York date).
- `paper` (string|number|boolean|null): letter (default) or A4, e.g. A4.
- `style` (string|number|boolean|null): standard (default, checkboxes) or kids (stars to colour in), e.g. kids.
- `title`: Heading, e.g. My November habits. Default: Habit tracker.

Output parameters:

- `assumptions` (array)
- `days` (number)
- `downloads` (object)
- `first_weekday` (string)
- `habits` (array)
- `kind` (string)
- `month` (string)
- `paper` (string)
- `style` (string)
- `summary` (string)
- `title` (string)

## Diagnostics

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

## Score history

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

## Common questions

### What is the Zovo Chore Chart MCP server?

Zovo Chore Chart is an MCP server listed in the public MCP registry as io.github.theluckystrike/chore-chart. Make a printable chore chart and a fair chore rotation schedule for kids, a family or roommates. This page covers its hosted endpoint (https://chore-chart.zovo.one/mcp).

### Is the Zovo Chore Chart MCP server safe to use?

Zovo Chore Chart 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 Zovo Chore Chart MCP server expose?

Zovo Chore Chart exposes 2 tools: generate_chore_chart, generate_habit_tracker. Their descriptions and schemas cost roughly 802 tokens of context every time the server is loaded.

### Does the Zovo Chore Chart MCP server require authentication?

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

### Is the Zovo Chore Chart MCP server still maintained?

Zovo Chore Chart 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 Chore Chart MCP server?

VerifyMCP ran 14 checks on Zovo Chore Chart, 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://chore-chart.zovo.one/mcp
- Website: https://chore-chart.zovo.one/
- Changelog RSS feed: https://verifymcp.io/servers/theluckystrike-chore-chart/chore-chart.xml
- Changelog JSON feed: https://verifymcp.io/servers/theluckystrike-chore-chart/chore-chart/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/theluckystrike-chore-chart/chore-chart.json
- HTML version of this page: https://verifymcp.io/servers/theluckystrike-chore-chart/chore-chart
