# Parsley MCP by usefulapi (remote · parsley.usefulapi.io)

Read Parsley menu items, nutrition, allergens, ingredients and events; record event sales and waste.

- Trust score: 62/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-25

## Components

- remote · `parsley.usefulapi.io`: 62/100 (this document), [markdown](https://verifymcp.io/servers/io-usefulapi-parsley/parsley.md), [page](https://verifymcp.io/servers/io-usefulapi-parsley/parsley)

## Channel facts

- Endpoint: `https://parsley.usefulapi.io/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `1.0.3`

## 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-10-25.

- **Endpoint Security**: 78/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
  - The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents.
- **Transport & Reachability**: 0/100
  - Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly.
- **Schema Quality & AI Usability**: 82/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 2033 tokens (~135/item across 15 items; 15 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 99/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 96% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 15 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 16 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

**Unverified: 1 category.** A category scored 0 because we could not verify it: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

## Install

### How do I install the Parsley MCP by usefulapi server?

Parsley MCP by usefulapi is a hosted endpoint at https://parsley.usefulapi.io/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 io-usefulapi-parsley 'https://parsley.usefulapi.io/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "io-usefulapi-parsley": {
      "url": "https://parsley.usefulapi.io/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "io-usefulapi-parsley": {
      "type": "http",
      "url": "https://parsley.usefulapi.io/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.io-usefulapi-parsley]
url = "https://parsley.usefulapi.io/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-usefulapi-parsley": {
      "type": "remote",
      "url": "https://parsley.usefulapi.io/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add io-usefulapi-parsley --url 'https://parsley.usefulapi.io/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  io-usefulapi-parsley:
    url: "https://parsley.usefulapi.io/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "io-usefulapi-parsley": {
      "Transport": "http",
      "Url": "https://parsley.usefulapi.io/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add io-usefulapi-parsley -t streamable-http -u 'https://parsley.usefulapi.io/mcp'
```

### Other

```json
{
  "mcpServers": {
    "io-usefulapi-parsley": {
      "type": "http",
      "url": "https://parsley.usefulapi.io/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-10-25 (score 62)

First indexed and scored.

## MCP tools (15)

### `parsley_list_menu_items` (~185 tokens)

List menu items

List the recipes, sub-recipes and ingredients in the Parsley account that can be used on events: id, name, item number, price, tags, active flag, chef and last-modified time. Use the ids with parsley_get_menu_item for nutrition, allergens and ingredients, and on events. The API returns the whole list at once; search/limit/offset slice it here. GET /menu_items.

Input parameters:

- `limit` (integer): Results to return, 1-500 (default 100).
- `offset` (integer): Skip this many results (default 0). Pass the previous reply's next_offset.
- `search` (string): Only menu items whose name contains this text (case-insensitive).
- `tag` (string): Only items carrying this tag (exact, case-insensitive).
- `type` (string): Only this kind of item.

### `parsley_get_menu_item` (~100 tokens)

Get menu item (nutrition, allergens, ingredients)

One menu item in full: names, description, price, cost, shelf life, serving size, nutrition facts (nutrients), the allergen flags and allergen text, dietary characteristics (meat, pork, corn, poultry) and the ingredient list. The photo link is returned without its access token. GET /menu_items/{id}.

Input parameters:

- `menu_item_id` (integer, required): Parsley menu item id (from parsley_list_menu_items).

### `parsley_list_menus` (~107 tokens)

List menus

List the menus (menu plans) in the account: id, name and last-modified time. Use the id with parsley_get_menu or when creating an event. GET /menus.

Input parameters:

- `limit` (integer): Results to return, 1-500 (default 100).
- `offset` (integer): Skip this many results (default 0). Pass the previous reply's next_offset.
- `search` (string): Only menus whose name contains this text (case-insensitive).

### `parsley_get_menu` (~51 tokens)

Get menu

One menu with its sections and the menu items in each section, and its serving stations. GET /menus/{id}.

Input parameters:

- `menu_id` (integer, required): Parsley menu id (from parsley_list_menus).

### `parsley_list_ingredients` (~148 tokens)

List ingredients

List the ingredients that can be used in recipes: id, parent id, name, label name, item number, supported units, and whether a recipe uses it. The API returns the whole list at once; search/limit/offset slice it here. GET /ingredients.

Input parameters:

- `limit` (integer): Results to return, 1-500 (default 100).
- `offset` (integer): Skip this many results (default 0). Pass the previous reply's next_offset.
- `search` (string): Only ingredients whose name contains this text (case-insensitive).
- `used_by_recipe` (boolean): true: only ingredients used by a recipe; false: only unused ones.

### `parsley_get_ingredient` (~91 tokens)

Get ingredient (costing and suppliers)

One ingredient in full: unit conversions, supported units, tags, the supply options (supplier, SKU, pack size, cost) used for costing and the preparations with yield. Parsley limits this call to 1 request every 3 seconds, so fetch ingredients one at a time. GET /ingredients/{id}.

Input parameters:

- `ingredient_id` (integer, required): Parsley ingredient id (from parsley_list_ingredients).

### `parsley_list_events` (~205 tokens)

List events

List events (a workday, shift, service or catering event) that fall in a date window: id, name, type (standard, cafe-hot-bar, sale, forecast), date, start and end time, menu id. A bare date means the whole day in the account timezone. GET /events.

Input parameters:

- `end` (string, required): Window end (inclusive): yyyy-mm-dd (to the end of that day) or an ISO 8601 date-time.
- `limit` (integer): Results to return, 1-500 (default 100).
- `offset` (integer): Skip this many results (default 0). Pass the previous reply's next_offset.
- `search` (string): Only events whose name contains this text (case-insensitive).
- `start` (string, required): Window start (inclusive): yyyy-mm-dd or an ISO 8601 date-time. Without a timezone the account timezone applies.
- `type` (string): Only this event type.

### `parsley_get_event` (~53 tokens)

Get event

One event with its metadata and all line items (menu item, amount, unit, station, section). GET /events/{id}.

Input parameters:

- `event_id` (integer, required): Parsley event id (from parsley_list_events).

### `parsley_list_serving_stations` (~84 tokens)

List serving stations

List the serving stations (id, name) that menu items and event line items can be assigned to. GET /tags/serving_stations.

Input parameters:

- `limit` (integer): Results to return, 1-500 (default 100).
- `offset` (integer): Skip this many results (default 0). Pass the previous reply's next_offset.

### `parsley_list_chef_tags` (~84 tokens)

List chef tags

List the chef tags (id, name) that recipes are attributed to. Only meaningful for accounts with Chef IDs enabled. GET /tags/chefs.

Input parameters:

- `limit` (integer): Results to return, 1-500 (default 100).
- `offset` (integer): Skip this many results (default 0). Pass the previous reply's next_offset.

### `parsley_list_chef_users` (~125 tokens)

List chef users

List the chef users of the account: id, email, join date, active flag, permission level and the chef tag they are tied to. Only meaningful for accounts with Chef IDs enabled. GET /users/chefs.

Input parameters:

- `limit` (integer): Results to return, 1-500 (default 100).
- `offset` (integer): Skip this many results (default 0). Pass the previous reply's next_offset.
- `search` (string): Only chef users (matched on email or chef name) whose name contains this text (case-insensitive).

### `parsley_create_event` (~219 tokens)

Create event

WRITE: create an event (a workday, shift, service or catering event) in Parsley with its menu items. This changes the account's production plan and is NOT idempotent: calling it twice creates two events. Returns the new event id. Use parsley_list_events first to avoid duplicates. POST /events.

Input parameters:

- `date` (string, required): The day of the event, yyyy-mm-dd.
- `description` (string)
- `end_time` (string): Time of day, HH:mm (24 hour).
- `line_items` (array, required): The menu items and amounts to produce or sell (may be empty).
- `menu_id` (integer): Parsley menu id the event uses (from parsley_list_menus).
- `name` (string, required): Event name, e.g. 'Brunch'.
- `private` (boolean): Mark the event private.
- `start_time` (string): Time of day, HH:mm (24 hour).
- `type` (string, required): Event type: standard, cafe-hot-bar, sale or forecast.

### `parsley_update_event_covers` (~113 tokens)

Update event covers

WRITE: set the forecast and/or actual number of covers (guests served) on an event. Only the fields you pass change. actual_covers works only on cafe/hot bar events. Setting the same values again has no further effect. PATCH /events/{id}.

Input parameters:

- `actual_covers` (integer): Real number of covers (cafe/hot bar events only).
- `event_id` (integer, required): Parsley event id.
- `forecast_covers` (integer): Predicted number of covers.

### `parsley_record_event_sales` (~107 tokens)

Record event sales

WRITE: push sold quantities per menu item to a cafe/hot bar event, which feeds Parsley's cost and usage reports. Other event types are refused by Parsley, as is a menu item with no made quantity on the event. Sending the same quantities again overwrites rather than adds. PUT /events/{id}/sales.

Input parameters:

- `event_id` (integer, required): Parsley event id of a cafe/hot bar event.
- `sales` (array, required): Sold amount per menu item.

### `parsley_record_waste_leftover` (~107 tokens)

Record waste and leftover

WRITE: push waste and/or leftover quantities per menu item to a cafe/hot bar event. If no sold quantity exists, Parsley derives it as made minus waste minus leftover. Parsley refuses amounts above what was made minus sold. Sending the same quantities again overwrites rather than adds. PUT /events/{id}/waste_leftover.

Input parameters:

- `event_id` (integer, required): Parsley event id of a cafe/hot bar event.
- `items` (array, required)

## Diagnostics

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

## Score history

- 2026-10-25: 62

## Common questions

### What is the Parsley MCP by usefulapi server?

Parsley MCP by usefulapi is listed in the public MCP registry as io.usefulapi/parsley. Read Parsley menu items, nutrition, allergens, ingredients and events; record event sales and waste. This page covers its hosted endpoint (https://parsley.usefulapi.io/mcp).

### Is the Parsley MCP by usefulapi server safe to use?

Parsley MCP by usefulapi scores 62 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 Parsley MCP by usefulapi server expose?

Parsley MCP by usefulapi exposes 15 tools: parsley_list_menu_items, parsley_get_menu_item, parsley_list_menus, parsley_get_menu, parsley_list_ingredients, and 10 more. Their descriptions and schemas cost roughly 1,779 tokens of context every time the server is loaded.

### Does the Parsley MCP by usefulapi server require authentication?

Yes. Parsley MCP by usefulapi 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 Parsley MCP by usefulapi server still maintained?

Parsley MCP by usefulapi is still listed as active in the MCP registry. We last reached this channel on 25 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://parsley.usefulapi.io/mcp
- Repository: https://github.com/m190/usefulapi-mcp
- Website: https://usefulapi.io/parsley/
- Changelog RSS feed: https://verifymcp.io/servers/io-usefulapi-parsley/parsley.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-usefulapi-parsley/parsley.json
- HTML version of this page: https://verifymcp.io/servers/io-usefulapi-parsley/parsley