Search / com.cordering/whitelabel-ordering
protogridR0· no sign-inOrder food from Cordering white-label restaurants: browse menus, confirm, then place an order.
v0.0.1 · active · repository · descriptor JSON · versions
{
"mcpServers": {
"whitelabel-ordering": {
"type": "http",
"url": "https://wl-mcp.cordering.com/mcp"
}
}
}claude mcp add --transport http whitelabel-ordering https://wl-mcp.cordering.com/mcp[mcp_servers.whitelabel-ordering]
url = "https://wl-mcp.cordering.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"whitelabel-ordering": {
"type": "remote",
"url": "https://wl-mcp.cordering.com/mcp",
"enabled": true
}
}
}{
"mcpServers": {
"whitelabel-ordering": {
"type": "http",
"url": "https://wl-mcp.cordering.com/mcp"
}
},
"deeplink": "cursor://anysphere.cursor-deeplink/mcp/install?name=whitelabel-ordering&config=eyJ0eXBlIjoiaHR0cCIsInVybCI6Imh0dHBzOi8vd2wtbWNwLmNvcmRlcmluZy5jb20vbWNwIn0%3D"
}{
"servers": {
"whitelabel-ordering": {
"type": "http",
"url": "https://wl-mcp.cordering.com/mcp"
}
}
}{
"mcpServers": {
"whitelabel-ordering": {
"httpUrl": "https://wl-mcp.cordering.com/mcp"
}
}
}extensions:
"whitelabel-ordering":
enabled: true
name: "whitelabel-ordering"
type: streamable_http
uri: "https://wl-mcp.cordering.com/mcp"
timeout: 300
protocol.modernnewest supported version is 2025-11-25; 2026-07-28 not supported, older versions are deprecated until 2027-07-28protocol.statelessonly applies to 2026-07-28 serversprotocol.transportstreamable HTTPprotocol.list_ttlonly applies to 2026-07-28 serversauth.prm, auth.as_metadata, auth.cimdno remote uses OAuthauth.secret_in_urlno templated URLtools.descriptionsevery tool has a descriptiontools.description_lengthdescriptions are concisetools.schemasevery tool has an object input schematools.annotations10 of 10 tools declare readOnlyHint or destructiveHinttools.directory_hints6 of 10 tools declare all four hints; missing: check_order (destructiveHint, idempotentHint); list_accounts (destructiveHint, idempotentHint); list_menu (destructiveHint, idempotentHint); …tools.token_costabout 2,257 tokens to load every tooltools.api_dumptools are not a one-to-one API dumpstability.changes10 tool changes in 30 daysstability.rug_pullno tool changed its meaning under the same namedeps.known_vulns, deps.mcp_sdk_version, deps.resolvableno npm or PyPI packageswitch_accountchangedtitle, annotationslist_accountschangedtitle, annotationssubmit_login_codechangedtitle, annotationslogoutchangedtitle, annotationsloginchangedtitle, annotationslist_vendorschangedtitle, annotationscheck_orderchangedtitle, annotationsplace_orderchangedtitle, annotationsprepare_orderchangedtitle, description, annotationsResolve 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.
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.
list_menuchangedtitle, annotationsFull history: list_changes · trend: quality JSON.
Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed. How it is computed.
+repository +dns-namespace +reachable +uptime-100% ~updated-53d-ago
Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed. How it is computed.
| remote | auth | reachable | uptime 30d | p50 | protocol | last ok |
|---|---|---|---|---|---|---|
https://wl-mcp.cordering.com/mcp streamable-http | none | yes | 100% | 533 ms | 2025-11-25 | 2026-10-20 |
check_orderread-only | 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. |
list_accountsread-only | Show which accounts are signed in, per restaurant, and which one is active. Useful when the user keeps separate work and personal accounts. |
list_menuread-only | 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.) |
list_vendorsread-only | 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. |
login | 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. |
logoutdestructive | 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. |
place_orderdestructive | 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. |
prepare_order | 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. |
submit_login_code | 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. |
switch_account | 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. |
Schemas: list_tools.
{
"name": "com.cordering/whitelabel-ordering",
"$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
"remotes": [
{
"url": "https://wl-mcp.cordering.com/mcp",
"type": "streamable-http"
}
],
"version": "0.0.1",
"repository": {
"url": "https://github.com/nistruct/cordering-whitelabel-mcp",
"source": "github"
},
"description": "Order food from Cordering white-label restaurants: browse menus, confirm, then place an order."
}