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

meang

https://meang.tw

Registry code: ce77825a51c1e9af

api record

Search Taiwan long-term care facilities; signed-in users get profile and notes.

from a public catalogue that lists it, not from the operator

endpoint
https://meang.tw/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 meang live?
Yes — it answered the hub's last check (checked 23m ago). It answered 100% of checks over the last 30 days.
Is meang free to use?
Partly — some of its tools are open, others need a key or payment.
What tools does meang have?
9 tools: list_district_counts, get_facility, get_note, upsert_note, delete_note, list_city_counts, search_facilities, list_notes, ….
Is meang 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
440ms

last good check

priced tools
0

of 9 tools

_ answered our checks, 90 days 2 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 9 tools
2 open2 auth-required 5 never probed 4 of 9 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_city_counts open 23m ago

    回傳 22 縣市與機構數（沒有機構的是 0）。

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "properties": {}
}
    arguments 5 lines
  • search_facilities open 23m ago

    依縣市、行政區或名稱搜尋長照機構。一頁最多 12 筆，回傳卡片欄位。

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "properties": {
    "q": {
      "type": "string",
      "description": "機構名稱關鍵字"
    },
    "city": {
      "type": "string",
      "description": "縣市，例如「臺中市」"
    },
    "page": {
      "type": "integer",
      "maximum": 9007199254740991,
      "description": "頁碼，預設 1",
      "exclusiveMinimum": 0
    },
    "district": {
      "type": "string",
      "description": "行政區，例如「北屯區」"
    }
  }
}
    arguments 24 lines
  • list_notes auth-required 27h ago

    列出目前登入者的私人筆記（需 Authorization Bearer）。

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "properties": {}
}
    arguments 5 lines
  • get_account_profile auth-required 23m ago

    回傳目前登入者的姓名與 email（需 Authorization Bearer／OAuth）。沒有則為 null。

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "properties": {}
}
    arguments 5 lines
  • list_district_counts unknown never probed

    回傳指定縣市的行政區與機構數。

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "city"
  ],
  "properties": {
    "city": {
      "type": "string",
      "minLength": 1,
      "description": "縣市，例如「臺中市」"
    }
  }
}
    arguments 14 lines
  • get_facility unknown never probed

    以機構 id 取得單一機構詳情（含名冊欄位；不含 sources／note／person_in_charge）。

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "id"
  ],
  "properties": {
    "id": {
      "type": "string",
      "minLength": 1,
      "description": "機構編號"
    }
  }
}
    arguments 14 lines
  • get_note unknown never probed

    讀取目前登入者對指定機構的筆記；沒有則 note 為 null（需 Authorization Bearer）。

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "facility_id"
  ],
  "properties": {
    "facility_id": {
      "type": "string",
      "minLength": 1,
      "description": "機構編號"
    }
  }
}
    arguments 14 lines
  • upsert_note unknown never probed

    新增或更新目前登入者對指定機構的筆記（需 Authorization Bearer）。body 最多 2000 字；status 可為 interested／considering／contacted／visited／waitlisted／rejected 或空。

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "facility_id"
  ],
  "properties": {
    "body": {
      "type": "string",
      "description": "筆記內文，可空"
    },
    "status": {
      "type": "string",
      "description": "狀態：interested、considering、contacted、visited、waitlisted、rejected，或省略／空字串表示未設定"
    },
    "facility_id": {
      "type": "string",
      "minLength": 1,
      "description": "機構編號"
    }
  }
}
    arguments 22 lines
  • delete_note unknown never probed

    刪除目前登入者對指定機構的筆記（需 Authorization Bearer）。

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "facility_id"
  ],
  "properties": {
    "facility_id": {
      "type": "string",
      "minLength": 1,
      "description": "機構編號"
    }
  }
}
    arguments 14 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 ce77825a51c1e9af.

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