# ChowDeck MCP by Nova (CIVAI) (remote · nova.civai.co)

Order food on ChowDeck: browse restaurants, set your delivery address, build a cart, and check out…

- Trust score: 76/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `nova.civai.co`: 76/100 (this document), [markdown](https://verifymcp.io/servers/co-civai-nova-mcp-bgpt-chowdeck/mcp-agents-mcp-bgpt-chowdeck.md), [page](https://verifymcp.io/servers/co-civai-nova-mcp-bgpt-chowdeck/mcp-agents-mcp-bgpt-chowdeck)

## Channel facts

- Endpoint: `https://nova.civai.co/mcp/agents/mcp-bgpt-chowdeck`
- Transports: `streamable-http`
- Auth: `required (not validated)`
- 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-05.

- **Endpoint Security**: 83/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - 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**: 80/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).
  - Tool/resource definitions use about 2455 tokens (~90/item across 27 items; 24 tools + 3 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 10/100
  - Stability observed for 3 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.
- **Tool Safety**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 0 of 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "request_login_otp" implies "send" and declares no destructiveHint at all, which the MCP spec reads as destructive by default.
  - An AI judge read all 25 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.

## Install

### How do I install the ChowDeck MCP by Nova (CIVAI) server?

ChowDeck MCP by Nova (CIVAI) is a hosted endpoint at https://nova.civai.co/mcp/agents/mcp-bgpt-chowdeck, 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 co-civai-nova-mcp-bgpt-chowdeck 'https://nova.civai.co/mcp/agents/mcp-bgpt-chowdeck'
```

### Cursor

```json
{
  "mcpServers": {
    "co-civai-nova-mcp-bgpt-chowdeck": {
      "url": "https://nova.civai.co/mcp/agents/mcp-bgpt-chowdeck"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "co-civai-nova-mcp-bgpt-chowdeck": {
      "type": "http",
      "url": "https://nova.civai.co/mcp/agents/mcp-bgpt-chowdeck"
    }
  }
}
```

### Codex

```toml
[mcp_servers.co-civai-nova-mcp-bgpt-chowdeck]
url = "https://nova.civai.co/mcp/agents/mcp-bgpt-chowdeck"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "co-civai-nova-mcp-bgpt-chowdeck": {
      "type": "remote",
      "url": "https://nova.civai.co/mcp/agents/mcp-bgpt-chowdeck",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add co-civai-nova-mcp-bgpt-chowdeck --url 'https://nova.civai.co/mcp/agents/mcp-bgpt-chowdeck' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  co-civai-nova-mcp-bgpt-chowdeck:
    url: "https://nova.civai.co/mcp/agents/mcp-bgpt-chowdeck"
```

### Netclaw

```json
{
  "McpServers": {
    "co-civai-nova-mcp-bgpt-chowdeck": {
      "Transport": "http",
      "Url": "https://nova.civai.co/mcp/agents/mcp-bgpt-chowdeck"
    }
  }
}
```

### Vellum

```bash
assistant mcp add co-civai-nova-mcp-bgpt-chowdeck -t streamable-http -u 'https://nova.civai.co/mcp/agents/mcp-bgpt-chowdeck'
```

### Other

```json
{
  "mcpServers": {
    "co-civai-nova-mcp-bgpt-chowdeck": {
      "type": "http",
      "url": "https://nova.civai.co/mcp/agents/mcp-bgpt-chowdeck"
    }
  }
}
```

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-05 (score 76, +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-03 (score 75, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-02 (score 74)

First indexed and scored.

## MCP tools (24)

### `request_login_otp` (~135 tokens)

Send ChowDeck login SMS (validate phone → auth/login). Does not accept OTP. Ask the user for their phone first, then for the SMS code, then call verify_login_otp.

Input parameters:

- `notification_message` (string): Short user-facing sentence for this action if the follow-up reply fails. Plain text only; do not mention template syntax or variable names.
- `step_2_body_country_code` (string): Country code (e.g. NG)
- `step_2_body_phone` (string, required): User-provided phone without country prefix (local NG format like 080…). Never invent or reuse another account's number.

### `verify_login_otp` (~125 tokens)

Complete ChowDeck login with SMS code (validate phone → validate OTP → refresh token). Does not send a new SMS.

Input parameters:

- `notification_message` (string): Short user-facing sentence for this action if the follow-up reply fails. Plain text only; do not mention template syntax or variable names.
- `step_2_body_country_code` (string): Country code (e.g. NG)
- `step_2_body_phone` (string, required): Same phone used in request_login_otp
- `step_5_body_otp` (string, required): SMS one-time code from the user

### `fetch_customer_settings` (~55 tokens)

Public customer app config (no auth). Good session probe.

Input parameters:

- `notification_message` (string): Short user-facing sentence for this action if the follow-up reply fails. Plain text only; do not mention template syntax or variable names.

### `view_cart` (~47 tokens)

View current cart contents.

Input parameters:

- `notification_message` (string): Short user-facing sentence for this action if the follow-up reply fails. Plain text only; do not mention template syntax or variable names.

### `get_addresses` (~48 tokens)

Run the get_addresses pipeline.

Input parameters:

- `notification_message` (string): Short user-facing sentence for this action if the follow-up reply fails. Plain text only; do not mention template syntax or variable names.

### `get_payment_methods` (~50 tokens)

Run the get_payment_methods pipeline.

Input parameters:

- `notification_message` (string): Short user-facing sentence for this action if the follow-up reply fails. Plain text only; do not mention template syntax or variable names.

### `list_orders_success` (~50 tokens)

Run the list_orders_success pipeline.

Input parameters:

- `notification_message` (string): Short user-facing sentence for this action if the follow-up reply fails. Plain text only; do not mention template syntax or variable names.

### `get_order_details` (~50 tokens)

Run the get_order_details pipeline.

Input parameters:

- `notification_message` (string): Short user-facing sentence for this action if the follow-up reply fails. Plain text only; do not mention template syntax or variable names.

### `get_customer_survey` (~52 tokens)

Run the get_customer_survey pipeline.

Input parameters:

- `notification_message` (string): Short user-facing sentence for this action if the follow-up reply fails. Plain text only; do not mention template syntax or variable names.

### `set_active_address_and_fetch_menu` (~122 tokens)

Set active delivery address and fetch chowsmart menu for that address.

Input parameters:

- `notification_message` (string): Short user-facing sentence for this action if the follow-up reply fails. Plain text only; do not mention template syntax or variable names.
- `step_37_body_addressId` (string): Same address id (duplicate field in API body)
- `step_37_body_address_id` (string, required): Address id to set as active (from get_addresses)
- `step_38_url_query_address_id` (string, required): Same address id for menu fetch

### `get_featured_vendors` (~131 tokens)

Featured and tagged vendors near a delivery address.

Input parameters:

- `notification_message` (string): Short user-facing sentence for this action if the follow-up reply fails. Plain text only; do not mention template syntax or variable names.
- `step_40_page` (integer): Page number for featured vendors (default 1). Use when user asks for more vendors or next page.
- `step_40_page_size` (integer): Vendors per page (default 25, max 100)
- `step_40_url_query_address_id` (string, required): Active delivery address id (from get_addresses or set_active_address)

### `get_chowpass_status` (~54 tokens)

Run the get_chowpass_status pipeline.

Input parameters:

- `notification_message` (string): Short user-facing sentence for this action if the follow-up reply fails. Plain text only; do not mention template syntax or variable names.

### `search_menu_by_address` (~52 tokens)

Run the search_menu_by_address pipeline.

Input parameters:

- `notification_message` (string): Short user-facing sentence for this action if the follow-up reply fails. Plain text only; do not mention template syntax or variable names.

### `search_product` (~139 tokens)

Search vendors/products by name near a delivery address. Each data[] entry: id = vendor id; products[].id = menu item id when present. If products[] empty, call view_vendor_items next.

Input parameters:

- `notification_message` (string): Short user-facing sentence for this action if the follow-up reply fails. Plain text only; do not mention template syntax or variable names.
- `step_52_url_query_address_id` (string, required): Delivery address id from get_addresses — never ask user to type the number.
- `step_52_url_query_query` (string, required): Product search term (e.g. jollof, omeprazole, Daytona)

### `get_country_list` (~50 tokens)

Run the get_country_list pipeline.

Input parameters:

- `notification_message` (string): Short user-facing sentence for this action if the follow-up reply fails. Plain text only; do not mention template syntax or variable names.

### `view_vendor_cart` (~84 tokens)

View cart for one vendor (vendor-specific checkout view).

Input parameters:

- `notification_message` (string): Short user-facing sentence for this action if the follow-up reply fails. Plain text only; do not mention template syntax or variable names.
- `step_60_url_path_3` (string, required): Vendor id (from search_product, view_cart data[].vendor_id, or featured vendors)

### `remove_cart_item` (~277 tokens)

Remove one line item (pack) from a vendor cart. POST /customer/cart/vendor/{vendor_id} with quantity 0. Run view_vendor_cart first — pass menu line ids from data.cart_items[] (type menu). Side-effect.

Input parameters:

- `notification_message` (string): Short user-facing sentence for this action if the follow-up reply fails. Plain text only; do not mention template syntax or variable names.
- `step_118_body_address_id` (string, required): Delivery address id from view_vendor_cart → data.address_id
- `step_118_body_class` (string): Order class from cart — usually delivery
- `step_118_body_items_0_cart_item_id` (string, required): Cart line id from view_vendor_cart → data.cart_items[].id
- `step_118_body_items_0_item_id` (string, required): Menu item id from view_vendor_cart → data.cart_items[].item_id (type menu line)
- `step_118_body_items_0_pack_reference` (string, required): Pack UUID from view_vendor_cart → data.cart_items[].pack_reference
- `step_56_url_path_3` (string, required): Vendor id (view_vendor_cart → data.vendor_id or same vendor as cart)
- `step_7_body_data_0_cart_items_0_type` (string): Must be menu for food lines (default menu)

### `duplicate_cart_pack` (~133 tokens)

Increase quantity by duplicating one pack (configured line item). POST /customer/cart/{cart_id}/pack/{pack_reference}/duplicate. Run view_vendor_cart first. Side-effect.

Input parameters:

- `notification_message` (string): Short user-facing sentence for this action if the follow-up reply fails. Plain text only; do not mention template syntax or variable names.
- `step_66_url_path_2` (string, required): Cart id from view_vendor_cart → data.id
- `step_66_url_path_4` (string, required): Pack reference UUID from view_vendor_cart → data.cart_items[].pack_reference for the line to duplicate

### `clear_vendor_cart` (~128 tokens)

Delete/clear the entire cart for one vendor (all items). Requires cart id from view_vendor_cart response data.id — not vendor id. Side-effect: use when user wants to empty cart or before re-adding after 'Active cart already exists'.

Input parameters:

- `notification_message` (string): Short user-facing sentence for this action if the follow-up reply fails. Plain text only; do not mention template syntax or variable names.
- `step_176_url_path_2` (string, required): Cart id to delete (view_vendor_cart → data.id, or view_cart → data[].id for matching vendor)

### `view_vendor_items` (~104 tokens)

Load a vendor menu. Pass vendor id from search_product data[].id as step_58_url_path_2 before add_item_to_cart when search products[] is empty.

Input parameters:

- `notification_message` (string): Short user-facing sentence for this action if the follow-up reply fails. Plain text only; do not mention template syntax or variable names.
- `step_58_url_path_2` (string, required): Vendor id from search_product data[].id for the restaurant the user picked.

### `add_item_to_cart` (~342 tokens)

Add an item to cart. Requires vendor id + menu item id from search_product (products[]) or view_vendor_items. Always pass item type menu.

Input parameters:

- `notification_message` (string): Short user-facing sentence for this action if the follow-up reply fails. Plain text only; do not mention template syntax or variable names.
- `step_37_body_addressId` (string): Same value as step_37_body_address_id.
- `step_37_body_address_id` (string, required): From get_addresses after user confirms pretty_name — never ask user to type this.
- `step_47_body_vendor_id` (string, required): Vendor id: search_product data[].id OR view_vendor_items vendor. Not the menu item id.
- `step_57_body_data_0_products_0_name` (string): Display name of the menu item from search/menu response.
- `step_61_body_items_0_discount_price` (string): Discount price in kobo; same as price_per_quantity if no discount.
- `step_61_body_items_0_item_id` (string, required): Menu item id: search_product data[].products[].id OR view_vendor_items menu item id.
- `step_61_body_items_0_pack_reference` (string): Pack reference if required; else empty string.
- `step_61_body_items_0_price_per_quantity` (string): Unit price in kobo from menu/search response.
- `step_61_body_items_0_quantity` (string): Quantity (default 1).
- `step_7_body_data_0_cart_items_0_type` (string): Always menu for food items (never container). Omit to use default menu.

### `view_wallet_balance` (~49 tokens)

Retrieve the user's wallet balance.

Input parameters:

- `notification_message` (string): Short user-facing sentence for this action if the follow-up reply fails. Plain text only; do not mention template syntax or variable names.

### `get_delivery_amount_for_order` (~53 tokens)

Fetch delivery fee details for an order.

Input parameters:

- `notification_message` (string): Short user-facing sentence for this action if the follow-up reply fails. Plain text only; do not mention template syntax or variable names.

### `place_order` (~63 tokens)

Place order with Pay for me — returns pay_for_me_url for the user to complete payment in browser.

Input parameters:

- `notification_message` (string): Short user-facing sentence for this action if the follow-up reply fails. Plain text only; do not mention template syntax or variable names.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/co-civai-nova-mcp-bgpt-chowdeck/mcp-agents-mcp-bgpt-chowdeck#diagnostics

## Score history

- 2026-11-05: 76
- 2026-11-04: 75
- 2026-11-03: 75
- 2026-11-02: 74

## Common questions

### What is the ChowDeck MCP by Nova (CIVAI) server?

ChowDeck MCP by Nova (CIVAI) is listed in the public MCP registry as co.civai.nova/mcp-bgpt-chowdeck. Order food on ChowDeck: browse restaurants, set your delivery address, build a cart, and check out… This page covers its hosted endpoint (https://nova.civai.co/mcp/agents/mcp-bgpt-chowdeck).

### Is the ChowDeck MCP by Nova (CIVAI) server safe to use?

ChowDeck MCP by Nova (CIVAI) scores 76 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 ChowDeck MCP by Nova (CIVAI) server expose?

ChowDeck MCP by Nova (CIVAI) exposes 24 tools: request_login_otp, verify_login_otp, fetch_customer_settings, view_cart, get_addresses, and 19 more. Their descriptions and schemas cost roughly 2,393 tokens of context every time the server is loaded.

### Does the ChowDeck MCP by Nova (CIVAI) server require authentication?

Yes. ChowDeck MCP by Nova (CIVAI) 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 ChowDeck MCP by Nova (CIVAI) server still maintained?

ChowDeck MCP by Nova (CIVAI) is still listed as active in the MCP registry. We last reached this channel on 5 November 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://nova.civai.co/mcp/agents/mcp-bgpt-chowdeck
- Website: https://nova.civai.co/agent/mcp-bgpt-chowdeck
- Changelog RSS feed: https://verifymcp.io/servers/co-civai-nova-mcp-bgpt-chowdeck/mcp-agents-mcp-bgpt-chowdeck.xml
- Changelog JSON feed: https://verifymcp.io/servers/co-civai-nova-mcp-bgpt-chowdeck/mcp-agents-mcp-bgpt-chowdeck.json
- HTML version of this page: https://verifymcp.io/servers/co-civai-nova-mcp-bgpt-chowdeck/mcp-agents-mcp-bgpt-chowdeck