Skip to content

korea-stay MCP server

app.sallim/korea-staysallim.appstreamable-httpv0.7.12Scanned

Korean lodging: 84,490 stays from 4 government permit ledgers + KTO TourAPI, honest gaps

4 tools: 3 change things and 1 only read.

Tools: 0 delete, 0 irreversible, 3 write, 1 read.
  • Reads private data · 0
  • Reads text others write · 3
  • Can send data out · 0
  • 1 finding

Tools listed without sign-in. Remote posture

With Anlyon

3 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the korea-stay MCP server can do

The korea-stay MCP server is published by sallim.app, a domain the MCP Registry verified. It has 4 tools. It can create or change data (3 tools: stay_detail, stay_booking_link and report_issue), but cannot delete data. 1 tool only reads.

3 tools bring in text other people can write (stay_search, stay_detail and stay_booking_link).

The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in, and its tools changed 5 times since Anlyon Radar first saw them.

Last scanned Nov 21, 2026, version 0.7.12.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

4 tools

Changes things 3Claude Code: ask
  • report_issue사용자가 **답변 오류 제보·개선 요청·문의를 전해 달라고 했을 때만** 운영자에게 전달한다.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    사용자가 **답변 오류 제보·개선 요청·문의를 전해 달라고 했을 때만** 운영자에게 전달한다. 쓰는 때: 사용자가 "이거 틀렸으니 신고해 줘", "운영자에게 알려 줘", "이 기능도 넣어 달라고 전해 줘"처럼 제보·요청을 부탁했을 때. 보내기 전에 무엇이 전달되는지 사용자에게 알린다. kind='결함'은 틀린 답 제보, kind='질문기록'은 개선 요청, kind='유료이용문의'·'후원문의'는 사용자가 유료 이용 희망·후원 의사를 운영자에게 전해 달라고 한 경우다. 사용자가 오류·불만·개선 희망·유료 이용 희망·후원 의사를 말했지만 전달을 부탁하지는 않았다면, 부르지 말고 "운영자에게 전해 드릴까요?"를 한 줄로 한 번만 물어 동의할 때만 부른다(거절·무반응이면 다시 묻지 않는다). 응답의 접수번호(ref)와 회신 방법(reply_path)을 사용자에게 알린다. 쓰지 않는 때: 사용자가 요청하지 않았는데 질문을 남기려고 부르지 않는다. 답하기 전에 먼저 부르지도 않는다 — 이 도구는 답변을 대신하지 않는다. 전달 내용(인자)과 같은 접속 주소 단위의 30분 안 직전 호출 최대 5건 요약이 운영자 검토용으로 저장된다(공유 망 뒤에서는 다른 사용자의 호출이 섞일 수 있다 · 주소 단위를 못 가리면 싣지 않는다) (개인정보처리방침 https://stay.sallim.app/privacy). 연락처(contact)는 사용자가 회신을 원해 직접 준 경우에만 담고, 그 건의 회신에만 쓴다. 무인증 공개 서버라 쓰기 표면을 이 도구 하나로 묶어 시간당 상한을 건다(CLAUDE.md 규칙 2).

    Annotations the server declares

    • title: 답변 오류 신고
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
  • stay_detail숙소 하나의 상세 정보(이름·주소·좌표·종류·원장 출처)를 조회한다.Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    숙소 하나의 상세 정보(이름·주소·좌표·종류·원장 출처)를 조회한다. **재고는 조회하지 못한다** — 이 서버에 붙은 재고 채널이 0개라 날짜·인원을 줘도 availability는 항상 unknown이다(사유는 unavailable_reason에 실린다). 만실도 빈방 있음도 아니다. 빈방·요금은 stay_booking_link로 원본 검색 링크를 받아 직접 확인하라. 관광공사(tourapi) 행에는 인허가 원장의 폐업 등록과 이름·주소 정확 일치로 대조한 결과가 ledger_closure로 온다 — closed_in_ledger면 원장 기준 폐업이고, 같은 주소의 영업 중 원장 등록도 찾지 못했다(대조한 주소 범위는 note에 있다). closed_in_ledger_address_active면 폐업 등록과 함께 같은 주소에 다른 상호로 영업 중인 원장 등록이 있다(same_address_active) — 같은 업소인지 판정하지 못하니 둘 다 전하라. closed_in_ledger_address_unchecked면 폐업 등록은 있지만 같은 주소의 영업 등록 대조를 이번에 못 했다(확인 안 됨). 폐업 등록을 못 찾은 것은 영업 중의 확증이 아니다.

    Annotations the server declares

    • title: 숙소 상세
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
Only reads 1Show 1 read-only tool

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write3
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:22 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
3
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 3 tools that change things (3 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://stay.sallim.app/mcp?via=official: tools/list returned 4 tools to an anonymous client, including stay_detail (write), stay_booking_link (write), report_issue (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

1 warn
  • The server marks "stay_booking_link" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The name "stay_booking_link" says "link": a word for a change.

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools2 changed.~2 changedView diff
  2. Tools1 changed.~1 changedView diff
  3. Tools1 changed.~1 changedView diff
  4. Tools1 changed.~1 changedView diff
  5. Tools1 changed.~1 changedView diff

Install

Pinned to version 0.7.12. Values in angle brackets are yours to fill in.

claude mcp add --transport http korea-stay https://stay.sallim.app/mcp?via=official
claude mcp add --transport http korea-stay https://stay.sallim.app/mcp?via=official

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__korea-stay__stay_search"
    ],
    "ask": [
      "mcp__korea-stay__stay_detail",
      "mcp__korea-stay__stay_booking_link",
      "mcp__korea-stay__report_issue"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as korea-stay. Review it before you use it.

Capability tags behind 3 rules
  • mcp__korea-stay__stay_search untrusted-input
  • mcp__korea-stay__stay_detail untrusted-input
  • mcp__korea-stay__stay_booking_link untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/app.sallim/korea-stay/verify?hash=8d36697dc8f0d840e9faffad548a7c9b7e875511cdc5ad68df8189786a3dc424" | jq -e '.changed == false'

Pinned hash 8d36697dc8f0, from Nov 21, 2026, 11:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/app.sallim/korea-stay/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for app.sallim/korea-stay
[![Anlyon Radar](https://radar.anlyon.com/badge/app.sallim/korea-stay.svg)](https://radar.anlyon.com/servers/app.sallim/korea-stay)

Source: MCP Registry. Synced Nov 21, 2026, 11:17 UTC.

korea-stay MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the korea-stay MCP server safe?

No scan can promise that. What its definitions show: 4 tools, 3 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the korea-stay MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the korea-stay MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the korea-stay MCP server have?

4 tools: 3 write, 1 read. stay_detail, stay_booking_link, report_issue and stay_search.

Does the korea-stay MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the korea-stay MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the korea-stay MCP server changed its tools?

Yes, 5 times since Anlyon Radar started tracking it, most recently on Nov 21, 2026. Every change is on this page and in its Atom feed.