Lokand Restaurant MCP
REMOTE · API.LOKAND.COM
Free restaurant websites and menus: read any public menu, or build, import and publish a site.
Available components
Last scanned (22 hours ago)
Scores higher than 52% of remote servers
Reachable. Last reached 21 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 Security60
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (create_full_menu). 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 is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability65
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management35
- Stability check failed: schema churn in the 11 days we've observed: 1 tool removals, 0 breaking changes, 0 auth/transport breaks, 8 additions. See how to fix → Fail
Tool Coverage86
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 58% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 10 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 80 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 21 Nov 26 0
- MCP protocol: Implements a current MCP spec version (2026-07-28). functional
- MCP protocol version: 2025-11-25 → 2026-07-28 functional
- 19 Nov 26 +1
- 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 security
- Server version: 1.0.4 → 1.0.5 functional
- New tool “create_business” functional
- 17 Nov 26 0
- Stability: 0.20 → fail ▼ security
- 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 security
- 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” functional
- “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” cosmetic
- 16 Nov 26 +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.
- 14 Nov 26 +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.
- 12 Nov 26 +1
- Tool “get_style” rewrote its description, which is the text the model reads security
- 11 Nov 26 0
- Stability: unverified → 0.03 ▲ functional
- 10 Nov 26 63
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 21 Nov 2026 · Probed https://api.lokand.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=lokand.com | CN=WE1,O=Google Trust Services,C=US | 18 Nov 2026 | 16 Feb 2027 | ECDSA 256 | ECDSA-SHA256 | 6d5f8514417328e0131c8a5ae2c021a2 |
| SANs: lokand.com, api.lokand.com, *.api.lokand.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of api.lokand.com. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| lokand.com. | DS published | 2371 | 13 | Verified |
| api.lokand.com. | Verified address RRset verified with the apex keys |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.lokand.com/mcp | Verified | 200 | |
| http (plaintext) | http://api.lokand.com/mcp | HTTPS enforced | 301 | https://api.lokand.com/mcp |
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 →
set_featured_items Set featured items ~94
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.
| Name | Type | Req | Description |
|---|---|---|---|
| business_id | string | yes | – |
| item_ids | array | yes | Menu item ids, in display order; [] = automatic |
| page_id | string | – | Defaults to the home page |
No output schema declared.
No examples provided.
set_nav_links Set nav links ~46
Replace the navigation with custom links ([] restores the automatic page list).
| Name | Type | Req | Description |
|---|---|---|---|
| business_id | string | yes | – |
| links | array | yes | Custom navigation; [] restores the automatic page list |
No output schema declared.
No examples provided.
set_page Set page ~161
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).
| Name | Type | Req | Description |
|---|---|---|---|
| business_id | string | yes | – |
| enabled | boolean | – | – |
| make_home | boolean | – | Serve this page at / |
| page_id | string | yes | 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 | – | – | – |
No output schema declared.
No examples provided.
set_system_theme Set system theme ~61
Switch to another system theme (get_site lists `system_themes`). Pages, sections and settings are kept.
| Name | Type | Req | Description |
|---|---|---|---|
| business_id | string | yes | – |
| theme_id | string | yes | A system theme id from get_site (e.g. lokand-base) |
No output schema declared.
No examples provided.
set_theme Set theme ~143
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.
| Name | Type | Req | Description |
|---|---|---|---|
| business_id | string | yes | – |
| 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) |
No output schema declared.
No examples provided.
set_translations Set translations ~142
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).
| Name | Type | Req | Description |
|---|---|---|---|
| business | object | – | – |
| business_id | string | yes | – |
| categories | array | – | – |
| items | array | – | – |
| locale | string | yes | Target locale, e.g. en |
| menus | array | – | – |
No output schema declared.
No examples provided.
suggest_styles Suggest styles ~114
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.
| Name | Type | Req | Description |
|---|---|---|---|
| business_id | string | yes | – |
No output schema declared.
No examples provided.
theme_delete Theme delete ~61
Delete a custom theme and all its stored versions. The live theme can't be deleted — unpublish it first.
| Name | Type | Req | Description |
|---|---|---|---|
| business_id | string | yes | – |
| theme_id | string | yes | A theme id from theme_list (or the system theme id lokand-base) |
No output schema declared.
No examples provided.
theme_get Theme get ~75
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).
| Name | Type | Req | Description |
|---|---|---|---|
| business_id | string | yes | – |
| theme_id | string | yes | A theme id from theme_list (or the system theme id lokand-base) |
No output schema declared.
No examples provided.
theme_git_access Theme git access ~134
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).
| Name | Type | Req | Description |
|---|---|---|---|
| business_id | string | yes | – |
| scope | string | – | – |
| theme_id | string | yes | A theme id from theme_list (or the system theme id lokand-base) |
| ttl_seconds | integer | – | – |
No output schema declared.
No examples provided.
theme_history Theme history ~81
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.
| Name | Type | Req | Description |
|---|---|---|---|
| business_id | string | yes | – |
| limit | integer | – | – |
| theme_id | string | yes | A theme id from theme_list (or the system theme id lokand-base) |
No output schema declared.
No examples provided.
theme_list Theme list ~66
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).
| Name | Type | Req | Description |
|---|---|---|---|
| business_id | string | yes | – |
No output schema declared.
No examples provided.
theme_publish Theme publish ~98
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).
| Name | Type | Req | Description |
|---|---|---|---|
| business_id | string | yes | – |
| theme_id | string | yes | A theme id from theme_list (or the system theme id lokand-base) |
No output schema declared.
No examples provided.
theme_pull Theme pull ~178
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.
| Name | Type | Req | Description |
|---|---|---|---|
| business_id | string | yes | – |
| 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 | yes | A theme id from theme_list (or the system theme id lokand-base) |
No output schema declared.
No examples provided.
theme_rollback Theme rollback ~116
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.
| Name | Type | Req | Description |
|---|---|---|---|
| business_id | string | yes | – |
| commit | string | – | Commit hash from theme_history |
| theme_id | string | yes | A theme id from theme_list (or the system theme id lokand-base) |
No output schema declared.
No examples provided.
theme_sync Theme sync ~108
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.
| Name | Type | Req | Description |
|---|---|---|---|
| business_id | string | yes | – |
| theme_id | string | yes | A theme id from theme_list (or the system theme id lokand-base) |
No output schema declared.
No examples provided.
theme_unpublish Theme unpublish ~40
Stop using custom theme code: the site goes back to its system theme. The custom theme is kept as unpublished.
| Name | Type | Req | Description |
|---|---|---|---|
| business_id | string | yes | – |
No output schema declared.
No examples provided.
theme_upload Theme upload ~253
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.
| Name | Type | Req | Description |
|---|---|---|---|
| allow_live | boolean | – | With the live theme's id: update the live site in place |
| business_id | string | yes | – |
| files | object | yes | 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) |
No output schema declared.
No examples provided.
theme_write_files Theme write files ~237
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.
| Name | Type | Req | Description |
|---|---|---|---|
| business_id | string | yes | – |
| 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 | yes | A theme id from theme_list (or the system theme id lokand-base) |
No output schema declared.
No examples provided.
update_block Update block ~152
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.
| Name | Type | Req | Description |
|---|---|---|---|
| block_id | string | yes | Block id from get_site |
| business_id | string | yes | – |
| hidden | boolean | – | – |
| page_id | string | yes | Page id, e.g. home, menu, about, loyalty |
| section_id | string | yes | Section id from get_site |
| settings | – | – | Settings as a JSON merge patch (null removes a key). get_site lists each type's settings. |
No output schema declared.
No examples provided.
update_business Update business ~545
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.
| Name | Type | Req | Description |
|---|---|---|---|
| about | – | – | – |
| business_id | string | yes | – |
| 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 |
No output schema declared.
No examples provided.
update_item Update item ~304
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).
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | – |
| 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… |
No output schema declared.
No examples provided.
update_loyalty_card Update loyalty card ~182
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).
| Name | Type | Req | Description |
|---|---|---|---|
| business_id | string | yes | – |
| 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) |
No output schema declared.
No examples provided.
update_menu Update menu ~78
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.
| Name | Type | Req | Description |
|---|---|---|---|
| description | – | – | – |
| is_active | boolean | – | Whether the menu is live on the public site |
| menu_id | string | yes | – |
| name | string | – | – |
No output schema declared.
No examples provided.
update_qr_design Update qr design ~220
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.
| Name | Type | Req | Description |
|---|---|---|---|
| accent | string | – | Frame color: caption text, card fill |
| bg | string | – | Background behind the code |
| business_id | string | yes | – |
| 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 | – | – |
No output schema declared.
No examples provided.
update_section Update section ~160
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.
| Name | Type | Req | Description |
|---|---|---|---|
| business_id | string | yes | – |
| hidden | boolean | – | – |
| page_id | string | yes | Page id, e.g. home, menu, about, loyalty |
| section_id | string | yes | Section id from get_site |
| settings | – | – | Settings as a JSON merge patch (null removes a key). get_site lists each type's settings. |
No output schema declared.
No examples provided.
update_site Update site ~132
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.
| Name | Type | Req | Description |
|---|---|---|---|
| business_id | string | yes | – |
| patch | object | yes | RFC 7386 JSON merge patch on the whole theme data document |
No output schema declared.
No examples provided.
update_theme Update theme ~142
Legacy look op: patch v2-style `tokens` (colors, fonts, radius, hero layout, …) or set custom CSS. Prefer update_theme_settings.
| Name | Type | Req | Description |
|---|---|---|---|
| business_id | string | yes | – |
| 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… |
No output schema declared.
No examples provided.
update_theme_settings Update theme settings ~111
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.
| Name | Type | Req | Description |
|---|---|---|---|
| business_id | string | yes | – |
| settings | object | yes | Merge patch on the theme's global settings |
No output schema declared.
No examples provided.
use_asset Use asset ~112
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.
| Name | Type | Req | Description |
|---|---|---|---|
| business_id | string | yes | – |
| item_id | string | – | The menu item, for target item |
| target | string | yes | – |
| url | string | yes | An image url from list_assets |
No output schema declared.
No examples provided.
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.
remote · api.lokand.com
claude mcp add --transport http com-lokand-lokand 'https://api.lokand.com/mcp'
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.