Comprehensive Model Context Protocol server for managing Home Assistant through AI assistants.
Nothing to run from here
Whitelabel Ordering is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
93/100
tool-list score
10
tools declared
remote
at its publisher
—
calls last 7d
What it does
Order food from Cordering white-label restaurants: browse menus, confirm, then place an order.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http whitelabel-ordering-mcp https://wl-mcp.cordering.com/mcp
# 2 — ask your agent for something these tools do
# list_menu, prepare_order, place_order and 7 more
Whitelabel Ordering costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
COAll 1 server
cordering1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http whitelabel-ordering-mcp https://wl-mcp.cordering.com/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
10 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Show 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_order resolves item names on its own.)
| Parameter | Type | Required | Notes |
|---|---|---|---|
| clientId | integer | no | clientId of the restaurant, from a list_vendors result. Omit only when the server is configured for a single restaurant. |
| vendorId | integer | no | vendorId of the restaurant, from a list_vendors result. Omit only when the server is configured for a single restaurant. |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| clientId | integer | no | clientId of the restaurant, from a list_vendors result. Omit only when the server is configured for a single restaurant. |
| vendorId | integer | no | vendorId of the restaurant, from a list_vendors result. Omit only when the server is configured for a single restaurant. |
| items | array | yes | The item(s) to order — one or more lines, each with an item name, an optional quantity (default 1), an optional size, and optional extra ingredients by name. |
| deliveryAddress | string | yes | Delivery address text, e.g. 'Orlovica Pavla 26'. |
| date | string | no | Delivery date-time as an ISO-8601 UTC instant, e.g. '2026-07-25T12:00:00Z'. Must be in the future. Defaults to 5 minutes from now (as soon as possible) — only pass this when the user asks for a specif |
| notes | string | no | Optional notes for the vendor. |
| cutlery | boolean | no | Whether to ask the restaurant to include disposable cutlery. Only pass this when the user says either way; omit to leave it to the restaurant's default. Ignored (with a note) by vendors that do not of |
| bringTerminal | boolean | no | Whether the courier should bring a card terminal so the order can be paid by card on delivery. Pass true when the user wants to pay by card, false for cash; omit when they do not say. Ignored (with a |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| confirmationToken | string | yes | The confirmationToken returned by prepare_order. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| orderId | integer | yes | The order number returned by place_order. |
| clientId | integer | no | clientId of the restaurant the order was placed with, from the list_vendors result. Omit only when the server is configured for a single restaurant. |
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 close
| Parameter | Type | Required | Notes |
|---|---|---|---|
| city | string | no | City to filter by. Pass this ONLY when the user named a city themselves; never guess one from context, because a filter that matches nothing hides restaurants the user could have ordered from. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| clientId | integer | no | clientId of the restaurant to sign in to, from a list_vendors result. Omit only when the server is configured for a single restaurant. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| clientId | integer | no | clientId of the restaurant to sign out of. Omit to sign out everywhere. |
| label | string | no | Account label to sign out, e.g. 'work'. Omit to sign out every account at that restaurant. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| code | string | yes | The code value copied from the redirect URL after signing in. |
| clientId | integer | no | clientId of the restaurant being signed in to. Omit if only one sign-in is in progress. |
| label | string | no | Optional label for this account, e.g. 'work' or 'personal'. Defaults to the email address on the account. |
Show which accounts are signed in, per restaurant, and which one is active. Useful when the user keeps separate work and personal accounts.
No parameter schema on file.
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| label | string | yes | Account label to make active, e.g. 'work'. |
| clientId | integer | no | clientId of the restaurant. Omit only when the server is configured for a single restaurant. |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Whitelabel Ordering or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATool-list grade · score 93 / 100
Release 0.0.1 · scanned 20 Oct 2026
Graded from the tools this server lists, not from its source code.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score93
Findings0 threat · 1 capability
Capabilitymoderate
Coveragemanifest
Verificationnot in this report
Surface digestab8a1879c930ec93ef4c834861793834429ecb1ac9774147d2cc985625a0e8a2
Score vectorthreat 100 → client 93
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
Tool surfaceread
Implementation sourcenot available
Package metadatanot available
Live transportnot available
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| list_menu | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| prepare_order | external-sink | external-sink: declares readOnlyHint: false, openWorldHint: true |
| place_order | external-sink | external-sink: declares readOnlyHint: false, destructiveHint: true, openWorldHint: true |
| check_order | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| list_vendors | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| login | state-write | state-write: declares readOnlyHint: false |
| logout | state-write | state-write: declares readOnlyHint: false, destructiveHint: true |
| submit_login_code | external-sink | external-sink: declares readOnlyHint: false, openWorldHint: true |
| list_accounts | no tags | |
| switch_account | state-write | state-write: declares readOnlyHint: false |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
flow-1
Untrusted input can drive an external action even though no sensitive source is exposed.
Supply chain and provenance
Integrityfirst-seen
Surface digestab8a1879c930ec93
Scanned2026-10-20
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 0.0.1.
0.0.1
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Whitelabel Ordering can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.