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

tw-digital-wellness

https://tw-digital-wellness.panda198271.workers.dev

Registry code: bae466a38142c81d

api record

台灣視訊看診資格、身心自評計分（附求助專線）、睡眠、呼吸放鬆、3C 使用。自評結果不是診斷；遇到自殺風險請提供 1925 安心專線。

endpoint
https://tw-digital-wellness.panda198271.workers.dev/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-digital-wellness live?
Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
Is tw-digital-wellness free to use?
Yes — the hub reached it with no key and no payment.
What tools does tw-digital-wellness have?
8 tools: score_mood_thermometer, score_phq9, crisis_lines, digital_wellness_guide, breathing_exercises, score_gad7, calc_sleep_times, check_telehealth_eligibility.
Is tw-digital-wellness 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 99.6%· all time 99.6%

latency
207ms

last good check

priced tools
0

of 8 tools

_ answered our checks, 90 days 274 checks · signed record
  • degraded → live
  • degraded → live
  • live → degraded· timeout after 20000ms
  • unknown → live
_ what it is for
topic
health & science health & medical
used for
  • score phq-9 depression screening
  • check telehealth eligibility
  • calculate sleep times
  • list crisis hotlines
takes → gives
text, data → text, data
tools
8 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 8 tools
1 open 7 never probed 1 of 8 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.

  • check_telehealth_eligibility reads open 16h ago

    台灣通訊診察（視訊、電話看診）資格：113-07-01 起 11 種特殊情形、可否開處方、流程。situation 可用：remote(山地、離島、偏僻地區)、acute_post(急性後期照護)、chronic_plan(慢性病照護計畫收案病人)、ltc(長期照顧服務對象)、family_doc(家庭醫師收治照護)、home_care(居家醫療照護)、terminal(疾病末期照護)、mobility(行動不便照護)、prison(矯正機關收容照護)、disaster(災害、傳染病或其他重大變故照護)、intl(國際醫療照護)；不填則列出全部。

    mcp-tool

    {
  "type": "object",
  "properties": {
    "situation": {
      "type": "string"
    }
  }
}
    arguments 8 lines
  • score_mood_thermometer reads unknown never probed

    心情溫度計（BSRS-5）計分：5 題 0–4 分加自殺意念附加題，回傳程度、建議與求助專線。不是診斷。

    mcp-tool

    {
  "type": "object",
  "required": [
    "answers"
  ],
  "properties": {
    "answers": {
      "type": "array",
      "items": {
        "type": "number"
      }
    },
    "suicide": {
      "type": "number"
    }
  }
}
    arguments 17 lines
  • score_phq9 reads unknown never probed

    PHQ-9 憂鬱症狀計分：9 題 0–3 分，回傳嚴重度與第 9 題警示。不是診斷。

    mcp-tool

    {
  "type": "object",
  "required": [
    "answers"
  ],
  "properties": {
    "answers": {
      "type": "array",
      "items": {
        "type": "number"
      }
    }
  }
}
    arguments 14 lines
  • crisis_lines reads unknown never probed

    台灣心理危機求助專線：1925 安心專線、1995 生命線、1980 張老師、119。

    mcp-tool

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

    兒童螢幕時間建議（WHO）、減少手機使用方法、健康與心理諮商 App 隱私檢查清單。

    mcp-tool

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

    呼吸放鬆方法：方塊呼吸、4-7-8、共振呼吸、生理嘆息的節奏與適用時機。

    mcp-tool

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

    GAD-7 焦慮症狀計分：7 題 0–3 分，回傳嚴重度。不是診斷。

    mcp-tool

    {
  "type": "object",
  "required": [
    "answers"
  ],
  "properties": {
    "answers": {
      "type": "array",
      "items": {
        "type": "number"
      }
    }
  }
}
    arguments 14 lines
  • calc_sleep_times reads unknown never probed

    依 90 分鐘睡眠週期計算建議就寢或起床時間，附各年齡建議睡眠時數。

    mcp-tool

    {
  "type": "object",
  "properties": {
    "bed": {
      "type": "string",
      "description": "HH:MM"
    },
    "wake": {
      "type": "string",
      "description": "HH:MM"
    },
    "latency": {
      "type": "number"
    }
  }
}
    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 bae466a38142c81d.

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