엔차 · 오래 버틴 맛집
REMOTE · NCHA.APP
Korean long-running restaurants (Seoul, Gyeonggi) from public license records, not reviews.
Available components
Last scanned (22 minutes ago)
Scores higher than 64% 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 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. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. 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 Usability60
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 707 tokens (~176/item across 4 items; 4 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 Management47
- Stability observed for 14 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage85
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 54% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 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
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.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 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.
- 28 Oct 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.
- 26 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.
- 24 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.
- 23 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
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://ncha.app/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.ncha.app | CN=YR2,O=Let's Encrypt,C=US | 18 Oct 2026 | 16 Jan 2027 | RSA 2048 | SHA256-RSA | 5ca0e3db40c3c5ee7a3d8fffbddcc30ddeb |
| SANs: *.ncha.app, ncha.app | ||||||
| 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 ncha.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| ncha.app. | 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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://ncha.app/mcp | Verified | 200 | |
| http (plaintext) | http://ncha.app/mcp | HTTPS enforced | 308 | https://ncha.app/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 →
find_long_running_restaurants 오래 버틴 맛집 찾기 ~325
지역·동·메뉴로 같은 자리에서 오래 영업 중인 음식점을 찾습니다(공공 인허가 기록 기준, 별점 없음). "동탄 국밥 맛집", "오산 노포", "평택 서정동 중국집", "마포 노포"처럼 맛집·노포·오래된 식당을 찾거나 맛집 글을 쓸 때 쓰세요. 경기도 31개 시·군(화성 동탄은 "동탄"으로 따로)과 서울 25개 구를 다룹니다.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | 업태 묶음. 선택. |
| dong | string | – | 동·읍·면 이름(예: 석우동, 서정동, 안중읍). 선택. |
| include_uncertain | boolean | – | 다른 가게일 수 있는 기록(확인 필요)도 넣을지. |
| limit | integer | – | – |
| menu | string | – | 메뉴나 가게 이름 낱말(예: 국밥, 짬뽕, 고기, 회, 칼국수). 선택. |
| min_years | integer | – | 최소 영업 햇수. 기본 10. |
| region | string | – | 경기도 시·군 또는 서울 구 이름(예: 수원, 화성 동탄, 경기 광주, 마포구, 서울 중구). "경기"·"서울"이면 그 시·도 전체, 비우면 전체. |
No output schema declared.
No examples provided.
find_restaurants_near 근처 오래 버틴 집 ~111
위도·경도 주변(기본 800m, 걸어서 10분)에서 오래 영업 중인 음식점을 햇수 순으로 찾습니다. 경기도·서울 안에서만 찾습니다(지도 좌표를 채운 가게만, 서울은 채우는 중).
| Name | Type | Req | Description |
|---|---|---|---|
| lat | number | yes | – |
| limit | integer | – | – |
| lng | number | yes | – |
| min_years | integer | – | – |
| radius_m | integer | – | – |
No output schema declared.
No examples provided.
get_restaurant 가게 근거 보기 ~65
가게 id로 주소, 영업 햇수, 인허가 기록(최초·승계·재신고), 확인할 점을 봅니다.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | 가게 id(예: s_6ed1b96dc2) |
No output schema declared.
No examples provided.
list_regions 다루는 지역 ~26
엔차가 다루는 지역과 동 목록, 가게 수를 봅니다.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the 엔차 · 오래 버틴 맛집 MCP server?
엔차 · 오래 버틴 맛집 is a hosted endpoint at https://ncha.app/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 · ncha.app
claude mcp add --transport http app-ncha-encha 'https://ncha.app/mcp'
What is the 엔차 · 오래 버틴 맛집 MCP server?
엔차 · 오래 버틴 맛집 is an MCP server listed in the public MCP registry as app.ncha/encha. Korean long-running restaurants (Seoul, Gyeonggi) from public license records, not reviews. This page covers its hosted endpoint (https://ncha.app/mcp).
Is the 엔차 · 오래 버틴 맛집 MCP server safe to use?
엔차 · 오래 버틴 맛집 scores 75 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 엔차 · 오래 버틴 맛집 MCP server expose?
엔차 · 오래 버틴 맛집 exposes 4 tools: find_long_running_restaurants, find_restaurants_near, get_restaurant, list_regions. Their descriptions and schemas cost roughly 527 tokens of context every time the server is loaded.
Does the 엔차 · 오래 버틴 맛집 MCP server require authentication?
No. We connected to 엔차 · 오래 버틴 맛집 without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the 엔차 · 오래 버틴 맛집 MCP server still maintained?
엔차 · 오래 버틴 맛집 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.