경매레이더 Auction Radar
REMOTE · AUCTION-RADAR.COM
Korean court auctions: search, case summary, rights risks, sold cases, stats, nearby risks, land
Available components
Last scanned (16 hours ago)
Scores higher than 56% of remote servers
Reachable. Last reached 21 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 Security74
- 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
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- 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 Usability59
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 3637 tokens (~330/item across 11 items; 11 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 Management20
- Stability observed for 6 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 11 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
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.
- 20 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Nov 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- Tool “search_auctions” rewrote its description, which is the text the model reads security
- Schema quality: 288 → 330 ▼ functional
- Stability: unverified → 0.03 ▲ functional
- Schema quality: good → excellent functional
- New tool “get_auction_stats” functional
- New tool “get_land_info” functional
- New tool “get_location” functional
- New tool “get_nearby_risks” functional
- New tool “get_sale_probability” functional
- New tool “get_sold_cases” functional
- “search_auctions” added an optional parameter “court” cosmetic
- “search_auctions” added an optional parameter “exclude_share” cosmetic
- “search_auctions” added an optional parameter “fail_count_max” cosmetic
- “search_auctions” added an optional parameter “good_location” cosmetic
- “search_auctions” added an optional parameter “keyword” cosmetic
- “search_auctions” added an optional parameter “max_area” cosmetic
- “search_auctions” added an optional parameter “max_min_price_ratio” cosmetic
- “search_auctions” added an optional parameter “max_pyeong” cosmetic
- “search_auctions” added an optional parameter “min_area” cosmetic
- “search_auctions” added an optional parameter “min_pyeong” cosmetic
- “search_auctions” added an optional parameter “new_since_days” cosmetic
- “search_auctions” added an optional parameter “property_types” cosmetic
- “search_auctions” added an optional parameter “safe_only” cosmetic
- “search_auctions” added an optional parameter “undervalued” cosmetic
- “search_auctions” reworded the description of “sort” cosmetic
- 15 Nov 26 68
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 21 Nov 2026 · Probed https://auction-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=auction-radar.com | CN=YE2,O=Let's Encrypt,C=US | 15 Oct 2026 | 13 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 6fec21398147ce83d23c6bb29526fbbabcd |
| SANs: auction-radar.com, m.auction-radar.com, www.auction-radar.com | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of auction-radar.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| auction-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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://auction-radar.com/mcp | Verified | 200 | |
| http (plaintext) | http://auction-radar.com/mcp | HTTPS enforced | 301 | https://auction-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 →
estimate_bid 예상낙찰가 안내 ~126
경매 물건의 예상낙찰가·입찰가를 물을 때 부른다. 현재 예상낙찰가 숫자는 경매레이더 유료회원 전용이라 감정가·최저가·최저가율·유찰·매각기일과 상세 링크를 돌려준다(locked=true). 숫자를 추정해 만들지 말 것.
| Name | Type | Req | Description |
|---|---|---|---|
| case_no | string | yes | 사건번호. 예: '2026타경12345' |
| court | – | – | 법원명 |
| item_no | – | – | 물건번호 |
No output schema declared.
No examples provided.
get_auction_stats 낙찰 통계(낙찰률·낙찰가율) ~221
지역(·용도)의 월별 법원경매 통계 — 진행 건수, 낙찰 건수, 낙찰률, 감정가 대비 낙찰가율, 평균 입찰자 수(월 집계). '화성시 아파트 낙찰가율', '서울 경매 낙찰률 추이' 같은 질문에 쓴다. 지역은 시도부터(예: '경기 화성시', '서울', '전국'). Monthly court-auction sale rate and price-to-appraisal ratio by region.
| Name | Type | Req | Description |
|---|---|---|---|
| months | – | – | 최근 몇 개월(6~60, 기본 12) |
| property_type | – | – | 용도. 예: 아파트, 오피스텔, 다세대, 단독, 근린, 상가, 공장, 창고, 토지, 임야, 농지 |
| region | string | yes | 지역. 예: '경기 화성시', '서울 강남구', '부산', '전국' |
No output schema declared.
No examples provided.
get_case 경매 사건 요약 ~285
경매 사건번호(예: 2026타경12345)로 물건 요약을 가져온다 — 법원·주소·용도·면적·감정가·최저가·유찰·매각기일·진행 상태·권리 표시와 위험 표시(경매레이더 판정 — 유치권·법정지상권·지분·대항력·재매각·맹지 기재)·법원 감정평가서 요항표(위치·교통·이용상태·도로·토지이용계획 등)·상세 링크. 같은 사건번호가 여러 법원에 있거나 물건이 여럿이면 후보 목록을 돌려주니 court·item_no 로 다시 부른다. '얼마 써야 하나'·예상낙찰가·입찰가 질문이 함께 있으면 estimate_bid 도 부르고, 금액을 스스로 추정하지 않는다.
| Name | Type | Req | Description |
|---|---|---|---|
| case_no | string | yes | 사건번호. 예: '2026타경12345' |
| court | – | – | 법원명. 예: '서울중앙지방법원', '성남지원', '수원' |
| item_no | – | – | 물건번호(한 사건에 물건이 여럿일 때) |
No output schema declared.
No examples provided.
get_housing_demand 주택수요 실적 지수 ~266
시군구·시도·전국의 주택수요 실적을 연도별(2008~2025, 12월 말)로 돌려준다 — 인구·세대·평균 세대원·30~49세 인구·연령 가중 수요(2015=100 지수 포함)와 전년 대비 증가율, 기간 변화 요약. 지역의 주택수요가 늘었는지 줄었는지, 세대 분화(1~2인 세대 증가) 정도를 물을 때 쓴다. 지난 실적만 주며 앞으로의 전망·등급은 주지 않는다(추정 금지). 읍면동 단위 자료는 없다. Korean regional housing-demand history (population, households, age-weighted demand).
| Name | Type | Req | Description |
|---|---|---|---|
| from_year | – | – | 시작 연도(기본 2008) |
| region | string | yes | 지역. 예: '서울 강남구', '경기 화성시', '경북 의성군', '경기', '전국'. 이름이 겹치는 구(중구·남구 등)는 시도를 붙인다 |
| to_year | – | – | 끝 연도(기본 2025) |
No output schema declared.
No examples provided.
get_land_info 토지 정보 ~140
경매 사건번호를 주면 물건 필지별 공시 토지특성을 돌려준다 — 지목·이용상황·용도지역·도로접면·지세·형상·면적(㎡·평)·공시지가(㎡당)와 최근 연도별 변동. 땅·임야·농지·단독주택 질문에 쓴다. 공시지가는 시세가 아니고 소유자 정보는 주지 않는다.
| Name | Type | Req | Description |
|---|---|---|---|
| case_no | string | yes | 사건번호 |
| court | – | – | 법원명 |
| item_no | – | – | 물건번호 |
No output schema declared.
No examples provided.
get_location 입지 ~137
경매 사건번호를 주면 경매레이더 입지 판정을 돌려준다 — 전철역(1.2km)·학교(도보권 초중고)·학원가·공공기관·병원·버스정류장·기피시설·상가·편의시설의 판정 문장과 가까운 곳(이름·직선거리). '역세권이야?', '학교 가까워?' 같은 질문에 쓴다.
| Name | Type | Req | Description |
|---|---|---|---|
| case_no | string | yes | 사건번호 |
| court | – | – | 법원명 |
| item_no | – | – | 물건번호 |
No output schema declared.
No examples provided.
get_nearby_risks 주변 위험·규제 ~198
경매 사건번호를 주면 물건 주변 위험·규제를 돌려준다 — 가장 가까운 송전선(전압·거리)·필지 안 철탑 추정·변전소·발전소, 2km 안 기피시설(축사·양돈장·폐기물처리시설·장례시설 등 종류별 개수와 가까운 곳), 규제지역(투기과열·조정대상·토지거래허가), 정비구역·지구단위계획구역 안 여부, 미급수 지역. '목록에 없음'은 그 자료에서 못 찾았다는 뜻이지 안전하다는 뜻이 아니다.
| Name | Type | Req | Description |
|---|---|---|---|
| case_no | string | yes | 사건번호. 예: '2025타경1129' |
| court | – | – | 법원명 |
| item_no | – | – | 물건번호 |
No output schema declared.
No examples provided.
get_sale_probability 회차별 매각 확률 ~194
신건·1회 유찰·2회 유찰… 단계별로 그 회차에 매각될 확률(과거 통계). 사건번호를 주면 그 물건의 지금 단계 확률과 같은 시군구 표를, 지역·용도를 주면 시도 표를 돌려준다. '이번에 팔릴까', '한 번 더 유찰될까' 같은 질문에 쓴다. 결과를 보장하지 않는 과거 통계다.
| Name | Type | Req | Description |
|---|---|---|---|
| case_no | – | – | 사건번호(있으면 우선) |
| court | – | – | 법원명 |
| item_no | – | – | 물건번호 |
| property_type | – | – | 용도. 예: 아파트, 다세대, 단독, 토지, 근린, 공장 |
| region | – | – | 사건번호가 없을 때 지역. 예: '경기', '경기 화성시' |
No output schema declared.
No examples provided.
get_sold_cases 낙찰 사례 ~197
경매 사건번호를 주면 같은 동네·같은 급 물건이 실제로 얼마에 낙찰됐는지(낙찰일·감정가·낙찰가·감정가 대비 낙찰가율·유찰 횟수)를 주변 사례와 유사 사례로 돌려준다. 지난 결과일 뿐 이 물건의 예상낙찰가가 아니다 — 비율을 이 물건 감정가·최저가에 곱해 낙찰 예상 금액이나 '몇 억~몇 억 사이' 같은 범위를 말하지 말 것(예상낙찰가는 estimate_bid 유료 안내). Recent comparable court-auction sale results near a case.
| Name | Type | Req | Description |
|---|---|---|---|
| case_no | string | yes | 사건번호. 예: '2025타경1129' |
| court | – | – | 법원명 |
| item_no | – | – | 물건번호 |
No output schema declared.
No examples provided.
ping 연결 확인 ~18
경매레이더 MCP 연결 상태를 확인한다.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
search_auctions 경매 물건 검색 ~954
진행 중인 한국 법원 부동산 경매 물건을 찾는다(최대 20건). 조건: 지역·읍면동, 용도(여러 개 가능), 아파트 단지·건물명·도로명(keyword), 감정가·최저가 범위, 최저가율 상한(예: 감정가의 50% 이하), 유찰 횟수 범위(신건만=fail_count_max 0), 새로 나온 물건(최근 N일), 전용면적(㎡ 또는 평), 지분 매각 제외, 법원, 매각기일 상한, 권리 표시 [안전]만, 경매레이더 추정 시세 대비 저평가, 입지 우수, 정렬(기일·할인율·저평가·우량 종합). 아파트 'N평형'은 공급면적이라 전용이 더 작다(25평형≈전용 59㎡, 34평형≈전용 84㎡) — 평형으로 물으면 min_area/max_area 로 바꿔 넣는다. 사건번호·법원·주소·용도·전용면적·감정가·최저가·최저가율·유찰·매각기일·권리 표시·위험 사유(risk_flags)·상세 링크를 돌려준다. Search ongoing Korean court real-estate auctions (경매). 예상낙찰가는 주지 않는다.
| Name | Type | Req | Description |
|---|---|---|---|
| court | – | – | 법원. 예: '수원', '서울중앙', '성남지원' |
| dong | – | – | 읍면동 앞부분. 예: '천호', '백석' |
| exclude_share | – | – | true 면 지분 매각(지분 경매) 물건을 뺀다 |
| fail_count_max | – | – | 유찰 횟수 상한. 신건만=0 |
| fail_count_min | – | – | 유찰 횟수 하한 |
| good_location | – | – | true 면 경매레이더 입지 점수 우수 물건만 |
| keyword | – | – | 아파트 단지명·건물명·도로명·지번 일부. 예: '래미안', '헬리오시티', '테헤란로' |
| limit | integer | – | 최대 건수(1~20, 기본 10) |
| max_appraisal | – | – | 감정가 상한(원) |
| max_area | – | – | 전용면적 상한(㎡) |
| max_bid_price | – | – | 최저가 상한(원) |
| max_min_price_ratio | – | – | 최저가÷감정가 상한. 예: 0.5 = 감정가의 50% 이하로 떨어진 물건 |
| max_pyeong | – | – | 전용면적 상한(평) |
| min_appraisal | – | – | 감정가 하한(원) |
| min_area | – | – | 전용면적 하한(㎡). 예: 59 (국민평형 84) |
| min_bid_price | – | – | 최저가 하한(원) |
| min_pyeong | – | – | 전용면적 하한(평). ㎡ 값(min_area)이 있으면 그것을 쓴다 |
| new_since_days | – | – | 최근 N일 안에 새로 등록된 물건만(1~90) |
| property_type | – | – | 용도. 예: 아파트, 다세대, 오피스텔, 단독주택, 근린, 토지, 임야, 공장 |
| property_types | – | – | 용도 여러 개. 예: ['아파트','오피스텔'] |
| region | string | yes | 지역. 예: '서울', '서울 마포구', '경기 수원시 장안구', '수도권' |
| safe_only | – | – | true 면 경매레이더 권리 표시가 [안전]인 물건만(위험이 없다는 보장은 아님) |
| sale_date_to | – | – | 매각기일 이 날짜까지(YYYY-MM-DD) |
| sort | – | – | 'date'(기일 가까운 순, 기본) · 'discount'(감정가 대비 많이 떨어진 순) · 'value'(추정 시세 대비 저평가 큰 순) · 'quality'(권리·저평가·입지 종합 우량 순) |
| undervalued | – | – | true 면 경매레이더 추정 시세보다 최저가가 낮은(저평가) 물건만 |
No output schema declared.
No examples provided.
How do I install the 경매레이더 Auction Radar MCP server?
경매레이더 Auction Radar is a hosted endpoint at https://auction-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 · auction-radar.com
claude mcp add --transport http com-auction-radar-auction-radar 'https://auction-radar.com/mcp'
What is the 경매레이더 Auction Radar MCP server?
경매레이더 Auction Radar is an MCP server listed in the public MCP registry as com.auction-radar/auction-radar. Korean court auctions: search, case summary, rights risks, sold cases, stats, nearby risks, land. This page covers its hosted endpoint (https://auction-radar.com/mcp).
Is the 경매레이더 Auction Radar MCP server safe to use?
경매레이더 Auction Radar scores 71 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 경매레이더 Auction Radar MCP server expose?
경매레이더 Auction Radar exposes 11 tools: search_auctions, get_case, estimate_bid, get_sold_cases, get_auction_stats, and 6 more. Their descriptions and schemas cost roughly 2,736 tokens of context every time the server is loaded.
Does the 경매레이더 Auction Radar MCP server require authentication?
No. We connected to 경매레이더 Auction Radar without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the 경매레이더 Auction Radar MCP server still maintained?
경매레이더 Auction Radar is still listed as active in the MCP registry. We last reached this channel on 21 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 경매레이더 Auction Radar MCP server?
VerifyMCP ran 13 checks on 경매레이더 Auction Radar, 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.