Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

覓安居

REMOTE · MEANG.TW

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

Available components

+3 this week 72 Trust /100

Last scanned (13 hours ago)

Scores higher than 57% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Health and Science

Recent critical change

Authorization (11 Nov 2026). See the changelog before you install this server.

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security63
Transport & Reachability100
Schema Quality & AI Usability74
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 491 tokens (~54/item across 9 items; 9 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management40
  • Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 20 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

  • 18 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

  • 16 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

  • 14 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

  • 12 Nov 26 0
    • Tool “upsert_note” is now declared destructive security
  • 11 Nov 26 +3
    • Authorization: unverified → fail ▼ critical
    • Tool “delete_note” is now declared destructive security
    • Destructive annotations: All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation. functional
    • Server version: 0.2.0 → 0.2.1 functional
  • 10 Nov 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 9 Nov 26 65

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Probed https://meang.tw/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=meang.tw CN=YR2,O=Let's Encrypt,C=US 28 Oct 2026 26 Jan 2027 RSA 2048 SHA256-RSA 54a0cc545b5837e1f03af08550dc4607d79
SANs: meang.tw
CN=YR2,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA 4ebd24947e24d394802d84a52fd5b319
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of meang.tw. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
tw. DS published 46902 13 Verified
meang.tw. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=63072000
content-security-policy default-src 'self'; base-uri 'self'; object-src 'none'; frame-ancestors 'none'; form-action 'self' https://*.supabase.co; script-src 'self' 'unsafe-inline' https://www.googletagmanager.com https://challenges.cloudflare.com https://accounts.google.com; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com https://accounts.google.com; font-src 'self' https://fonts.gstatic.com data:; img-src 'self' data: https:; connect-src 'self' https://www.google-analytics.com https://analytics.google.com https://*.google-analytics.com https://challenges.cloudflare.com; frame-src https://challenges.cloudflare.com https://accounts.google.com
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://meang.tw/mcp Verified 200
http (plaintext) http://meang.tw/mcp HTTPS enforced 308 https://meang.tw/mcp
MCP tools · 9 exposed · ~491 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
delete_note ~41

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

NameTypeReqDescription
facility_idstringyes機構編號

No output schema declared.

No examples provided.

get_account_profile ~31

回傳目前登入者的姓名與 email(需 Authorization Bearer/OAuth)。沒有則為 null。

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_facility ~53

以機構 id 取得單一機構詳情(含名冊欄位;不含 sources/note/person_in_charge)。

NameTypeReqDescription
idstringyes機構編號

No output schema declared.

No examples provided.

get_note ~48

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

NameTypeReqDescription
facility_idstringyes機構編號

No output schema declared.

No examples provided.

list_city_counts ~29

回傳 22 縣市與機構數(沒有機構的是 0)。

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_district_counts ~40

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

NameTypeReqDescription
citystringyes縣市,例如「臺中市」

No output schema declared.

No examples provided.

list_notes ~24

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

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

search_facilities ~101

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

NameTypeReqDescription
citystring–縣市,例如「臺中市」
districtstring–行政區,例如「北屯區」
pageinteger–頁碼,預設 1
qstring–機構名稱關鍵字

No output schema declared.

No examples provided.

upsert_note ~124

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

NameTypeReqDescription
bodystring–筆記內文,可空
facility_idstringyes機構編號
statusstring–狀態:interested、considering、contacted、visited、waitlisted、rejected,或省略/空字串表示未設定

No output schema declared.

No examples provided.

Install

How do I install the 覓安居 MCP server?

覓安居 is a hosted endpoint at https://meang.tw/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · meang.tw

# add to Claude Code
claude mcp add --transport http tw-meang-meang 'https://meang.tw/mcp'
Common questions

What is the 覓安居 MCP server?

覓安居 is an MCP server listed in the public MCP registry as tw.meang/meang. Search Taiwan long-term care facilities; signed-in users get profile and notes. This page covers its hosted endpoint (https://meang.tw/mcp).

Is the 覓安居 MCP server safe to use?

覓安居 scores 72 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the 覓安居 MCP server expose?

覓安居 exposes 9 tools: search_facilities, get_facility, list_city_counts, list_district_counts, get_account_profile, and 4 more. Their descriptions and schemas cost roughly 491 tokens of context every time the server is loaded.

Does the 覓安居 MCP server require authentication?

No. We connected to 覓安居 without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the 覓安居 MCP server still maintained?

覓安居 is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the 覓安居 MCP server?

VerifyMCP ran 13 checks on 覓安居, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.