accueil / serveurs / Recherche & Web / com.shortlistpass/local-businesses
com.shortlistpass/local-businesses
serveur MCP (Model Context Protocol) · shortlist-pass 1.0.0
Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur.
Est-ce que com.shortlistpass/local-businesses est sûr ?
Au dernier audit MCP Hub, le serveur MCP « com.shortlistpass/local-businesses » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.
Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.
Les 6 outils
- get_business≈ 206 tokens
Returns the public profile of one Shortlist business: name, type, description, town, phone, website, page URL, hours (fixed locations only), whether online ordering is open, and the order page URL when it is. Mobile businesses (food trucks) have no fixed address; their locations are the upcoming stops in the upcoming-events data.
Paramètres, retour & exemple (1)
Paramètressubdomain· string · requis
The business subdomain, e.g. "nitos" for nitos.shortlistpass.com
Exemple d'appel{"name": "get_business", "arguments": {"subdomain": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - get_menu≈ 268 tokens
Returns the current public menu of one business: every active item with its id (use it in start_order), name, description, price, category, tags, available and sold_out flags, an image URL, and options: its sizes and add-ons (group key, label, and each choice's value, label and price). Prices are in US dollars. For a business with menu_source "event" (food trucks), this is the full catalog of everything it sells; what is sold on a given day is listed per stop in the upcoming-events data, and the note field states this. The response includes the business summary with the order page URL when ordering is open.
Paramètres, retour & exemple (1)
Paramètressubdomain· string · requis
The business subdomain, e.g. "nitos"
Exemple d'appel{"name": "get_menu", "arguments": {"subdomain": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - get_trucks_tonight≈ 369 tokens
Food trucks in one city today (local time), in two lists. "tonight" (status "out_tonight"): trucks with a stop confirmed for today — truck name, park if it is at one, address, start and end time, open_now, the truck page link, and order_url only when that truck is taking preorders for that stop. "usually_here" (status "usually_here"): trucks that regularly park at a listed park but have NO stop confirmed for today — say "usually here", never "out tonight". Also lists the parks with today's and usual truck counts. Optional "days" (1-7, default 1): also returns "days", the posted stops for today and the next days grouped by date (truck, where, start, end, open_now, page link); a day with no posted stop is left out. Test pages, private events and cancelled or hidden stops are never included. Cities: Myrtle Beach, Austin.
Paramètres, retour & exemple (2)
Paramètrescity· string · requis
City name or slug, e.g. "Austin" or "myrtle-beach"days· integer · optionnel
How many days from today, 1-7 (default 1)
Exemple d'appel{"name": "get_trucks_tonight", "arguments": {"city": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - get_upcoming_events≈ 329 tokens
Returns the upcoming published events and stops for one business; for a food truck these are its locations. Each has a name, ISO start and end with the local offset, location name and address, whether pre-orders are open for that stop, the pickup time slots still available with remaining capacity (null means no cap), and a menu with menu_status: "set" means the items listed are what is sold at that stop and their offering ids are accepted by start_order for that stop; "not_live" means the business has not put a menu on that stop yet, the menu is empty, menu_note carries the explanation, and start_order does not accept the stop; "catalog" means a fixed business whose standing menu applies. Recurring events carry a recurrence description and the next date. Cancelled and test events are not included.
Paramètres, retour & exemple (1)
Paramètressubdomain· string · requis
The business subdomain, e.g. "nitos"
Exemple d'appel{"name": "get_upcoming_events", "arguments": {"subdomain": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - search_businesses≈ 386 tokens
Searches real local businesses on Shortlist Pass (food trucks, restaurants, shops, HOAs and more). Optional filters: a town slug (e.g. "myrtle-beach"), a business category key (e.g. "food_truck", "restaurant", "bakery"), and a free-text query. The query matches every word, in any order, against the business name, headline and type, and also against its active menu items (name, description, tags, category); a business found through its menu carries matched_items (id, name, price, up to 5). For food trucks, matched items come from the full catalog and menu_note says so; what is sold on a given day is per stop. Businesses with a menu match rank first. Returns up to 25 matches, each with its subdomain, which is the identifier the other tools take. Demo and test pages are not included.
Paramètres, retour & exemple (3)
Paramètrestown· string · optionnel
Town slug, e.g. "myrtle-beach"query· string · optionnel
Free-text query, e.g. "empanadas" or "buffalo chicken fries"; matched word-by-word against the business and its menu itemscategory· string · optionnel
Business category key, e.g. "food_truck"
Exemple d'appel{"name": "search_businesses", "arguments": {"town": "texte", "query": "texte", "category": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - start_order≈ 1032 tokens
Creates a short-lived cart for a customer at one Shortlist business and returns a cart_url on the business's own page, where the customer reviews the order and pays through the business's checkout. Input is offering ids (preferred) or item names, and quantities; prices are not accepted. Order by id from get_menu or the stop's menu. If you only have a name, send it as name: when it is unclear or not on the menu, no cart is made and the reply (error "needs_choice") lists each line as matched, choose (options with ids) or not_found (genuinely close items with ids, or none) with a message to read to your user; ask them and resend with the offering_id. The server prices every line from the menu, applies the business's deals and tax, and returns the resulting quote. For businesses with menu_source "event" (food trucks), event_id is required and identifies one upcoming stop; the offering ids accepted are those listed in that stop's menu in the upcoming-events data, and pickup_time is one of that stop's open pickup_slots. A stop whose menu_status is "not_live" is refused. The cart expires in 30 minutes. This tool does not accept payment details or addresses; payment happens on the business's page at the returned cart_url. In the quote, total_before_tip excludes the optional tip, which the customer chooses on the checkout page; quote.tip.note states the business's suggested percentage. agent.name is recorded on the cart and the order so the business can see which assistant helped.
Paramètres, retour & exemple (6)
Paramètresagent· object · optionnel
The name of the assistant placing the order, e.g. { "name": "Claude" }. Optional; defaults to "AI assistant".items· array · requiscustomer· object · optionnel
Customer details, if provided; pre-filled on the order sheetevent_id· string · optionnel
A stop id from the upcoming-events results. Required for businesses with menu_source "event".subdomain· string · requis
The business subdomain, e.g. "nitos"pickup_time· string · optionnel
One of the stop's open pickup_slots, "HH:MM" 24-hour
Exemple d'appel{"name": "start_order", "arguments": {"items": [], "subdomain": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]}
C'est votre serveur ?
Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».