NameCatcher
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NAMECATCHER_API_ORIGIN | No | Override the API origin for the NameCatcher MCP server. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| score_nameA | Score a Telegram username as an asset: namability 0-100 (validated against real Fragment sales), quality band, fair price estimate in GRAM, and a positioning thesis when available. Use when the user asks whether a username is good, what it is worth, or before buying/minting it. |
| compare_namesA | Score several username candidates (max 20) and rank them by score. Use when choosing between name options for a brand, bot, channel or investment. |
| check_fragment_askA | Pre-purchase check: compare a Fragment asking price against the name's class valuation (fair price). Returns the fair/ask ratio — ratio >= 1.2 means the lot is priced below its class valuation. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool serves a distinct, non-overlapping purpose: one compares ask prices, one ranks multiple candidates, and one evaluates a single name. No ambiguity.
All tool names follow a consistent verb_noun pattern in snake_case, using verbs like check, compare, and score.
Three tools is appropriate for a focused server that handles Telegram username valuation and comparison. Not too few or too many.
Covers core valuation and comparison operations. Lacks direct buy/mint actions, but these are not valuation tasks. Minor gap in lifecycle coverage.