# Zovo Meal Planner (remote · meal-planner.zovo.one)

Plan a week of meals and turn it into one grocery list grouped by store section.

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

## Components

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

## Channel facts

- Endpoint: `https://meal-planner.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 1446 tokens (~482/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 Meal Planner MCP server?

Zovo Meal Planner is a hosted endpoint at https://meal-planner.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-meal-planner 'https://meal-planner.zovo.one/mcp'
```

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

```yaml
mcp_servers:
  theluckystrike-meal-planner:
    url: "https://meal-planner.zovo.one/mcp"
```

### Netclaw

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

### Vellum

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

### Other

```json
{
  "mcpServers": {
    "theluckystrike-meal-planner": {
      "type": "http",
      "url": "https://meal-planner.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 (2)

### `generate_meal_plan` (~677 tokens)

Generate meal plan and grocery list

Use this when the user wants a weekly meal plan, a meal planner template filled in, or a grocery list from their meal plan or meal prep. First turn what the user pasted (a plan, recipe, spreadsheet or e-mail) into meals: one entry per day and slot with its name, recipe servings and ingredient lines, one meal per day for lines like "Mon-Fri lunch". Put the original text in plan only when you cannot do that. If you propose the meals, pass them the same way. The tool parses quantities and units, scales servings to the number of people, merges the same ingredient across the week (volume with volume, weight with weight, not volume to weight), groups the list by store section, removes items the user already has, and returns a PDF (week grid plus checklist), CSV and text. Does not give nutrition, calorie or diet advice and does not order groceries.

Input parameters:

- `already_have`: Items already in the kitchen to leave off the list, as a list or comma-separated text, e.g. ["salt", "olive oil", "rice"]. A section name such as "spices" removes that whole section.
- `meals`: Preferred. The week as structured meals you build from what the user pasted: one entry per meal and day, e.g. [{"day":"Monday","slot":"Dinner","name":"Tacos","servings":4,"ingredients":["1 lb ground…
- `page_size` (string|null): PDF paper: "letter" (default) or "a4".
- `people` (number|string|null): Servings to cook for each meal, e.g. 4 or "4 people". Each meal with a recipe yield (servings) is scaled to this number; meals without a yield are used as written. Default: no scaling.
- `plan`: Fallback when you cannot build meals: the week as the user wrote it. Easiest: a list of meals, e.g. [{"day":"Monday","meal":"Dinner","name":"Chicken stir fry","servings":4,"ingredients":["1 lb chicke…
- `title` (string|null): Title printed on the PDF, e.g. "Family dinners". Default "Weekly meal plan" or "Grocery list". Longer than 80 characters is shortened.
- `units` (string|null): How to show merged amounts: "us" (cups, tbsp, oz, lb), "metric" (ml, l, g, kg) or "auto" (default: the system most lines use). Volume is never converted to weight.
- `week_of` (string|null): Optional label for the week, e.g. "Nov 2, 2026". Printed as given; longer than 40 characters is shortened.

Output parameters:

- `already_have_removed` (array)
- `days` (array)
- `downloads` (object)
- `items_count` (number)
- `meals` (array)
- `meals_count` (number)
- `notes` (array)
- `people` (number|null)
- `sections` (array)
- `title` (string)
- `units` (string)
- `unparsed_lines` (array)

### `generate_grocery_list` (~635 tokens)

Generate grocery list from recipes

Use this when the user wants one combined grocery list or shopping list from several recipes or a pasted list of ingredients, without a weekly grid. First turn what the user pasted (a list, recipe, store order, receipt or e-mail) into items with name, quantity and unit, plus meal and servings for recipe lines; leave out prices, totals, headers and e-mail text. Put the original text in recipes only when you cannot do that. Merges the same ingredient with unit conversion inside one dimension, scales servings, groups by store section, leaves off items the user already has, and keeps unreadable lines as written. Returns a printable checklist PDF, CSV and text. Does not give nutrition or diet advice.

Input parameters:

- `already_have`: Items already in the kitchen to leave off the list, as a list or comma-separated text, e.g. ["salt", "olive oil", "rice"]. A section name such as "spices" removes that whole section.
- `items`: Preferred for a pasted list, order, receipt or e-mail: one entry per ingredient with the amount you read, e.g. [{"name":"eggs","quantity":24},{"name":"whole milk","quantity":1,"unit":"gallon"},{"name…
- `page_size` (string|null): PDF paper: "letter" (default) or "a4".
- `people` (number|string|null): Servings to cook for each meal, e.g. 4 or "4 people". Each meal with a recipe yield (servings) is scaled to this number; meals without a yield are used as written. Default: no scaling.
- `recipes`: Fallback, or recipes with their servings. Recipes or ingredient lines, e.g. [{"name":"Tacos","servings":4,"ingredients":["1 lb ground beef","8 corn tortillas","1 cup shredded cheddar"]},{"name":"Guac…
- `title` (string|null): Title printed on the PDF, e.g. "Family dinners". Default "Weekly meal plan" or "Grocery list". Longer than 80 characters is shortened.
- `units` (string|null): How to show merged amounts: "us" (cups, tbsp, oz, lb), "metric" (ml, l, g, kg) or "auto" (default: the system most lines use). Volume is never converted to weight.
- `week_of` (string|null): Optional label for the week, e.g. "Nov 2, 2026". Printed as given; longer than 40 characters is shortened.

Output parameters:

- `already_have_removed` (array)
- `days` (array)
- `downloads` (object)
- `items_count` (number)
- `meals` (array)
- `meals_count` (number)
- `notes` (array)
- `people` (number|null)
- `sections` (array)
- `title` (string)
- `units` (string)
- `unparsed_lines` (array)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/theluckystrike-meal-planner/meal-planner#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 Meal Planner MCP server?

Zovo Meal Planner is an MCP server listed in the public MCP registry as io.github.theluckystrike/meal-planner. Plan a week of meals and turn it into one grocery list grouped by store section. This page covers its hosted endpoint (https://meal-planner.zovo.one/mcp).

### Is the Zovo Meal Planner MCP server safe to use?

Zovo Meal Planner 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 Meal Planner MCP server expose?

Zovo Meal Planner exposes 2 tools: generate_meal_plan, generate_grocery_list. Their descriptions and schemas cost roughly 1,312 tokens of context every time the server is loaded.

### Does the Zovo Meal Planner MCP server require authentication?

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

### Is the Zovo Meal Planner MCP server still maintained?

Zovo Meal Planner 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 Meal Planner MCP server?

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