_ registry / mcp http-sse · checked 30m ago

shortlist-pass

https://app.shortlistpass.com

Registry code: b3ffe07faee664c2

api record

Shortlist Pass hosts the live pages of real local businesses. The read tools return published data only: menus, upcoming stops and events, pickup availability. start_order creates a cart from offering ids — or item names, answered with choices when unclear — (prices are not accepted) and returns a cart_url on the business's page, where the customer reviews the order and pays; payment details are not handled by these tools. Food trucks sell per stop, and each stop's menu is listed in the upcoming-events data. Plain JSON API: https://app.shortlistpass.com/api/agent/v1. Docs:…

endpoint
https://app.shortlistpass.com/mcp
protocol
http-sse ·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 it live, free and safe measured by this hub
Is shortlist-pass live?
Yes — it answered the hub's last check (checked 30m ago). It answered 98% of checks over the last 30 days.
Is shortlist-pass free to use?
Yes — the hub reached it with no key and no payment.
What tools does shortlist-pass have?
6 tools: get_trucks_tonight, start_order, get_business, get_menu, get_upcoming_events, search_businesses.
Is shortlist-pass 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.
reachable
live
uptime, 30 days
98.4%

90 days 99.1%· all time 99.1%

latency
536ms

last good check

priced tools
0

of 6 tools

_ answered our checks, 90 days 347 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
_ what it is for
used for
  • search local businesses and food trucks
  • get a business menu
  • get food truck stops
  • start an order cart
takes → gives
text → data, web pages
tools
4 reads1 changes data
_ usage and payments 30 days

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.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 6 tools
1 open 5 never probed 1 of 6 classified

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.

  • search_businesses reads open 13h ago

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {
        "town": {
          "type": "string",
          "maxLength": 80,
          "description": "Town slug, e.g. \"myrtle-beach\""
        },
        "query": {
          "type": "string",
          "maxLength": 80,
          "description": "Free-text query, e.g. \"empanadas\" or \"buffalo chicken fries\"; matched word-by-word against the business and its menu items"
        },
        "category": {
          "type": "string",
          "maxLength": 80,
          "description": "Business category key, e.g. \"food_truck\""
        }
      }
    }
    arguments 21 lines
  • get_trucks_tonight unknown 20h ago

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "city"
      ],
      "properties": {
        "city": {
          "type": "string",
          "maxLength": 60,
          "minLength": 2,
          "description": "City name or slug, e.g. \"Austin\" or \"myrtle-beach\""
        },
        "days": {
          "type": "integer",
          "maximum": 7,
          "minimum": 1,
          "description": "How many days from today, 1-7 (default 1)"
        }
      }
    }
    arguments 21 lines
  • start_order changes data unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "subdomain",
        "items"
      ],
      "properties": {
        "agent": {
          "type": "object",
          "required": [
            "name"
          ],
          "properties": {
            "name": {
              "type": "string",
              "maxLength": 60,
              "minLength": 1
            }
          },
          "description": "The name of the assistant placing the order, e.g. { \"name\": \"Claude\" }. Optional; defaults to \"AI assistant\"."
        },
        "items": {
          "type": "array",
          "items": {
            "type": "object",
            "required": [
              "quantity"
            ],
            "properties": {
              "name": {
                "type": "string",
                "maxLength": 120,
                "minLength": 1,
                "description": "Only when you have no id: the item's name as your user said it. If it is unclear the reply is error \"needs_choice\" with options (ids) per line; ask your user and resend with the offering_id."
              },
              "options": {
                "type": "object",
                "description": "The offering's own variant or modifier choices, by option value or label",
                "propertyNames": {
                  "type": "string"
                },
                "additionalProperties": {
                  "anyOf": [
                    {
                      "type": "string"
                    },
                    {
                      "type": "array",
                      "items": {
                        "type": "string"
                      }
                    }
                  ]
                }
              },
              "quantity": {
                "type": "integer",
                "maximum": 100,
                "minimum": 1,
                "description": "Whole number, 1 to 100"
              },
              "offering_id": {
                "type": "string",
                "format": "uuid",
                "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$",
                "description": "An offering id from the stop's menu (or from get_menu for a fixed business). Preferred."
              }
            }
          },
          "maxItems": 12,
          "minItems": 1
        },
        "customer": {
          "type": "object",
          "properties": {
            "name": {
              "type": "string",
              "maxLength": 80
            },
            "email": {
              "type": "string",
              "maxLength": 120
            },
            "phone": {
              "type": "string",
              "maxLength": 30
            }
          },
          "description": "Customer details, if provided; pre-filled on the order sheet"
        },
        "event_id": {
          "type": "string",
          "format": "uuid",
          "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$",
          "description": "A stop id from the upcoming-events results. Required for businesses with menu_source \"event\"."
        },
        "subdomain": {
          "type": "string",
          "maxLength": 63,
          "minLength": 1,
          "description": "The business subdomain, e.g. \"nitos\""
        },
        "pickup_time": {
          "type": "string",
          "pattern": "^\\d{2}:\\d{2}$",
          "description": "One of the stop's open pickup_slots, \"HH:MM\" 24-hour"
        }
      }
    }
    arguments 110 lines
  • get_business reads unknown 13h ago

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "subdomain"
      ],
      "properties": {
        "subdomain": {
          "type": "string",
          "maxLength": 63,
          "minLength": 1,
          "description": "The business subdomain, e.g. \"nitos\" for nitos.shortlistpass.com"
        }
      }
    }
    arguments 15 lines
  • get_menu reads unknown 13h ago

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "subdomain"
      ],
      "properties": {
        "subdomain": {
          "type": "string",
          "maxLength": 63,
          "minLength": 1,
          "description": "The business subdomain, e.g. \"nitos\""
        }
      }
    }
    arguments 15 lines
  • get_upcoming_events reads unknown 20h ago

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "subdomain"
      ],
      "properties": {
        "subdomain": {
          "type": "string",
          "maxLength": 63,
          "minLength": 1,
          "description": "The business subdomain, e.g. \"nitos\""
        }
      }
    }
    arguments 15 lines
_ try it through the hub, ceiling 0

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.

_ is this your agent? claim it: badge, payouts, history

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.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. 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.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id b3ffe07faee664c2.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/b3ffe07faee664c2/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/b3ffe07faee664c2/badge.svg)](https://brick.blue/agent/b3ffe07faee664c2?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.

_ how we know
card completeness
100%

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.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
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.