# Zovo Bill Calendar (remote · bill-calendar.zovo.one)

Make a bill payment calendar from your list of bills: a printable monthly bill calendar.

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

## Components

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

## Channel facts

- Endpoint: `https://bill-calendar.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**: 68/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 899 tokens (~449/item across 2 items; 1 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 1 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 3 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 Bill Calendar MCP server?

Zovo Bill Calendar is a hosted endpoint at https://bill-calendar.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-bill-calendar 'https://bill-calendar.zovo.one/mcp'
```

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

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

### Netclaw

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

### Vellum

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

### Other

```json
{
  "mcpServers": {
    "theluckystrike-bill-calendar": {
      "type": "http",
      "url": "https://bill-calendar.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-20 (score 78, +1)

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

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

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

### 2026-11-16 (score 76, +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-13 (score 75, +1)

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

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

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

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

- [functional improvement] Stability: unverified → 0.03

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

First indexed and scored.

## MCP tools (1)

### `generate_bill_calendar` (~743 tokens)

Generate bill calendar

Use this when the user wants a bill payment calendar, a bill tracker printable, a monthly bill calendar, bill reminders, or to know which paycheck pays which bill. Put each bill into bills (name, amount, due_day or due_date, frequency, autopay) and pay into paychecks (amount, frequency, first_date); convert a pasted list or a screenshot into those fields, and use bills_text only as a fallback. Returns a printable calendar PDF for 1 to 12 months with bills on their due days and month totals, an ICS file with one reminder per bill (2 days before by default), and an Excel plan that assigns each bill to the last paycheck on or before its due date with the money left. Bills due on the 29th to 31st move to the last day of shorter months; weekend_rule can move weekend due dates. Does not pay bills, connect to banks, or know bank holidays.

Input parameters:

- `bills`: The bills as objects: [{"name":"Rent","amount":1500,"due_day":1},{"name":"Phone","amount":65,"due_day":31,"autopay":true},{"name":"Car insurance","amount":420,"frequency":"quarterly","due_date":"2026…
- `bills_text` (string|null): Fallback only: bills pasted as text, one per line, e.g. "Rent 1500 on the 1st\nPhone 65 on the 31st autopay". Prefer bills.
- `currency` (string|null): Optional currency, e.g. "USD", "GBP", "€". Default: from the amounts, else no symbol.
- `date_order` (string|null): Optional order for dates like 03/04/2026: "mdy" (US, default) or "dmy".
- `include_paydays` (boolean|string|null): Add paydays to the ICS file as events without alarms. Default true.
- `months` (number|string|null): How many months, 1 to 12. Default 3.
- `page_size` (string|null): "Letter" (default) or "A4", printed landscape.
- `paychecks`: Optional paychecks: [{"amount":2100,"frequency":"biweekly","first_date":"2026-11-06"}]. With paychecks the plan shows which paycheck pays which bill and the money left.
- `reminder_days_before` (number|string|null): Days before the due date for the calendar reminder, 0 to 30. Default 2.
- `reminder_time` (string|null): Time of day for the reminder, e.g. "09:00" (default) or "8am".
- `start_month` (string|null): First month, e.g. "2026-11" or "November 2026". Default: this month.
- `starting_balance` (number|string|null): Optional money in the account before the first paycheck in the plan, e.g. 600 (negative such as -200 when overdrawn). Pays the bills that fall before the first paycheck and shows the lowest point.
- `title` (string|null): Optional title printed on each page, e.g. "Household bills".
- `week_start` (string|null): "Sunday" (default) or "Monday".
- `weekend_rule` (string|null): Optional: "previous_business_day" moves a Saturday or Sunday due date to the Friday before; "next_business_day" to the Monday after. Default: "none".

Output parameters:

- `assumptions` (array)
- `currency` (string|null)
- `downloads` (object)
- `lowest_point`
- `months` (array)
- `months_count` (number)
- `occurrences` (number)
- `paychecks` (array)
- `paychecks_shown` (object)
- `period` (object)
- `reminder` (object)
- `short_month_notes` (array)
- `title` (string)
- `total_bills` (string)
- `total_formatted` (string)
- `upcoming` (array)
- `upcoming_shown` (object)
- `warnings` (array)
- `weekend_moves` (number)
- `weekend_rule` (string)

## Diagnostics

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

## Score history

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

## Common questions

### What is the Zovo Bill Calendar MCP server?

Zovo Bill Calendar is an MCP server listed in the public MCP registry as io.github.theluckystrike/bill-calendar. Make a bill payment calendar from your list of bills: a printable monthly bill calendar. This page covers its hosted endpoint (https://bill-calendar.zovo.one/mcp).

### Is the Zovo Bill Calendar MCP server safe to use?

Zovo Bill Calendar 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 Bill Calendar MCP server expose?

Zovo Bill Calendar exposes 1 tool: generate_bill_calendar. Their descriptions and schemas cost roughly 743 tokens of context every time the server is loaded.

### Does the Zovo Bill Calendar MCP server require authentication?

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

### Is the Zovo Bill Calendar MCP server still maintained?

Zovo Bill Calendar 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 Bill Calendar MCP server?

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