Skip to content
External endpointresponds

guest

Guest API for meni.ge restaurants: browse menus, place orders, reserve tables. No auth needed.

Endpoint URL
https://api.meni.ge/llm/mcp
Current status
responds
Last checked
Aug 17, 2026, 04:59 AM UTC
Check
MCP initialize · 8s limit
Latency
259 ms
Response record
4 of 4 rounds
Transport
streamable-http
Source
mcp_registry
Registry name
ge.meni/guest

Current observation

This endpoint answered at its latest recorded check.

What this server reports about itself

Self-reported at initialize. Not verified by Licium.

Server name
meni-ge-llm-api
Version
1.0.0
Capability keys
tools
Tool names
get_menu, get_item, search_products, update_cart, get_cart, get_store_info, search_policies_and_faqs, create_order, get_order_status, check_table_availability, create_reservation, get_reservation_status, cancel_reservation
Instructions excerpt

Tools for reading meni.ge restaurant menus, placing orders and reserving tables. A location is addressed by its uppercase domain code (from the menu URL or QR). Catalog questions ("do you have…", "recommend…"): search_products instead of paging through get_menu; get_item accepts itemIds for a bulk lookup. Ordering: get_menu → create_order → get_order_status. Cart flow: update_cart → get_cart → create_order(cartId); the cart view carries a checkoutUrl for handing the order to a human. Store questions ("are you open?", "do you deliver?", refunds, privacy): get_store_info / search_policies_and_faqs. Use idempotencyKey on create_order retries. Reservations: check_table_availability → create_reservation → get_reservation_status / cancel_reservation. Sign in (see .well-known/oauth-protected-resource) to unlock account data tools (resolve_domain, list_files, read_file, write_file, delete_file, write_signal) and client-site configuration tools (get_site_settings, update_site_se

Reported Aug 17, 2026, 04:59 AM UTC.

Check history

Oldest to newest. Each row is one recorded check.

  1. responds
    MCP initialize · 8s limit · HTTP 200 · 152ms
  2. responds
    MCP initialize · 8s limit · HTTP 200 · 435ms
  3. responds
    MCP initialize · 8s limit · HTTP 200 · 442ms
  4. responds
    MCP initialize · 8s limit · HTTP 200 · 259ms