Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

WordRadar

REMOTE · WWW.WORDRADAR.DEV

Keyword intelligence via MCP: emerging search terms, SERP difficulty, site radar, Stripe rankings

+4 this week 63 Trust /100

Last scanned (4 hours ago)

Scores higher than 44% of remote servers

Reachable. Last reached 5 Nov 2026.

Category Marketing and SEO

Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Endpoint Security57
Transport & Reachability100
Schema Quality & AI Usability58
  • AI-judged instruction clarity (fair).Partial
  • Tool/resource definitions use about 528 tokens (~58/item across 9 items; 9 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management37
  • Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage73
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 20% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 5 Nov 26 +1

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

  • 3 Nov 26 +1

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

  • 1 Nov 26 +1
    • Schema quality: 51 → 58 ▼ functional
    • Tool coverage: 8% → 20% ▲ functional
    • New tool “meme_radar” functional
  • 31 Oct 26 +1

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

  • 29 Oct 26 +1

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

  • 27 Oct 26 +1

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

  • 26 Oct 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 25 Oct 26 57

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 5 Nov 2026 · Probed https://www.wordradar.dev/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=wordradar.dev CN=YE1,O=Let's Encrypt,C=US 19 Oct 2026 17 Jan 2027 ECDSA 256 ECDSA-SHA384 64b5ad237cfd5393817c3cc7b3e8d9ee3e8
SANs: *.wordradar.dev, wordradar.dev
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of www.wordradar.dev. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
dev. present 60074 8 Verified
wordradar.dev. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://www.wordradar.dev/mcp Verified 200
http (plaintext) http://www.wordradar.dev/mcp HTTPS enforced 301 https://www.wordradar.dev/mcp
MCP tools · 9 exposed · ~488 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
domain_timeline ~42

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

NameTypeReqDescription
domainstringyes–

No output schema declared.

No examples provided.

get_usage ~16

查我的 credits 余额(免费)

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

ledger_pulse ~30

新词脉搏:最新账本期的首现新词数(免费端点)

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

ledger_words ~98

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

NameTypeReqDescription
directionstring––
limitnumber––
sitestring–站群匹配(如 voicememotext)——该词该进你哪个站
typestring––

No output schema declared.

No examples provided.

meme_radar ~117

梗雷达:梗词监控层(KYM/新闻/TikTok 官方榜/Trends/Reddit)新捕获的梗词,含首见时间、来源与 flag。带 term 查单条,不带则列近期(默认仅 flagged)。1 credit

NameTypeReqDescription
flagged_onlyboolean–列表模式是否只看词面规则命中
limitnumber––
termstring–精确查单条(大小写不敏感)

No output schema declared.

No examples provided.

proxy_kd_score ~57

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

NameTypeReqDescription
keywordstring––
resultsarrayyes–

No output schema declared.

No examples provided.

site_radar_latest ~55

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

NameTypeReqDescription
hostingstring––
limitnumber––
min_pointsnumber––

No output schema declared.

No examples provided.

stripe_leaderboard ~36

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

NameTypeReqDescription
monthstring––

No output schema declared.

No examples provided.

trends_rising ~37

谷歌趋势上升词(Breakout 优先,读采集缓存)。2 credits

NameTypeReqDescription
keywordstringyes–

No output schema declared.

No examples provided.

Install

How do I install the WordRadar MCP server?

WordRadar is a hosted endpoint at https://www.wordradar.dev/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.

remote · www.wordradar.dev

# add to Claude Code
claude mcp add --transport http lian-yang-wordradar 'https://www.wordradar.dev/mcp'
Common questions

What is the WordRadar MCP server?

WordRadar is an MCP server listed in the public MCP registry as io.github.lian-yang/wordradar. Keyword intelligence via MCP: emerging search terms, SERP difficulty, site radar, Stripe rankings. This page covers its hosted endpoint (https://www.wordradar.dev/mcp).

Is the WordRadar MCP server safe to use?

WordRadar scores 63 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 WordRadar MCP server expose?

WordRadar exposes 9 tools: ledger_pulse, ledger_words, proxy_kd_score, site_radar_latest, trends_rising, and 4 more. Their descriptions and schemas cost roughly 488 tokens of context every time the server is loaded.

Does the WordRadar MCP server require authentication?

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

Is the WordRadar MCP server still maintained?

WordRadar is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.