# KnockWatch (remote · knockwatch.co.kr)

Public signal records and exchange alerts for Upbit KRW coins, from KnockWatch (Korean).

- Trust score: 72/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `knockwatch.co.kr`: 72/100 (this document), [markdown](https://verifymcp.io/servers/kr-co-knockwatch-coin-check/knockwatch.md), [page](https://verifymcp.io/servers/kr-co-knockwatch-coin-check/knockwatch)

## Channel facts

- Endpoint: `https://knockwatch.co.kr/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.1`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 63/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 229 tokens (~45/item across 5 items; 5 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 7/100
  - Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the KnockWatch MCP server?

KnockWatch is a hosted endpoint at https://knockwatch.co.kr/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.

### Claude

```bash
claude mcp add --transport http kr-co-knockwatch-coin-check 'https://knockwatch.co.kr/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "kr-co-knockwatch-coin-check": {
      "url": "https://knockwatch.co.kr/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "kr-co-knockwatch-coin-check": {
      "type": "http",
      "url": "https://knockwatch.co.kr/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.kr-co-knockwatch-coin-check]
url = "https://knockwatch.co.kr/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "kr-co-knockwatch-coin-check": {
      "type": "remote",
      "url": "https://knockwatch.co.kr/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add kr-co-knockwatch-coin-check --url 'https://knockwatch.co.kr/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  kr-co-knockwatch-coin-check:
    url: "https://knockwatch.co.kr/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "kr-co-knockwatch-coin-check": {
      "Transport": "http",
      "Url": "https://knockwatch.co.kr/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add kr-co-knockwatch-coin-check -t streamable-http -u 'https://knockwatch.co.kr/mcp'
```

### Other

```json
{
  "mcpServers": {
    "kr-co-knockwatch-coin-check": {
      "type": "http",
      "url": "https://knockwatch.co.kr/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 72, 0)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “check_coin” rewrote its description, which is the text the model reads
- [security] Tool “facts” rewrote its description, which is the text the model reads
- [security] Tool “recent_signals” rewrote its description, which is the text the model reads
- [security] Tool “signal_guide” rewrote its description, which is the text the model reads
- [security] Tool “signal_record” rewrote its description, which is the text the model reads
- [functional improvement] Schema quality: fail → pass
- [cosmetic] “check_coin” reworded the description of “coin”
- [cosmetic] “recent_signals” reworded the description of “limit”
- [cosmetic] “signal_record” reworded the description of “signal”
- [cosmetic] Tool “check_coin” changed its title: 코인 점검 → Coin check
- [cosmetic] Tool “facts” changed its title: 공개 숫자 모음 → Published numbers
- [cosmetic] Tool “recent_signals” changed its title: 최근 신호 → Recent signals
- [cosmetic] Tool “signal_guide” changed its title: 신호 설명 → Signal guide
- [cosmetic] Tool “signal_record” changed its title: 신호 결과 기록 → Signal record

### 2026-11-04 (score 72, +3)

- [security improvement] HSTS header: fail → pass
- [functional improvement] Stability: unverified → 0.03

### 2026-11-03 (score 69)

First indexed and scored.

## MCP tools (5)

### `check_coin` (~59 tokens)

Coin check

Public KnockWatch record for one Upbit KRW-market coin: recent signals with outcomes, Upbit warning and caution flags, delisting and withdrawal dates, Binance notices.

Input parameters:

- `coin` (string, required): Upbit KRW-market coin symbol or Korean name.

### `recent_signals` (~46 tokens)

Recent signals

Latest public KnockWatch signals with outcomes vs. the market, shown after the public channel digest.

Input parameters:

- `limit` (integer): Number of signals, default 10, max 20.

### `signal_record` (~40 tokens)

Signal record

Cumulative outcomes per signal, the same numbers as knockwatch.co.kr/record.

Input parameters:

- `signal` (string): Optional signal name. Omit for both.

### `signal_guide` (~23 tokens)

Signal guide

What each KnockWatch signal shows, its limits and alert start date.

### `facts` (~19 tokens)

Published numbers

Statistics KnockWatch has already published, with period and source.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/kr-co-knockwatch-coin-check/knockwatch#diagnostics

## Score history

- 2026-11-05: 72
- 2026-11-04: 72
- 2026-11-03: 69

## Common questions

### What is the KnockWatch MCP server?

KnockWatch is an MCP server listed in the public MCP registry as kr.co.knockwatch/coin-check. Public signal records and exchange alerts for Upbit KRW coins, from KnockWatch (Korean). This page covers its hosted endpoint (https://knockwatch.co.kr/mcp).

### Is the KnockWatch MCP server safe to use?

KnockWatch scores 72 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 KnockWatch MCP server expose?

KnockWatch exposes 5 tools: check_coin, recent_signals, signal_record, signal_guide, facts. Their descriptions and schemas cost roughly 187 tokens of context every time the server is loaded.

### Does the KnockWatch MCP server require authentication?

No. We connected to KnockWatch without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the KnockWatch MCP server still maintained?

KnockWatch 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.

## Links

- Remote endpoint: https://knockwatch.co.kr/mcp
- Website: https://knockwatch.co.kr/ai
- Changelog RSS feed: https://verifymcp.io/servers/kr-co-knockwatch-coin-check/knockwatch.xml
- Changelog JSON feed: https://verifymcp.io/servers/kr-co-knockwatch-coin-check/knockwatch.json
- HTML version of this page: https://verifymcp.io/servers/kr-co-knockwatch-coin-check/knockwatch