Skip to content

MCP servers › com.foreclosure-radar › mcp

MCP server · registry snapshot 2026-10-27 · last tested 2026-10-27

com.foreclosure-radar/mcp

AI法拍雷達 — the publisher's title

by foreclosure-radar.com · domain (the registry's namespace rule)Website ↗

台灣法院法拍案件唯讀查詢:搜尋案件、單案標的與風險字樣、縣市行政區概況、知識庫、降價階梯與逾期差額試算。免費免註冊。 — the publisher's description

1 of 2 record checks metRead-only · tools listed 2026-10-27version 1.1.0streamable HTTP7 tools

Summary

com.foreclosure-radar/mcp is a remote MCP server listed in the official MCP registry at version 1.1.0, under the namespace of the domain foreclosure-radar.com. On 2026-10-27 ProtocolProbe connected to it in read-only mode and read its inventory: 7 tools, 0 resources and 0 prompts.

Record checks

1 of 2 record checks met · 7 do not apply

  • met: Registry entry is active and says how to run it
  • not met: Source repository link opens
  • not applicable: Repository is not archived
  • not applicable: Code pushed to the repository in the 90 days before our check
  • not applicable: Repository publishes a security policy (SECURITY.md)
  • not applicable: Package names its licence with a standard (SPDX) identifier
  • not applicable: The version the registry lists can be installed and is not withdrawn
  • not applicable: npm package carries build provenance (attestation)
  • not applicable: No known critical or high advisory in the package or its dependencies
  • Not ranked by downloads: a remote server publishes no download figure
  • Not ranked by stars: no public GitHub repository

From public records, not a safety rating. Each check with its reason

Key facts

Runs
remote (hosted by the publisher)
Transport
streamable HTTP
Your own values
none declared (not a guarantee)
Sign-in
none needed to open a session
Tools
7
Last tested
2026-10-27

Tool list size

3,421 tokens on Claude Opus 5.5

Added to every request that loads this server's tools (7 tools). Counted with Anthropic's token counter on 2026-10-27, from the tool list we read on 2026-10-27. Median across 23,424 counted servers: 2,725 tokens. How it is counted

How a client gets in

Connects without signing in

Read from the server's public metadata on 2026-10-27 (foreclosure-radar.com), in our read-only connection; no tool was called. It may have changed since. How it is read

Tool list at the three APIs

Not sent yet for this version (1.1.0).

Add to your client

How fresh this is

Live-tested
yes, a real session (not a text-only review)
Last tested
2026-10-27
Mode
read-only (no tool calls)
Latest version
1.1.0, published 2026-10-27 (registry, as of the 2026-10-27 snapshot)
First listed version
2026-10-27 (earliest version still in the registry; older removed versions would be earlier)
Registry data
snapshot 2026-10-27
Package and repository
checked 2026-10-27
Engine
mcp-runtime-engine@0.1.0 · sdk@1.32.0

Dead or stale signals

None found in the records we hold

Looked for and not found: deprecated in the registry. Does not apply: listed version cannot be installed or is withdrawn; repository link does not open; repository archived; no push in over 365 days. Each line is a dated fact from a public record. It does not say whether the server still works, and a record can change after the date shown.

Changes since the last refresh

New in the registry: not in the list of 2026-10-26, listed on 2026-10-27 with version 1.1.0 (published 2026-10-27).

Source: the official MCP Registry list on 2026-10-26 and on 2026-10-27.

What it is

What does this server offer?

Observed inventory
7tools
0resources
0prompts

None of its 7 tools are described as changing anything. For 7 the reading was uncertain, so no mark is shown.

  • get_auction_overview

    “回傳 AI法拍雷達收錄的法拍案件概況:進行中與停拍件數、房屋/土地/動產件數、7 天與 30 天內開標件數、近期新上架,以及資料更新到什麼時候(司法院系統停機時會明講資料停更)。回答「現在有多少法拍」前先看這個。”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    Takes no inputs.

  • search_auctionson 2 other servers

    “依縣市、行政區、類型(房屋/土地/動產)、拍次、點交、開標日期範圍、法院、地址關鍵字、風險字樣排除、空屋、全部產權篩選進行中的法拍案件,最多 10 筆;每筆有地址、法院與案號、拍次、開標日、點交、公告風險字樣、使用分區與案件頁網址。不提供底價,也不能依價格篩選或排序(底價登入網站後查看)。”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    14 inputs
    • countystring“縣市,臺/台皆可。可用:基隆市、臺北市、新北市、桃園市、新竹市、新竹縣、苗栗縣、臺中市、彰化縣、南投縣、雲林縣、嘉義市、嘉義縣、臺南市、高雄市、屏東縣、宜蘭縣、花蓮縣、臺東縣、澎湖縣、金門縣、連江縣”
    • districtstring“鄉鎮市區,例如「大安區」;要同時給 county”
    • kindstring“house=房屋、land=土地、movable=動產”
    • roundstring“拍次:1~4=第幾拍(4=第 4 拍以上)、buy=特別程序(應買)”
    • handoverstring“公告「點交」欄:Y=點交、N=不點交(只看公告明確寫的)”
    • sale_within_daysinteger“開標日在今天起幾天內(不含應買)”
    • courtstring“法院名稱關鍵字,例如「臺北」「新北」”
    • keywordstring“地址、地號或案號關鍵字”
    • exclude_risksstring“不要有這些風險字樣,逗號分隔。可用:occ、rent、illegal、defect、death、noroad、landbuild、unclear、prior(沒解析到的案件不受影響)”
    • vacant_onlyboolean“只看公告標示空屋或空地的”
    • whole_ownership_onlyboolean“只看全部產權(排除持分與公同共有)”
    • statusstring“進行中(預設)、停拍、或全部”
    • sortstring“sale_date=開標日由近到遠、newest=最近上架。刻意沒有價格排序”
    • limitinteger“最多回幾筆(上限 10)”
  • get_auction_case

    “用案件 id 或案件頁路徑查一案的公開資訊:標的物(地址/地號、面積、權利範圍、點交)、拍次與開標日、公告風險字樣(附判定依據)、公告載明的使用分區、承買資格限制、拍次變化記錄。底價、拍定價與官方公告 PDF 需登入網站查看,會在 locked_on_website 說明。”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    1 input, 1 required
    • casestringrequired“案件 id(search_auctions 回的 id,例如 TPD_115_司執_085340),或案件頁路徑(例如 TPD/115-司執-085340)”
  • get_district_overviewon 1 other server

    “查某縣市或某行政區進行中的法拍件數、房屋/土地/動產分布、最近開標日、30 天內開標件數、公告點交比例;不給縣市時列出各區件數。不含底價或行情。”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    2 inputs, 1 required
    • countystringrequired“縣市,臺/台皆可。可用:基隆市、臺北市、新北市、桃園市、新竹市、新竹縣、苗栗縣、臺中市、彰化縣、南投縣、雲林縣、嘉義市、嘉義縣、臺南市、高雄市、屏東縣、宜蘭縣、花蓮縣、臺東縣、澎湖縣、金門縣、連江縣”
    • districtstring“鄉鎮市區(可省略,省略則列出該縣市各區的件數)”
  • calc_price_cut_floor

    “給第一拍的底價(你自己填的數字),算出二拍、三拍底價「依法不會低於」多少(強制執行法第 91、92 條:每次酌減不得逾 20%,所以二拍不低於 80%、三拍不低於 64%);選填目前公告底價,可再算「下一次減價的最低可能」。這是法定下限不是預測,不查任何案件、不提供案件底價。”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    2 inputs, 1 required
    • first_round_price_twdnumberrequired“第一拍的底價(新臺幣元)。由你提供,這個工具不會去查任何案件”
    • current_price_twdnumber“(選填)目前公告的底價(元);給的話會多算「再減一次依法最低不會低於多少」”
  • calc_payment_shortfall

    “給得標價與已繳保證金(你自己填的數字),算尾款(得標價減保證金);若逾期不繳,依強制執行法第 68-2 條試算「再拍賣價金低於原得標價加費用」的差額、保證金能不能抵、還欠多少。再拍賣價金與費用是你的假設(不給就回 100%/90%/80%/70% 對照),不是預測。”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    4 inputs, 2 required
    • bid_price_twdnumberrequired“得標價(新臺幣元)”
    • deposit_twdnumberrequired“已繳保證金(元,不可大於得標價)”
    • resale_price_twdnumber“(選填)假設的再拍賣價金(元);給的話算單一情境,不給就回 100%/90%/80%/70% 四種對照”
    • resale_cost_twdnumber“(選填)假設的再拍賣所生費用(元,預設 0)”
  • “用問題或關鍵字檢索 AI法拍雷達的法拍知識庫(強制執行法、土地法等法條逐條核對):點交與不點交、優先承買權、繳款期限與逾期差額、農地與原住民保留地誰不能買、公告怎麼讀等,回傳摘要、簡短回答、法規出處(全國法規資料庫)與查證日。”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    2 inputs, 1 required
    • qstringrequired“問題或關鍵字,例如「不點交是什麼意思」「拍到後要多久繳款」「農地誰不能買」”
    • limitinteger“最多回幾篇(上限 5)”

Each quoted sentence is the first sentence of the publisher’s own description. The kind of tool and the “changes data” mark are our AI model’s reading of that description, not something we tested: two differently worded runs had to agree, otherwise no label is shown, and nobody has checked them by hand. A tool without the “changes data” mark is described as only reading, searching or calculating, or the two runs did not agree. No tool was called. Read the publisher’s full description before relying on it. “Publisher declares” lists the hints the server itself sends with the tool (MCP annotations: read-only, destructive, idempotent, open-world); they are the publisher's claims, not checked by us. Inputs are the parameters in the tool's own input schema: name, declared type, whether it is required, and the first sentence of its description. Read 2026-10-27.

How well are its tools described?

Features #4 and #5

How clearly this server's own tool descriptions say what a tool does, and how consistent its tool list is. The first part is an AI model's yes/no reading of each description; the second part is counted. We do not turn it into a grade.

Descriptions

AI reading of each description

No AI reading was available for this server's tools (the two runs did not agree, or the listing was not reviewed).

Counted from the listing

Parameters with a description
100% of 25
Tools with a description
100% of 7
Typical description length
121 characters

The tool set

Counted from the listing

Tools
7
Size of the list
about 1,401 tokens for an agent to load (characters ÷ 4)
Naming
7 of 7 names use snake_case

AI reading: easy to mix up

No pair found.

The AI items cover 0 of 7 tools: for a tool where two differently worded runs disagreed, that item is left out. They were not checked by hand, and no tool was called. “Easy to mix up” means two tools whose names or descriptions overlap without saying how they differ; the AI found none. We do not rate whether the tool set is complete or whether side effects are spelled out, because our AI reading of those was not reliable enough.

How do I add it to my client?

Config from the registry entry

From the remote endpoint (Streamable HTTP)

We connected to this URL on 2026-10-27 (a read-only session: no tool was called).

Add to CursorAn install link in the format Cursor documents, holding the Cursor config below.

Claude Desktop or claude.ai
Settings → Connectors → Add custom connector, then paste:
https://foreclosure-radar.com/mcp
Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json
{
  "mcpServers": {
    "mcp": {
      "url": "https://foreclosure-radar.com/mcp"
    }
  }
}
VS Code · .vscode/mcp.json
{
  "servers": {
    "mcp": {
      "type": "http",
      "url": "https://foreclosure-radar.com/mcp"
    }
  }
}
VS Code (command line) · Bash or zsh terminal (macOS, Linux)
code --add-mcp '{"name":"mcp","type":"http","url":"https://foreclosure-radar.com/mcp"}'
Claude Code
claude mcp add --transport http mcp https://foreclosure-radar.com/mcp
Cline · cline_mcp_settings.json (Cline CLI: ~/.cline/data/settings/; in the editor: MCP Servers → Configure → Configure MCP Servers)
{
  "mcpServers": {
    "mcp": {
      "type": "streamableHttp",
      "url": "https://foreclosure-radar.com/mcp",
      "disabled": false,
      "autoApprove": []
    }
  }
}
Gemini CLI · ~/.gemini/settings.json, or .gemini/settings.json in a project
{
  "mcpServers": {
    "mcp": {
      "httpUrl": "https://foreclosure-radar.com/mcp"
    }
  }
}
OpenAI Codex · ~/.codex/config.toml, or .codex/config.toml in a trusted project
[mcp_servers.mcp]
url = "https://foreclosure-radar.com/mcp"
Zed · Zed settings file (command: zed: open settings file)
{
  "context_servers": {
    "mcp": {
      "url": "https://foreclosure-radar.com/mcp"
    }
  }
}
Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+
npx @modelcontextprotocol/inspector@2.11.0 --server-url https://foreclosure-radar.com/mcp --transport http
  • The server runs on the operator's infrastructure; it may ask you to sign in when you first connect.
  • Zed's docs we read on 2026-10-26 describe remote servers by URL and do not name the transport.
  • The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.

Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21; Cline, Gemini CLI, OpenAI Codex and Zed 2026-10-26). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.

Does the registry listing match what we found?

Feature #6

The registry verifies a package once, when it is published, and does not re-check it. A difference below is about the listing, not a judgement of the publisher.

Registry saysWe foundResultSource · date
Remote endpoint foreclosure-radar.com/mcpSession openedmatchesour test · 2026-10-27
No credential declared as requiredOpened a session without any credentialmatchesour test · 2026-10-27

Choosing

Record checks

Public records · not a safety rating

1 of 2 record checks met · 7 do not apply

  • Not ranked by downloads: a remote server publishes no download figure
  • Not ranked by stars: no public GitHub repository
  • MetRegistry entry is active and says how to run itActive, with a package or a remote address.
  • Not metSource repository link opensThe registry entry gives no repository link.
  • Does not applyRepository is not archivedNo public GitHub repository to read.
  • Does not applyCode pushed to the repository in the 90 days before our checkNo public GitHub repository to read.
  • Does not applyRepository publishes a security policy (SECURITY.md)No public GitHub repository to read.
  • Does not applyPackage names its licence with a standard (SPDX) identifierRemote server: it ships no package.
  • Does not applyThe version the registry lists can be installed and is not withdrawnRemote server: it ships no package.
  • Does not applynpm package carries build provenance (attestation)Remote server: it ships no package.
  • Does not applyNo known critical or high advisory in the package or its dependenciesRemote server: it ships no package.

Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-10-27. No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating. How each check works · Leaderboards

Common questions about com.foreclosure-radar/mcp

Answered from the data above

Who publishes com.foreclosure-radar/mcp?

The registry ties the namespace com.foreclosure-radar to the domain foreclosure-radar.com; only its owner can publish under it. These are facts from the registry and GitHub, not a rating.

Does com.foreclosure-radar/mcp need an API key or sign-in?

It opened a session without any credential on 2026-10-27. The registry entry declares no required credential; no declaration is not a guarantee.

Has com.foreclosure-radar/mcp been security tested?

Partly. 2 of the 14 checks that apply to it were exercised. We connected and read what the server declares, but did not call its tools: ProtocolProbe calls no server's tools for anything it publishes. This is our choice, not a block by the server. No security verdict is published before verification.

Found this page useful?

Anonymous · no sign-in

A quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.

Compare with another server

Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.

Security testing

What did we test, and what did we leave out?

18 checks · features #1, #2

Not probed (we call no server's tools)

We connected and read what the server declares, but did not call its tools: ProtocolProbe calls no server's tools for anything it publishes. This is our choice, not a block by the server. No security score is given; a check we did not run is never counted as passed.

The 18 checks at a glanceour test · 2026-10-27
  1. Inventory: exercised
  2. Hidden instructions: exercised
  3. Real execution: not run · our policy
  4. Secret leak: not run · nothing to check it against
  5. Internal addresses: not run · our policy
  6. Unconfirmed changes: not run · our policy
  7. Bad input: not run · our policy
  8. Model requests: not run · nothing to check it against
  9. Sensitive questions: not run · nothing to check it against
  10. Folder boundary: not run · our policy
  11. Log leaks: not run · nothing to check it against
  12. Hidden content: not run · nothing to check it against
  13. Fake assistant turns: not applicable
  14. Token passthrough: not applicable
  15. Token audience: not applicable
  16. Sign-in redirect: not run · our policy
  17. Consent handling: not testable from outside
  18. Sign-in metadata: not applicable

2 exercised12 not run (reason given)4 not applicable

Each check ends in exactly one state: exercised, not run (with the reason), or not applicable (with the reason). 2 of the 14 checks that apply to it were exercised. We do not publish security-check outcomes for named servers.

Exercised · 2
  • 1Inventory
    tool-list
    Reads the declared tools, resources and prompts.exercised
  • 2Hidden instructions
    description-poisoning
    Looks for hidden instructions in tool descriptions.exercised
Not run, with the reason · 12
  • 3Real execution
    real-execution
    Calls a tool and checks what really happens.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 4Secret leak
    canary-leak
    Plants a fake secret and checks whether it leaks.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 5Internal addresses
    ssrf
    Checks whether a tool can be steered to internal addresses.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 6Unconfirmed changes
    write-without-confirmation
    Checks whether tools that change data act without asking.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 7Bad input
    error-handling
    Sends bad input and watches how the server answers.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 8Model requests
    sampling
    Checks whether the server asks the client's model to act for it.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 9Sensitive questions
    elicitation-sensitive-data
    Checks whether the server asks users for sensitive data.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 10Folder boundary
    root-boundary
    Checks whether the server reaches outside the folders it was given.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 11Log leaks
    logging-side-channel
    Checks whether log messages carry data they should not.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 12Hidden content
    audience-hiding
    Checks resources that hide content from the user.This check needs content the server returns, and nothing was read or called.not run · nothing to check it against
  • 16Sign-in redirect
    open-redirect
    Checks the sign-in redirect for abuse.Testing the sign-in redirect means sending probes to the operator's sign-in service, which we do not do.not run · our policy
  • 17Consent handling
    confused-deputy
    Checks consent handling when one service acts for another.Depends on the operator's own consent screen, which differs per server and cannot be tested from outside.not testable from outside
Does not apply to this server · 4
  • 13Fake assistant turns
    fake-assistant-turn
    Checks prompts that pose as the assistant's own words.The server exposes no prompts.not applicable
  • 14Token passthrough
    token-passthrough
    Checks whether the server forwards a user's token to other services.The server opened a session without sign-in, so there is no token flow to check.not applicable
  • 15Token audience
    token-audience-validation
    Checks whether tokens meant for another service are accepted.The server opened a session without sign-in, so there is no token flow to check.not applicable
  • 18Sign-in metadata
    oauth-url-scheme
    Checks the published sign-in metadata for unsafe URLs.No sign-in (OAuth) metadata is published, so there are no sign-in addresses to check.not applicable

Source: our own test, 2026-10-27, mcp-runtime-engine@0.1.0. Which checks count and why follows our published scoring model.

What happened during the test?

Feature #8

The steps in order, as the test record holds them.

  1. 0 msStarted a read-only session with the server's remote endpoint
  2. 702 msConnected after 0 redirects. No credential was sent or needed.
  3. Read the inventory: 7 tools, 0 resources, 0 prompts.
  4. 2,580 msFinished: 2 checks exercised.

Reference

How is it classified?

18 fields

One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.

TopicAI-classified
pending: added in the weekly update
listed 2026-10-27; not classified yet
Pricing modelAI-classified
pending: added in the weekly update
the website is not read yet
Programming language
does not apply
no existing GitHub repository (server declares no repository link, so there is nothing to fetch)
Hosting type
registry · 2026-10-27
MCP capability
tools
our test · 2026-10-27
Transport
streamable HTTP
registry · 2026-10-27
Required credentials
none declared
registry · no declaration is not a guarantee
Package registry
does not apply
remote-only server: no package is shipped, so there is no package registry
Freshness
0–30 days
registry updatedAt · 2026-10-27
Lifecycle status
registry · 2026-10-27
License class
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Integrity hash
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Signature / provenance
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Dependency advisories
does not apply
ships no package, so there are no dependencies to audit
Popularity
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Publisher signals
not stated
no readable GitHub owner to describe
Maintenance
does not apply
server declares no repository link, so there is nothing to fetch
Environment
the publisher's infrastructure
where it runs, from the hosting type

“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.

Cite or correct this page

Sources and corrections

Suggested citation

ProtocolProbe. “com.foreclosure-radar/mcp: MCP server record.” Data checked 2026-10-27. https://protocolprobe.com/mcp/servers/com.foreclosure-radar/mcp

Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.

As JSON: this record in the API · API documentation.

Badge for your README

ProtocolProbe: 1 of 2 record checks met

[![ProtocolProbe](https://protocolprobe.com/api/v1/badge/com.foreclosure-radar/mcp)](https://protocolprobe.com/mcp/servers/com.foreclosure-radar/mcp)

It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.

Something wrong, or is this yours?

If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here.

Write to hello@protocolprobe.com · corrections log · methodology