Remote MCP · Endpoint
エージェント図鑑(医療・介護・保育) MCP server
Yes, as of 1 day ago: the server returned an HTTP error.
DownLast checked 1 day ago
Server URL
https://agentzukan.com/mcp
The last check failed: the server returned an HTTP error.
- Registry name
- com.agentzukan/japan-medical-facilities
- Transport
- Streamable HTTP
- Protocol negotiated
- Not measured yet
- Handshake latency
- —
- Tools exposed
- 10 tools
- Uptime, last 30 days
- 3 checks from 3 checks
- Described by its publisher as
- 全国の医療機関224,540件・介護事業所189,943件・保育施設(東京・大阪パイロット)を検索できるMCPサーバー。地点と半径による商圏集計にも対応。
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 day ago | Failed - the server returned an HTTP error | — |
| 5 days ago | Handshake completed | 69 ms |
| 16 days ago | Handshake completed | 99 ms |
The last 3 checks. Full history is kept for 30 days; the all-time counter stands at 2 responding of 3.
How to read this
- ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
- ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
- ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
- ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.
Listing data comes from the official MCP registry. Glide is not affiliated with エージェント図鑑(医療・介護・保育) and makes no claim about it beyond what these checks measured.