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

wordradar

https://www.wordradar.dev

Registry code: 0cab9a1121885392

api record

wordradar 数据工具：新词/新站/KD/趋势/域名历史。鉴权 Bearer wr_…（ledger_pulse/get_usage 免登录）

endpoint
https://www.wordradar.dev/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 wordradar live?
Yes — it answered the hub's last check (checked 3h ago). It answered 100% of checks over the last 30 days.
Is wordradar free to use?
Not anonymously — it asks for a key or a login before it will serve. Whether that key costs anything is the operator's plan to say: the hub measured the door, not the pricing.
What tools does wordradar have?
8 tools: ledger_pulse, ledger_words, proxy_kd_score, site_radar_latest, trends_rising, domain_timeline, stripe_leaderboard, get_usage.
Is wordradar 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
588ms

last good check

priced tools
0

of 8 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

_ what it can do 8 tools
1 auth-required 7 never probed 1 of 8 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.

  • get_usage auth-required 3h ago

    查我的 credits 余额（免费）

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • ledger_pulse unknown never probed

    新词脉搏：最新账本期的首现新词数（免费端点）

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • ledger_words unknown never probed

    词账本查询：按类型(新词|二次爆火|长期大词|存量)/方向(AI|游戏|工具)/站群匹配过滤。1 credit

    mcp-tool

    {
  "type": "object",
  "properties": {
    "site": {
      "type": "string",
      "description": "站群匹配（如 voicememotext）——该词该进你哪个站"
    },
    "type": {
      "enum": [
        "新词",
        "二次爆火",
        "长期大词",
        "存量"
      ],
      "type": "string"
    },
    "limit": {
      "type": "number",
      "default": 30
    },
    "direction": {
      "enum": [
        "AI",
        "游戏",
        "工具"
      ],
      "type": "string"
    }
  }
}
    arguments 30 lines
  • proxy_kd_score unknown never probed

    SERP 前十构成打分（proxy-kd，0-100+判定）。喂入 [{url,domain?}]。1 credit

    mcp-tool

    {
  "type": "object",
  "required": [
    "results"
  ],
  "properties": {
    "keyword": {
      "type": "string"
    },
    "results": {
      "type": "array",
      "items": {
        "type": "object"
      }
    }
  }
}
    arguments 17 lines
  • site_radar_latest unknown never probed

    HN 新站发现（free=免费托管子域/custom=自有域名）。1 credit

    mcp-tool

    {
  "type": "object",
  "properties": {
    "limit": {
      "type": "number",
      "default": 30
    },
    "hosting": {
      "enum": [
        "free",
        "custom",
        "all"
      ],
      "type": "string"
    },
    "min_points": {
      "type": "number"
    }
  }
}
    arguments 20 lines
  • trends_rising unknown never probed

    谷歌趋势上升词（Breakout 优先，读采集缓存）。2 credits

    mcp-tool

    {
  "type": "object",
  "required": [
    "keyword"
  ],
  "properties": {
    "keyword": {
      "type": "string",
      "maxLength": 120
    }
  }
}
    arguments 12 lines
  • domain_timeline unknown never probed

    域名历史：RDAP 注册事件 × Wayback 分段/空窗/换主结论。2 credits

    mcp-tool

    {
  "type": "object",
  "required": [
    "domain"
  ],
  "properties": {
    "domain": {
      "type": "string"
    }
  }
}
    arguments 11 lines
  • stripe_leaderboard unknown never probed

    Stripe 官方引荐月榜（跑通闭环的新玩家信号）。1 credit

    mcp-tool

    {
  "type": "object",
  "properties": {
    "month": {
      "type": "string",
      "pattern": "^\\d{6}$"
    }
  }
}
    arguments 9 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 0cab9a1121885392.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/0cab9a1121885392/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/0cab9a1121885392/badge.svg)](https://brick.blue/agent/0cab9a1121885392?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
100%

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.