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…
Available components
Last scanned (1 hour ago)
Scores higher than 66% of remote servers
Reachable. Last reached 5 Nov 2026.
Category E-commerce
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. How we score → Why this is hard to score →
Endpoint Security83
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability80
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 2455 tokens (~90/item across 27 items; 24 tools + 3 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management10
- Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 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. See how to fix → Fail
- An AI judge read all 25 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 +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.
- 3 Nov 26 +1
- Stability: unverified → 0.03 ▲ functional
- 2 Nov 26 74
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://nova.civai.co/mcp/agents/mcp-bgpt-chowdeck
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=api.vearn.co | CN=YR2,O=Let's Encrypt,C=US | 18 Oct 2026 | 16 Jan 2027 | RSA 2048 | SHA256-RSA | 5989a0174450d554cb27dbfdec88b2ff58a |
| SANs: allegedly-api.crypvestai.cloud, allegedly.crypvestai.cloud, api.agi.civai.co, api.browser.civai.co, api.nova.civai.co, api.vearn.co, app.browsergpt.co, app.vearn.co, arcade-assets.civai.co, audience-resolver-api.civai.co, audience-resolver.civai.co, audience.civai.co and 11 more | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of nova.civai.co. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| co. | present | 7786 | 8 | Verified |
| civai.co. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Challenged, unverified
The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.
| Result | Challenged, unverified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
Protected resource metadata
| Retrieved | No |
|---|---|
| Problem | no_resource_metadata |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://nova.civai.co/mcp/agents/mcp-bgpt-chowdeck | Verified | 400 | |
| http (plaintext) | http://nova.civai.co/mcp/agents/mcp-bgpt-chowdeck | HTTPS enforced | 301 | https://nova.civai.co/mcp/agents/mcp-bgpt-chowdeck |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
add_item_to_cart ~342
Add an item to cart. Requires vendor id + menu item id from search_product (products[]) or view_vendor_items. Always pass item type menu.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | From get_addresses after user confirms pretty_name — never ask user to type this. |
| step_47_body_vendor_id | string | yes | 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 | yes | 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. |
No output schema declared.
No examples provided.
clear_vendor_cart ~128
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'.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Cart id to delete (view_vendor_cart → data.id, or view_cart → data[].id for matching vendor) |
No output schema declared.
No examples provided.
duplicate_cart_pack ~133
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Cart id from view_vendor_cart → data.id |
| step_66_url_path_4 | string | yes | Pack reference UUID from view_vendor_cart → data.cart_items[].pack_reference for the line to duplicate |
No output schema declared.
No examples provided.
fetch_customer_settings ~55
Public customer app config (no auth). Good session probe.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
get_addresses ~48
Run the get_addresses pipeline.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
get_chowpass_status ~54
Run the get_chowpass_status pipeline.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
get_country_list ~50
Run the get_country_list pipeline.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
get_customer_survey ~52
Run the get_customer_survey pipeline.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
get_delivery_amount_for_order ~53
Fetch delivery fee details for an order.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
get_featured_vendors ~131
Featured and tagged vendors near a delivery address.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Active delivery address id (from get_addresses or set_active_address) |
No output schema declared.
No examples provided.
get_order_details ~50
Run the get_order_details pipeline.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
get_payment_methods ~50
Run the get_payment_methods pipeline.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
list_orders_success ~50
Run the list_orders_success pipeline.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
place_order ~63
Place order with Pay for me — returns pay_for_me_url for the user to complete payment in browser.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
remove_cart_item ~277
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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 | yes | Cart line id from view_vendor_cart → data.cart_items[].id |
| step_118_body_items_0_item_id | string | yes | Menu item id from view_vendor_cart → data.cart_items[].item_id (type menu line) |
| step_118_body_items_0_pack_reference | string | yes | Pack UUID from view_vendor_cart → data.cart_items[].pack_reference |
| step_56_url_path_3 | string | yes | 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) |
No output schema declared.
No examples provided.
request_login_otp ~135
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | User-provided phone without country prefix (local NG format like 080…). Never invent or reuse another account's number. |
No output schema declared.
No examples provided.
search_menu_by_address ~52
Run the search_menu_by_address pipeline.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
search_product ~139
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Delivery address id from get_addresses — never ask user to type the number. |
| step_52_url_query_query | string | yes | Product search term (e.g. jollof, omeprazole, Daytona) |
No output schema declared.
No examples provided.
set_active_address_and_fetch_menu ~122
Set active delivery address and fetch chowsmart menu for that address.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Address id to set as active (from get_addresses) |
| step_38_url_query_address_id | string | yes | Same address id for menu fetch |
No output schema declared.
No examples provided.
verify_login_otp ~125
Complete ChowDeck login with SMS code (validate phone → validate OTP → refresh token). Does not send a new SMS.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Same phone used in request_login_otp |
| step_5_body_otp | string | yes | SMS one-time code from the user |
No output schema declared.
No examples provided.
view_cart ~47
View current cart contents.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
view_vendor_cart ~84
View cart for one vendor (vendor-specific checkout view).
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Vendor id (from search_product, view_cart data[].vendor_id, or featured vendors) |
No output schema declared.
No examples provided.
view_vendor_items ~104
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Vendor id from search_product data[].id for the restaurant the user picked. |
No output schema declared.
No examples provided.
view_wallet_balance ~49
Retrieve the user's wallet balance.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
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.
remote · nova.civai.co
claude mcp add --transport http co-civai-nova-mcp-bgpt-chowdeck 'https://nova.civai.co/mcp/agents/mcp-bgpt-chowdeck'
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.