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 分