KnockWatch MCP server
kr.co.knockwatch/coin-checkknockwatch.co.krstreamable-httpv1.0.1Scanned
Public signal records and exchange alerts for Upbit KRW coins, from KnockWatch (Korean).
5 tools: 5 change things.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
5 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.
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 KnockWatch MCP server can do
The KnockWatch MCP server is published by knockwatch.co.kr, a domain the MCP Registry verified. It has 5 tools. It can create or change data (5 tools: check_coin, recent_signals, signal_record, signal_guide and 1 more), but cannot delete data. None of its tools only reads.
None of its tools reads private data, brings in text other people write, or sends data out.
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.
Last scanned Nov 16, 2026, version 1.0.1.
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.
5 tools
Changes things 5Claude Code: ask
check_coin업비트 원화 마켓 코인 하나의 노크워치 공개 기록을 보여 드립니다.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.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 업비트 원화 마켓 코인 하나의 노크워치 공개 기록을 보여 드립니다. 최근 30일 공개 신호와 그 후 시장 대비 결과, 지금 업비트 유의 종목 표시와 주의 표시, 거래지원 종료와 출금 마감 일정, 최근 30일 바이낸스 상장폐지와 모니터링 태그 공지, 원화 마켓 상장 30일 이내인지, 빙산 매도벽 대상인지를 알려 드립니다. Public KnockWatch record for one Upbit KRW-market coin: recent signals with outcomes, Upbit warning and caution flags, delisting and withdrawal dates, Binance notices.
Annotations the server declares
- title: 코인 점검
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
facts노크워치가 이미 공개한 숫자를 한 줄씩 모았습니다.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.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 노크워치가 이미 공개한 숫자를 한 줄씩 모았습니다. 신호별 과거 데이터 결과와 거래소 경보 사례를 기간, 출처와 함께 보여 드립니다. Statistics KnockWatch has already published, with period and source.
Annotations the server declares
- title: 공개 숫자 모음
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
recent_signals노크워치가 공개한 최근 신호를 최신순으로 보여 드립니다.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.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 노크워치가 공개한 최근 신호를 최신순으로 보여 드립니다. 9시 급등 반납과 빙산 매도벽의 알림 시각, 코인, 그 후 시장 대비 결과입니다. 공개 채널 요약에 올라간 알림만 보여 드려 유료 즉시 알림보다 늦습니다. Latest public KnockWatch signals with outcomes vs. the market, shown after the public channel digest.
Annotations the server declares
- title: 최근 신호
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
signal_guide노크워치 신호마다 어떤 코인을 알려 드리는지, 어디에 참고하는지, 한계와 알림 시작일을 보여 드립니다.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.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 노크워치 신호마다 어떤 코인을 알려 드리는지, 어디에 참고하는지, 한계와 알림 시작일을 보여 드립니다. What each KnockWatch signal shows, its limits and alert start date.
Annotations the server declares
- title: 신호 설명
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
signal_record신호별 누적 결과를 'N건 중 M건 시장보다 낮았음'으로 보여 드립니다.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.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 신호별 누적 결과를 'N건 중 M건 시장보다 낮았음'으로 보여 드립니다. 오픈 전 과거 데이터 결과와 오픈 후 실제 알림 결과를 기간과 함께 나눠 보여 드리며 숫자는 knockwatch.co.kr/record와 같습니다. Cumulative outcomes per signal, the same numbers as knockwatch.co.kr/record.
Annotations the server declares
- title: 신호 결과 기록
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
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 untrusted-input or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- 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.
Looked at Nov 18, 2026, 16:23 UTC, unchanged since Nov 4, 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
- 5
- 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 5 tools that change things (5 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://knockwatch.co.kr/mcp: tools/list returned 5 tools to an anonymous client, including check_coin (write), recent_signals (write), signal_record (write), signal_guide (write), facts (write)
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools2 changed.~2 changedView diff
- Changed:recent_signalsChanges thingsdescription
- Changed:signal_recordChanges thingsinputSchema
Install
Pinned to version 1.0.1. Values in angle brackets are yours to fill in.
claude mcp add --transport http coin-check https://knockwatch.co.kr/mcpclaude mcp add --transport http coin-check https://knockwatch.co.kr/mcpRun 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.
{
"permissions": {
"allow": [],
"ask": [
"mcp__coin-check__check_coin",
"mcp__coin-check__recent_signals",
"mcp__coin-check__signal_record",
"mcp__coin-check__signal_guide",
"mcp__coin-check__facts"
],
"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 coin-check. Review it before you use it.
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/kr.co.knockwatch/coin-check/verify?hash=3a1307f507746045116e36d94687a03351109284f1905a3b496ebd888dc665df" | jq -e '.changed == false'Pinned hash 3a1307f50774, from Nov 16, 2026, 18:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/kr.co.knockwatch/coin-check/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/kr.co.knockwatch/coin-check)Source: MCP Registry. Synced Nov 3, 2026, 08:18 UTC.
KnockWatch MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the KnockWatch MCP server safe?
- No scan can promise that. What its definitions show: 5 tools, 5 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the KnockWatch MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the KnockWatch 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 KnockWatch MCP server have?
- 5 tools: 5 write. check_coin, recent_signals, signal_record, signal_guide and facts.
Does the KnockWatch MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the KnockWatch MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the KnockWatch MCP server changed its tools?
- Yes, once since Anlyon Radar started tracking it, most recently on Nov 16, 2026. Every change is on this page and in its Atom feed.