NameCatcher

https://server.smithery.ai/ceo-j1pw/namecatcher/mcp

● healthy

Valuation brain for collectible Telegram usernames. Score any name 0–100 (namability, validated against 111k+ real Fragment sales), estimate fair price in GRAM, and run pre-purchase checks against Fragment asking prices. Free public API — no key, no wallet, no setup. **Tools** - `score_name` — namability score, quality band, fair price, positioning thesis - `compare_names` — rank up to 20 candidates for a brand, bot or investment - `check_fragment_ask` — is a Fragment ask below its class valuation? fair/ask ratio + verdict Pairs naturally with TON wallet tooling: evaluate → then buy. Rate limits: 60 req/min, 1,000 req/day per IP.

Transport

streamable-http

Auth

smithery_api_key

Cost

—

Protocol revision

2025-06-18

negotiated, not declared

MCP readiness

B · 86/100

Readiness is how fully this listing follows its protocol and how it behaved in our probes over 30 days. It is shown for reference and does not move it in search. Search order and leaderboards use the separate quality grade (here B, 77.4/100), which weighs availability, conformance, p95 speed and descriptor. How the two differ

Valid MCP handshake	10/10	initialize and tools/list both answered.
Live MCP endpoint	25/25	Endpoint answers the MCP initialize handshake (1520 ms).
Protocol revision	6/10	Speaks MCP 2025-06-18, 2 revision(s) behind 2026-07-28.
Signed descriptor	n/a	No MCP standard defines a signed server descriptor.
Uptime (30 days)	15/15	30/30 probes succeeded over 30 days (100%).
Tool declaration	10/10	Lists 3 tool(s) with descriptions.
Verified identity	5/10	Publisher declared (repository, package or homepage); claim this listing to verify domain control.
Freshness + modern flags	4/5	seen in a source within 7 days.
Auth declaration	2/5	Declares credential scheme: smithery_api_key.

Applicable criteria total 90 points, scaled to 100.

Responsiveness: Responsive (1520 ms; bands ≤2.5 s, ≤5 s, ≤8 s, slower; penalty only).

Measured 2026-11-11.

Nine criteria, the same as the A2A readiness score, read from our daily MCP probe (initialize + tools/list) and 30-day probe history. No MCP standard defines a signed server descriptor, so that criterion is n/a and the other 90 points are scaled to 100. Grades: A>=90, B>=75, C>=60, D>=40, F<40. Display only: search order uses the quality grade.

Compared with peers

Against 53,039 reachable MCP servers in our daily snapshot (2026-11-12 06:46 UTC). Display only; it does not change search order.

Readiness: Higher than 80% of peers; This listing 86 · peer median 81
Latency: Faster than 44% of peers; This listing 378 ms · peer median 326 ms

Where it loses the most points, and how to win them back

Verified identity −5 — Claim the listing and prove control of its domain.
Now: Publisher declared (repository, package or homepage); claim this listing to verify domain control.
Protocol revision −4 — Support the current protocol revision.
Now: Speaks MCP 2025-06-18, 2 revision(s) behind 2026-07-28.
Auth declaration −3 — State how to authenticate (an auth scheme, or that none is needed).
Now: Declares credential scheme: smithery_api_key.

How many agent tools actually work · All statistics

Listed in

Directories this entry was found in.

smithery since 2026-07-16 ↗

How to connect

MCP endpoint (streamable-http)

https://server.smithery.ai/ceo-j1pw/namecatcher/mcp

JSON-RPC initialize probe

curl -X POST https://server.smithery.ai/ceo-j1pw/namecatcher/mcp \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json, text/event-stream' \
  -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{}}'

Homepage

https://mcp-namecatcher.rocketname.com

Listed at (smithery)

https://mcp-namecatcher.rocketname.com