mcpbeat Sign in

Trend MCP Server

answering

Trend is answering right now. Last checked 7 min ago. It exposes 3 tools.

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

Uptime history 4 days of history
4 days agonow
100.0%
Uptime 24h
91 of 91 checks
3
Tools
read from the server
733 ms
Response time
average over 24h
open, no key
Access
streamable-http

What changed 1

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 23 October 2026. No other catalogue keeps this.

23 Oct a tool description was rewritten repository

Nothing serious here today

Today is the operative word: we check Trend every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 7 min ago.

run in your terminal
claude mcp add trend --transport http https://trend.ondo.sh/mcp
Settings → Connectors → Add custom connector, then paste this address
https://trend.ondo.sh/mcp
~/.codex/config.toml
[mcp_servers.trend]
url = "https://trend.ondo.sh/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "trend": {
      "url": "https://trend.ondo.sh/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "trend": {
      "type": "http",
      "url": "https://trend.ondo.sh/mcp"
    }
  }
}

Available tools 3

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

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

Endpoints

URLTransportStateLatencyChecked
https://trend.ondo.sh/mcp streamable-http answering 343 ms 7 min ago

Alternatives to Trend

same job, measured the same way
FactGrid (Renamed to FactReason)
by factgridai

Renamed to FactReason. Now published as io.github.factreason/factreason — please use that entry.

11 tools answering
Audit
by commitshow

Score a public GitHub repo 0-100, or search Legit.Show for launched software by what we measured.

32 installs/wk local only
StarHunt
by getstarhunt

Find engineers by what they build on GitHub. Search by technology, location and role.

answering
Sexai MCP
by sexai

The network where AI agents breed — publish, import a GitHub repo as an agent, cross them.

27 installs/wk local only
star365 HQ
by star365

Keyless web, GitHub, YouTube and Reddit search and read. Delegated shop, booking and signup.

15 tools answering
SocialSwarm
by socialswarm

Discover GitHub projects welcoming AI agent contributions. Public search and listing reads.

4 tools answering
Herohunt MCP
by herohunt-ai

People search API - find 1 billion candidates across LinkedIn and GitHub with real-time data.

14 installs/wk local only
AyHire
by ayhire

Hire engineers by what they shipped: find, judge and shortlist developers from public GitHub work.

answering

Trend — questions

Answers built from our own checks of this server.

What can Trend do?
It exposes 3 tools, read directly from the server on our last check. Among them: keyword, repository, today. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Trend working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 733 ms. The bar chart above shows every period we have measured.
How do I connect Trend?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Trend need an API key?
No. Trend completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 3 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Trend?
It answers our handshake in 733 ms on average, which is faster than 14% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.