# KTRENZ K-Data (remote · ktrenz.com)

K-pop artists and releases: search, trending by 7-day velocity, and AI answer-engine reach.

- Trust score: 82/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-22

## Components

- remote · `ktrenz.com`: 82/100 (this document), [markdown](https://verifymcp.io/servers/com-ktrenz-kdata/api-mcp.md), [page](https://verifymcp.io/servers/com-ktrenz-kdata/api-mcp)

## Channel facts

- Endpoint: `https://ktrenz.com/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## 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-09-22.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 4 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - 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**: 81/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 368 tokens (~92/item across 4 items; 4 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 100/100
  - No destabilizing schema changes in the last 30 days.
- **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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 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 KTRENZ K-Data MCP server?

KTRENZ K-Data is a hosted endpoint at https://ktrenz.com/api/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 com-ktrenz-kdata 'https://ktrenz.com/api/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-ktrenz-kdata": {
      "url": "https://ktrenz.com/api/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-ktrenz-kdata": {
      "type": "http",
      "url": "https://ktrenz.com/api/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-ktrenz-kdata]
url = "https://ktrenz.com/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-ktrenz-kdata": {
      "type": "remote",
      "url": "https://ktrenz.com/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-ktrenz-kdata --url 'https://ktrenz.com/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-ktrenz-kdata:
    url: "https://ktrenz.com/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-ktrenz-kdata": {
      "Transport": "http",
      "Url": "https://ktrenz.com/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-ktrenz-kdata -t streamable-http -u 'https://ktrenz.com/api/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-ktrenz-kdata": {
      "type": "http",
      "url": "https://ktrenz.com/api/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-09-20 (score 82, +1)

- [security] Stability: 0.97 → pass

### 2026-09-18 (score 81, +1)

No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-16 (score 80, +1)

No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-13 (score 79, +1)

No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-11 (score 78, +1)

No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-09 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-07 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-05 (score 75, +1)

No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (4)

### `search_kdata` (~90 tokens)

Search KTRENZ K-pop / K-culture entities (artists) by name; returns matches with slugs + reach-map URLs. Use the slug with get_artist_reach or get_release_reach.

Input parameters:

- `limit` (integer): Max results (1–25, default 10).
- `query` (string, required): Name or partial name (e.g. "RESCENE", "aespa").

### `get_artist_reach` (~79 tokens)

An artist's measured reach across AI answer engines (which vendors cite them, answer-time vs training) + tracked releases + external demand (Naver + YouTube) with 7d momentum. Measured first-party by KTRENZ.

Input parameters:

- `slug` (string, required): Artist slug (from search_kdata), e.g. "rescene".

### `get_trending` (~84 tokens)

Top rising K-pop artists right now, ranked by 7-day VELOCITY (rate of change), not standing popularity. Blends Korea search momentum, YouTube upload traction, third-party media pickup and fan-challenge volume — all external to KTRENZ. Rank is the signal.

Input parameters:

- `limit` (integer): How many (1–30, default 15).

### `get_release_reach` (~65 tokens)

A specific release's (comeback / MV / tour / chart announcement) measured AI-citation reach across answer engines. Measured first-party by KTRENZ.

Input parameters:

- `slug` (string, required): Release slug (from an artist's releases), e.g. a comeback slug.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-ktrenz-kdata/api-mcp#diagnostics

## Score history

- 2026-09-22: 82
- 2026-09-21: 82
- 2026-09-20: 82
- 2026-09-19: 81
- 2026-09-18: 81
- 2026-09-17: 80
- 2026-09-16: 80
- 2026-09-15: 79
- 2026-09-14: 79
- 2026-09-13: 79
- 2026-09-12: 78
- 2026-09-11: 78
- 2026-09-10: 77
- 2026-09-09: 77
- 2026-09-08: 76
- 2026-09-07: 76
- 2026-09-06: 75
- 2026-09-05: 75
- 2026-09-04: 74
- 2026-09-03: 74
- 2026-09-02: 73
- 2026-09-01: 73
- 2026-08-31: 72
- 2026-08-30: 72
- 2026-08-29: 72
- 2026-08-28: 71
- 2026-08-27: 71
- 2026-08-26: 70
- 2026-08-25: 68
- 2026-08-24: 68

## Common questions

### What is the KTRENZ K-Data MCP server?

KTRENZ K-Data is an MCP server listed in the public MCP registry as com.ktrenz/kdata. K-pop artists and releases: search, trending by 7-day velocity, and AI answer-engine reach. This page covers its hosted endpoint (https://ktrenz.com/api/mcp).

### Is the KTRENZ K-Data MCP server safe to use?

KTRENZ K-Data scores 82 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 KTRENZ K-Data MCP server expose?

KTRENZ K-Data exposes 4 tools: search_kdata, get_artist_reach, get_trending, get_release_reach. Their descriptions and schemas cost roughly 318 tokens of context every time the server is loaded.

### Does the KTRENZ K-Data MCP server require authentication?

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

### Is the KTRENZ K-Data MCP server still maintained?

KTRENZ K-Data is still listed as active in the MCP registry. We last reached this channel on 22 September 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://ktrenz.com/api/mcp
- Website: https://ktrenz.com/mcp
- Changelog RSS feed: https://verifymcp.io/servers/com-ktrenz-kdata/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-ktrenz-kdata/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-ktrenz-kdata/api-mcp