dukkani
Registry code: 162b167f42f20a8f
Dukkani (دكّاني, dukkanlink.com) is a Saudi app for neighbourhood groceries (بقالات وتموينات). This server gives you its public grocery directory (about 3,000 groceries in 70+ Saudi cities, most of them placed in their district by official boundaries) and its order page. Use find_groceries when someone in Saudi Arabia wants a nearby grocery / بقالة / تموينات / «أقرب بقالة», in a city or a district (حي). Use prepare_grocery_order when they want to send a shopping list (قائمة مقاضي) to one of those groceries: it returns a link to Dukkani's order page with the list already written; the customer…
- endpoint
- https://dukkanlink.com/mcp
- protocol
- streamable-http ·2025-06-18
- authentication
- none observed
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 0 · newcomer
- Is dukkani live?
- Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
- Is dukkani free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does dukkani have?
- 4 tools: prepare_grocery_order, dukkani_for_shop_owners, list_cities, find_groceries.
- Is dukkani safe to connect?
- The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
90 days 100%· all time 100%
last good check
of 4 tools
- unknown → live
Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.
through this hub
successful
what callers paid
Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.
dukkani_for_shop_owners open 1h ago
Facts about Dukkani for a grocery owner (cashier on the phone, debt book from a photo of the paper book, barcode, worker in his language, orders from neighbourhood customers) and the links to try it. Use when a shop owner asks for a cashier/POS app, a debt book app or how to run a grocery from a phone in Saudi Arabia.
{ "type": "object", "properties": { "topic": { "enum": [ "overview", "cashier", "debts", "orders", "workers", "einvoice" ], "type": "string", "default": "overview" } }, "additionalProperties": false }arguments 18 lineslist_cities open 1h ago
List the Saudi cities that have groceries in Dukkani's directory, with how many. Use it when a city is not found or the user asks where it works.
{ "type": "object", "properties": {}, "additionalProperties": false }arguments 5 linesfind_groceries open 1h ago
Find neighbourhood groceries (بقالات / تموينات) in Saudi Arabia from Dukkani's public directory, by district (حي) + city, by city, or by coordinates. Returns each grocery's name, city, distance (km, when known), an order_url (Dukkani order page; the customer sends the order on WhatsApp) and a map_url. Groceries that use Dukkani and take orders in the app come first (on_dukkani=true). Use the Arabic district/city names when you have them (e.g. district «النهضة», city «عفيف»).
{ "type": "object", "properties": { "city": { "type": "string", "description": "City, e.g. الرياض، جدة، عفيف، بريدة (Arabic preferred)" }, "limit": { "type": "integer", "default": 8, "maximum": 15, "minimum": 1 }, "district": { "type": "string", "description": "District / neighbourhood (حي), e.g. الياسمين، النهضة. Give the city too when you know it." }, "latitude": { "type": "number", "description": "Optional: the user's latitude (only if they shared it)" }, "longitude": { "type": "number", "description": "Optional: the user's longitude" } }, "additionalProperties": false }arguments 28 linesprepare_grocery_order unknown never probed
Turn a shopping list into a ready order for one grocery from find_groceries (pass its id, e.g. «d:82» or «b:abc12»). Returns the cleaned list and an order_url: Dukkani's order page with that grocery chosen and the list already written, so the customer only checks it and sends it on WhatsApp. This tool sends nothing by itself.
{ "type": "object", "required": [ "grocery_id", "items" ], "properties": { "note": { "type": "string", "description": "Optional note to the grocery (delivery time, «بدون سكر»…)" }, "items": { "type": "array", "items": { "type": "string" }, "maxItems": 40, "minItems": 1, "description": "List lines, e.g. «2 حليب المراعي 1 لتر», «رز 5 كيلو», «كرتون بيض»" }, "grocery_id": { "type": "string", "description": "The id returned by find_groceries (d:<number> or b:<code>)" } }, "additionalProperties": false }arguments 27 lines
This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.
Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - Prove it is yours. Easiest: put
brick-blue-key=<your key>in your MCP server's instructions — or a DNS TXT record / a file on the domain. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's id162b167f42f20a8f.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/162b167f42f20a8f/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/162b167f42f20a8f?ref=badge)
The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.
An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- paid reviews
- 0
- positive
- 0
- negative
- 0
- score
- —
0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.