Skip to content

MCP servers › com.lokand › lokand

MCP server · registry snapshot 2026-11-17 · last tested 2026-11-17

lokand MCP server

Registry name com.lokand/lokand

Lokand Restaurant MCP — the publisher's title

by lokand.com · domain (the registry's namespace rule)Website ↗

Free restaurant websites and menus: read any public menu, or build, import and publish a site. — the publisher's description

1 of 2 record checks metRead-only · tools listed 2026-11-17version 1.0.4streamable HTTP78 tools

Summary

com.lokand/lokand is a remote MCP server listed in the official MCP registry at version 1.0.4, under the namespace of the domain lokand.com. On 2026-11-17 ProtocolProbe connected to it in read-only mode and read its inventory: 78 tools, 0 resources and 0 prompts.

Record checks

1 of 2 record checks met · 7 do not apply

  • met: Registry entry is active and says how to run it
  • not met: Source repository link opens
  • not applicable: Repository is not archived
  • not applicable: Code pushed to the repository in the 90 days before our check
  • not applicable: Repository publishes a security policy (SECURITY.md)
  • not applicable: Package names its licence with a standard (SPDX) identifier
  • not applicable: The version the registry lists can be installed and is not withdrawn
  • not applicable: npm package carries build provenance (attestation)
  • not applicable: No known critical or high advisory in the package or its dependencies
  • Not ranked by downloads: a remote server publishes no download figure
  • Not ranked by stars: no public GitHub repository

From public records, not a safety rating. Each check with its reason

Operate this server? Correct a fact · README badge · Run the checks yourself · Claim it

Key facts

Runs
remote (hosted by the publisher)
Transport
streamable HTTP
Your own values
none declared (not a guarantee)
Sign-in
none needed to open a session
Tools
78
Last tested
2026-11-17

Tool list size

41,564 tokens on Claude Opus 5.5

Added to every request that loads this server's tools (78 tools). Counted with Anthropic's token counter on 2026-11-17, from the tool list we read on 2026-11-17. Median across 28,560 counted servers: 2,657 tokens. How it is counted

How a client gets in

Connects without signing in

Read from the server's public metadata on 2026-11-17 (api.lokand.com), in our read-only connection; no tool was called. It may have changed since. How it is read

Tool list at the three APIs

Not sent yet for this version (1.0.4).

Add to your client

Observed fact

This server accepted a session without any credential and lists 52 tools whose name or declaration suggests they change data (create_full_menu, create_menu, add_category, add_item, update_item and 47 more). That is our reading of the names; we did not call them. Source: our connection, 2026-11-17.

How fresh this is

Live-tested
yes, a real session (not a text-only review)
Last tested
2026-11-17
Mode
read-only (no tool calls)
Latest version
1.0.4, published 2026-11-17 (registry, as of the 2026-11-17 snapshot)
First listed version
2026-11-10 (earliest version still in the registry; older removed versions would be earlier)
Version history
4 versions listed, 2026-11-10 to 2026-11-17; 4 in the 90 days before the 2026-11-17 snapshot.
Most recent 4 versions
  • 1.0.4 · 2026-11-17
  • 1.0.3 · 2026-11-17
  • 1.0.2 · 2026-11-10
  • 1.0.0 · 2026-11-10
(versions still listed in the registry only)
Registry data
snapshot 2026-11-17
Package and repository
checked 2026-11-17
Engine
mcp-runtime-engine@0.1.0 · sdk@1.32.0

Dead or stale signals

None found in the records we hold

Looked for and not found: deprecated in the registry. Does not apply: listed version cannot be installed or is withdrawn; repository link does not open; repository archived; no push in over 365 days. Each line is a dated fact from a public record. It does not say whether the server still works, and a record can change after the date shown.

Changes since the last refresh

Version 1.0.2 (published 2026-11-10) → 1.0.4 (published 2026-11-17), between the registry lists of 2026-11-16 and 2026-11-17.

No release note: the registry entry links no GitHub repository.

Source: the official MCP Registry list on 2026-11-16 and on 2026-11-17; release notes from the GitHub Releases API, checked 2026-11-17.

What it is

What does this server offer?

Observed inventory
78tools
0resources
0prompts

None of its 78 tools are described as changing anything. For 78 the reading was uncertain, so no mark is shown.

  • “How to use Lokand as an agent: the recipes for creating a restaurant for a customer, editing menus, and handing over ownership.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    Takes no inputs.

  • list_businesseson 3 other servers

    “List the businesses the signed-in user is a member of (id, name, slug, role).”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    Takes no inputs.

  • “Look up a public Lokand restaurant/business by its slug.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    1 input, 1 required
    • slugstringrequired“The business's public slug”
  • “List the active menus of a public Lokand restaurant by its slug.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    1 input, 1 required
    • slugstringrequired“The business's public slug”
  • “Fetch a single menu (categories + items with prices) of a public Lokand restaurant.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    2 inputs, 2 required
    • slugstringrequired“The business's public slug”
    • menu_idstringrequired“The menu id from list_menus”
  • “Private status of a business the caller manages: profile (including unpublished state), all menus (active and inactive), and plan.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    1 input, 1 required
    • business_idstringrequired“The business id”
  • create_full_menu

    “Create a COMPLETE menu (sections + items) in one call — prefer this over separate create_menu/add_category/add_item calls.”

    Publisher declares: read-only no · destructive yes · idempotent no · open-world yes

    3 inputs, 2 required
    • business_idstringrequired
    • menuobjectrequired
    • replaceboolean“Deactivate the business's other menus in the same step”
  • create_menu

    “Create an EMPTY menu on a business the caller manages (add sections with add_category, dishes with add_item).”

    Publisher declares: read-only no · destructive no · idempotent no · open-world yes

    5 inputs, 2 required
    • business_idstringrequired
    • idstring“Optional caller-chosen id (8-64 chars).”
    • namestringrequired“Menu name, e.g.”
    • descriptionstring
    • is_activeboolean“Whether the menu is live on the public site”
  • add_category

    “Add a category (section) to a menu.”

    Publisher declares: read-only no · destructive no · idempotent no · open-world yes

    4 inputs, 2 required
    • menu_idstringrequired
    • idstring“Optional caller-chosen id (8-64 chars).”
    • namestringrequired“Category name, e.g.”
    • sort_orderinteger
  • “Add a dish/item to a menu (optionally inside a category).”

    Publisher declares: read-only no · destructive no · idempotent no · open-world yes

    10 inputs, 2 required
    • menu_idstringrequired
    • idstring“Optional caller-chosen id (8-64 chars).”
    • category_idstring
    • namestringrequired“Item name, e.g.”
    • descriptionstring
    • pricenumber“Price in the business's currency.”
    • variationsarray“Variations of this dish — sizes, volumes, portions, cuts — each with its own ABSOLUTE price (not a surcharge): e.g.”
    • is_availableboolean
    • sort_orderinteger
    • dietary_infoobject“Allergen and dietary labels shown to diners.”
  • “Update a menu item's fields (name, description, price, availability, category, sort order).”

    Publisher declares: read-only no · destructive yes · idempotent no · open-world yes

    9 inputs, 1 required
    • item_idstringrequired
    • namestring
    • descriptionstring or null
    • dietary_infoobject or null“Allergen and dietary labels shown to diners.”
    • pricenumber
    • variationsarray or null“Replaces the item's whole variation list.”
    • is_availableboolean
    • category_idstring or null
    • sort_orderinteger
  • “Delete a menu item.”

    Publisher declares: read-only no · destructive yes · idempotent no · open-world yes

    1 input, 1 required
    • item_idstringrequired
Show 66 more tools
  • “Rename a menu, change its description, or switch it on/off on the public site (is_active).”

    Publisher declares: read-only no · destructive yes · idempotent no · open-world yes

    4 inputs, 1 required
    • menu_idstringrequired
    • namestring
    • descriptionstring or null
    • is_activeboolean“Whether the menu is live on the public site”
  • delete_menu

    “Permanently delete a menu together with ALL of its sections and items.”

    Publisher declares: read-only no · destructive yes · idempotent no · open-world yes

    1 input, 1 required
    • menu_idstringrequired
  • rename_category

    “Rename a menu category (section).”

    Publisher declares: read-only no · destructive yes · idempotent no · open-world yes

    2 inputs, 2 required
    • category_idstringrequired
    • namestringrequired“The new name”
  • reorder_categories

    “Set the order of a menu's categories (sections).”

    Publisher declares: read-only no · destructive yes · idempotent no · open-world yes

    2 inputs, 2 required
    • menu_idstringrequired
    • category_idsarrayrequired
  • delete_categoryon 4 other servers

    “Delete a menu category (section).”

    Publisher declares: read-only no · destructive yes · idempotent no · open-world yes

    1 input, 1 required
    • category_idstringrequired
  • reorder_itemson 1 other server

    “Set the order of the items in one section of a menu.”

    Publisher declares: read-only no · destructive yes · idempotent no · open-world yes

    3 inputs, 3 required
    • menu_idstringrequired
    • category_idstring or nullrequired“The section being ordered; null = items without a section”
    • item_idsarrayrequired
  • update_businesson 4 other servers

    “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 det…”

    Publisher declares: read-only no · destructive yes · idempotent no · open-world yes

    14 inputs, 1 required
    • business_idstringrequired
    • namestring
    • descriptionstring or null
    • aboutstring or null
    • hoursobject“Opening hours keyed mon..sun, each {"open":"10:30","close":"22:00"} or {"closed":true}”
    • contact_infoobject“Contact info: phone, email, address, instagram”
    • currency_codestring
    • default_localestring
    • supported_localesarray“Locales visitors can switch between, e.g.”
    • menu_optionsobject“How the published menu presents itself: `menuNotice` (free text shown above the menu, in the owner's own words), `showPriceEffectiveDate`, and `orderingExclude…”
    • country_codestring“ISO 3166-1 alpha-2 country the business operates in.”
    • legal_infoobject“Business details published on the site when filled in: tradeName, taxNumber, registrationNumber, registeredAddress, contactEmail, contactPhone, plus `extra` la…”
    • placeobject“Where the business is and what kind of place it is: lat/lng; address {streetAddress, addressLocality (district), addressRegion (city or province), postalCode, …”
    • maps_urlstring“A Google Maps, Apple Maps, Yandex or OpenStreetMap link (short share links work), or a "lat, lng" pair.”
  • “Switch the site to a system theme with `theme_id` (lokand-base; get_site lists them; pages, sections and settings are kept).”

    Publisher declares: read-only no · destructive yes · idempotent no · open-world yes

    3 inputs, 1 required
    • business_idstringrequired
    • theme_idstring“A system theme id from get_site (e.g.”
    • theme_configobject“Legacy: merge patch such as {"colors":{"primary":"#aa3300"},"fonts":{"heading":"..."}}”
  • “Publish (or unpublish) the business's public menu site at https://<slug>.lokand.co.”

    Publisher declares: read-only no · destructive yes · idempotent no · open-world yes

    2 inputs, 1 required
    • business_idstringrequired
    • publishboolean“true to go live, false to take the site offline”
  • 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).”

    Publisher declares: read-only no · destructive no · idempotent no · open-world yes

    14 inputs, 3 required
    • client_idstringrequired“Registered OAuth client id”
    • client_secretstringrequired“The client's secret”
    • namestringrequired“Restaurant name”
    • slugstring“Optional site slug (<slug>.lokand.co); generated from the name when omitted.”
    • descriptionstring
    • customer_emailstring“Customer's email: binds the claim to it and sends them the claim link”
    • menuobject“The full menu, inline — pass this to go live in one call instead of separate create_menu/add_category/add_item calls”
    • hoursobject“Opening hours keyed mon..sun, each {"open":"10:30","close":"22:00"} or {"closed":true}”
    • contact_infoobject“Contact info: phone, email, address, instagram”
    • placeobject“Where the business is and what kind of place it is: lat/lng; address {streetAddress, addressLocality (district), addressRegion (city or province), postalCode, …”
    • maps_urlstring“A Google Maps, Apple Maps, Yandex or OpenStreetMap link (short share links work), or a "lat, lng" pair.”
    • currency_codestring“ISO currency for menu prices, e.g.”
    • themeobject
    • publishboolean“Put the site live immediately (default true).”
  • claim_statuson 5 other servers

    “Check whether the customer has claimed an agent-created restaurant.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    3 inputs, 3 required
    • client_idstringrequired“Registered OAuth client id”
    • client_secretstringrequired“The client's secret”
    • claim_tokenstringrequired
  • create_checkout_linkon 36 other servers

    “Create a Stripe Checkout link to upgrade a business to a paid plan.”

    Publisher declares: read-only no · destructive no · idempotent no · open-world yes

    3 inputs, 2 required
    • business_idstringrequired
    • product_keystringrequired“The plan to purchase (Pro is monthly-only)”
    • customer_countrystring“Customer's ISO country code, e.g.”
  • get_billing_summary

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

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    1 input, 1 required
    • business_idstringrequired
  • “Start an AI import of a restaurant's menu from the URL of its existing website.”

    Publisher declares: read-only no · destructive no · idempotent no · open-world yes

    2 inputs, 2 required
    • business_idstringrequired
    • urlstringrequired“Public https URL of the site to import the menu from”
  • import_statuson 2 other servers

    “Check an AI menu import: processing, complete (draft ready to commit), or failed.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    1 input, 1 required
    • import_idstringrequired
  • commit_importon 2 other servers

    “Commit a completed AI menu import as a real menu (creates the menu, categories, and items).”

    Publisher declares: read-only no · destructive no · idempotent no · open-world yes

    1 input, 1 required
    • import_idstringrequired
  • check_complianceon 16 other servers

    “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.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    2 inputs, 1 required
    • business_idstringrequired
    • countrystring“ISO country to check against.”
  • 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.”

    Publisher declares: read-only no · destructive yes · idempotent no · open-world yes

    4 inputs, 1 required
    • business_idstringrequired
    • countrystring“Defaults to the business's own country_code.”
    • overwriteboolean“false (default) fills only options the owner hasn't set; true replaces their existing values.”
    • localestring“Language for any suggested copy.”
  • “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 them…”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    2 inputs, 1 required
    • business_idstringrequired
    • detailstring
  • “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).”

    Publisher declares: read-only no · destructive yes · idempotent no · open-world yes

    2 inputs, 2 required
    • business_idstringrequired
    • patchobjectrequired“RFC 7386 JSON merge patch on the whole theme data document”
  • update_theme_settingson 1 other server

    “Merge-patch the theme's global settings (keys from get_site.theme.theme_settings, e.g.”

    Publisher declares: read-only no · destructive yes · idempotent no · open-world yes

    2 inputs, 2 required
    • business_idstringrequired
    • settingsobjectrequired“Merge patch on the theme's global settings”
  • update_themeon 3 other servers

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

    Publisher declares: read-only no · destructive yes · idempotent no · open-world yes

    3 inputs, 1 required
    • business_idstringrequired
    • tokensobject“Merge patch on theme tokens: colors{primary,accent,bg,fg,primaryFg,card,muted,line,line2}, loyalty{bg,ink}, fonts{heading,body,mono}, radius, radiusButton, her…”
    • custom_cssstring or null“Extra CSS; null clears it.”
  • apply_templateon 1 other server

    “Rebuild the site's pages and sections from a segment template (cafe, ghost-kitchen, fine-dining, chain, bar, bakery — see get_site.templates).”

    Publisher declares: read-only no · destructive yes · idempotent no · open-world yes

    3 inputs, 2 required
    • business_idstringrequired
    • templatestringrequired“cafe | ghost-kitchen | fine-dining | chain | bar | bakery”
    • keep_themeboolean“Keep the current style instead of the template's (default false)”
  • apply_site_preset

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

    Publisher declares: read-only no · destructive yes · idempotent no · open-world yes

    3 inputs, 2 required
    • business_idstringrequired
    • presetstringrequired“cafe | ghost-kitchen | fine-dining | chain | bar | bakery”
    • keep_themeboolean
  • “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.”

    Publisher declares: read-only no · destructive yes · idempotent no · open-world yes

    8 inputs, 2 required
    • business_idstringrequired
    • page_idstringrequired“Page id, e.g.”
    • enabledboolean
    • show_in_navboolean
    • titlestring or null
    • pathstring“One segment like /wine”
    • make_homeboolean“Serve this page at /”
    • positioninteger“Move the page to this position in the navigation”
  • “Add a new page with a text section (add more with add_section).”

    Publisher declares: read-only no · destructive yes · idempotent no · open-world yes

    4 inputs, 2 required
    • business_idstringrequired
    • titlestringrequired
    • pathstring
    • positioninteger“0-based position”
  • “Remove a custom page and its sections.”

    Publisher declares: read-only no · destructive yes · idempotent no · open-world yes

    2 inputs, 2 required
    • business_idstringrequired
    • page_idstringrequired“Page id, e.g.”
  • set_nav_links

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

    Publisher declares: read-only no · destructive yes · idempotent no · open-world yes

    2 inputs, 2 required
    • business_idstringrequired
    • linksarrayrequired“Custom navigation; [] restores the automatic page list”
  • “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).”

    Publisher declares: read-only no · destructive yes · idempotent no · open-world yes

    7 inputs, 2 required
    • business_idstringrequired
    • page_idstringrequired“Page id, e.g.”
    • typestring“Section type from get_site”
    • kind“Alias of type”
    • settingsobject“Settings as a JSON merge patch (null removes a key).”
    • positioninteger“0-based position”
    • presetstring“Start from one of the type's presets”
  • update_sectionon 4 other servers

    “Change one section: merge-patch its settings (null removes a key; settings: null resets them all) and/or hide/show it.”

    Publisher declares: read-only no · destructive yes · idempotent no · open-world yes

    5 inputs, 3 required
    • business_idstringrequired
    • page_idstringrequired“Page id, e.g.”
    • section_idstringrequired“Section id from get_site”
    • settingsobject or null“Settings as a JSON merge patch (null removes a key).”
    • hiddenboolean
  • remove_sectionon 2 other servers

    “Remove a section from a page.”

    Publisher declares: read-only no · destructive yes · idempotent no · open-world yes

    3 inputs, 3 required
    • business_idstringrequired
    • page_idstringrequired“Page id, e.g.”
    • section_idstringrequired“Section id from get_site”
  • move_sectionon 2 other servers

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

    Publisher declares: read-only no · destructive yes · idempotent no · open-world yes

    4 inputs, 4 required
    • business_idstringrequired
    • page_idstringrequired“Page id, e.g.”
    • section_idstringrequired“Section id from get_site”
    • positionintegerrequired“0-based position”
  • “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).”

    Publisher declares: read-only no · destructive yes · idempotent no · open-world yes

    8 inputs, 4 required
    • business_idstringrequired
    • page_idstringrequired“Page id, e.g.”
    • section_idstringrequired“Section id from get_site”
    • parent_block_idstring“Nest inside this block instead of the section”
    • typestringrequired“Block type the section accepts (see get_site)”
    • settingsobject“Settings as a JSON merge patch (null removes a key).”
    • positioninteger“0-based position”
    • presetstring“Start from one of the block type's presets”
  • update_blockon 4 other servers

    “Merge-patch one block's settings (null removes a key) and/or hide/show it.”

    Publisher declares: read-only no · destructive yes · idempotent no · open-world yes

    6 inputs, 4 required
    • business_idstringrequired
    • page_idstringrequired“Page id, e.g.”
    • section_idstringrequired“Section id from get_site”
    • block_idstringrequired“Block id from get_site”
    • settingsobject or null“Settings as a JSON merge patch (null removes a key).”
    • hiddenboolean
  • “Move a block to a 0-based position among its siblings.”

    Publisher declares: read-only no · destructive yes · idempotent no · open-world yes

    5 inputs, 5 required
    • business_idstringrequired
    • page_idstringrequired“Page id, e.g.”
    • section_idstringrequired“Section id from get_site”
    • block_idstringrequired“Block id from get_site”
    • positionintegerrequired“0-based position”
  • remove_blockon 4 other servers

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

    Publisher declares: read-only no · destructive yes · idempotent no · open-world yes

    4 inputs, 4 required
    • business_idstringrequired
    • page_idstringrequired“Page id, e.g.”
    • section_idstringrequired“Section id from get_site”
    • block_idstringrequired“Block id from get_site”
  • 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).”

    Publisher declares: read-only no · destructive yes · idempotent no · open-world yes

    3 inputs, 2 required
    • business_idstringrequired
    • item_idsarrayrequired“Menu item ids, in display order; [] = automatic”
    • page_idstring“Defaults to the home page”
  • set_system_theme

    “Switch to another system theme (get_site lists `system_themes`).”

    Publisher declares: read-only no · destructive yes · idempotent no · open-world yes

    2 inputs, 2 required
    • business_idstringrequired
    • theme_idstringrequired“A system theme id from get_site (e.g.”
  • make_menu_only

    “Turn the site into a single menu page (the menu becomes the home page, every other page is disabled).”

    Publisher declares: read-only no · destructive yes · idempotent no · open-world yes

    1 input, 1 required
    • business_idstringrequired
  • 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.”

    Publisher declares: read-only no · destructive yes · idempotent no · open-world yes

    2 inputs, 2 required
    • business_idstringrequired
    • linkedbooleanrequired“true = show the brand's shared site here; false = this location's own site”
  • 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).”

    Publisher declares: read-only no · destructive yes · idempotent no · open-world yes

    1 input, 1 required
    • business_idstringrequired
  • 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).”

    Publisher declares: read-only no · destructive yes · idempotent no · open-world yes

    1 input, 1 required
    • business_idstringrequired
  • 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.”

    Publisher declares: read-only no · destructive yes · idempotent no · open-world yes

    5 inputs, 1 required
    • business_idstringrequired
    • stamps_requiredinteger“Stamps needed for one reward (2-30)”
    • reward_textstring“What the guest gets, e.g.”
    • is_activeboolean“Whether diners can join and collect stamps”
    • card_configobject or null“The card's look — colors{cardBg,cardFg,stampFilled,stampEmpty}, stampIcon, headline, subline.”
  • theme_list

    “List the business's custom themes (id, name, role live|unpublished|development, version, upload status) and the system themes.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    1 input, 1 required
    • business_idstringrequired
  • 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).”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    2 inputs, 2 required
    • business_idstringrequired
    • theme_idstringrequired“A theme id from theme_list (or the system theme id lokand-base)”
  • theme_pull

    “Download a theme's files ({path: text}).”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    5 inputs, 2 required
    • business_idstringrequired
    • theme_idstringrequired“A theme id from theme_list (or the system theme id lokand-base)”
    • list_onlyboolean“Return only {path, size} for every file”
    • pathsarray“Return only these files”
    • searchstring“Case-insensitive text to find, e.g.”
  • theme_upload

    “Upload a complete custom theme (Pro plan) as a new commit in its Git repo.”

    Publisher declares: read-only no · destructive yes · idempotent no · open-world yes

    7 inputs, 2 required
    • business_idstringrequired
    • filesobjectrequired“Theme files by path, e.g.”
    • namestring
    • theme_idstring“A theme id from theme_list (or the system theme id lokand-base)”
    • rolestring“development = your private work-in-progress theme (one per user, replaced on each upload); unpublished = a saved theme ready to publish”
    • allow_liveboolean“With the live theme's id: update the live site in place”
    • messagestring“Commit message”
  • theme_write_files

    “Change some files of a custom theme (Pro plan) as one new commit: files maps path → whole new text (null deletes), edits are find/replace changes.”

    Publisher declares: read-only no · destructive yes · idempotent no · open-world yes

    7 inputs, 2 required
    • business_idstringrequired
    • theme_idstringrequired“A theme id from theme_list (or the system theme id lokand-base)”
    • filesobject“path → whole new file text, or null to delete the file”
    • editsarray“Find/replace changes inside existing files.”
    • namestring
    • messagestring“Commit message describing the change”
    • publishboolean“Go live once compiled (always the case when editing the live theme)”
  • theme_publish

    “Make a custom theme the live site's code (Pro plan).”

    Publisher declares: read-only no · destructive yes · idempotent no · open-world yes

    2 inputs, 2 required
    • business_idstringrequired
    • theme_idstringrequired“A theme id from theme_list (or the system theme id lokand-base)”
  • theme_unpublish

    “Stop using custom theme code: the site goes back to its system theme.”

    Publisher declares: read-only no · destructive yes · idempotent no · open-world yes

    1 input, 1 required
    • business_idstringrequired
  • theme_delete

    “Delete a custom theme and all its stored versions.”

    Publisher declares: read-only no · destructive yes · idempotent no · open-world yes

    2 inputs, 2 required
    • business_idstringrequired
    • theme_idstringrequired“A theme id from theme_list (or the system theme id lokand-base)”
  • 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 f…”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    2 inputs, 1 required
    • business_idstringrequired
    • localestring“Defaults to the business's default locale”
  • theme_history

    “The commit history of a custom theme's code, newest first: hash, message, author, time.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    3 inputs, 2 required
    • business_idstringrequired
    • theme_idstringrequired“A theme id from theme_list (or the system theme id lokand-base)”
    • limitinteger
  • theme_rollback

    “Restore a custom theme's code to an earlier commit (Pro plan).”

    Publisher declares: read-only no · destructive yes · idempotent no · open-world yes

    3 inputs, 2 required
    • business_idstringrequired
    • theme_idstringrequired“A theme id from theme_list (or the system theme id lokand-base)”
    • commitstring“Commit hash from theme_history”
  • 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).”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    4 inputs, 2 required
    • business_idstringrequired
    • theme_idstringrequired“A theme id from theme_list (or the system theme id lokand-base)”
    • scopestring
    • ttl_secondsinteger
  • theme_sync

    “Compile the latest commit on a custom theme's main branch now (Pro plan).”

    Publisher declares: read-only no · destructive yes · idempotent no · open-world yes

    2 inputs, 2 required
    • business_idstringrequired
    • theme_idstringrequired“A theme id from theme_list (or the system theme id lokand-base)”
  • “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.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    2 inputs, 1 required
    • business_idstringrequired
    • kindstring“Only photos or only logos; default any”
  • 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).”

    Publisher declares: read-only no · destructive no · idempotent no · open-world yes

    4 inputs, 3 required
    • business_idstringrequired
    • urlstringrequired“An image url from list_assets”
    • targetstringrequired
    • item_idstring“The menu item, for target item”
  • 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.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    1 input, 1 required
    • business_idstringrequired
  • “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), pl…”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    5 inputs, 2 required
    • business_idstringrequired
    • stylestringrequired
    • levelstring
    • seed_colorstring“Lead color to build the palette from, e.g.”
    • use_logo_colorsboolean“Default true”
  • “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).”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    1 input, 1 required
    • business_idstringrequired
  • create_tables

    “Add tables in bulk — each gets its own permanent table-ordering QR code with its name printed under it.”

    Publisher declares: read-only no · destructive no · idempotent no · open-world yes

    6 inputs, 1 required
    • business_idstringrequired
    • namesarray“Exact table names”
    • countinteger“How many numbered tables to add”
    • prefixstring“Name before the number; default "Table"”
    • start_numberinteger“First number; default continues after existing ones”
    • zonestring“Area, e.g.”
  • 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.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    1 input, 1 required
    • business_idstringrequired
  • update_qr_design

    “Change how the business's printed QR codes look.”

    Publisher declares: read-only no · destructive no · idempotent no · open-world yes

    10 inputs, 1 required
    • business_idstringrequired
    • fgstring“Code color (dark modules)”
    • bgstring“Background behind the code”
    • module_stylestring“square (classic), rounded (soft, joined) or dots”
    • eye_stylestring“Corner markers: square, rounded or circle”
    • logoboolean“Put the business logo in the middle”
    • framestring“none (code + label only), caption (call-to-action text above the code) or card (filled color card around the code)”
    • accentstring“Frame color: caption text, card fill”
    • ctastring or null“Optional text above the code, e.g.”
    • resetboolean
  • export_qr_codes

    “Render the business's QR codes as a printable file and return a download URL.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    12 inputs, 2 required
    • business_idstringrequired
    • purposestringrequired
    • formatstring“Default home_pdf”
    • table_idsarray“table_ordering: which tables; default all active ones”
    • shortlink_idsarray“link: which short links (default all); menu: the short link to encode”
    • copiesinteger“menu/link: copies of each code; default fills one sheet”
    • layoutstring“home_pdf: default medium”
    • paperstring“home_pdf: default a4”
    • size_mmnumber“press_pdf/svg_zip: printed code width in mm; default 90”
    • bleed_mmnumber“press_pdf: default 3”
    • designobject
    • print_linkboolean“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).”
  • set_translationson 2 other servers

    “Write translations of a business's menu into one locale: section names, dish names and descriptions, menu names, and the business name/description.”

    Publisher declares: read-only no · destructive no · idempotent no · open-world yes

    6 inputs, 2 required
    • business_idstringrequired
    • localestringrequired“Target locale, e.g.”
    • businessobject
    • menusarray
    • categoriesarray
    • itemsarray

Each quoted sentence is the first sentence of the publisher’s own description. The kind of tool and the “changes data” mark are our AI model’s reading of that description, not something we tested: two differently worded runs had to agree, otherwise no label is shown, and nobody has checked them by hand. A tool without the “changes data” mark is described as only reading, searching or calculating, or the two runs did not agree. No tool was called. Read the publisher’s full description before relying on it. “Publisher declares” lists the hints the server itself sends with the tool (MCP annotations: read-only, destructive, idempotent, open-world); they are the publisher's claims, not checked by us. Inputs are the parameters in the tool's own input schema: name, declared type, whether it is required, and the first sentence of its description. Read 2026-11-17.

How well are its tools described?

Features #4 and #5

How clearly this server's own tool descriptions say what a tool does, and how consistent its tool list is. The first part is an AI model's yes/no reading of each description; the second part is counted. We do not turn it into a grade.

Descriptions

AI reading of each description

No AI reading was available for this server's tools (the two runs did not agree, or the listing was not reviewed).

Counted from the listing

Parameters with a description
57% of 277
Tools with a description
100% of 78
Typical description length
218 characters

The tool set

Counted from the listing

Tools
78
Size of the list
about 29,312 tokens for an agent to load (characters ÷ 4)
Naming
78 of 78 names use snake_case

AI reading: easy to mix up

No pair found.

The AI items cover 0 of 78 tools: for a tool where two differently worded runs disagreed, that item is left out. They were not checked by hand, and no tool was called. “Easy to mix up” means two tools whose names or descriptions overlap without saying how they differ; the AI found none, comparing tools within groups of 40. We do not rate whether the tool set is complete or whether side effects are spelled out, because our AI reading of those was not reliable enough.

How do I add it to my client?

Config from the registry entry

From the remote endpoint (Streamable HTTP)

We connected to this URL on 2026-11-17 (a read-only session: no tool was called).

Add to CursorAn install link in the format Cursor documents, holding the Cursor config below.

Claude Desktop or claude.ai
Settings → Connectors → Add custom connector, then paste:
https://api.lokand.com/mcp
Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json
{
  "mcpServers": {
    "lokand": {
      "url": "https://api.lokand.com/mcp"
    }
  }
}
VS Code · .vscode/mcp.json
{
  "servers": {
    "lokand": {
      "type": "http",
      "url": "https://api.lokand.com/mcp"
    }
  }
}
VS Code (command line) · Bash or zsh terminal (macOS, Linux)
code --add-mcp '{"name":"lokand","type":"http","url":"https://api.lokand.com/mcp"}'
Claude Code
claude mcp add --transport http lokand https://api.lokand.com/mcp
Cline · cline_mcp_settings.json (Cline CLI: ~/.cline/data/settings/; in the editor: MCP Servers → Configure → Configure MCP Servers)
{
  "mcpServers": {
    "lokand": {
      "type": "streamableHttp",
      "url": "https://api.lokand.com/mcp",
      "disabled": false,
      "autoApprove": []
    }
  }
}
Gemini CLI · ~/.gemini/settings.json, or .gemini/settings.json in a project
{
  "mcpServers": {
    "lokand": {
      "httpUrl": "https://api.lokand.com/mcp"
    }
  }
}
OpenAI Codex · ~/.codex/config.toml, or .codex/config.toml in a trusted project
[mcp_servers.lokand]
url = "https://api.lokand.com/mcp"
Zed · Zed settings file (command: zed: open settings file)
{
  "context_servers": {
    "lokand": {
      "url": "https://api.lokand.com/mcp"
    }
  }
}
Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+
npx @modelcontextprotocol/inspector@2.11.0 --server-url https://api.lokand.com/mcp --transport http
  • The server runs on the operator's infrastructure; it may ask you to sign in when you first connect.
  • Zed's docs we read on 2026-10-26 describe remote servers by URL and do not name the transport.
  • The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.

Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21; Cline, Gemini CLI, OpenAI Codex and Zed 2026-10-26). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.

What do the published files and outside lists say?

Read as text · nothing run · no tool called

Package files

  • MCP SDK in the package files. Not read yet: added with the next daily run.
  • Build workflow. Not read yet: added with the next daily run.

Outside lists

  • CVE records (NVD). No CVE record in the NVD feeds we read links this server's repository. Source: read 2026-11-17. This product uses the NVD API but is not endorsed or certified by the NVD.
  • GitHub advisories. No GitHub advisory names this entry's listed package. Source: read 2026-11-17. GitHub Advisory Database, CC BY 4.0
  • Docker MCP catalogue. Not in the Docker MCP catalogue on 2026-11-17. Source: read 2026-11-17.
  • Cline marketplace. Not in the Cline marketplace on 2026-11-17. Source: read 2026-11-17.

Own host

  • security.txt. No security.txt at https://api.lokand.com/.well-known/ (HTTP 404, 2026-11-17). No security.txt at https://lokand.com/.well-known/ (HTTP 404, 2026-11-17). Source: api.lokand.com/.well-known/security.txt · read 2026-11-17.
  • A2A agent card. No A2A agent card at https://api.lokand.com/.well-known/ (HTTP 404, 2026-11-17). No A2A agent card at https://lokand.com/.well-known/ (HTTP 404, 2026-11-17). Source: api.lokand.com/.well-known/agent-card.json · read 2026-11-17.

Read as text from published files and outside lists. Nothing was installed or run, and no tool was called. A fact, not a rating. How each fact is read

Does the registry listing match what we found?

Feature #6

The registry checks an entry when it is published (each new version), and nothing re-checks it on a schedule. A difference below is about the listing, not a judgement of the publisher.

Registry saysWe foundResultSource · date
Remote endpoint api.lokand.com/mcpSession openedmatchesour test · 2026-11-17
No credential declared as requiredOpened a session without any credentialmatchesour test · 2026-11-17

Tool list changes

Our reads compared · no tool called

Hosted endpoint api.lokand.com/mcp

1 of 1 comparison between consecutive reads showed a change (2 reads, 2026-11-12 to 2026-11-17; versions 1.0.2 to 1.0.4).

Last change seen between our reads on 2026-11-12 (version 1.0.2) and 2026-11-17 (version 1.0.4).

Added (6):

create_tablesexport_qr_codesget_qr_designlist_tablesset_translationsupdate_qr_design

Removed (1):

apply_style_preset

Changed (16):

get_site: descriptionset_system_theme: input schemaset_theme: description, input schematheme_delete: input schematheme_get: input schematheme_git_access: input schematheme_history: input schematheme_publish: input schematheme_pull: description, input schematheme_rollback: input schematheme_sync: input schematheme_upload: input schematheme_write_files: description, input schemaupdate_business: description, input schemaupdate_theme: description, input schemaupdate_theme_settings: description

Compared from the tool lists our read-only connection recorded, separately for each hosted endpoint and each package: each tool's name, title, description, input schema and annotations (the order of keys and of tools is ignored). We see a list only when we read it: a change is shown between the two reads where we first saw it, and anything after 2026-11-17 is not known yet. No tool was called. How it is compared

Choosing

Record checks

Public records · not a safety rating

1 of 2 record checks met · 7 do not apply

  • Not ranked by downloads: a remote server publishes no download figure
  • Not ranked by stars: no public GitHub repository
  • MetRegistry entry is active and says how to run itActive, with a package or a remote address.
  • Not metSource repository link opensThe registry entry gives no repository link.What changes this check: This check opens the repository link in the registry entry. GitHub's documentation describes changing a repository's visibility in its Settings, under Danger Zone, Change visibility. GitHub: setting repository visibility
  • Does not applyRepository is not archivedNo public GitHub repository to read.
  • Does not applyCode pushed to the repository in the 90 days before our checkNo public GitHub repository to read.
  • Does not applyRepository publishes a security policy (SECURITY.md)No public GitHub repository to read.
  • Does not applyPackage names its licence with a standard (SPDX) identifierRemote server: it ships no package.
  • Does not applyThe version the registry lists can be installed and is not withdrawnRemote server: it ships no package.
  • Does not applynpm package carries build provenance (attestation)Remote server: it ships no package.
  • Does not applyNo known critical or high advisory in the package or its dependenciesRemote server: it ships no package.

Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-11-17. No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating, and the same rules apply to every server. How each check works · Leaderboards · How we stay neutral

Common questions about com.lokand/lokand

Answered from the data above

Who publishes com.lokand/lokand?

The registry ties the namespace com.lokand to the domain lokand.com; only its owner can publish under it. These are facts from the registry and GitHub, not a rating.

Does com.lokand/lokand need an API key or sign-in?

It opened a session without any credential on 2026-11-17. The registry entry declares no required credential; no declaration is not a guarantee.

Has com.lokand/lokand been security tested?

Partly. 3 of the 15 checks that apply to it were exercised. It accepted a session without any credential and lists tools whose names suggest they change data. We did not call them. ProtocolProbe publishes no security verdict for a named server.

Found this page useful?

Anonymous · no sign-in

A quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.

Compare with another server

Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.

Security testing

What did we test, and what did we leave out?

18 checks · features #1, #2

Open without sign-in

It accepted a session without any credential and lists tools whose names suggest they change data. We did not call them. No security score is given; a check we did not run is never counted as passed.

The 18 checks at a glanceour test · 2026-11-17
  1. Inventory: exercised
  2. Hidden instructions: exercised
  3. Real execution: not run · our policy
  4. Secret leak: not run · nothing to check it against
  5. Internal addresses: not run · our policy
  6. Unconfirmed changes: not run · our policy
  7. Bad input: not run · our policy
  8. Model requests: not run · nothing to check it against
  9. Sensitive questions: not run · nothing to check it against
  10. Folder boundary: not run · our policy
  11. Log leaks: not run · nothing to check it against
  12. Hidden content: not run · nothing to check it against
  13. Fake assistant turns: not applicable
  14. Token passthrough: not applicable
  15. Token audience: not applicable
  16. Sign-in redirect: not run · our policy
  17. Consent handling: not testable from outside
  18. Sign-in metadata: exercised

3 exercised12 not run (reason given)3 not applicable

Each check ends in exactly one state: exercised, not run (with the reason), or not applicable (with the reason). 3 of the 15 checks that apply to it were exercised. We do not publish security-check outcomes for named servers. These 18 checks are separate from the record checks at the top of this page, which read public records only.

Exercised · 3
  • 1Inventory
    tool-list
    Reads the declared tools, resources and prompts.exercised
  • 2Hidden instructions
    description-poisoning
    Looks for hidden instructions in tool descriptions.exercised
  • 18Sign-in metadata
    oauth-url-scheme
    Checks the published sign-in metadata for unsafe URLs.exercised
Not run, with the reason · 12
  • 3Real execution
    real-execution
    Calls a tool and checks what really happens.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy
  • 4Secret leak
    canary-leak
    Plants a fake secret and checks whether it leaks.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 5Internal addresses
    ssrf
    Checks whether a tool can be steered to internal addresses.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy
  • 6Unconfirmed changes
    write-without-confirmation
    Checks whether tools that change data act without asking.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy
  • 7Bad input
    error-handling
    Sends bad input and watches how the server answers.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy
  • 8Model requests
    sampling
    Checks whether the server asks the client's model to act for it.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 9Sensitive questions
    elicitation-sensitive-data
    Checks whether the server asks users for sensitive data.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 10Folder boundary
    root-boundary
    Checks whether the server reaches outside the folders it was given.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy
  • 11Log leaks
    logging-side-channel
    Checks whether log messages carry data they should not.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 12Hidden content
    audience-hiding
    Checks resources that hide content from the user.This check needs content the server returns, and nothing was read or called.not run · nothing to check it against
  • 16Sign-in redirect
    open-redirect
    Checks the sign-in redirect for abuse.Testing the sign-in redirect means sending probes to the operator's sign-in service, which we do not do.not run · our policy
  • 17Consent handling
    confused-deputy
    Checks consent handling when one service acts for another.Depends on the operator's own consent screen, which differs per server and cannot be tested from outside.not testable from outside
Does not apply to this server · 3
  • 13Fake assistant turns
    fake-assistant-turn
    Checks prompts that pose as the assistant's own words.The server exposes no prompts.not applicable
  • 14Token passthrough
    token-passthrough
    Checks whether the server forwards a user's token to other services.The server opened a session without sign-in, so there is no token flow to check.not applicable
  • 15Token audience
    token-audience-validation
    Checks whether tokens meant for another service are accepted.The server opened a session without sign-in, so there is no token flow to check.not applicable

Source: our own test, 2026-11-17, mcp-runtime-engine@0.1.0. Which checks count and why follows our published scoring model.

What happened during the test?

Feature #8

The steps in order, as the test record holds them.

  1. 0 msStarted a read-only session with the server's remote endpoint
  2. 5,809 msConnected after 0 redirects. No credential was sent or needed.
  3. Read the inventory: 78 tools, 0 resources, 0 prompts.
  4. 10,633 msFinished: 3 checks exercised.

Reference

How is it classified?

18 fields

One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.

TopicAI-classified
pending: added at the next monthly refresh
listed 2026-11-17; not classified yet
Pricing modelAI-classified
pending: added at the next monthly refresh
the website is not read yet
Programming language
does not apply
no existing GitHub repository (server declares no repository link, so there is nothing to fetch)
Hosting type
registry · 2026-11-17
MCP capability
tools
our test · 2026-11-17
Transport
streamable HTTP
registry · 2026-11-17
Required credentials
none declared
registry · 2026-11-17 · no declaration is not a guarantee
Package registry
does not apply
remote-only server: no package is shipped, so there is no package registry
Freshness
0–30 days
registry updatedAt · 2026-11-17
Lifecycle status
registry · 2026-11-17
License class
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Integrity hash
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Signature / provenance
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Dependency advisories
does not apply
ships no package, so there are no dependencies to audit
Popularity
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Publisher signals
not stated
no readable GitHub owner to describe
Maintenance
does not apply
server declares no repository link, so there is nothing to fetch
Environment
the publisher's infrastructure
where it runs, from the hosting type · 2026-11-17

“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.

Cite or correct this page

Sources and corrections

Suggested citation

ProtocolProbe. “com.lokand/lokand: MCP server record.” Data checked 2026-11-17. https://protocolprobe.com/mcp/servers/com.lokand/lokand

Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.

As JSON: this record in the API · API documentation.

Badge for your README

ProtocolProbe: 1 of 2 record checks met

[![ProtocolProbe](https://protocolprobe.com/api/v1/badge/com.lokand/lokand)](https://protocolprobe.com/mcp/servers/com.lokand/lokand)

It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.

Something wrong, or is this yours?

If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here, except for a server whose operator has claimed it and given permission (that server's page says so).

Write to hello@protocolprobe.com · corrections log · methodology