AI法拍雷達
REMOTE · FORECLOSURE-RADAR.COM
台灣法院法拍案件唯讀查詢：搜尋案件、單案標的與風險字樣、縣市行政區概況、知識庫、降價階梯與逾期差額試算。免費免註冊。
Available components
Last scanned (8 hours ago)
Scores higher than 62% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Finance and Payments
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 Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability64
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 2020 tokens (~288/item across 7 items; 7 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management30
- Stability observed for 9 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
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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 →
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.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 27 Oct 26 70
First indexed and scored.
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 5 Nov 2026 · Probed https://foreclosure-radar.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=enterprise-radar.com | CN=YR2,O=Let's Encrypt,C=US | 21 Oct 2026 | 19 Jan 2027 | RSA 2048 | SHA256-RSA | 62598ca8ac214782acc9c6968582f6c9e6e |
| SANs: enterprise-radar.com, foreclosure-radar.com, tenderrader.com, wecan-ai.com, www.enterprise-radar.com, www.foreclosure-radar.com, www.tenderrader.com, www.wecan-ai.com | ||||||
| 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 foreclosure-radar.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| foreclosure-radar.com. | 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=31556926 |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(), payment=(), usb=(), magnetometer=(), gyroscope=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://foreclosure-radar.com/mcp | Verified | 200 | |
| http (plaintext) | http://foreclosure-radar.com/mcp | HTTPS enforced | 301 | https://foreclosure-radar.com/mcp |
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 →
calc_payment_shortfall 得標後尾款與逾期差額試算 ~265
給得標價與已繳保證金（你自己填的數字），算尾款（得標價減保證金）；若逾期不繳，依強制執行法第 68-2 條試算「再拍賣價金低於原得標價加費用」的差額、保證金能不能抵、還欠多少。再拍賣價金與費用是你的假設（不給就回 100%／90%／80%／70% 對照），不是預測。
| Name | Type | Req | Description |
|---|---|---|---|
| bid_price_twd | number | yes | 得標價（新臺幣元） |
| deposit_twd | number | yes | 已繳保證金（元，不可大於得標價） |
| resale_cost_twd | number | – | （選填）假設的再拍賣所生費用（元，預設 0） |
| resale_price_twd | number | – | （選填）假設的再拍賣價金（元）；給的話算單一情境，不給就回 100%／90%／80%／70% 四種對照 |
No output schema declared.
No examples provided.
calc_price_cut_floor 降價階梯計算（法定下限） ~198
給第一拍的底價（你自己填的數字），算出二拍、三拍底價「依法不會低於」多少（強制執行法第 91、92 條：每次酌減不得逾 20%，所以二拍不低於 80%、三拍不低於 64%）；選填目前公告底價，可再算「下一次減價的最低可能」。這是法定下限不是預測，不查任何案件、不提供案件底價。
| Name | Type | Req | Description |
|---|---|---|---|
| current_price_twd | number | – | （選填）目前公告的底價（元）；給的話會多算「再減一次依法最低不會低於多少」 |
| first_round_price_twd | number | yes | 第一拍的底價（新臺幣元）。由你提供，這個工具不會去查任何案件 |
No output schema declared.
No examples provided.
get_auction_case 查單一法拍案件 ~165
用案件 id 或案件頁路徑查一案的公開資訊：標的物（地址／地號、面積、權利範圍、點交）、拍次與開標日、公告風險字樣（附判定依據）、公告載明的使用分區、承買資格限制、拍次變化記錄。底價、拍定價與官方公告 PDF 需登入網站查看，會在 locked_on_website 說明。
| Name | Type | Req | Description |
|---|---|---|---|
| case | string | yes | 案件 id（search_auctions 回的 id，例如 TPD_115_司執_085340），或案件頁路徑（例如 TPD/115-司執-085340） |
No output schema declared.
No examples provided.
get_auction_overview 法拍概況與資料新鮮度 ~99
回傳 AI法拍雷達收錄的法拍案件概況：進行中與停拍件數、房屋／土地／動產件數、7 天與 30 天內開標件數、近期新上架，以及資料更新到什麼時候（司法院系統停機時會明講資料停更）。回答「現在有多少法拍」前先看這個。
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_district_overview 縣市／行政區法拍概況 ~229
查某縣市或某行政區進行中的法拍件數、房屋／土地／動產分布、最近開標日、30 天內開標件數、公告點交比例；不給縣市時列出各區件數。不含底價或行情。
| Name | Type | Req | Description |
|---|---|---|---|
| county | string | yes | 縣市，臺／台皆可。可用：基隆市、臺北市、新北市、桃園市、新竹市、新竹縣、苗栗縣、臺中市、彰化縣、南投縣、雲林縣、嘉義市、嘉義縣、臺南市、高雄市、屏東縣、宜蘭縣、花蓮縣、臺東縣、澎湖縣、金門縣、連江縣 |
| district | string | – | 鄉鎮市區（可省略，省略則列出該縣市各區的件數） |
No output schema declared.
No examples provided.
search_auctions 搜尋法拍案件 ~610
依縣市、行政區、類型（房屋／土地／動產）、拍次、點交、開標日期範圍、法院、地址關鍵字、風險字樣排除、空屋、全部產權篩選進行中的法拍案件，最多 10 筆；每筆有地址、法院與案號、拍次、開標日、點交、公告風險字樣、使用分區與案件頁網址。不提供底價，也不能依價格篩選或排序（底價登入網站後查看）。
| Name | Type | Req | Description |
|---|---|---|---|
| county | string | – | 縣市，臺／台皆可。可用：基隆市、臺北市、新北市、桃園市、新竹市、新竹縣、苗栗縣、臺中市、彰化縣、南投縣、雲林縣、嘉義市、嘉義縣、臺南市、高雄市、屏東縣、宜蘭縣、花蓮縣、臺東縣、澎湖縣、金門縣、連江縣 |
| court | string | – | 法院名稱關鍵字，例如「臺北」「新北」 |
| district | string | – | 鄉鎮市區，例如「大安區」；要同時給 county |
| exclude_risks | string | – | 不要有這些風險字樣，逗號分隔。可用：occ、rent、illegal、defect、death、noroad、landbuild、unclear、prior（沒解析到的案件不受影響） |
| handover | string | – | 公告「點交」欄：Y＝點交、N＝不點交（只看公告明確寫的） |
| keyword | string | – | 地址、地號或案號關鍵字 |
| kind | string | – | house＝房屋、land＝土地、movable＝動產 |
| limit | integer | – | 最多回幾筆（上限 10） |
| round | string | – | 拍次：1～4＝第幾拍（4＝第 4 拍以上）、buy＝特別程序（應買） |
| sale_within_days | integer | – | 開標日在今天起幾天內（不含應買） |
| sort | string | – | sale_date＝開標日由近到遠、newest＝最近上架。刻意沒有價格排序 |
| status | string | – | 進行中（預設）、停拍、或全部 |
| vacant_only | boolean | – | 只看公告標示空屋或空地的 |
| whole_ownership_only | boolean | – | 只看全部產權（排除持分與公同共有） |
No output schema declared.
No examples provided.
search_guides 檢索法拍知識庫 ~171
用問題或關鍵字檢索 AI法拍雷達的法拍知識庫（強制執行法、土地法等法條逐條核對）：點交與不點交、優先承買權、繳款期限與逾期差額、農地與原住民保留地誰不能買、公告怎麼讀等，回傳摘要、簡短回答、法規出處（全國法規資料庫）與查證日。
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | 最多回幾篇（上限 5） |
| q | string | yes | 問題或關鍵字，例如「不點交是什麼意思」「拍到後要多久繳款」「農地誰不能買」 |
No output schema declared.
No examples provided.
How do I install the AI法拍雷達 MCP server?
AI法拍雷達 is a hosted endpoint at https://foreclosure-radar.com/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 · foreclosure-radar.com
claude mcp add --transport http com-foreclosure-radar-mcp 'https://foreclosure-radar.com/mcp'
What is the AI法拍雷達 MCP server?
AI法拍雷達 is an MCP server listed in the public MCP registry as com.foreclosure-radar/mcp. 台灣法院法拍案件唯讀查詢：搜尋案件、單案標的與風險字樣、縣市行政區概況、知識庫、降價階梯與逾期差額試算。免費免註冊。 This page covers its hosted endpoint (https://foreclosure-radar.com/mcp).
Is the AI法拍雷達 MCP server safe to use?
AI法拍雷達 scores 74 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 AI法拍雷達 MCP server expose?
AI法拍雷達 exposes 7 tools: get_auction_overview, search_auctions, get_auction_case, get_district_overview, calc_price_cut_floor, and 2 more. Their descriptions and schemas cost roughly 1,737 tokens of context every time the server is loaded.
Does the AI法拍雷達 MCP server require authentication?
No. We connected to AI法拍雷達 without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the AI法拍雷達 MCP server still maintained?
AI法拍雷達 is still listed as active in the MCP registry. We last reached this channel on 5 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 AI法拍雷達 MCP server?
VerifyMCP ran 13 checks on AI法拍雷達, 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.