whitelabel-ordering
Server Details
Order food from Cordering white-label restaurants: browse menus, confirm, then place an order.
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 10 tools
Each tool targets a distinct step in the ordering or authentication lifecycle: discovery (list_vendors), menu display (list_menu), auth (login, submit_login_code, logout, list_accounts, switch_account), order staging (prepare_order), placement (place_order), and status (check_order). The descriptions explicitly separate prepare_order from place_order and login from submit_login_code, so an agent can reliably choose the right tool.
Most tools follow a clear verb_noun pattern (check_order, list_accounts, list_menu, list_vendors, place_order, prepare_order, switch_account), with only minor deviations: login and logout are bare verbs, and submit_login_code is a three-word variant. The convention is still highly predictable overall.
Ten tools is well-scoped for a food-ordering server, covering discovery, menu, authentication, order staging/placement, and status without redundancy. Each tool earns its place and the count is in the ideal range.
The surface covers the core ordering lifecycle from vendor discovery through placement and status checking, plus full authentication. Missing operations like order cancellation or modification and order history are minor gaps that can be worked around for most workflows.
Available Tools
10 toolscheck_orderCheck an orderARead-onlyInspect
Check the current status of an order the user has already placed, using the order number returned by place_order. Reports whether the restaurant has accepted it, whether it is on its way, and whether it has finished (delivered or declined). There is no background tracking and no notification: call this again when the user asks, and only until the order is reported as finished.
Inputs: orderId (required), clientId.
list_accountsList signed-in accountsARead-onlyInspect
Show which accounts are signed in, per restaurant, and which one is active. Useful when the user keeps separate work and personal accounts.
Inputs: no named parameters.
list_vendorsList restaurantsARead-onlyInspect
Find restaurants (vendors) available for ordering. This is the discovery entry point: each card shows the clientId and vendorId that list_menu and prepare_order need. Call it with no arguments to list every restaurant — that is the normal case. Returns a complete, self-contained HTML document of vendor cards (logo, address, phone, delivery fee) — restaurants open today first in colour, those closed today greyed out at the bottom. Present the returned HTML to the user by opening it as an HTML artifact; do not paste the markup into the chat.
Inputs: city.
loginStart signing inAInspect
Start signing the user in to a restaurant so they can place orders. Browsing the menu never needs this — only ordering and saving an address do. Returns a URL the user must open in a browser to sign in with Google or Apple; afterwards they copy the 'code' value from the address bar and you call submit_login_code. Each restaurant has its own login, so this must be done per restaurant.
Inputs: clientId.
logoutSign outADestructiveIdempotentInspect
Sign the user out. By default signs out of every restaurant; pass a clientId to sign out of one, and an account label to sign out just that account.
Inputs: label, clientId.
place_orderPlace the orderADestructiveInspect
Place an order previously staged by prepare_order. Requires the confirmationToken returned by prepare_order. This causes a real order to be sent to the vendor.
Inputs: confirmationToken (required).
prepare_orderPrepare an orderAInspect
Resolve a natural-language food order (one or more items) to concrete menu items and return a summary plus a confirmation token. Does NOT place the order. Call place_order with the returned token to actually place it. Delivery is as soon as possible by default; pass 'date' to ask for a later time instead. Each call covers one delivery, so an order for more than one day means one call per day. The restaurant may still refuse a time it is not open for.
Inputs: items (required), deliveryAddress (required), date, notes, +4 more.
submit_login_codeFinish signing inAInspect
Complete a sign-in started by login, using the 'code' value the user copied from the browser address bar. On success the user can place orders from that restaurant.
Inputs: code (required), label, clientId.
switch_accountSwitch accountAIdempotentInspect
Choose which signed-in account to order with at a restaurant, e.g. to switch between work and personal. The account must already be signed in via login.
Inputs: label (required), clientId.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Discover Servd venues, browse menus, validate carts, place confirmed orders, and track status.
Pickup orders at Japanese restaurants for AI agents: find stores, read menus, place orders. No auth.
Find local shops, read live menus and free times, and order or book on the user's behalf.
Related MCP Servers
- AlicenseAqualityCmaintenanceEnables an AI assistant to browse restaurants and menus, manage a cart, reorder past orders, review checkout details, and place food delivery orders, returning a payment link to complete payment.13MIT
- AlicenseNot gradedqualityBmaintenanceEnables ordering from McDonald's through an interactive UI: selecting stores, browsing menus, managing a cart, applying coupons, placing orders, paying, and tracking orders.MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to find nearby venues, browse menus and dish details with pictures, and get links that open items in the service for ordering.MIT
- FlicenseNot gradedqualityCmaintenanceEnables voice-driven food ordering by providing tools to search restaurants, browse menus, check item availability, manage carts, calculate optimal coupon discounts, confirm and place orders, and track deliveries. It also supports long-term preference memory and order history for natural, multi-turn conversational commerce.-
Glama MCP Gateway
Add one secure layer between your agents and this server.