# Trend (remote · trend.ondo.sh)

What rose on GitHub and in Korean shopping search each day, as published on trend.ondo.sh

- Trust score: 64/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-24

## Components

- remote · `trend.ondo.sh`: 64/100 (this document), [markdown](https://verifymcp.io/servers/sh-ondo-trend/trend.md), [page](https://verifymcp.io/servers/sh-ondo-trend/trend)

## Channel facts

- Endpoint: `https://trend.ondo.sh/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-10-24.

- **Endpoint Security**: 74/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.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - 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**: 29/100
  - 0% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (fair).
  - Context-footprint check failed: tool/resource definitions use about 1230 tokens (~307/item across 4 items; 3 tools + 1 resources), over budget; trim descriptions and params.
  - 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.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 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 current MCP spec version (2026-07-28).
  - Supports UI / widget rendering.

## Install

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

Trend is a hosted endpoint at https://trend.ondo.sh/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 sh-ondo-trend 'https://trend.ondo.sh/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "sh-ondo-trend": {
      "url": "https://trend.ondo.sh/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "sh-ondo-trend": {
      "type": "http",
      "url": "https://trend.ondo.sh/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.sh-ondo-trend]
url = "https://trend.ondo.sh/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "sh-ondo-trend": {
      "type": "remote",
      "url": "https://trend.ondo.sh/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add sh-ondo-trend --url 'https://trend.ondo.sh/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  sh-ondo-trend:
    url: "https://trend.ondo.sh/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "sh-ondo-trend": {
      "Transport": "http",
      "Url": "https://trend.ondo.sh/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add sh-ondo-trend -t streamable-http -u 'https://trend.ondo.sh/mcp'
```

### Other

```json
{
  "mcpServers": {
    "sh-ondo-trend": {
      "type": "http",
      "url": "https://trend.ondo.sh/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-10-24 (score 64, +11)

- [security improvement] Transport: fail → pass
- [security] Tool “repository” rewrote its description, which is the text the model reads

### 2026-10-23 (score 53, −11)

- [security regression] Transport: pass → fail
- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “keyword” rewrote its description, which is the text the model reads
- [security] Tool “repository” rewrote its description, which is the text the model reads
- [security] Tool “today” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 211 → 297
- [functional improvement] Stability: unverified → 0.03
- [functional] Schema quality: good → fair

### 2026-10-22 (score 64)

First indexed and scored.

## MCP tools (3)

### `today` (~454 tokens)

오늘

그날 트렌드 지면에 실린 것. 깃허브(github): 머리기사, 7일 동안 별이 가장 많이 늘어난 저장소 10개, 처음 트렌딩에 오른 저장소(since 날짜 이후 처음), 깃허브 일간 트렌딩 목록(rank_day_before가 비면 전날 목록에 없던 저장소, first_trending은 since 날짜 이후 처음 오른 저장소). 쇼핑(commerce): 일주일 사이 분야 10위 안으로 오른 검색어와 작년 이맘때 줄(last_year — times: 검색량이 작년 이맘때의 N배, new: 작년 이맘때엔 거의 찾지 않던 말, holiday: 그 명절마다 오르는 말), 그 아래 함께 본 사실 한 줄(clue — 명절까지 남은 날 · 지난 3년 같은 철 · 같은 분야에서 함께 오른 말, 원인이나 예측이 아닙니다), 분야마다 많이 찾은 검색어 다섯, 분야 100위 안에 새로 든 검색어(since 날짜 이후 새로). since는 트렌드가 그 세계를 기록하기 시작한 날입니다 — 사람에게 전할 때는 지면처럼 그 날이 무엇인지 함께 말해 주세요("트렌드가 기록을 시작한 {since} 이후 처음"). 깃허브의 머리기사(lead의 headline · dek)와 저장소의 kind · summary 가운데 AI가 미리 써 둔 것은 lead와 저장소마다의 ai_written이 적습니다(카드가 없는 저장소의 kind는 저장소가 깃허브에 적은 설명입니다). The day's page on trend.ondo.sh as it prints it: GitHub trending, or what Korean shoppers searched; ``since`` is the day trend began recording that world; only the fields listed in ai_written were written by AI. 이용 조건 · Terms of use: https://trend.ondo.sh/about/terms/

Input parameters:

- `date`: YYYY-MM-DD. 없으면 가장 최근 날
- `world` (string, required): github = 깃허브 트렌딩, commerce = 쇼핑 검색어

### `repository` (~343 tokens)

저장소

트렌드에 페이지가 있는 깃허브 저장소 하나 — 그 페이지에 실린 수(깃허브 트렌딩 기록 · 별 · 7일 동안 늘어난 별 · 기여자 · 최근 릴리스 …), 이름 아래의 한 줄(kind)과 그 아래 문장(line — 소개 글이 있으면 글의 도입, 없으면 짧은 소개), 그 페이지의 날짜(date)와 깃허브에서 그 수를 읽은 날(figures_read_on), 주소. kind와 line 가운데 AI가 저장소의 설명과 README를 읽고 미리 써 둔 것은 답의 ai_written이 적습니다(카드가 없는 저장소의 kind는 저장소가 깃허브에 적은 설명입니다). 소개 글이 원문 README의 라이선스에 기대어 쓴 글이면 그 라이선스(license)도 답합니다. 소개 글 전체는 페이지(page)에서 읽습니다. 최근 30일 사이 깃허브 트렌딩에 올랐거나 소개 글이 있는 저장소만 답합니다. A repository's page on trend.ondo.sh: its figures, the lines under its name (only those listed in ai_written were written by AI), the page's date and the day its figures were read from GitHub, the address, and the license its article leans on when it leans on one. 이용 조건 · Terms of use: https://trend.ondo.sh/about/terms/

Input parameters:

- `name` (string, required): 소유자/이름, 예: vllm-project/vllm (깃허브 주소도 됩니다)

### `keyword` (~143 tokens)

검색어

트렌드의 쇼핑 지면에 실린 검색어 하나 — 그 말을 실은 가장 최근 날, 그날 실린 칸(10위 안으로 오른 검색어 · 분야별 많이 찾은 검색어 · 100위 안에 새로 든 검색어)과 순위, 작년 이맘때 줄, 함께 본 사실 한 줄(clue). 검색량 원값은 싣지 않습니다. A shopping keyword as the last page that printed it shows it. 이용 조건 · Terms of use: https://trend.ondo.sh/about/terms/

Input parameters:

- `word` (string, required): 쇼핑 검색어, 예: 경량패딩

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/sh-ondo-trend/trend#diagnostics

## Score history

- 2026-10-24: 64
- 2026-10-23: 53
- 2026-10-22: 64

## Common questions

### What is the Trend MCP server?

Trend is an MCP server listed in the public MCP registry as sh.ondo/trend. What rose on GitHub and in Korean shopping search each day, as published on trend.ondo.sh. This page covers its hosted endpoint (https://trend.ondo.sh/mcp).

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

Trend scores 64 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 Trend MCP server expose?

Trend exposes 3 tools: today, repository, keyword. Their descriptions and schemas cost roughly 940 tokens of context every time the server is loaded.

### Does the Trend MCP server require authentication?

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

### Is the Trend MCP server still maintained?

Trend is still listed as active in the MCP registry. We last reached this channel on 24 October 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://trend.ondo.sh/mcp
- Website: https://trend.ondo.sh/en.html
- Changelog RSS feed: https://verifymcp.io/servers/sh-ondo-trend/trend.xml
- Changelog JSON feed: https://verifymcp.io/servers/sh-ondo-trend/trend.json
- HTML version of this page: https://verifymcp.io/servers/sh-ondo-trend/trend