Remote MCP · Endpoint
AI法拍雷達 MCP server
No. AI法拍雷達 answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://foreclosure-radar.com/mcp
The last check completed an MCP handshake.
- Registry name
- com.foreclosure-radar/mcp
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 293 ms
- Tools exposed
- 7 tools
- Uptime, last 30 days
- 4 checks from 4 checks
- Described by its publisher as
- 台灣法院法拍案件唯讀查詢：搜尋案件、單案標的與風險字樣、縣市行政區概況、知識庫、降價階梯與逾期差額試算。免費免註冊。
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 293 ms |
| 9 hours ago | Handshake completed | 326 ms |
| 2 days ago | Handshake completed | 315 ms |
| 4 days ago | Handshake completed | 337 ms |
The last 4 checks. Full history is kept for 30 days; the all-time counter stands at 4 responding of 4.
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 AI法拍雷達 and makes no claim about it beyond what these checks measured.