Agent Tools
List
Back to MCP servers

com.cordering/whitelabel-ordering

https://wl-mcp.cordering.com/mcp
● healthy

Order food from Cordering white-label restaurants: browse menus, confirm, then place an order.

What we measured

Over the last 30 days we probed this MCP server 30 times on 30 days; it answered 30 (100%). Median response 466 ms, 95th percentile 588 ms.

When we called tools/list it returned 10 tools, including list_menu, prepare_order, place_order, over MCP protocol revision 2025-11-25.

Among the 53,642 reachable MCP servers in our snapshot of 2026-11-13 01:12 UTC, it is faster than 42% and higher on readiness than 60%.

From agent-tools.cloud's own probes, last checked 2026-11-12. How we measure

Tools (10)

As returned by the server's own tools/list when we called it.

list_menu
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 retu…
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
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.
check_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…
list_vendors
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…
logout
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.
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 t…
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 restaur…
list_accounts
Show which accounts are signed in, per restaurant, and which one is active. Useful when the user keeps separate work and personal accounts.
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.
Transport
streamable-http
Auth
—
Cost
—
Protocol revision
2025-11-25
negotiated, not declared

MCP readiness

B · 83/100

Readiness is how fully this listing follows its protocol and how it behaved in our probes over 30 days. For x402 and A2A listings it contributes up to 15 of the 100 quality points; for MCP listings it is shown for reference only. Search order and leaderboards use the separate quality grade (here B+, 91.5/100), which weighs availability, conformance, p95 speed and descriptor. How the two differ

Valid MCP handshake 10/10 initialize and tools/list both answered.
Live MCP endpoint 25/25 Endpoint answers the MCP initialize handshake (604 ms).
Protocol revision 8/10 Speaks MCP 2025-11-25, 1 revision(s) behind 2026-07-28.
Signed descriptor n/a No MCP standard defines a signed server descriptor.
Uptime (30 days) 15/15 30/30 probes succeeded over 30 days (100%).
Tool declaration 10/10 Lists 10 tool(s) with descriptions.
Verified identity 7/10 Namespace verified by the official MCP Registry (GitHub or DNS proof at publish time).
Freshness + modern flags 0/5 not seen in a source for over 30 days.
Auth declaration 0/5 How to authenticate is not stated.
Applicable criteria total 90 points, scaled to 100.
Responsiveness: Responsive (604 ms; bands ≤2.5 s, ≤5 s, ≤8 s, slower; penalty only).
Measured 2026-11-12.
Nine criteria, the same as the A2A readiness score, read from our daily MCP probe (initialize + tools/list) and 30-day probe history. No MCP standard defines a signed server descriptor, so that criterion is n/a and the other 90 points are scaled to 100. Grades: A>=90, B>=75, C>=60, D>=40, F<40. Display only: search order uses the quality grade.

Compared with peers

Against 53,642 reachable MCP servers in our daily snapshot (2026-11-13 01:12 UTC). Display only; it does not change search order.

Readiness
Higher than 60% of peers
This listing 83 · peer median 81
Latency
Faster than 42% of peers
This listing 431 ms · peer median 349 ms

Where it loses the most points, and how to win them back

  • Freshness + modern flags −5 — Keep the listing current in the registry or source it comes from.
    Now: not seen in a source for over 30 days.
  • Auth declaration −5 — State how to authenticate (an auth scheme, or that none is needed).
    Now: How to authenticate is not stated.
  • Verified identity −3 — Claim the listing and prove control of its domain.
    Now: Namespace verified by the official MCP Registry (GitHub or DNS proof at publish time).

How many agent tools actually work · All statistics

Listed in

Directories this entry was found in.

mcp-registry since 2026-08-28 wellknown since 2026-09-23 ↗ agenstry since 2026-10-22 ↗ capkey since 2026-10-26 ↗

How to connect

MCP endpoint (streamable-http)
https://wl-mcp.cordering.com/mcp
JSON-RPC initialize probe
curl -X POST https://wl-mcp.cordering.com/mcp \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json, text/event-stream' \
  -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{}}'
Source code
https://github.com/nistruct/cordering-whitelabel-mcp