io.github.Rakesh1002/namemyapp
NPM · @NAMEMYAPP/MCP · 3 COMPONENTS
Brandable business names with live domain availability + one-click buy URLs.
Available components
Last scanned (18 hours ago)
Scores higher than 69% of npm servers
Category Marketing and SEO
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 → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 34 of 98 dependencies flagged as unhealthy (1 deprecated). 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 13 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability69
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1735 tokens (~123/item across 14 items; 14 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage83
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 49% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 14 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 14 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
- 3 Nov 26 0
- Stability: 0.97 → pass security
- 2 Nov 26 0
- Stability: pass → 0.97 functional
- 27 Oct 26 0
- Stability: 0.97 → pass security
- 26 Oct 26 0
- Stability: pass → 0.97 functional
- 22 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 21 Oct 26 −16
- Malware scan: pass → unverified ▼ security
- Schema quality: pass → fail ▼ functional
- Tool coverage: 44% → 49% ▲ functional
- Package version: 1.1.8 → 1.1.10 functional
- 20 Oct 26 −3
- Schema quality: 108 → 1333 ▼ functional
- Tool coverage: 100% → 44% ▼ functional
- Security disclosure: fail → unverified ▼ functional
- Schema quality: excellent → good functional
- Package version: 1.1.5 → 1.1.8 functional
- 17 Oct 26 +2
- Stability: 0.87 → pass security
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 4 Nov 2026 · Analysed npm/@namemyapp/mcp@1.1.10
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 98 packages
| Packages resolved | 98 |
|---|---|
| Deprecated | 1 |
| Stale | 33 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
brand_conflict_check ~91
Check if a brand name conflicts with USPTO trademarks, live company homepages, or search results. Free for all tiers. [Requires a free namemy.app API key — get one at https://namemy.app/app/api-keys]
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | – | Optional industry/product context to narrow results (e.g., 'AI task manager') |
| name | string | yes | Brand name to check |
No output schema declared.
No examples provided.
buy_domain ~194
Purchase a domain for one year using the stored payment method. Needs a WHOIS contact: the one saved at namemy.app/app/settings, or pass `contact`. A `contact_required` error lists the missing fields to collect from the user. Pass `connect` to also point it at a deployment (Vercel, Netlify, Cloudflare Pages, GitHub Pages, Render, Railway, Fly) in the same call. [Requires a free namemy.app API key — get one at https://namemy.app/app/api-keys]
| Name | Type | Req | Description |
|---|---|---|---|
| connect | object | – | Optional: after the purchase succeeds, point the domain at this deployment (same as connect_domain). It is validated before anything is bought; its result is reported under `connect`, and a connect f… |
| contact | object | – | Registrant contact. Overrides the saved contact. |
| domain | string | yes | Domain to purchase |
No output schema declared.
No examples provided.
buy_link ~108
Build a one-click purchase URL the user can open to buy a domain on namemy.app. Always available (works without an API key). Use this when the user has decided on a name they like — hand them the URL and they sign up + pay in their browser.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Fully-qualified domain to buy, e.g. 'codeflow.ai' |
| priceUsd | number | – | Optional quoted price in USD. If omitted, the checkout page will fetch the live price. |
No output schema declared.
No examples provided.
check_domain ~70
Check if a domain is available. Returns the retail price, renewal price and a one-click buyUrl. [Requires a free namemy.app API key — get one at https://namemy.app/app/api-keys]
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Domain to check, e.g. 'taskflow.app' |
No output schema declared.
No examples provided.
check_domain_public ~136
PUBLIC, NO API KEY required. The one-stop tool for handing a user a domain decision. Returns ALL of: availability (boolean), retail price (USD), renewal price, registrar, AND a ready-to-use buyUrl the user can click to register the domain on namemy.app. Use this for EVERY candidate before recommending — never invent URLs or prices, always trust the buyUrl this returns. Rate-limited per IP. For bulk checks (multiple domains in one call), use check_domains_public_bulk.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Fully-qualified domain to check, e.g. 'taskflow.app' or 'cronflow.ai' |
No output schema declared.
No examples provided.
check_domains_public_bulk ~127
PUBLIC, NO API KEY required. Same as check_domain_public but checks up to 50 domains in ONE call (faster + fewer rate-limit hits). Returns an array where each item has availability, price, renewal price, registrar, and a clickable buyUrl. ALWAYS prefer this over multiple check_domain_public calls when you have more than one candidate. For 5 brandable .ai suggestions, this is one call instead of five.
| Name | Type | Req | Description |
|---|---|---|---|
| domains | array | yes | Array of fully-qualified domains to check, e.g. ['taskflow.ai','codeflow.ai','shipsync.ai'] |
No output schema declared.
No examples provided.
connect_domain ~313
Point a domain the user owns on namemy.app at their deployment in one call: writes the platform's root and www records, replacing existing A/AAAA/CNAME records on those two hosts (other records are kept). Free. Returns the records applied and removed, plus `nextSteps` the user must do on the platform (e.g. add the domain in the Vercel project settings, or copy a verification TXT record). On failure, `restored: true` means nothing changed; `restored: false` comes with `live`, the records in place now (null if unknown), which is what to report. [Requires a free namemy.app API key — get one at https://namemy.app/app/api-keys]
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Domain the user owns, e.g. 'taskflow.dev' |
| dryRun | boolean | – | Validate and return the records that would be written, without changing anything |
| includeWww | boolean | – | Also point www at the deployment |
| target | string | yes | – |
| value | string | – | The platform's hostname for the deployment: my-site.netlify.app, my-app.pages.dev, octocat.github.io, my-app.onrender.com, the *.up.railway.app target Railway shows after you add the domain there, or… |
No output schema declared.
No examples provided.
generate_brand_kit ~99
Generate a complete brand kit (essentials, audience, personality, visual identity, voice, imagery, applications, dos-and-donts). Requires Founder sub or BRAND_KIT purchase. [Requires a free namemy.app API key — get one at https://namemy.app/app/api-keys]
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | – |
| includeVisuals | boolean | – | – |
| industry | string | – | – |
| name | string | yes | – |
No output schema declared.
No examples provided.
generate_legal_docs ~118
Generate Privacy Policy, Terms of Service, and Cookie Policy for a business. Region-aware (GDPR, CCPA, LGPD). Requires Founder sub or LEGAL_KIT purchase. [Requires a free namemy.app API key — get one at https://namemy.app/app/api-keys]
| Name | Type | Req | Description |
|---|---|---|---|
| businessName | string | yes | – |
| businessType | string | yes | saas | ecommerce | agency | marketplace | … |
| contactEmail | string | – | – |
| regions | array | – | – |
| websiteUrl | string | – | – |
No output schema declared.
No examples provided.
generate_logo ~114
Generate AI logo concepts (icon + palette + typography + layout) for a business. Returns N variations. Requires Founder sub or one-time LOGO_PACK/BRAND_KIT purchase. [Requires a free namemy.app API key — get one at https://namemy.app/app/api-keys]
| Name | Type | Req | Description |
|---|---|---|---|
| count | number | – | Number of variations (1-9) |
| description | string | yes | What the business does |
| name | string | yes | – |
| preferences | object | – | – |
| slogan | string | – | – |
No output schema declared.
No examples provided.
generate_names ~114
Generate brandable business names with real-time domain availability. Returns names that are ACTUALLY available to register, with pricing. [Requires a free namemy.app API key — get one at https://namemy.app/app/api-keys]
| Name | Type | Req | Description |
|---|---|---|---|
| count | number | – | Max results |
| description | string | yes | What does the project/business do? |
| industry | string | – | Industry context (e.g., 'saas', 'fintech', 'healthcare') |
| tlds | array | – | Preferred TLDs |
No output schema declared.
No examples provided.
generate_social_kit ~113
Generate a social media strategy + content kit (posts, captions, calendar, analytics framework). Requires Founder sub or SOCIAL_MEDIA_KIT purchase. [Requires a free namemy.app API key — get one at https://namemy.app/app/api-keys]
| Name | Type | Req | Description |
|---|---|---|---|
| businessName | string | yes | – |
| description | string | – | – |
| goals | array | – | – |
| industry | string | yes | – |
| platforms | array | – | – |
| targetAudience | string | yes | – |
| voiceTone | string | – | – |
No output schema declared.
No examples provided.
list_domains ~39
List all domains owned by the user. [Requires a free namemy.app API key — get one at https://namemy.app/app/api-keys]
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
set_dns_record ~99
Add or update a DNS record for a domain. Useful for pointing domains to Vercel, Netlify, or email services. [Requires a free namemy.app API key — get one at https://namemy.app/app/api-keys]
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | – |
| host | string | yes | Subdomain or @ for root |
| ttl | number | – | – |
| type | string | yes | – |
| value | string | yes | – |
No output schema declared.
No examples provided.
How do I install the io.github.Rakesh1002/namemyapp MCP server?
io.github.Rakesh1002/namemyapp runs locally as an npm package, launched with npx -y @namemyapp/mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @namemyapp/mcp
claude mcp add rakesh1002-namemyapp -- npx -y @namemyapp/mcp
What is the io.github.Rakesh1002/namemyapp MCP server?
io.github.Rakesh1002/namemyapp is an MCP server listed in the public MCP registry as io.github.Rakesh1002/namemyapp. Brandable business names with live domain availability + one-click buy URLs. This page covers its npm package (@namemyapp/mcp).
Is the io.github.Rakesh1002/namemyapp MCP server safe to use?
io.github.Rakesh1002/namemyapp scores 81 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 November 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.Rakesh1002/namemyapp MCP server expose?
io.github.Rakesh1002/namemyapp exposes 14 tools: check_domains_public_bulk, check_domain_public, buy_link, generate_names, check_domain, and 9 more. Their descriptions and schemas cost roughly 1,735 tokens of context every time the server is loaded.
Is the io.github.Rakesh1002/namemyapp MCP server still maintained?
io.github.Rakesh1002/namemyapp is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.Rakesh1002/namemyapp MCP server under?
io.github.Rakesh1002/namemyapp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.