Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.Rakesh1002/namemyapp

REMOTE · MCP.NAMEMY.APP · 3 COMPONENTS

Brandable business names with live domain availability + one-click buy URLs.

0 this week 76 Trust /100

Last scanned (2 hours ago)

Scores higher than 66% of remote servers

Reachable. Last reached 5 Nov 2026.

Category Marketing and SEO

Recent critical change

Authorization (20 Oct 2026). See the changelog before you install this server.

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security63
Transport & Reachability100
Schema Quality & AI Usability68
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 1729 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 15 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities40
  • Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28. See how to fix → Fail
Changelog

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.

  • 21 Oct 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • New tool “connect_domain”, which the server declares destructive security
    • Tool “buy_domain” rewrote its description, which is the text the model reads security
    • Schema quality: pass → fail ▼ functional
    • Tool coverage: 44% → 49% ▲ functional
    • “buy_domain” added an optional parameter “connect” cosmetic
  • 20 Oct 26 0
    • Authorization: unverified → fail ▼ critical
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “check_domain” rewrote its description, which is the text the model reads security
    • Tool “buy_domain” is now declared destructive security
    • Tool “set_dns_record” is now declared destructive security
    • “buy_domain” reworded the description of “years” cosmetic
    • Tool “set_dns_record” changed its title: Set a DNS record cosmetic
    • Tool “brand_conflict_check” changed its title: Check brand name conflicts cosmetic
    • Tool “buy_domain” changed its title: Buy a domain cosmetic
    • Tool “buy_link” changed its title: Get a domain buy link cosmetic
    • Tool “check_domain” changed its title: Check domain availability (signed in) cosmetic
    • Tool “check_domain_public” changed its title: Check domain availability and price cosmetic
    • Tool “check_domains_public_bulk” changed its title: Check many domains at once cosmetic
    • Tool “generate_brand_kit” changed its title: Generate a brand kit cosmetic
    • Tool “generate_legal_docs” changed its title: Generate legal documents cosmetic
    • Tool “generate_logo” changed its title: Generate logo concepts cosmetic
    • Tool “generate_names” changed its title: Generate available business names cosmetic
    • Tool “generate_social_kit” changed its title: Generate a social media kit cosmetic
    • Tool “list_domains” changed its title: List my domains cosmetic
  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 26 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Aug 26 0
    • Stability: 0.97 → pass security
  • 11 Aug 26 0
    • 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 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostics

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 5 Nov 2026 · Probed https://mcp.namemy.app/direct

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=namemy.app CN=WE1,O=Google Trust Services,C=US 19 Oct 2026 17 Jan 2027 ECDSA 256 ECDSA-SHA256 76f04c806430cd2b0e864c3d940b6f49
SANs: namemy.app, mcp.namemy.app, *.mcp.namemy.app
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of mcp.namemy.app. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
app. present 23684 8 Verified
namemy.app. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=15552000; includeSubDomains; preload
x-content-type-options nosniff

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.namemy.app/direct Verified 200
http (plaintext) http://mcp.namemy.app/direct HTTPS enforced 301 https://mcp.namemy.app/direct
MCP tools · 14 exposed · ~1,681 tokens

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 →

Tool Tokens
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]

NameTypeReqDescription
contextstring–Optional industry/product context to narrow results (e.g., 'AI task manager')
namestringyesBrand name to check

No output schema declared.

No examples provided.

buy_domain ~175

Purchase a domain using the stored payment method. Returns success/failure. 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]

NameTypeReqDescription
connectobject–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…
domainstringyesDomain to purchase
yearsnumber–Registration years. Omit to use the registry minimum (1 year; .ai is 2 years, charged at 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.

NameTypeReqDescription
domainstringyesFully-qualified domain to buy, e.g. 'codeflow.ai'
priceUsdnumber–Optional quoted price in USD. If omitted, the checkout page will fetch the live price.

No output schema declared.

No examples provided.

check_domain ~60

Check if a domain is available and get its price. [Requires a free namemy.app API key — get one at https://namemy.app/app/api-keys]

NameTypeReqDescription
domainstringyesDomain to check, e.g. 'taskflow.app'

No output schema declared.

No examples provided.

check_domain_public ~128

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.

NameTypeReqDescription
domainstringyesDomain to check, e.g. 'taskflow.app'

No output schema declared.

No examples provided.

check_domains_public_bulk ~110

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.

NameTypeReqDescription
domainsarrayyesArray 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]

NameTypeReqDescription
domainstringyesDomain the user owns, e.g. 'taskflow.dev'
dryRunboolean–Validate and return the records that would be written, without changing anything
includeWwwboolean–Also point www at the deployment
targetstringyes–
valuestring–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]

NameTypeReqDescription
descriptionstring––
includeVisualsboolean––
industrystring––
namestringyes–

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]

NameTypeReqDescription
businessNamestringyes–
businessTypestringyessaas | ecommerce | agency | marketplace | …
contactEmailstring––
regionsarray––
websiteUrlstring––

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]

NameTypeReqDescription
countnumber–Number of variations (1-9)
descriptionstringyesWhat the business does
namestringyes–
preferencesobject––
sloganstring––

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]

NameTypeReqDescription
countnumber–Max results
descriptionstringyesWhat does the project/business do?
industrystring–Industry context (e.g., 'saas', 'fintech', 'healthcare')
tldsarray–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]

NameTypeReqDescription
businessNamestringyes–
descriptionstring––
goalsarray––
industrystringyes–
platformsarray––
targetAudiencestringyes–
voiceTonestring––

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]

NameTypeReqDescription
domainstringyes–
hoststringyesSubdomain or @ for root
ttlnumber––
typestringyes–
valuestringyes–

No output schema declared.

No examples provided.

Install

How do I install the io.github.Rakesh1002/namemyapp MCP server?

io.github.Rakesh1002/namemyapp is a hosted endpoint at https://mcp.namemy.app/direct, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · mcp.namemy.app

# add to Claude Code
claude mcp add --transport http rakesh1002-namemyapp 'https://mcp.namemy.app/direct'
Common questions

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 hosted endpoint (https://mcp.namemy.app/direct).

Is the io.github.Rakesh1002/namemyapp MCP server safe to use?

io.github.Rakesh1002/namemyapp scores 76 out of 100 on VerifyMCP. 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,681 tokens of context every time the server is loaded.

Does the io.github.Rakesh1002/namemyapp MCP server require authentication?

No. We connected to io.github.Rakesh1002/namemyapp without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

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 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.