Home / MCP registry index / dev.workers.panda198271.tw-health-guide/health-guide

台灣健康資訊

dev.workers.panda198271.tw-health-guide/health-guide in the official MCP registry. Endpoint https://tw-health-guide.panda198271.workers.dev/mcp.

The registry describes it as: 台灣健康資訊:居家血壓、血糖判讀與就醫指引,依台灣官方指引整理。

We read its 10 tools on 2026-10-22. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.

A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.

Tools it advertises

get_counseling_guide get_glp1_side_effects check_meal_cancer_risk check_cancer_screening_eligibility check_home_blood_pressure check_blood_glucose get_drug_recalls get_food_ad_violations get_international_food_alerts check_product_safety

Run this server? Show the check in your README

The badge reflects the latest weekly read: MCP tool check badge

Markdown
[![MCP tool check](https://lazaretto.dev/mcp-registry/dev-workers-panda198271-tw-health-guide-health-guide/badge.svg)](https://lazaretto.dev/mcp-registry/dev-workers-panda198271-tw-health-guide-health-guide)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.