Online store and commerce
whitelabel-ordering
whitelabel-ordering was answering at the last check. Checked on 2026-10-05 (daily check).
Order food from Cordering white-label restaurants: browse menus, confirm, then place an order.
Agents use servers like this to search products, build carts and place orders.
4 read-only3 change data3 high risk
https://wl-mcp.cordering.com/mcp
Follow (RSS): status changes, tool-list changes, new advisories and owner verification, in any feed reader.
Tools
10 tools: 4 read-only, 3 change data, 3 high risk (delete, pay, send or run code).
2 tools can move money or change orders; they are listed first.
- read-only
- Only reads or looks things up. Safe for an agent to call on its own.
- changes data
- Creates, edits or sends something. Worth a person's approval the first time.
- high risk
- Can delete, pay, send on your behalf or run code. Hard or impossible to undo.
Connecting costs an agent about 2,470 tokens of tool definitions and a 745 ms handshake.
- high risk
prepare_ordermoves money or changes ordersResolve 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... - high risk
place_ordermoves money or changes ordersPlace 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. - high risk
logoutSign 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. - changes data
loginStart 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 s... - changes data
submit_login_codeComplete 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. - changes data
switch_accountChoose 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. - read-only
list_menuShow the restaurant's menu to the user as a visual HTML document - a horizontally-scrollable category strip with item photos, names and prices. Present the returned HTML by opening it as an HTML artifact; do NOT paste the markup into the chat as text. (Ordering does not require this - prepare_ord... - read-only
check_orderCheck 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: cal... - read-only
list_vendorsFind 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 ... - read-only
list_accountsShow which accounts are signed in, per restaurant, and which one is active. Useful when the user keeps separate work and personal accounts.
Levels are automated estimates from each tool's public name, description and annotations, and can be wrong. Descriptions as the server publishes them.
Trust and supply chain
No owner has verified this server yet.
No tool change since tracking began on 2026-10-02.
Status
Newest check: answered with tools, from the daily check, 2026-10-05, 745 ms.
From one check a day over the last 4 days. Servers whose owner verified them are checked every 5 minutes. Sign-in and payment answers count as up.
Last 30 days
2026-09-062026-10-05
answered with toolssign-in or payment askednot answeringnot checked
Compare: the most reliable servers in Online store and commerce, ranked by days answering.
Badge
Live: status, days reachable, the tokens its tool list costs an agent. For a README:
[](https://7it.co.il/7maps/s/wl-mcp.cordering.com/mcp)
Other styles: add ?style=uptime (30-day uptime), ?style=stars (agents’ rating) or ?style=verified (owner mark) to the image address, or ?style=top (shows "top 10%" when the server ranks in the top tenth of its category by days answering; otherwise the standard badge).
Is this badge genuine? Anyone can check what a genuine badge for this server says right now: /7maps/verify/badge?server=wl-mcp.cordering.com%2Fmcp (add the same &style= for another style).
Own this server? Verify that it is yours.
Status widget
A live status card for a status page, docs or a dashboard: current status, the 30-day strip, uptime and handshake time.
Script (renders where it is placed, in its own shadow DOM):
<script src="https://7it.co.il/7maps/widget/wl-mcp.cordering.com/mcp.js" async></script>
Or an iframe:
<iframe src="https://7it.co.il/7maps/widget/wl-mcp.cordering.com/mcp" title="7Maps status" width="360" height="176" style="border:0;max-width:100%" loading="lazy"></iframe>
The widget is drawn only from 7it.co.il. Is a status shown elsewhere genuine? Check it: /7maps/verify/badge?server=wl-mcp.cordering.com%2Fmcp.
Add ?theme=light or ?theme=dark to either address (default: follows the visitor's setting). Refreshed every 5 minutes. Open the card · script.
For AI agents
Before connecting, an agent can ask 7Maps for this server's full condition, every tool's risk level and what changed since a person approved it: the road_conditions, watch and route tools on https://7it.co.il/7maps/mcp, paid per call in USDC via x402. About 7Maps.
7Maps by 7IT maps the MCP servers AI agents use, from public listings. Observations with a date, not a judgement. Methodology · How we collect, and opting out.