Namecatcher Skills

io.github.productmap由 GitHub 帳號 productmap 發布v0.1.1更新於 Oct 24, 2026

Score and value collectible Telegram usernames: namability 0-100, fair price, thesis. No API key.

已驗證STDIO僅桌面金融商業與電商

概覽

AI 產生的概覽

為可收藏的 Telegram 使用者名稱評分與估值，提供可命名性分數、合理價格估算與定位論述。

可以做什麼
Namecatcher Skills 是 NameCatcher 公開 API 的輕量 stdio 橋接，針對可收藏的 Telegram 使用者名稱。它提供三個工具：score_name（可命名性 0-100 分、等級、以 GRAM 計的合理價格與簡短論述）、compare_names（為最多 20 個候選名稱評分並排序）、check_fragment_ask（將 Fragment 要價與類別估值比較，回傳合理/要價比值與結論）。分數依模型版本決定，可安全快取。
適用情境
適合在購買或出價前評估、比較與定價可收藏的 Telegram 使用者名稱，例如篩選具品牌潛力的名稱，或判斷某個 Fragment 要價高於還是低於類別估值。
執行需求
以 npm 套件形式透過 npx 在本機執行（需要 Node.js），也可使用遠端 Streamable HTTP 端點。不需要 API 金鑰、錢包或帳號。選用環境變數 NAMECATCHER_API_ORIGIN 可覆寫 API 來源。需要能連線至 NameCatcher API 的網路。
安裝前請注意
分數衡量的是命名品質，而非某個特定標的的需求，做任何金錢決策前請先查看 Fragment 即時價格。API 限制為每 IP 每分鐘 60 次、每天 1,000 次請求。查詢的使用者名稱會傳送給第三方 NameCatcher API。

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 Namecatcher Skills，將其新增到工作區。
  2. 為需要使用其工具的對話啟用該服務。

Desktop only，透過 STDIO。 STDIO 服務會啟動本機處理程序，因此需要 SourceWeft 桌面主機。

其他 MCP 客戶端

參照 儲存庫 中的啟動說明。

README

NameCatcher — username intelligence for AI agents

Score and value collectible Telegram usernames: namability score (0–100) validated against 111k+ real Fragment sales, fair price estimation in GRAM, and positioning theses. Free public API — no key, no wallet, no setup.

Three ways to plug in, thinnest first:

LayerForInstall
Plain HTTPany agent that can curl/fetchnothing
Agent SkillClaude Code / skills-compatible agentsnpx skills add productmap/namecatcher-skills
MCP serverClaude Desktop/Code, any MCP clientnpx -y namecatcher-mcp

Built by NameCatcher — the Telegram mini app for username investors: mint catching, market analytics, portfolio, value passports.

Quick try

bash
curl -s "https://api-namecatcher.rocketname.com/public/score/wearlab?lang=en" | jq
json
{  "username": "wearlab",  "score": 67,  "band": "strong",  "fair_price_ton": 400,  "thesis": "A crisp fusion of \"wear\" and \"lab\" …",  "lang": "en",  "analysis_url": "https://t.me/NameCatcherBot?startapp=name_wearlab__pub_api",  "fragment_url": "https://fragment.com/username/wearlab"}

API reference

One endpoint, no auth:

GET https://api-namecatcher.rocketname.com/public/score/{name}?lang={en|ru}

Parameters

ParamInRequiredDescription
namepathyesUsername without @. 4–32 chars, a-z 0-9 _
langquerynoen (default) or ru — language of thesis

Response fields

FieldTypeDescription
usernamestringCanonical (lowercase) username
scoreint 0–100Namability — quality of the name as a brandable asset. Market-validated: names scoring 90+ sell for a multiple of 80–89 names
bandstringpremium (≥80) · strong (≥66) · medium (≥50) · weak (<50). Below 50 is not investment-grade
fair_price_tonnumber | nullClass-based fair price estimate in GRAM (length × score class)
thesisstring | nullShort positioning summary (why the name works, for whom). Present only for names already analyzed — null is not a quality signal
langstringLanguage the thesis was returned in
analysis_urlstringFull breakdown in the NameCatcher mini app
fragment_urlstringThe name's page on Fragment (live market status, buy/bid)

Errors

StatusBodyMeaning
400{"error":"INVALID_NAME"}Not a valid username string
400{"error":"NOT_COLLECTIBLE"}Valid string, but not scorable as a collectible (e.g. too short)
429{"error":"RATE_LIMITED","retry_after_s":n}Over 60 req/min per IP — wait retry_after_s and retry
429{"error":"DAILY_LIMIT","limit_per_day":1000}Over 1,000 req/day per IP

Rate limits

60 requests/min and 1,000 requests/day per IP. Generous for agent workflows (evaluating and comparing dozens of names); not enough for bulk scraping — that's intentional. Need more for a legitimate use case? Ping @BrandEvangelist.

curl cookbook

bash
# Score one name (Russian thesis)curl -s "https://api-namecatcher.rocketname.com/public/score/morya?lang=ru" | jq '{score, band, fair_price_ton}'
# Compare candidates: pick the best of threefor n in pulsefit traintrack fitwave; do  curl -s "https://api-namecatcher.rocketname.com/public/score/$n" | jq -c '{username, score, band}'done | sort -t: -k2 -rn
# Pre-purchase check: is a 300 GRAM ask below class valuation?curl -s "https://api-namecatcher.rocketname.com/public/score/vault" \  | jq '{score, fair_price_ton, below_class: (.fair_price_ton / 300 >= 1.2)}'

Agent Skill

The names/ton-usernames skill teaches an agent the full workflow: single-name evaluation, candidate comparison, and pre-purchase checks against Fragment asks.

bash
npx skills add productmap/namecatcher-skills --skill ton-usernames# or manually:cp -r names/ton-usernames ~/.claude/skills/

A PR adding this skill to the official ton-org/skills is open.

MCP server

A thin stdio bridge over the same API — for Claude Desktop, Claude Code, and any MCP client. No key needed. Published on npm as namecatcher-mcp (GitHub install npx -y github:productmap/namecatcher-skills also works).

[smithery badge]

Remote endpoint (Streamable HTTP) — same three tools, zero install:

https://mcp-namecatcher.rocketname.com/mcp
bash
claude mcp add --transport http namecatcher https://mcp-namecatcher.rocketname.com/mcp

Claude Code:

bash
claude mcp add namecatcher -- npx -y namecatcher-mcp

Claude Desktop / other MCP clients (mcpServers config):

json
{  "mcpServers": {    "namecatcher": {      "command": "npx",      "args": ["-y", "namecatcher-mcp"]    }  }}

Tools

ToolDescriptionArguments
score_nameScore one username: namability, band, fair price, thesisname, lang?
compare_namesScore up to 20 candidates and rank them by scorenames[], lang?
check_fragment_askCompare a Fragment asking price to the class valuation → fair/ask ratio + verdictname, ask_ton

Environment: NAMECATCHER_API_ORIGIN (optional) — override the API origin.

Notes for builders

  • The score measures naming quality, deterministic per model version — safe to cache
  • It is not demand for a specific lot: always check the live Fragment price before money decisions
  • Pairs naturally with TON wallet tooling (@ton/mcp): evaluate → then buy

Links

License

MIT

來源：README.md，提交 c916d7b

工具

0
SourceWeft 尚未在沙箱中啟動過該軟體包，因此其工具未知。

版本歷史

1
  1. v0.1.1最新Sep 16, 2026

評分

已滿足適用檢查項的 50%

該評分衡量此收錄條目的完整程度，依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價，也不表示伺服器安全或目前可用：可連通性是帶日期的檢查結果，評分也不包含安裝量或使用者評價。

  • 近 30 天內可連通25 分

    請保持端點能夠回應 MCP 握手；SourceWeft 每 30 天探測一次。

  • 已宣告認證方式10 分

    請在註冊中心條目中宣告憑證請求標頭，或保持端點能夠回應探測，以便判定其認證方式。

  • 已列出工具15 分

    請讓伺服器在無憑證時回應 tools/list，或發布可在沙箱中無憑證啟動的軟體包。

  • 描述必需15 分
  • 圖示10 分
  • 文件15 分
  • 授權條款10 分