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

tw-life-info

https://life.penguindriver.com

Registry code: c61b27b6ad502694

api record

台灣連假與補班、彩券開獎與對獎、統一發票對獎、油價。

endpoint
https://life.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-life-info live?
Yes — it answered the hub's last check (checked 4h ago). It answered 100% of checks over the last 30 days.
Is tw-life-info free to use?
Yes — the hub reached it with no key and no payment.
What tools does tw-life-info have?
7 tools: check_lottery, is_holiday, get_lottery_results, check_invoice, get_fuel_prices, get_holidays, get_invoice_numbers.
Is tw-life-info 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
100%

90 days 100%· all time 100%

latency
121ms

last good check

priced tools
0

of 7 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ 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 7 tools
3 open 4 never probed 3 of 7 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.

  • get_fuel_prices open 4h ago

    取得台灣中油本週油價（92、95、98 無鉛汽油、酒精汽油、超級柴油，每公升新台幣）與比上週漲跌。

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • get_holidays open 4h ago

    取得台灣國定假日、連假與補班日（依人事行政總處辦公日曆），含今天是否放假、下一個連假。

    mcp-tool

    {
  "type": "object",
  "properties": {
    "year": {
      "type": "number",
      "description": "年份（西元），不填則回傳今天起的近期資訊"
    }
  }
}
    arguments 9 lines
  • get_invoice_numbers open 4h ago

    取得台灣統一發票中獎號碼（特別獎、特獎、頭獎）與領獎期間。

    mcp-tool

    {
  "type": "object",
  "properties": {
    "period": {
      "type": "string",
      "description": "期別，例如 115-05-06；不填為最新一期"
    }
  }
}
    arguments 9 lines
  • check_lottery unknown never probed

    幫使用者對彩券：輸入遊戲與號碼，回傳對中幾個、獎項、每注獎金與兌獎期限。

    mcp-tool

    {
  "type": "object",
  "required": [
    "game",
    "numbers"
  ],
  "properties": {
    "game": {
      "enum": [
        "lotto649",
        "superlotto638",
        "daily539"
      ],
      "type": "string"
    },
    "period": {
      "type": "string"
    },
    "second": {
      "type": "number",
      "description": "威力彩第二區（1–8）"
    },
    "numbers": {
      "type": "array",
      "items": {
        "type": "number"
      }
    }
  }
}
    arguments 30 lines
  • is_holiday unknown never probed

    查詢台灣某一天是否放假（含補假、補班）。

    mcp-tool

    {
  "type": "object",
  "required": [
    "date"
  ],
  "properties": {
    "date": {
      "type": "string",
      "description": "YYYY-MM-DD"
    }
  }
}
    arguments 12 lines
  • get_lottery_results unknown never probed

    取得台灣彩券大樂透、威力彩、今彩539 開獎號碼與各獎項獎金。

    mcp-tool

    {
  "type": "object",
  "properties": {
    "game": {
      "enum": [
        "lotto649",
        "superlotto638",
        "daily539"
      ],
      "type": "string"
    },
    "period": {
      "type": "string",
      "description": "期別，不填為最新"
    }
  }
}
    arguments 17 lines
  • check_invoice unknown never probed

    幫使用者對統一發票：輸入 8 碼發票號碼，回傳是否中獎、獎別、獎金與領獎期間。

    mcp-tool

    {
  "type": "object",
  "required": [
    "number"
  ],
  "properties": {
    "number": {
      "type": "string",
      "description": "8 碼發票號碼"
    },
    "period": {
      "type": "string",
      "description": "期別，不填為最新一期"
    }
  }
}
    arguments 16 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 c61b27b6ad502694.

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

_ also on penguindriver.com 9 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.

1 more sit on this domain. All of them.