io.github.productmap/namecatcher-skills
NPM · NAMECATCHER-MCP · SCANNED AUG 3
Score and value collectible Telegram usernames: namability 0-100, fair price, thesis. No API key.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score →
Supply Chain Security87
- No malware found by supply-chain analysis.Pass
- Only part of the dependency tree could be resolved (95 of 99), so this covers what we could see, not the whole tree.Partial
- No install/post-install scripts declared.Pass
- Only part of the dependency tree could be resolved (95 of 99), so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 17 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability66
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 242 tokens (~80/item across 3 items; 3 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
- Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage94
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 83% of tool parameters carry a description.Partial
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
npm · namecatcher-mcp
claude mcp add productmap-namecatcher-skills -- npx -y namecatcher-mcp
codex mcp add productmap-namecatcher-skills -- npx -y namecatcher-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"productmap-namecatcher-skills": {
"type": "local",
"command": [
"npx",
"-y",
"namecatcher-mcp"
],
"enabled": true
}
}
} openclaw mcp add productmap-namecatcher-skills --command npx --arg -y --arg namecatcher-mcp
mcp_servers:
productmap-namecatcher-skills:
command: "npx"
args: ["-y", "namecatcher-mcp"] {
"mcpServers": {
"productmap-namecatcher-skills": {
"command": "npx",
"args": [
"-y",
"namecatcher-mcp"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 2 Aug 26 +53
- Known CVEs: unverified → partial ▲ security
- Malware scan: unverified → pass ▲ security
- Security disclosure: fail → unverified ▼ functional
- Schema quality: unverified → good ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Stability: unverified → 0.20 ▲ functional
- Dependency health: unverified → partial ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- 1 Aug 26 −15
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 +4
- Malware scan: pass → unverified ▼ security
- Tool coverage: unverified → 100 ▲ functional
- 28 Jul 26 −22
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 27 Jul 26 46
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 3 Aug 2026 · Analysed npm/[email protected]
Provenance none
Ecosystem: npm · Outcome: none
Dependencies 95 packages
95 packages in the resolved dependency tree · 95 deprecated · 29 stale.
The dependency tree was only partially resolved, so these counts may be incomplete.
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.
check_fragment_ask ~82
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.
| Name | Type | Req | Description |
|---|---|---|---|
| ask_ton | number | yes | Asking price / current bid in GRAM (TON) |
| name | string | yes | Username without @ |
No output schema declared.
No examples provided.
compare_names ~55
Score several username candidates (max 20) and rank them by score. Use when choosing between name options for a brand, bot, channel or investment.
| Name | Type | Req | Description |
|---|---|---|---|
| lang | string | — | — |
| names | array | yes | Candidate usernames |
No output schema declared.
No examples provided.
score_name ~105
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.
| Name | Type | Req | Description |
|---|---|---|---|
| lang | string | — | Thesis language, default en |
| name | string | yes | Username without @ (4-32 chars, a-z 0-9 _) |
No output schema declared.
No examples provided.