Korean Real Estate Transactions
REMOTE · REALESTATE-API.GOYOSTUDIO.IO
Korean apartment and housing sale/rent records (MOLIT) by natural-language address. No key.
Available components
Last scanned (7 hours ago)
Scores higher than 44% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Maps and Location
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 Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 1 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- 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 Usability61
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 790 tokens (~790/item across 1 items; 1 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 Management40
- Stability observed for 12 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 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 1 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
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 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 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 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 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 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 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 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.
- 27 Oct 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.
- 25 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
- 24 Oct 26 57
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://realestate-api.goyostudio.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=goyostudio.io | CN=WE1,O=Google Trust Services,C=US | 17 Sept 2026 | 16 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 7522e2ebd59379ac1382a6d8b4d7d5c7 |
| SANs: goyostudio.io, realestate-api.goyostudio.io, *.realestate-api.goyostudio.io | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of realestate-api.goyostudio.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 38690 | 8 | Verified |
| goyostudio.io. | absent | 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://realestate-api.goyostudio.io/mcp | Verified | 200 | |
| http (plaintext) | http://realestate-api.goyostudio.io/mcp | Inconclusive | 405 |
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 →
get_korean_real_estate_transactions ~790
Query official Korean real-estate transaction records (국토교통부 실거래가, MOLIT via data.go.kr) with a natural-language Korean address or apartment-complex name, e.g. '강남구 대치동 은마 아파트 매매'. Returns flat JSON: period statistics (avg/min/max price in KRW, or deposit/monthly-rent stats for rentals) plus individual transactions, newest first. For trend questions ('월별 추이', 'how did prices move'), pass groupBy=month to get stats_by_month[]; for a size condition ('전용 84', '국평'), pass an areaMin/areaMax band — both aggregate over the full matching set, unlike the row list which is capped at limit. Hint words inside q (아파트/오피스텔…, 매매/전세/월세) are auto-inferred as type/tradeType/rentSubtype; explicit fields always win. Ambiguous locations return HTTP 422 with candidates[] — pick one and retry. Unresolvable locations return 404. All inferences are disclosed in resolved_note; coverage gaps in missing_months. Terms (as-is, no warranty): https://realestate-api.goyostudio.io/terms — data may be corrected or cancelled after initial publication; not investment advice. PRICING: currently free within edge or app rate limits (50 requests / 10 seconds per IP). HTTP 429 with error RATE_LIMITED and a Retry-After header — wait that many seconds, then retry. x402-ready: a fixed micro-price per request (indicative $0.001–$0.01, USDC on Base) may be enabled later, after which unpaid requests receive HTTP 402 Payment Required per the x402 protocol (https://x402.org); agents with x402 support handle this automatically. Current pricing status: GET https://realestate-api.goyostudio.io/openapi.json → x-pricing.
| Name | Type | Req | Description |
|---|---|---|---|
| areaMax | number | – | Maximum EXCLUSIVE area (전용면적) in ㎡, inclusive. |
| areaMin | number | – | Minimum EXCLUSIVE area (전용면적) in ㎡, inclusive. Not supply area (공급면적). A '84 type' apartment is usually 84.0-85.9㎡, so pin it with areaMin=84 & areaMax=86. |
| endDate | string | – | YYYY-MM inclusive. Default: current month. |
| groupBy | string | – | Set to 'month' for stats_by_month[] — per-month aggregates over the full matching set. Required for trend/추이 questions: the transaction rows are capped at limit, so a trend cannot be rebuilt from the… |
| limit | integer | – | Max transaction rows returned (default 100). Statistics always cover the full matching set regardless of limit. |
| q | string | yes | Natural-language Korean address and/or complex name. Max ~30 Korean characters (90 UTF-8 bytes), max 8 whitespace-separated tokens. Do not include period words ('최근 3개월' is ignored — use startDate/en… |
| rentSubtype | string | – | Only with tradeType=rent. jeonse (전세) = deposit-only; wolse (월세) = has monthly rent. |
| startDate | string | – | YYYY-MM inclusive. Default: 11 months before endDate (12-month window). Max range 24 months. |
| tradeType | string | – | sale = 매매 (default), rent = 전월세 (jeonse + wolse combined unless rentSubtype filters). |
| type | string | – | Property type. Default apartment unless inferred from q. rent is available only for apartment/officetel/rowhouse/detached; presale/land/commercial/industrial are sale-only. |
No output schema declared.
No examples provided.
How do I install the Korean Real Estate Transactions MCP server?
Korean Real Estate Transactions is a hosted endpoint at https://realestate-api.goyostudio.io/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 · realestate-api.goyostudio.io
claude mcp add --transport http goyo-studio-korean-real-estate-mcp 'https://realestate-api.goyostudio.io/mcp'
What is the Korean Real Estate Transactions MCP server?
Korean Real Estate Transactions is an MCP server listed in the public MCP registry as io.github.goyo-studio/korean-real-estate-mcp. Korean apartment and housing sale/rent records (MOLIT) by natural-language address. No key. This page covers its hosted endpoint (https://realestate-api.goyostudio.io/mcp).
Is the Korean Real Estate Transactions MCP server safe to use?
Korean Real Estate Transactions scores 63 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 Korean Real Estate Transactions MCP server expose?
Korean Real Estate Transactions exposes 1 tool: get_korean_real_estate_transactions. Their descriptions and schemas cost roughly 790 tokens of context every time the server is loaded.
Does the Korean Real Estate Transactions MCP server require authentication?
No. We connected to Korean Real Estate Transactions without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Korean Real Estate Transactions MCP server still maintained?
Korean Real Estate Transactions 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.