
Namecatcher Skills
io.github.productmapPublished by GitHub account productmapv0.1.1Updated Oct 24, 2026
Score and value collectible Telegram usernames: namability 0-100, fair price, thesis. No API key.
Overview
Scores and values collectible Telegram usernames, giving a namability score, fair price estimate, and positioning thesis.
- What you can do
- Namecatcher Skills is a thin stdio bridge over the NameCatcher public API for collectible Telegram usernames. It exposes three tools: score_name (namability score 0-100, band, fair price in GRAM, and a short thesis), compare_names (score and rank up to 20 candidates), and check_fragment_ask (compare a Fragment asking price to the class valuation and return a fair/ask ratio and verdict). Scores are deterministic per model version and safe to cache.
- When to use it
- Use it when evaluating, comparing, or pricing collectible Telegram usernames before buying or bidding, for example shortlisting brandable names or checking whether a Fragment ask is above or below the class valuation.
- Requirements
- Runs locally as an npm package via npx (Node.js required) or as a remote Streamable HTTP endpoint. No API key, wallet, or account is needed. Optional environment variable NAMECATCHER_API_ORIGIN overrides the API origin. Network access to the NameCatcher API is required.
Installation
In SourceWeft
- Open Namecatcher Skills in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
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:
Built by NameCatcher — the Telegram mini app for username investors: mint catching, market analytics, portfolio, value passports.
Quick try
API reference
One endpoint, no auth:
Parameters
Response fields
Errors
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
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.
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).
Remote endpoint (Streamable HTTP) — same three tools, zero install:
Claude Code:
Claude Desktop / other MCP clients (mcpServers config):
Tools
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
- 🤖 Bot & mini app: @NameCatcherBot
- 🛒 Username market: fragment.com
- 🧩 TON MCP ecosystem: mcp.ton.org
License
MIT
Source: README.md at commit c916d7b
Tools
0Version history
1- v0.1.1LatestSep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts