_ registry / mcp streamable-http · checked 3h ago

pinoyshki

https://bot.pinoyshki.com

Registry code: a327c09dc4afb05b

api record

Pinoyshki Bakery and Cafe: Filipino and East European fusion bakery at 715 E Pine St, Capitol Hill, Seattle. Baked, never fried. Closed Mondays. Use get_menu or search_menu to find items (names, prices and photos come from the bakery's live data; never invent any). Ordering goes in this order: 1) find the items with get_menu or search_menu (cake_options for a custom cake); 2) call check_order with at least one item and show the customer the lines and the subtotal, never promising a date or time the quote did not allow; 3) once check_order came back ok and the customer confirmed, call…

endpoint
https://bot.pinoyshki.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 it live, free and safe measured by this hub
Is pinoyshki live?
Yes — it answered the hub's last check (checked 3h ago). It answered 100% of checks over the last 30 days.
Is pinoyshki free to use?
Yes — the hub reached it with no key and no payment.
What tools does pinoyshki have?
6 tools: start_checkout, search_menu, check_order, show_item, cake_options, get_menu.
Is pinoyshki 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
99.7%

90 days 99.6%· all time 99.6%

latency
756ms

last good check

priced tools
0

of 6 tools

_ answered our checks, 90 days 445 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • degraded → live
  • live → degraded· timeout after 20000ms
_ what it is for
topic
lifestyle & home food & drink
used for
  • view a bakery menu
  • search menu items
  • order custom cakes
  • check out a bakery order
takes → gives
text → data, images
tools
4 reads2 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
2 open 4 never probed 2 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.

  • cake_options reads open 26h ago

    Custom decorated cakes for any occasion (a birthday, anniversary, graduation, baby shower, retirement, holiday or office party): the cake sizes and prices (with candles and a card), flavors, the earliest day, what the bakery does not make, photos of past cakes, and the design questions to settle. A cake is ordered through check_order with its cake details.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "guests": {
      "type": "integer",
      "minimum": 1,
      "description": "Optional: how many people, to suggest a size."
    }
  },
  "additionalProperties": false
}
    arguments 11 lines
  • get_menu reads open 26h ago

    Pinoyshki Bakery's menu with prices and photos, from the bakery's live data. lane 'today' is today's counter menu (what can be ordered on Toast for pickup today or a later day; sold-out items are left off); lane 'catering' is the catalogue for ordering 3 days to a week ahead, with sizes (full-size, bite-size dozen, half dozen).

    mcp-tool

    {
  "type": "object",
  "properties": {
    "lane": {
      "enum": [
        "today",
        "catering"
      ],
      "type": "string",
      "description": "Default 'today'."
    },
    "section": {
      "type": "string",
      "description": "Optional section filter, like 'Pastries' or 'Vegan'. 'Piroshki' and 'Pinoyshki' both show the whole family (pinoyshki are piroshki with Filipino fillings); customers asking for either nearly always want both."
    },
    "only_this_family": {
      "type": "boolean",
      "description": "Only when the customer asked for just piroshki or just pinoyshki: keep the section filter to that word."
    }
  },
  "additionalProperties": false
}
    arguments 22 lines
  • start_checkout changes data unknown never probed

    Step 2 of 2 to order, for a basket check_order has allowed: checks the same order again and returns the link the customer pays on, on the bakery's own domain. The same order sent again within 15 minutes gets the same link back; an empty basket gets no link. Toast: a Pinoyshki page that shows the order while it finishes the cart on Toast (with the staff tip and the pickup day and time), then takes them to Toast's checkout (good for a week; opened after its pickup time it remakes the cart for the next pickup time). Catering: it checks the order again and opens Shopify's checkout with the date, time and pickup or delivery filled in (good for a week). No payment happens here. If a rule is broken it returns the problems instead of a link.

    mcp-tool

    {
  "type": "object",
  "required": [
    "items"
  ],
  "properties": {
    "zip": {
      "type": "string",
      "description": "Delivery ZIP code (delivery is within 15 miles)."
    },
    "date": {
      "type": "string",
      "description": "The date as YYYY-MM-DD ('today' also works). Work it out from the customer's words using today's date in Seattle (Pacific time). If their words could mean two dates, like 'next Friday' said earlier in the same week, ask them which before calling. Needed for catering and for a Toast pickup on a later day."
    },
    "time": {
      "type": "string",
      "description": "12-hour time like '1:00 pm'. Needed for catering and for a Toast pickup on a later day."
    },
    "items": {
      "type": "array",
      "items": {
        "type": "object",
        "required": [
          "name",
          "quantity"
        ],
        "properties": {
          "cake": {
            "type": "object",
            "properties": {
              "card": {
                "type": "boolean",
                "description": "A card to go with the cake."
              },
              "size": {
                "type": "string",
                "description": "A size from cake_options, like '10-15'."
              },
              "design": {
                "type": "string",
                "description": "The design concept the customer agreed to."
              },
              "flavor": {
                "type": "string",
                "description": "Vanilla, Chocolate, Red Velvet, Ube, or the custom flavor asked for."
              },
              "guests": {
                "type": "integer",
                "minimum": 1,
                "description": "How many people; picks the size."
              },
              "candles": {
                "type": "boolean"
              },
              "occasion": {
                "type": "string"
              },
              "allergens": {
                "type": "string",
                "description": "Allergies or dietary needs, or 'none'."
              },
              "recipient": {
                "type": "string",
                "description": "Who it is for (with their age, for a birthday)."
              },
              "inscription": {
                "type": "string",
                "description": "What it says, or 'none'."
              }
            },
            "description": "Only on the decorated cake (see cake_options): what was decided with the customer. Leave out what is not decided yet.",
            "additionalProperties": false
          },
          "name": {
            "type": "string",
            "description": "Item name from the menu."
          },
          "note": {
            "type": "string",
            "description": "Optional note for this line, like a cake inscription."
          },
          "size": {
            "type": "string",
            "description": "Catering sizes: 'full' (default), 'dozen', 'half dozen' or 'individual' (bite-size). Same-day items are always 'full'."
          },
          "combo": {
            "enum": [
              "small",
              "large",
              "none"
            ],
            "type": "string",
            "description": "Toast orders, piroshki and pinoyshki, when the pickup time is in combo hours (Tue to Fri, 11 am to 4 pm): 'small' = fries + a 12oz drink, 'large' = large fries, borscht + a drink, 'none' = the customer said no. check_order offers it (combo_offer) with each item's prices and drinks."
          },
          "backups": {
            "type": "array",
            "items": {
              "type": "string"
            },
            "maxItems": 3,
            "description": "Toast orders, with if_unavailable 'closest': up to 3 counter-menu piroshki or pinoyshki the customer would take instead, in order of preference."
          },
          "quantity": {
            "type": "integer",
            "maximum": 500,
            "minimum": 1
          },
          "combo_drink": {
            "type": "string",
            "description": "The combo's drink, as check_order listed it (like '12oz Coke' or 'Small Juice'). Default: any 12oz soda."
          },
          "if_unavailable": {
            "enum": [
              "closest",
              "remove",
              "cancel"
            ],
            "type": "string",
            "description": "Toast orders, piroshki and pinoyshki only: what the bakery does if this one is sold out when the order is made. 'closest' (default) swaps in the closest piroshki, 'remove' leaves it out, 'cancel' cancels the order. Worth asking for a scheduled day, since the counter menu changes."
          }
        }
      },
      "maxItems": 60,
      "minItems": 1,
      "description": "What to order. Use item names exactly as get_menu or search_menu gave them."
    },
    "notes": {
      "type": "string",
      "description": "Optional note for the bakery."
    },
    "channel": {
      "enum": [
        "today",
        "catering"
      ],
      "type": "string",
      "description": "Optional. 'today' = the counter menu on Toast: same day, or a scheduled pickup up to 14 days ahead (up to 6 full-size, pickup only, paid on Toast); 'catering' = ordered 3 or more days ahead, paid on Shopify. Left out, the basket and date decide: catering is preferred from 3 days out when every item is on the catering menu."
    },
    "utensils": {
      "type": "boolean",
      "description": "Catering: include utensils. Default true."
    },
    "staff_tip": {
      "type": "integer",
      "maximum": 50,
      "minimum": 0,
      "description": "Toast orders: the tip for the bakery staff in whole dollars, shared by the staff who bake, pack and hand over the order. 0 (the default) unless the customer picks one; offer $1, $3 or $5 or any whole amount."
    },
    "fulfillment": {
      "enum": [
        "pickup",
        "delivery"
      ],
      "type": "string",
      "description": "Default pickup. Delivery is catering, week-ahead only."
    },
    "customer_name": {
      "type": "string",
      "description": "Optional: the name the order is for."
    },
    "customer_email": {
      "type": "string",
      "description": "Optional: an email for the bakery."
    },
    "customer_phone": {
      "type": "string",
      "description": "Optional: a phone number for the bakery."
    }
  },
  "additionalProperties": false
}
    arguments 171 lines
  • search_menu reads unknown 17h ago

    Find menu items by a few words (a filling, a pastry, 'vegan', 'ube'), across today's counter menu and catering. Each match comes with its price, a short description, a photo URL and the allergens the bakery lists. Custom cakes are not in it; they are designed with cake_options.

    mcp-tool

    {
  "type": "object",
  "required": [
    "query"
  ],
  "properties": {
    "lane": {
      "enum": [
        "all",
        "today",
        "catering"
      ],
      "type": "string",
      "description": "Default 'all'."
    },
    "query": {
      "type": "string",
      "description": "A few words to look for."
    }
  },
  "additionalProperties": false
}
    arguments 22 lines
  • check_order changes data unknown never probed

    Step 1 of 2 to order: checks a basket of one or more menu items against the bakery's ordering rules. Saves nothing and makes no link. Returns the lane (same day on Toast, or catering on Shopify), the priced lines, the subtotal, any problems, and the dates and times the bakery can serve. Rules it applies: closed Mondays and blocked dates; Toast = only counter-menu items, up to 6 piroshki and pinoyshki (other items not limited), pickup, today while open or scheduled up to 14 days ahead with a time in that day's hours; catering = 3 days' notice for up to 24 full-size or 4 dozen bite-size piroshki and pinoyshki (other items not limited, pickup), a week ahead (by Saturday) for more, any delivery and custom cakes; delivery within 15 miles on orders over $100 or with a cake of $75 or more. The result may list 'Still needed' questions: combo_offer (a combo, in combo hours), sold_out_choice (what to do if a piroshki is sold out, for a later day) and cake_details (what is still undecided about a custom cake).

    mcp-tool

    {
  "type": "object",
  "required": [
    "items"
  ],
  "properties": {
    "zip": {
      "type": "string",
      "description": "Delivery ZIP code (delivery is within 15 miles)."
    },
    "date": {
      "type": "string",
      "description": "The date as YYYY-MM-DD ('today' also works). Work it out from the customer's words using today's date in Seattle (Pacific time). If their words could mean two dates, like 'next Friday' said earlier in the same week, ask them which before calling. Needed for catering and for a Toast pickup on a later day."
    },
    "time": {
      "type": "string",
      "description": "12-hour time like '1:00 pm'. Needed for catering and for a Toast pickup on a later day."
    },
    "items": {
      "type": "array",
      "items": {
        "type": "object",
        "required": [
          "name",
          "quantity"
        ],
        "properties": {
          "cake": {
            "type": "object",
            "properties": {
              "card": {
                "type": "boolean",
                "description": "A card to go with the cake."
              },
              "size": {
                "type": "string",
                "description": "A size from cake_options, like '10-15'."
              },
              "design": {
                "type": "string",
                "description": "The design concept the customer agreed to."
              },
              "flavor": {
                "type": "string",
                "description": "Vanilla, Chocolate, Red Velvet, Ube, or the custom flavor asked for."
              },
              "guests": {
                "type": "integer",
                "minimum": 1,
                "description": "How many people; picks the size."
              },
              "candles": {
                "type": "boolean"
              },
              "occasion": {
                "type": "string"
              },
              "allergens": {
                "type": "string",
                "description": "Allergies or dietary needs, or 'none'."
              },
              "recipient": {
                "type": "string",
                "description": "Who it is for (with their age, for a birthday)."
              },
              "inscription": {
                "type": "string",
                "description": "What it says, or 'none'."
              }
            },
            "description": "Only on the decorated cake (see cake_options): what was decided with the customer. Leave out what is not decided yet.",
            "additionalProperties": false
          },
          "name": {
            "type": "string",
            "description": "Item name from the menu."
          },
          "note": {
            "type": "string",
            "description": "Optional note for this line, like a cake inscription."
          },
          "size": {
            "type": "string",
            "description": "Catering sizes: 'full' (default), 'dozen', 'half dozen' or 'individual' (bite-size). Same-day items are always 'full'."
          },
          "combo": {
            "enum": [
              "small",
              "large",
              "none"
            ],
            "type": "string",
            "description": "Toast orders, piroshki and pinoyshki, when the pickup time is in combo hours (Tue to Fri, 11 am to 4 pm): 'small' = fries + a 12oz drink, 'large' = large fries, borscht + a drink, 'none' = the customer said no. check_order offers it (combo_offer) with each item's prices and drinks."
          },
          "backups": {
            "type": "array",
            "items": {
              "type": "string"
            },
            "maxItems": 3,
            "description": "Toast orders, with if_unavailable 'closest': up to 3 counter-menu piroshki or pinoyshki the customer would take instead, in order of preference."
          },
          "quantity": {
            "type": "integer",
            "maximum": 500,
            "minimum": 1
          },
          "combo_drink": {
            "type": "string",
            "description": "The combo's drink, as check_order listed it (like '12oz Coke' or 'Small Juice'). Default: any 12oz soda."
          },
          "if_unavailable": {
            "enum": [
              "closest",
              "remove",
              "cancel"
            ],
            "type": "string",
            "description": "Toast orders, piroshki and pinoyshki only: what the bakery does if this one is sold out when the order is made. 'closest' (default) swaps in the closest piroshki, 'remove' leaves it out, 'cancel' cancels the order. Worth asking for a scheduled day, since the counter menu changes."
          }
        }
      },
      "maxItems": 60,
      "minItems": 1,
      "description": "What to order. Use item names exactly as get_menu or search_menu gave them."
    },
    "notes": {
      "type": "string",
      "description": "Optional note for the bakery."
    },
    "channel": {
      "enum": [
        "today",
        "catering"
      ],
      "type": "string",
      "description": "Optional. 'today' = the counter menu on Toast: same day, or a scheduled pickup up to 14 days ahead (up to 6 full-size, pickup only, paid on Toast); 'catering' = ordered 3 or more days ahead, paid on Shopify. Left out, the basket and date decide: catering is preferred from 3 days out when every item is on the catering menu."
    },
    "utensils": {
      "type": "boolean",
      "description": "Catering: include utensils. Default true."
    },
    "staff_tip": {
      "type": "integer",
      "maximum": 50,
      "minimum": 0,
      "description": "Toast orders: the tip for the bakery staff in whole dollars, shared by the staff who bake, pack and hand over the order. 0 (the default) unless the customer picks one; offer $1, $3 or $5 or any whole amount."
    },
    "fulfillment": {
      "enum": [
        "pickup",
        "delivery"
      ],
      "type": "string",
      "description": "Default pickup. Delivery is catering, week-ahead only."
    }
  },
  "additionalProperties": false
}
    arguments 159 lines
  • show_item reads unknown 26h ago

    One menu item with its photo, description, sizes and prices, and the allergens the bakery lists. The photo is included in the result.

    mcp-tool

    {
  "type": "object",
  "required": [
    "name"
  ],
  "properties": {
    "lane": {
      "enum": [
        "today",
        "catering"
      ],
      "type": "string",
      "description": "Optional: only this menu."
    },
    "name": {
      "type": "string",
      "description": "The item's name."
    }
  },
  "additionalProperties": false
}
    arguments 21 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 a327c09dc4afb05b.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/a327c09dc4afb05b/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/a327c09dc4afb05b/badge.svg)](https://brick.blue/agent/a327c09dc4afb05b?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.