# Lokand Restaurant MCP (remote · api.lokand.com)

Free restaurant websites and menus: read any public menu, or build, import and publish a site.

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

## Components

- remote · `api.lokand.com`: 67/100 (this document), [markdown](https://verifymcp.io/servers/com-lokand-lokand/api.md), [page](https://verifymcp.io/servers/com-lokand-lokand/api)

## Channel facts

- Endpoint: `https://api.lokand.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.5`

## 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**: 60/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (create_full_menu).
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 65/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 10053 tokens (~125/item across 80 items; 80 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 35/100
  - Stability check failed: schema churn in the 11 days we've observed: 1 tool removals, 0 breaking changes, 0 auth/transport breaks, 8 additions.
- **Tool Coverage**: 86/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 58% 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.
  - All 10 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 80 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the Lokand Restaurant MCP server?

Lokand Restaurant MCP is a hosted endpoint at https://api.lokand.com/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 com-lokand-lokand 'https://api.lokand.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-lokand-lokand": {
      "url": "https://api.lokand.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-lokand-lokand": {
      "type": "http",
      "url": "https://api.lokand.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-lokand-lokand]
url = "https://api.lokand.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-lokand-lokand": {
      "type": "remote",
      "url": "https://api.lokand.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-lokand-lokand --url 'https://api.lokand.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-lokand-lokand:
    url: "https://api.lokand.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-lokand-lokand": {
      "Transport": "http",
      "Url": "https://api.lokand.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-lokand-lokand -t streamable-http -u 'https://api.lokand.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-lokand-lokand": {
      "type": "http",
      "url": "https://api.lokand.com/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-21 (score 67, 0)

- [functional] MCP protocol: Implements a current MCP spec version (2026-07-28).
- [functional] MCP protocol version: 2025-11-25 → 2026-07-28

### 2026-11-19 (score 67, +1)

- [security] New tool “connect_registered_domain”, which the server declares destructive
- [security] Tool “theme_write_files” rewrote its description, which is the text the model reads
- [security] Tool “update_block” rewrote its description, which is the text the model reads
- [security] Tool “update_section” rewrote its description, which is the text the model reads
- [security] Tool “update_site” rewrote its description, which is the text the model reads
- [security] Tool “update_theme_settings” rewrote its description, which is the text the model reads
- [security] Tool “add_block” rewrote its description, which is the text the model reads
- [security] Tool “add_section” rewrote its description, which is the text the model reads
- [security] Tool “list_assets” rewrote its description, which is the text the model reads
- [security] Tool “theme_git_access” rewrote its description, which is the text the model reads
- [security] Tool “theme_list” rewrote its description, which is the text the model reads
- [security] Tool “theme_publish” rewrote its description, which is the text the model reads
- [security] Tool “theme_rollback” rewrote its description, which is the text the model reads
- [security] Tool “theme_sync” rewrote its description, which is the text the model reads
- [security] Tool “theme_upload” rewrote its description, which is the text the model reads
- [functional] Server version: 1.0.4 → 1.0.5
- [functional] New tool “create_business”

### 2026-11-17 (score 66, 0)

- [security regression] Stability: 0.20 → fail
- [security regression] Tool “apply_style_preset” was removed
- [security] Tool “update_business” rewrote its description, which is the text the model reads
- [security] Tool “get_site” rewrote its description, which is the text the model reads
- [security] Tool “set_theme” rewrote its description, which is the text the model reads
- [security] Tool “theme_pull” rewrote its description, which is the text the model reads
- [security] Tool “theme_write_files” rewrote its description, which is the text the model reads
- [security] Tool “update_theme” rewrote its description, which is the text the model reads
- [security] Tool “update_theme_settings” rewrote its description, which is the text the model reads
- [functional] Server version: 1.0.3 → 1.0.4
- [functional] Server version: 1.0.2 → 1.0.3
- [functional] New tool “set_translations”
- [functional] New tool “create_tables”
- [functional] New tool “export_qr_codes”
- [functional] New tool “get_qr_design”
- [functional] New tool “list_tables”
- [functional] New tool “update_qr_design”
- [cosmetic] “update_business” added an optional parameter “supported_locales”
- [cosmetic] “set_system_theme” reworded the description of “theme_id”
- [cosmetic] “set_theme” reworded the description of “theme_id”
- [cosmetic] “theme_delete” reworded the description of “theme_id”
- [cosmetic] “theme_get” reworded the description of “theme_id”
- [cosmetic] “theme_git_access” reworded the description of “theme_id”
- [cosmetic] “theme_history” reworded the description of “theme_id”
- [cosmetic] “theme_publish” reworded the description of “theme_id”
- [cosmetic] “theme_pull” reworded the description of “theme_id”
- [cosmetic] “theme_rollback” reworded the description of “theme_id”
- [cosmetic] “theme_sync” reworded the description of “theme_id”
- [cosmetic] “theme_upload” reworded the description of “theme_id”
- [cosmetic] “theme_write_files” reworded the description of “theme_id”
- [cosmetic] “set_theme” dropped the optional parameter “theme_key”
- [cosmetic] “update_theme” dropped the optional parameter “preset”

### 2026-11-16 (score 66, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-14 (score 65, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-12 (score 64, +1)

- [security] Tool “get_style” rewrote its description, which is the text the model reads

### 2026-11-11 (score 63, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-10 (score 63)

First indexed and scored.

## MCP tools (80)

### `get_started` (~45 tokens)

Get started

How to use Lokand as an agent: the recipes for creating a restaurant for a customer, editing menus, and handing over ownership. Call this first if you're unsure what to do.

### `list_businesses` (~40 tokens)

List businesses

List the businesses the signed-in user is a member of (id, name, slug, role). Use it to pick the business_id other ops need.

### `get_business` (~45 tokens)

Get business

Look up a public Lokand restaurant/business by its slug. Returns profile, hours, contact info, locale and theme metadata.

Input parameters:

- `slug` (string, required): The business's public slug

### `list_menus` (~35 tokens)

List menus

List the active menus of a public Lokand restaurant by its slug.

Input parameters:

- `slug` (string, required): The business's public slug

### `get_menu` (~53 tokens)

Get menu

Fetch a single menu (categories + items with prices) of a public Lokand restaurant.

Input parameters:

- `menu_id` (string, required): The menu id from list_menus
- `slug` (string, required): The business's public slug

### `get_status` (~53 tokens)

Get status

Private status of a business the caller manages: profile (including unpublished state), all menus (active and inactive), and plan. Requires the menu:read scope and membership.

Input parameters:

- `business_id` (string, required): The business id

### `create_full_menu` (~93 tokens)

Create full menu

Create a COMPLETE menu (sections + items) in one call — prefer this over separate create_menu/add_category/add_item calls. With replace=true, existing menus are deactivated so this becomes the business's live menu (their data is kept, just hidden).

Input parameters:

- `business_id` (string, required)
- `menu` (object, required)
- `replace` (boolean): Deactivate the business's other menus in the same step

### `create_menu` (~130 tokens)

Create menu

Create an EMPTY menu on a business the caller manages (add sections with add_category, dishes with add_item). For a whole menu at once, use create_full_menu instead. Returns the new menu_id.

Input parameters:

- `business_id` (string, required)
- `description` (string)
- `id` (string): Optional caller-chosen id (8-64 chars). Reuse the same id when retrying so a retry can never create a duplicate.
- `is_active` (boolean): Whether the menu is live on the public site
- `name` (string, required): Menu name, e.g. "Dinner"

### `add_category` (~90 tokens)

Add category

Add a category (section) to a menu. Returns the new category_id.

Input parameters:

- `id` (string): Optional caller-chosen id (8-64 chars). Reuse the same id when retrying so a retry can never create a duplicate.
- `menu_id` (string, required)
- `name` (string, required): Category name, e.g. "Starters"
- `sort_order` (integer)

### `add_item` (~406 tokens)

Add item

Add a dish/item to a menu (optionally inside a category). Returns the new item_id.

Input parameters:

- `category_id` (string)
- `description` (string)
- `dietary_info` (object): Allergen and dietary labels shown to diners. `allergens` uses the 14 standard codes (gluten, crustaceans, eggs, fish, peanuts, soybeans, milk, nuts, celery, mustard, sesame, sulphites, lupin, mollusc…
- `id` (string): Optional caller-chosen id (8-64 chars). Reuse the same id when retrying so a retry can never create a duplicate.
- `is_available` (boolean)
- `menu_id` (string, required)
- `name` (string, required): Item name, e.g. "Cacio e pepe"
- `price` (number): Price in the business's currency. Required unless `variations` is given, in which case it is derived from the cheapest variation.
- `sort_order` (integer)
- `variations` (array): Variations of this dish — sizes, volumes, portions, cuts — each with its own ABSOLUTE price (not a surcharge): e.g. [{name:'Small',price:3},{name:'Large',price:4.5}]. Use this instead of creating one…

### `update_item` (~304 tokens)

Update item

Update a menu item's fields (name, description, price, availability, category, sort order). Only provided fields change. Setting is_available=false takes a dish off the public site (86 it).

Input parameters:

- `category_id`
- `description`
- `dietary_info`: Allergen and dietary labels shown to diners. `allergens` uses the 14 standard codes (gluten, crustaceans, eggs, fish, peanuts, soybeans, milk, nuts, celery, mustard, sesame, sulphites, lupin, mollusc…
- `is_available` (boolean)
- `item_id` (string, required)
- `name` (string)
- `price` (number)
- `sort_order` (integer)
- `variations`: Replaces the item's whole variation list. Variations keep their identity by name, so re-sending the list to change one price is safe. Pass null to drop variations entirely — send `price` alongside it…

### `delete_item` (~21 tokens)

Delete item

Delete a menu item.

Input parameters:

- `item_id` (string, required)

### `update_menu` (~78 tokens)

Update menu

Rename a menu, change its description, or switch it on/off on the public site (is_active). Only provided fields change. Menu ids come from get_status.

Input parameters:

- `description`
- `is_active` (boolean): Whether the menu is live on the public site
- `menu_id` (string, required)
- `name` (string)

### `delete_menu` (~49 tokens)

Delete menu

Permanently delete a menu together with ALL of its sections and items. To take a menu off the site but keep it, use update_menu is_active=false instead.

Input parameters:

- `menu_id` (string, required)

### `rename_category` (~33 tokens)

Rename category

Rename a menu category (section).

Input parameters:

- `category_id` (string, required)
- `name` (string, required): The new name

### `reorder_categories` (~56 tokens)

Reorder categories

Set the order of a menu's categories (sections). List category ids top to bottom; any you leave out keep their current relative order after the listed ones.

Input parameters:

- `category_ids` (array, required)
- `menu_id` (string, required)

### `delete_category` (~52 tokens)

Delete category

Delete a menu category (section). Its items are NOT deleted — they stay on the menu without a section; move them with update_item category_id or delete them with delete_item.

Input parameters:

- `category_id` (string, required)

### `reorder_items` (~87 tokens)

Reorder items

Set the order of the items in one section of a menu. List item ids top to bottom; listed items from another section are moved into this one, and the section's other items keep their relative order after the listed ones.

Input parameters:

- `category_id` (required): The section being ordered; null = items without a section
- `item_ids` (array, required)
- `menu_id` (string, required)

### `update_business` (~545 tokens)

Update business

Update a business's profile: name, description, about text, opening hours, contact info, currency, default locale, the locales visitors can switch between, menu display options, country, business details, or place (location, address, timezone, category, cuisines). Only provided fields change.

Input parameters:

- `about`
- `business_id` (string, required)
- `contact_info` (object): Contact info: phone, email, address, instagram
- `country_code` (string): ISO 3166-1 alpha-2 country the business operates in. ADVISORY: it seeds suggested menu options (apply_country_settings) and drives check_compliance. It never changes what the site renders.
- `currency_code` (string)
- `default_locale` (string)
- `description`
- `hours` (object): Opening hours keyed mon..sun, each {"open":"10:30","close":"22:00"} or {"closed":true}
- `legal_info` (object): Business details published on the site when filled in: tradeName, taxNumber, registrationNumber, registeredAddress, contactEmail, contactPhone, plus `extra` label/value pairs for anything a jurisdict…
- `maps_url` (string): A Google Maps, Apple Maps, Yandex or OpenStreetMap link (short share links work), or a "lat, lng" pair. Sets the coordinates.
- `menu_options` (object): How the published menu presents itself: `menuNotice` (free text shown above the menu, in the owner's own words), `showPriceEffectiveDate`, and `orderingExcludedTags` (tags that can be listed but not…
- `name` (string)
- `place` (object): Where the business is and what kind of place it is: lat/lng; address {streetAddress, addressLocality (district), addressRegion (city or province), postalCode, addressCountry (ISO 3166-1 alpha-2)}; ti…
- `supported_locales` (array): Locales visitors can switch between, e.g. ["pl","en"]; the default locale is always included

### `set_theme` (~143 tokens)

Set theme

Switch the site to a system theme with `theme_id` (lokand-base; get_site lists them; pages, sections and settings are kept). Legacy shape: a v1 `theme_config` patch (colors, fonts, hero title/subtitle) — prefer update_theme_settings, or get_style for a whole look. Revertible with revert_last_site_change.

Input parameters:

- `business_id` (string, required)
- `theme_config` (object): Legacy: merge patch such as {"colors":{"primary":"#aa3300"},"fonts":{"heading":"..."}}
- `theme_id` (string): A system theme id from get_site (e.g. lokand-base)

### `publish_site` (~56 tokens)

Publish site

Publish (or unpublish) the business's public menu site at https://<slug>.lokand.co.

Input parameters:

- `business_id` (string, required)
- `publish` (boolean): true to go live, false to take the site offline

### `create_restaurant` (~528 tokens)

Create restaurant

Create a new Lokand restaurant on a customer's behalf — ONE call can produce a complete LIVE website when you pass `menu` (and optionally hours/theme). Returns working OAuth tokens (Bearer, for follow-up edit ops), the live site_url, and a claim_url. NEXT STEPS after this call: refine with add_item/update_item/set_theme if needed, then give the customer the claim_url so they take ownership (free signup); poll claim_status to keep access after they claim. Requires a client registered once via POST /api/auth/oauth2/register (see https://lokand.com/auth.md).

Input parameters:

- `client_id` (string, required): Registered OAuth client id
- `client_secret` (string, required): The client's secret
- `contact_info` (object): Contact info: phone, email, address, instagram
- `currency_code` (string): ISO currency for menu prices, e.g. "USD"
- `customer_email` (string): Customer's email: binds the claim to it and sends them the claim link
- `description` (string)
- `hours` (object): Opening hours keyed mon..sun, each {"open":"10:30","close":"22:00"} or {"closed":true}
- `maps_url` (string): A Google Maps, Apple Maps, Yandex or OpenStreetMap link (short share links work), or a "lat, lng" pair. Sets the coordinates.
- `menu` (object): The full menu, inline — pass this to go live in one call instead of separate create_menu/add_category/add_item calls
- `name` (string, required): Restaurant name
- `place` (object): Where the business is and what kind of place it is: lat/lng; address {streetAddress, addressLocality (district), addressRegion (city or province), postalCode, addressCountry (ISO 3166-1 alpha-2)}; ti…
- `publish` (boolean): Put the site live immediately (default true). Pass false to keep it a draft.
- `slug` (string): Optional site slug (<slug>.lokand.co); generated from the name when omitted. If taken, a suffixed variant is used automatically.
- `theme` (object)

### `create_business` (~431 tokens)

Create business

Create a new restaurant owned by the signed-in user (no claim step) — ONE call can produce a complete LIVE website when you pass `menu` (and optionally hours/theme). Returns the business_id for follow-up ops and the live site_url. To create a restaurant for someone else, use create_restaurant and hand them the claim link instead.

Input parameters:

- `contact_info` (object): Contact info: phone, email, address, instagram
- `currency_code` (string): ISO currency for menu prices, e.g. "USD"
- `description` (string)
- `hours` (object): Opening hours keyed mon..sun, each {"open":"10:30","close":"22:00"} or {"closed":true}
- `maps_url` (string): A Google Maps, Apple Maps, Yandex or OpenStreetMap link (short share links work), or a "lat, lng" pair. Sets the coordinates.
- `menu` (object): The full menu, inline — pass this to go live in one call instead of separate create_menu/add_category/add_item calls
- `name` (string, required): Restaurant name
- `place` (object): Where the business is and what kind of place it is: lat/lng; address {streetAddress, addressLocality (district), addressRegion (city or province), postalCode, addressCountry (ISO 3166-1 alpha-2)}; ti…
- `publish` (boolean): Put the site live immediately (default true). Pass false to keep it a draft.
- `slug` (string): Optional site slug (<slug>.lokand.co); generated from the name when omitted. If taken, a suffixed variant is used automatically.
- `theme` (object)

### `claim_status` (~74 tokens)

Claim status

Check whether the customer has claimed an agent-created restaurant. On the first poll after a claim with consent granted, returns fresh OAuth tokens for continued management (delivered exactly once).

Input parameters:

- `claim_token` (string, required)
- `client_id` (string, required): Registered OAuth client id
- `client_secret` (string, required): The client's secret

### `create_checkout_link` (~123 tokens)

Create checkout link

Create a Stripe Checkout link to upgrade a business to a paid plan. Hand the returned URL to the customer — anyone who opens it can pay; the plan activates automatically after payment (3-month free trial). Pass customer_country (ISO 3166-1 alpha-2) so first-time pricing is quoted in the customer's region, not the agent's.

Input parameters:

- `business_id` (string, required)
- `customer_country` (string): Customer's ISO country code, e.g. DE
- `product_key` (string, required): The plan to purchase (Pro is monthly-only)

### `get_billing_summary` (~34 tokens)

Get billing summary

Current plan, billing region, and subscription state of a business the caller manages.

Input parameters:

- `business_id` (string, required)

### `import_menu` (~76 tokens)

Import menu

Start an AI import of a restaurant's menu from the URL of its existing website. Returns an import_id to poll with import_status; when complete, call commit_import to turn the draft into a real menu.

Input parameters:

- `business_id` (string, required)
- `url` (string, required): Public https URL of the site to import the menu from

### `import_status` (~54 tokens)

Import status

Check an AI menu import: processing, complete (draft ready to commit), or failed. `progress.found` lists what is known so far; complete responses include the draft for review.

Input parameters:

- `import_id` (string, required)

### `commit_import` (~42 tokens)

Commit import

Commit a completed AI menu import as a real menu (creates the menu, categories, and items). Returns the new menu_id.

Input parameters:

- `import_id` (string, required)

### `check_compliance` (~127 tokens)

Check compliance

Check a business's published menu against what a country's menu rules ask for — allergen and calorie declarations, price-list notices, banned surcharges, operator identity. Returns each requirement with its official sources, plus which ones the menu currently falls short of and the item ids involved. ADVISORY ONLY: it reports, it never changes the site, and it is not legal advice.

Input parameters:

- `business_id` (string, required)
- `country` (string): ISO country to check against. Defaults to the business's own country_code; pass one explicitly to check against a market the business is considering.

### `apply_country_settings` (~124 tokens)

Apply country settings

Fill the business's menu display options with the values a country's rules suggest — a notice about tax-inclusive pricing, the price-effective date, ordering restrictions. These are DEFAULTS: the owner can change any of them afterwards, and nothing here is enforced.

Input parameters:

- `business_id` (string, required)
- `country` (string): Defaults to the business's own country_code.
- `locale` (string): Language for any suggested copy. Defaults to the business's.
- `overwrite` (boolean): false (default) fills only options the owner hasn't set; true replaces their existing values.

### `get_site` (~202 tokens)

Get site

Read the business's website: `document` (the v3 site document — settings, home, pages, and templates[page_id] → sections → blocks, with the ids every other site op needs), `theme` (what the live theme offers: every section and block type with its settings, the theme settings), `resolved_settings` (the concrete theme settings the site renders with), `live_theme` (the custom theme code in use, with its file paths, or null for a system theme), `style_hooks` (stable [data-lk="…"] attributes custom_css can target on a system theme), `system_themes` (for set_system_theme) and `templates` (segment layouts for apply_template). Settings are listed compactly as "id:type(options)"; pass detail: "full" for labels and defaults. ALWAYS call this before changing the site.

Input parameters:

- `business_id` (string, required)
- `detail` (string)

### `update_site` (~132 tokens)

Update site

Low-level escape hatch: apply an RFC 7386 JSON merge patch to the whole v3 site document returned by get_site.document (objects merge, null deletes a key, arrays REPLACE). Prefer the specific site ops. The result is validated against the theme before anything is saved. An outside image url in an image setting is copied into the business's media library and the setting stores our copy; if it can't be downloaded the call fails with image_fetch_failed and nothing changes.

Input parameters:

- `business_id` (string, required)
- `patch` (object, required): RFC 7386 JSON merge patch on the whole theme data document

### `update_theme_settings` (~111 tokens)

Update theme settings

Merge-patch the theme's global settings (keys from get_site.theme.theme_settings, e.g. color_primary, font_heading, radius, custom_css). null resets a key to the theme default. An outside image url in an image setting is copied into the business's media library and the setting stores our copy; if it can't be downloaded the call fails with image_fetch_failed and nothing changes.

Input parameters:

- `business_id` (string, required)
- `settings` (object, required): Merge patch on the theme's global settings

### `update_theme` (~142 tokens)

Update theme

Legacy look op: patch v2-style `tokens` (colors, fonts, radius, hero layout, …) or set custom CSS. Prefer update_theme_settings.

Input parameters:

- `business_id` (string, required)
- `custom_css`: Extra CSS; null clears it. No @import, url() or <
- `tokens` (object): Merge patch on theme tokens: colors{primary,accent,bg,fg,primaryFg,card,muted,line,line2}, loyalty{bg,ink}, fonts{heading,body,mono}, radius, radiusButton, heroLayout, serif, density, headingCase, bu…

### `apply_template` (~123 tokens)

Apply template

Rebuild the site's pages and sections from a segment template (cafe, ghost-kitchen, fine-dining, chain, bar, bakery — see get_site.templates). Replaces the page structure; hero copy and custom CSS carry over. keep_theme=true keeps the current style. Revertible with revert_last_site_change.

Input parameters:

- `business_id` (string, required)
- `keep_theme` (boolean): Keep the current style instead of the template's (default false)
- `template` (string, required): cafe | ghost-kitchen | fine-dining | chain | bar | bakery

### `apply_site_preset` (~59 tokens)

Apply site preset

Alias of apply_template (`preset` = template id).

Input parameters:

- `business_id` (string, required)
- `keep_theme` (boolean)
- `preset` (string, required): cafe | ghost-kitchen | fine-dining | chain | bar | bakery

### `set_page` (~161 tokens)

Set page

Change one page: enable/disable it, show/hide it in the navigation, rename its title, change its path, make it the home page, or move it in the navigation. Only provided fields change. Page ids come from get_site.document.pages (built-ins: home, menu, about, loyalty).

Input parameters:

- `business_id` (string, required)
- `enabled` (boolean)
- `make_home` (boolean): Serve this page at /
- `page_id` (string, required): Page id, e.g. home, menu, about, loyalty
- `path` (string): One segment like /wine
- `position` (integer): Move the page to this position in the navigation
- `show_in_nav` (boolean)
- `title`

### `add_page` (~69 tokens)

Add page

Add a new page with a text section (add more with add_section). Returns the updated document, where the new page's id appears.

Input parameters:

- `business_id` (string, required)
- `path` (string)
- `position` (integer): 0-based position
- `title` (string, required)

### `remove_page` (~63 tokens)

Remove page

Remove a custom page and its sections. The home page can't be removed — make another page home first (set_page make_home).

Input parameters:

- `business_id` (string, required)
- `page_id` (string, required): Page id, e.g. home, menu, about, loyalty

### `set_nav_links` (~46 tokens)

Set nav links

Replace the navigation with custom links ([] restores the automatic page list).

Input parameters:

- `business_id` (string, required)
- `links` (array, required): Custom navigation; [] restores the automatic page list

### `add_section` (~202 tokens)

Add section

Add a section of a given `type` (keys of get_site.theme.sections) to a page, optionally from one of its presets, with a settings patch and a 0-based position (default: the end). Sections hold blocks; add them with add_block. An outside image url in an image setting is copied into the business's media library and the setting stores our copy; if it can't be downloaded the call fails with image_fetch_failed and nothing changes.

Input parameters:

- `business_id` (string, required)
- `kind`: Alias of type
- `page_id` (string, required): Page id, e.g. home, menu, about, loyalty
- `position` (integer): 0-based position
- `preset` (string): Start from one of the type's presets
- `settings` (object): Settings as a JSON merge patch (null removes a key). get_site lists each type's settings.
- `type` (string): Section type from get_site

### `update_section` (~160 tokens)

Update section

Change one section: merge-patch its settings (null removes a key; settings: null resets them all) and/or hide/show it. Ids come from get_site.document.templates[page_id]. An outside image url in an image setting is copied into the business's media library and the setting stores our copy; if it can't be downloaded the call fails with image_fetch_failed and nothing changes.

Input parameters:

- `business_id` (string, required)
- `hidden` (boolean)
- `page_id` (string, required): Page id, e.g. home, menu, about, loyalty
- `section_id` (string, required): Section id from get_site
- `settings`: Settings as a JSON merge patch (null removes a key). get_site lists each type's settings.

### `remove_section` (~72 tokens)

Remove section

Remove a section from a page. To keep it for later, hide it with update_section hidden=true instead.

Input parameters:

- `business_id` (string, required)
- `page_id` (string, required): Page id, e.g. home, menu, about, loyalty
- `section_id` (string, required): Section id from get_site

### `move_section` (~74 tokens)

Move section

Move a section to a 0-based position within its page.

Input parameters:

- `business_id` (string, required)
- `page_id` (string, required): Page id, e.g. home, menu, about, loyalty
- `position` (integer, required): 0-based position
- `section_id` (string, required): Section id from get_site

### `add_block` (~225 tokens)

Add block

Add a block (a repeatable piece inside a section: a link, a photo, a testimonial, …) of a `type` the section accepts (get_site.theme.sections[type].blocks). Nest it in another block with parent_block_id. An outside image url in an image setting is copied into the business's media library and the setting stores our copy; if it can't be downloaded the call fails with image_fetch_failed and nothing changes.

Input parameters:

- `business_id` (string, required)
- `page_id` (string, required): Page id, e.g. home, menu, about, loyalty
- `parent_block_id` (string): Nest inside this block instead of the section
- `position` (integer): 0-based position
- `preset` (string): Start from one of the block type's presets
- `section_id` (string, required): Section id from get_site
- `settings` (object): Settings as a JSON merge patch (null removes a key). get_site lists each type's settings.
- `type` (string, required): Block type the section accepts (see get_site)

### `update_block` (~152 tokens)

Update block

Merge-patch one block's settings (null removes a key) and/or hide/show it. An outside image url in an image setting is copied into the business's media library and the setting stores our copy; if it can't be downloaded the call fails with image_fetch_failed and nothing changes.

Input parameters:

- `block_id` (string, required): Block id from get_site
- `business_id` (string, required)
- `hidden` (boolean)
- `page_id` (string, required): Page id, e.g. home, menu, about, loyalty
- `section_id` (string, required): Section id from get_site
- `settings`: Settings as a JSON merge patch (null removes a key). get_site lists each type's settings.

### `move_block` (~87 tokens)

Move block

Move a block to a 0-based position among its siblings.

Input parameters:

- `block_id` (string, required): Block id from get_site
- `business_id` (string, required)
- `page_id` (string, required): Page id, e.g. home, menu, about, loyalty
- `position` (integer, required): 0-based position
- `section_id` (string, required): Section id from get_site

### `remove_block` (~74 tokens)

Remove block

Remove a block (and any blocks nested in it).

Input parameters:

- `block_id` (string, required): Block id from get_site
- `business_id` (string, required)
- `page_id` (string, required): Page id, e.g. home, menu, about, loyalty
- `section_id` (string, required): Section id from get_site

### `set_featured_items` (~94 tokens)

Set featured items

Choose the dishes shown in the home page's "featured" section, in order (menu item ids, max 12; [] lets the site pick automatically). Adds the section after the hero if the page has none.

Input parameters:

- `business_id` (string, required)
- `item_ids` (array, required): Menu item ids, in display order; [] = automatic
- `page_id` (string): Defaults to the home page

### `set_system_theme` (~61 tokens)

Set system theme

Switch to another system theme (get_site lists `system_themes`). Pages, sections and settings are kept.

Input parameters:

- `business_id` (string, required)
- `theme_id` (string, required): A system theme id from get_site (e.g. lokand-base)

### `make_menu_only` (~58 tokens)

Make menu only

Turn the site into a single menu page (the menu becomes the home page, every other page is disabled). Use when the owner wants "just the menu". Revertible with revert_last_site_change.

Input parameters:

- `business_id` (string, required)

### `set_brand_link` (~106 tokens)

Set brand link

Chains only: link this location to its brand's shared site (linked=true) so it shows the brand template's pages and theme, or unlink it (linked=false) to use its own site again. Hours, address, menus and ordering always stay this location's own. The brand template is set with publish_brand_template.

Input parameters:

- `business_id` (string, required)
- `linked` (boolean, required): true = show the brand's shared site here; false = this location's own site

### `publish_brand_template` (~52 tokens)

Publish brand template

Chains only: make this location's published site the brand template that every linked location of its organization shows (see set_brand_link). Requires brand owner/admin and the franchise plan.

Input parameters:

- `business_id` (string, required)

### `revert_last_site_change` (~62 tokens)

Revert last site change

Undo the most recent site change made through the site ops or set_theme (up to the last 10, kept for 30 days). Call repeatedly to step further back. 404 when there is nothing to undo.

Input parameters:

- `business_id` (string, required)

### `update_loyalty_card` (~182 tokens)

Update loyalty card

Set up or change the business's loyalty stamp card: how many stamps earn the reward, the reward text, whether the card is live, and its look. Only provided fields change; the first call must include stamps_required and reward_text. Requires the Pro plan (402 plan_required otherwise — offer create_checkout_link).

Input parameters:

- `business_id` (string, required)
- `card_config`: The card's look — colors{cardBg,cardFg,stampFilled,stampEmpty}, stampIcon, headline, subline. Replaces the whole style; null resets it to match the site theme.
- `is_active` (boolean): Whether diners can join and collect stamps
- `reward_text` (string): What the guest gets, e.g. "A free coffee"
- `stamps_required` (integer): Stamps needed for one reward (2-30)

### `theme_list` (~66 tokens)

Theme list

List the business's custom themes (id, name, role live|unpublished|development, version, upload status) and the system themes. Custom theme code is a Pro feature (free on every plan until 2027-01-01).

Input parameters:

- `business_id` (string, required)

### `theme_get` (~75 tokens)

Theme get

One theme's details and upload status: ready (the version is stored and can be published), processing (poll again in a second or two) or failed (with the error).

Input parameters:

- `business_id` (string, required)
- `theme_id` (string, required): A theme id from theme_list (or the system theme id lokand-base)

### `theme_pull` (~178 tokens)

Theme pull

Download a theme's files ({path: text}). theme_id "lokand-base" returns the system theme to start from. Custom themes return their latest stored version. A whole theme is large: pass search to find the lines you need to change, or list_only for paths and sizes, then paths for whole files.

Input parameters:

- `business_id` (string, required)
- `list_only` (boolean): Return only {path, size} for every file
- `paths` (array): Return only these files
- `search` (string): Case-insensitive text to find, e.g. ".menu-item .name"; returns matching lines as {path, line, text} instead of files (combine with paths to limit where it looks)
- `theme_id` (string, required): A theme id from theme_list (or the system theme id lokand-base)

### `theme_upload` (~253 tokens)

Theme upload

Upload a complete custom theme (Pro plan; free on every plan until 2027-01-01) as a new commit in its Git repo. Files are validated and compiled at once — a 422 lists every problem as `path: message` lines — then compiled in the background: poll theme_get until status is ready, then theme_publish. Without theme_id, role development reuses your one development theme and role unpublished creates a new theme; with theme_id it stores the next version of that theme. Updating the live theme needs allow_live: true.

Input parameters:

- `allow_live` (boolean): With the live theme's id: update the live site in place
- `business_id` (string, required)
- `files` (object, required): Theme files by path, e.g. {"sections/hero.liquid": "...", "config/settings_schema.json": "..."}
- `message` (string): Commit message
- `name` (string)
- `role` (string): development = your private work-in-progress theme (one per user, replaced on each upload); unpublished = a saved theme ready to publish
- `theme_id` (string): A theme id from theme_list (or the system theme id lokand-base)

### `theme_write_files` (~237 tokens)

Theme write files

Change some files of a custom theme (Pro plan; free on every plan until 2027-01-01) as one new commit: files maps path → whole new text (null deletes), edits are find/replace changes. Read the current files with theme_pull first. Same validation and background compile as theme_upload. On the LIVE theme the change goes live automatically once compiled; theme_rollback undoes it. On the system theme id lokand-base it creates a new unpublished theme from it; pass publish: true to make that live too.

Input parameters:

- `business_id` (string, required)
- `edits` (array): Find/replace changes inside existing files. Prefer this over whole files: send only the lines that change
- `files` (object): path → whole new file text, or null to delete the file
- `message` (string): Commit message describing the change
- `name` (string)
- `publish` (boolean): Go live once compiled (always the case when editing the live theme)
- `theme_id` (string, required): A theme id from theme_list (or the system theme id lokand-base)

### `theme_publish` (~98 tokens)

Theme publish

Make a custom theme the live site's code (Pro plan; free on every plan until 2027-01-01). The previous live theme becomes unpublished and cached pages refresh. `warnings` lists parts of the current site document the new theme doesn't define (fix them with the site ops).

Input parameters:

- `business_id` (string, required)
- `theme_id` (string, required): A theme id from theme_list (or the system theme id lokand-base)

### `theme_unpublish` (~40 tokens)

Theme unpublish

Stop using custom theme code: the site goes back to its system theme. The custom theme is kept as unpublished.

Input parameters:

- `business_id` (string, required)

### `theme_delete` (~61 tokens)

Theme delete

Delete a custom theme and all its stored versions. The live theme can't be deleted — unpublish it first.

Input parameters:

- `business_id` (string, required)
- `theme_id` (string, required): A theme id from theme_list (or the system theme id lokand-base)

### `get_storefront_context` (~105 tokens)

Get storefront context

The exact data a theme renders with (the StorefrontData Liquid objects are built from): the business (localized, brand site applied), every active menu with items, primary menu id, loyalty/ordering flags, the stamp-card program and its resolved style — plus theme_data (the site document) and live_theme. Use it to preview or test theme code locally.

Input parameters:

- `business_id` (string, required)
- `locale` (string): Defaults to the business's default locale

### `theme_history` (~81 tokens)

Theme history

The commit history of a custom theme's code, newest first: hash, message, author, time. The `commit` on theme_get is the one the site renders.

Input parameters:

- `business_id` (string, required)
- `limit` (integer)
- `theme_id` (string, required): A theme id from theme_list (or the system theme id lokand-base)

### `theme_rollback` (~116 tokens)

Theme rollback

Restore a custom theme's code to an earlier commit (Pro plan; free on every plan until 2027-01-01). It is saved as a new commit, so the rollback itself can be undone; on the live theme it goes live once compiled. Without commit, restores the version before the latest change.

Input parameters:

- `business_id` (string, required)
- `commit` (string): Commit hash from theme_history
- `theme_id` (string, required): A theme id from theme_list (or the system theme id lokand-base)

### `theme_git_access` (~134 tokens)

Theme git access

Git access to a custom theme's code: the HTTPS remote and a repo-scoped token (read, or write on the Pro plan; free on every plan until 2027-01-01). Pushes to main compile automatically and, for the live theme, publish once compiled; theme_get shows a push that failed to compile as push_error. Tokens expire (default 1 hour).

Input parameters:

- `business_id` (string, required)
- `scope` (string)
- `theme_id` (string, required): A theme id from theme_list (or the system theme id lokand-base)
- `ttl_seconds` (integer)

### `theme_sync` (~108 tokens)

Theme sync

Compile the latest commit on a custom theme's main branch now (Pro plan; free on every plan until 2027-01-01). Pushes compile on their own; call this to apply a push immediately or to retry. Validates like an upload and, for the live theme, publishes once compiled. Poll theme_get for status.

Input parameters:

- `business_id` (string, required)
- `theme_id` (string, required): A theme id from theme_list (or the system theme id lokand-base)

### `list_assets` (~165 tokens)

List assets

List every image the business owns: its media library (uploads, photos copied from its old website at import, photos the owner attached in chat), its logo and every menu item photo. Each entry has its url, kind, source, where it is used, width/height in pixels and size in bytes (null when unknown), and tags a vision model read off the image: subject (dish, drink, interior, exterior, people, logo, menu), what it shows, whether it matches the dish it is labelled as, quality 1-5, dominant colors and alt text. Use these urls for any site or menu image; never use an outside image.

Input parameters:

- `business_id` (string, required)
- `kind` (string): Only photos or only logos; default any

### `use_asset` (~112 tokens)

Use asset

Put one of the business's own images (a url from list_assets) to use: as the logo (target "logo") or as a menu item's photo (target "item" with item_id). For a site section or block image, pass the same url to update_section / update_block instead.

Input parameters:

- `business_id` (string, required)
- `item_id` (string): The menu item, for target item
- `target` (string, required)
- `url` (string, required): An image url from list_assets

### `suggest_styles` (~114 tokens)

Suggest styles

Recommend looks for the business's website from Lokand's style library (14 hand-made looks, from a Michelin-style 'gastronomique' to a street 'bufe'), read from its menu, prices, logo and photos. Returns the three best fits, how bold to go (safe / distinct / bold, from how much material the business has) and why, and the whole library. Call this before a new look or a redesign, then get_style for the chosen look.

Input parameters:

- `business_id` (string, required)

### `get_style` (~188 tokens)

Get style

Compile one look from the style library into the exact settings to send in ONE update_theme_settings call (palette, fonts, shape, spacing and a signature custom_css on the stable [data-lk] hooks), plus the menu section style to set, the photo to put in the home hero (hero_image, if any), how to shape the home page, the copy voice, and do / don't lists. By default it uses the logo's color when the logo has a strong one. level: safe, distinct or bold (from suggest_styles, or the owner's ask: 'bolder' / 'simpler').

Input parameters:

- `business_id` (string, required)
- `level` (string)
- `seed_color` (string): Lead color to build the palette from, e.g. the owner's brand color
- `style` (string, required)
- `use_logo_colors` (boolean): Default true

### `list_tables` (~63 tokens)

List tables

List the business's tables — the places that each need their own QR code for table ordering (the code tells the order which table it's from). Returns each table's name, zone, code and the order URL its QR encodes.

Input parameters:

- `business_id` (string, required)

### `create_tables` (~179 tokens)

Create tables

Add tables in bulk — each gets its own permanent table-ordering QR code with its name printed under it. Either pass `names` (["Table 1","Terrace 2"]) or `count` with an optional `prefix` ("Table" → "Table 4", "Table 5", … continuing after the highest existing number). Names that already exist are skipped. Follow with export_qr_codes(purpose: table_ordering) to print them.

Input parameters:

- `business_id` (string, required)
- `count` (integer): How many numbered tables to add
- `names` (array): Exact table names
- `prefix` (string): Name before the number; default "Table"
- `start_number` (integer): First number; default continues after existing ones
- `zone` (string): Area, e.g. "Terrace"

### `get_qr_design` (~49 tokens)

Get qr design

Read how the business's printed QR codes look: colors, module and corner style, frame, call-to-action and whether the logo is in the middle.

Input parameters:

- `business_id` (string, required)

### `update_qr_design` (~220 tokens)

Update qr design

Change how the business's printed QR codes look. Only the fields you pass change. The code color must be darker than the background with enough contrast to scan — rejected otherwise. `reset: true` restores the default look.

Input parameters:

- `accent` (string): Frame color: caption text, card fill
- `bg` (string): Background behind the code
- `business_id` (string, required)
- `cta`: Optional text above the code, e.g. "Scan to order". null = none (only the name is printed)
- `eye_style` (string): Corner markers: square, rounded or circle
- `fg` (string): Code color (dark modules)
- `frame` (string): none (code + label only), caption (call-to-action text above the code) or card (filled color card around the code)
- `logo` (boolean): Put the business logo in the middle
- `module_style` (string): square (classic), rounded (soft, joined) or dots
- `reset` (boolean)

### `export_qr_codes` (~381 tokens)

Export qr codes

Render the business's QR codes as a printable file and return a download URL. purpose: menu (one code to the menu site, repeated `copies` times), table_ordering (ONE CODE PER TABLE, each with its table name printed under it — needs tables, see create_tables) or link (its short links). format: home_pdf (A4/Letter sheets with cut guides, for a home printer; layout large=1, medium=4, small=12 per page), press_pdf (print shop: one code per page at size_mm wide, 3 mm bleed, trim box and crop marks, all vector) or svg_zip (one vector SVG per code, for a designer). Uses the saved design (get_qr_design) unless `design` overrides it for this file only.

Input parameters:

- `bleed_mm` (number): press_pdf: default 3
- `business_id` (string, required)
- `copies` (integer): menu/link: copies of each code; default fills one sheet
- `design` (object)
- `format` (string): Default home_pdf
- `layout` (string): home_pdf: default medium
- `paper` (string): home_pdf: default a4
- `print_link` (boolean): Also return print_link: a short link to forward to a print shop, opening a download page with the press PDF + SVGs and their specs (expires in 60 days). Default true for press_pdf and svg_zip
- `purpose` (string, required)
- `shortlink_ids` (array): link: which short links (default all); menu: the short link to encode
- `size_mm` (number): press_pdf/svg_zip: printed code width in mm; default 90
- `table_ids` (array): table_ordering: which tables; default all active ones

### `set_translations` (~142 tokens)

Set translations

Write translations of a business's menu into one locale: section names, dish names and descriptions, menu names, and the business name/description. Use the menu's own wording when the owner has it (e.g. a bilingual printed menu) rather than machine-translating. Fields you leave out keep their current translation. Visitors see a locale once it is in the business's supported_locales (update_business).

Input parameters:

- `business` (object)
- `business_id` (string, required)
- `categories` (array)
- `items` (array)
- `locale` (string, required): Target locale, e.g. en
- `menus` (array)

### `connect_registered_domain` (~92 tokens)

Connect registered domain

STAFF ONLY. Connect a domain already registered in Lokand's registrar account to a business as its menu domain: records it as a managed domain, provisions HTTPS, and points its DNS here. Fails unless the caller is Lokand staff and an owner/admin of the business.

Input parameters:

- `business_id` (string, required): The business id
- `domain` (string, required): The registered domain, e.g. myrestaurant.com

## Diagnostics

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

## Score history

- 2026-11-21: 67
- 2026-11-20: 67
- 2026-11-19: 67
- 2026-11-18: 66
- 2026-11-17: 66
- 2026-11-16: 66
- 2026-11-15: 65
- 2026-11-14: 65
- 2026-11-13: 64
- 2026-11-12: 64
- 2026-11-11: 63
- 2026-11-10: 63

## Common questions

### What is the Lokand Restaurant MCP server?

Lokand Restaurant MCP is listed in the public MCP registry as com.lokand/lokand. Free restaurant websites and menus: read any public menu, or build, import and publish a site. This page covers its hosted endpoint (https://api.lokand.com/mcp).

### Is the Lokand Restaurant MCP server safe to use?

Lokand Restaurant MCP scores 67 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 Lokand Restaurant MCP server expose?

Lokand Restaurant MCP exposes 80 tools: get_started, list_businesses, get_business, list_menus, get_menu, and 75 more. Their descriptions and schemas cost roughly 10,053 tokens of context every time the server is loaded.

### Does the Lokand Restaurant MCP server require authentication?

No. We connected to Lokand Restaurant MCP without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Lokand Restaurant MCP server still maintained?

Lokand Restaurant MCP 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 Lokand Restaurant MCP server?

VerifyMCP ran 13 checks on Lokand Restaurant MCP, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 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://api.lokand.com/mcp
- Website: https://lokand.com/ai/
- Changelog RSS feed: https://verifymcp.io/servers/com-lokand-lokand/api.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-lokand-lokand/api/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-lokand-lokand/api.json
- HTML version of this page: https://verifymcp.io/servers/com-lokand-lokand/api
