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

tw-food-oracle

https://food.penguindriver.com

Registry code: 17d5eca638fc0e27

api record

臺灣「今天吃什麼」美食抽籤(繁體中文):選神明、餐別、美食種類與預算抽籤;給座標可找附近營業中店家。店家資料來自 OpenStreetMap(或 Google 地圖),附 Google 地圖與 Uber Eats 連結。

endpoint
https://food.penguindriver.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 tw-food-oracle live?
Yes — it answered the hub's last check (checked 1h ago). It answered 99% of checks over the last 30 days.
Is tw-food-oracle free to use?
Yes — the hub reached it with no key and no payment.
What tools does tw-food-oracle have?
4 tools: draw_food_fortune, find_nearby_restaurants, list_food_categories, list_deities.
Is tw-food-oracle 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.2%

90 days 99.5%· all time 99.5%

latency
340ms

last good check

priced tools
0

of 4 tools

_ answered our checks, 90 days 368 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • unknown → live
_ what it is for
used for
  • draw a random food suggestion
  • find nearby open restaurants in taiwan
  • list food categories by budget
takes → gives
text → data
tools
4 reads
_ 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 4 tools
2 open 2 never probed 2 of 4 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.

  • list_food_categories reads open 7h ago

    列出 Uber Eats 常見的美食種類(台式早餐、便當、牛肉麵、火鍋、拉麵、手搖飲…),可依餐別與總預算篩選,附一般價格帶。

    mcp-tool

    {
      "type": "object",
      "properties": {
        "meal": {
          "enum": [
            "breakfast",
            "lunch",
            "snack",
            "dinner",
            "latenight"
          ],
          "type": "string"
        },
        "budget": {
          "type": "number"
        },
        "people": {
          "type": "integer"
        }
      }
    }
    arguments 21 lines
  • list_deities reads open 7h ago

    列出 10 位臺灣知名廟宇主神(媽祖、關聖帝君、土地公、月老、文昌帝君、觀音、保生大帝、玄天上帝、城隍爺、財神)與各自的美食風格。

    mcp-tool

    {
      "type": "object",
      "properties": {}
    }
    arguments 4 lines
  • draw_food_fortune reads unknown never probed

    美食神仙籤筒:今天吃什麼?依神明、餐別、美食種類與預算抽籤,回傳原創籤詩、料理;提供臺灣座標時,另從附近營業中的店家抽一間(附 Google 地圖與 Uber Eats 連結)。

    mcp-tool

    {
      "type": "object",
      "properties": {
        "lat": {
          "type": "number"
        },
        "lon": {
          "type": "number"
        },
        "meal": {
          "enum": [
            "breakfast",
            "lunch",
            "snack",
            "dinner",
            "latenight"
          ],
          "type": "string"
        },
        "deity": {
          "type": "string",
          "description": "神明 id 或名稱:mazu(媽祖)、guangong(關聖帝君)、tudigong(福德正神)、yuelao(月下老人)、wenchang(文昌帝君)、guanyin(觀世音菩薩)、baosheng(保生大帝)、xuantian(玄天上帝)、chenghuang(城隍爺)、caishen(財神爺)"
        },
        "budget": {
          "type": "number",
          "description": "總預算(新臺幣)"
        },
        "people": {
          "type": "integer"
        },
        "radius": {
          "type": "integer",
          "description": "公尺,預設 1500,最大 5000"
        },
        "category": {
          "type": "string",
          "description": "美食種類 id 或名稱,auto=神明決定"
        }
      }
    }
    arguments 40 lines
  • find_nearby_restaurants reads unknown 7h ago

    查臺灣某座標附近、符合美食種類且營業中(或未標示營業時間)的店家,依距離排序,附 Google 地圖與 Uber Eats 連結。

    mcp-tool

    {
      "type": "object",
      "required": [
        "lat",
        "lon",
        "category"
      ],
      "properties": {
        "lat": {
          "type": "number"
        },
        "lon": {
          "type": "number"
        },
        "radius": {
          "type": "integer"
        },
        "category": {
          "type": "string"
        }
      }
    }
    arguments 22 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 17d5eca638fc0e27.

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

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.

_ also on penguindriver.com 10 entries

Served from the same domain, which is what was measured. Not a claim that one owner runs them: ownership is what a passport proves, and each of these says for itself.

2 more sit on this domain. All of them.