LeashIndex Get the report

Index / crm

ChowDeck MCP by Nova (CIVAI)

co-civai-nova-mcp-bgpt-chowdeck declares 24 capabilities across 24 tools, with 2 critical issues. One of them, no-revocation, is recorded for every server in the index because MCP has no field in which to declare a way to switch a tool off; a missing declaration is not evidence that the control is missing.

62/100 exposureElevated

Manifest recorded 2026-11-08 from tools/list on https://nova.civai.co/mcp/agents/mcp-bgpt-chowdeck, published in the official MCP registry as co.civai.nova/mcp-bgpt-chowdeck 1.0.0. The date changes only when the manifest does. Not verified by a maintainer.

Issues

These describe what this server's manifest declares. A product can provide controls that MCP has no way to express — token revocation, an admin console, audit logs — and this page cannot see them. The absence of a declaration is not evidence that a control is absent.

critical · no-revocation · All 24 tools

24 of 24 tools declare no way for the customer to switch them off once granted. This applies to every tool because MCP has no field in which to declare a revocation mechanism; the product may provide one outside MCP that a manifest cannot show.

critical · irreversible-uncapped · 2 of 24 tools

2 tools are classified as irreversible and declare no limit.

high · no-expiry · All 24 tools

24 of 24 tools declare no expiry. This applies to every tool because MCP has no field in which to declare an expiry; the product may provide one outside MCP that a manifest cannot show.

high · no-audit-trail · All 24 tools

24 of 24 tools declare no record of their actions that the customer can read. This applies to every tool because MCP has no field in which to declare an audit requirement; the product may provide one outside MCP that a manifest cannot show.

high · uncapped-write · 4 of 24 tools

4 tools can modify data and declare no limit.

low · uncapped-read · 18 of 24 tools

18 tools can read data and declare no limit.

Declared capabilities

How each tool was read. declared means the server's own annotation said so — self-reported and unverified. inferred is from the tool's name. assumed means nothing indicated either way.

ToolRead asBasis
request_login_otpwrite inferred
verify_login_otpread inferred
fetch_customer_settingsread inferred
view_cartread inferred
get_addressesread inferred
get_payment_methodsread inferred
list_orders_successread inferred
get_order_detailsread inferred
get_customer_surveyread inferred
set_active_address_and_fetch_menuread inferred
get_featured_vendorsread inferred
get_chowpass_statusread inferred
search_menu_by_addressread inferred
search_productread inferred
get_country_listread inferred
view_vendor_cartread inferred
remove_cart_itemdelete inferred
duplicate_cart_packwrite assumed
clear_vendor_cartdelete inferred
view_vendor_itemsread inferred
add_item_to_cartwrite inferred
view_wallet_balanceread inferred
get_delivery_amount_for_orderread inferred
place_orderwrite assumed
Answering this question about your own agent? The self-serve stack report applies the same reading to your own stack or server and gives you a dated document you can hand to a customer's security review. It is generated in your browser, with nobody to wait for. Buying one does not change this page, its score or its place in the index — see Independence.
Maintain this server? If this page misreads your manifest, or your server has changed, submit its current tools/list response and it will be re-scored and dated. Corrections are published alongside the original, not in place of it.