_ registry / mcp streamable-http · checked 3h ago

trend

https://trend.ondo.sh

Registry code: c4d1d447f889193e

api record

트렌드(https://trend.ondo.sh)가 매일 싣는 지면 — 깃허브 트렌딩과 쇼핑 검색어 — 에 실린 것만 답합니다. 답마다 그 지면의 날짜(date)와 주소(page)가 붙어 있으니, 사람에게 전할 때 주소를 함께 보여 주세요. 지면에 없는 날짜 · 저장소 · 검색어는 거절하고 까닭을 한 줄로 말합니다. Answers carry only what trend.ondo.sh's daily pages print — GitHub trending and Korean shopping searches — each with the page's date and address; anything the pages do not print is refused.

endpoint
https://trend.ondo.sh/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is trend live?
Yes — it answered the hub's last check (checked 3h ago). It answered 100% of checks over the last 30 days.
Is trend free to use?
Yes — the hub reached it with no key and no payment.
What tools does trend have?
3 tools: repository, keyword, today.
Is trend safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
296ms

last good check

priced tools
0

of 3 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

inferred, not observed

Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run

_ what it can do 3 tools
3 never probed 0 of 3 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • repository unknown 3h ago

    트렌드에 페이지가 있는 깃허브 저장소 하나 — 그 페이지에 실린 수(깃허브 트렌딩 기록 · 별 · 7일 동안 늘어난 별 · 기여자 · 최근 릴리스 …), 이름 아래의 한 줄(kind)과 그 아래 문장(line — 소개 글이 있으면 글의 도입, 없으면 짧은 소개), 그 페이지의 날짜(date)와 깃허브에서 그 수를 읽은 날(figures_read_on), 주소. 소개 글 전체는 페이지(page)에서 읽습니다. 최근 30일 사이 깃허브 트렌딩에 올랐거나 소개 글이 있는 저장소만 답합니다. A repository's page on trend.ondo.sh: its figures, the lines under its name, the page's date and the day its figures were read from GitHub, and the address.

    mcp-tool

    {
      "type": "object",
      "title": "repositoryArguments",
      "required": [
        "name"
      ],
      "properties": {
        "name": {
          "type": "string",
          "title": "Name",
          "description": "소유자/이름, 예: vllm-project/vllm (깃허브 주소도 됩니다)"
        }
      }
    }
    arguments 14 lines
  • keyword unknown 3h ago

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

    mcp-tool

    {
      "type": "object",
      "title": "keywordArguments",
      "required": [
        "word"
      ],
      "properties": {
        "word": {
          "type": "string",
          "title": "Word",
          "description": "쇼핑 검색어, 예: 경량패딩"
        }
      }
    }
    arguments 14 lines
  • today unknown 3h ago

    그날 트렌드 지면에 실린 것. 깃허브(github): 머리기사, 7일 동안 별이 가장 많이 늘어난 저장소 10개, 처음 트렌딩에 오른 저장소(since 날짜 이후 처음), 깃허브 일간 트렌딩 목록(rank_day_before가 비면 전날 목록에 없던 저장소, first_trending은 since 날짜 이후 처음 오른 저장소). 쇼핑(commerce): 일주일 사이 분야 10위 안으로 오른 검색어와 작년 이맘때 줄(last_year — times: 검색량이 작년 이맘때의 N배, new: 작년 이맘때엔 거의 찾지 않던 말, holiday: 그 명절마다 오르는 말), 그 아래 함께 본 사실 한 줄(clue — 명절까지 남은 날 · 지난 3년 같은 철 · 같은 분야에서 함께 오른 말, 원인이나 예측이 아닙니다), 분야마다 많이 찾은 검색어 다섯, 분야 100위 안에 새로 든 검색어(since 날짜 이후 새로). since는 트렌드가 그 세계를 기록하기 시작한 날입니다 — 사람에게 전할 때는 지면처럼 그 날이 무엇인지 함께 말해 주세요("트렌드가 기록을 시작한 {since} 이후 처음"). 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.

    mcp-tool

    {
      "type": "object",
      "title": "todayArguments",
      "required": [
        "world"
      ],
      "properties": {
        "date": {
          "anyOf": [
            {
              "type": "string"
            },
            {
              "type": "null"
            }
          ],
          "title": "Date",
          "default": null,
          "description": "YYYY-MM-DD. 없으면 가장 최근 날"
        },
        "world": {
          "enum": [
            "github",
            "commerce"
          ],
          "type": "string",
          "title": "World",
          "description": "github = 깃허브 트렌딩, commerce = 쇼핑 검색어"
        }
      }
    }
    arguments 31 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id c4d1d447f889193e.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/c4d1d447f889193e/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/c4d1d447f889193e/badge.svg)](https://brick.blue/agent/c4d1d447f889193e?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
70%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.