mcp-server-domain-evaluator
Related Servers
Alternatives to mcp-server-domain-evaluator
No user-submitted related servers found.
Related Servers
- AlicenseBqualityCmaintenanceEnables domain investors, webmasters, and autonomous agents to perform comprehensive domain audits including brand scoring, TLD tier analysis, and DNS connectivity checks, and to generate strategic brand suffixes and industry compound variations for portfolio expansion.28 npmMIT
- AlicenseAqualityDmaintenanceEnables domain name availability checking through DNS and WHOIS lookups with confidence scoring. It supports searching across alternative TLDs and generating domain name variations for branding purposes.4ISC
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to check domain availability across multiple TLDs with real-time pricing, brainstorm creative domain names, analyze domains for brandability and SEO potential, and search for domains by price and category without CAPTCHAs.17 npm3MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to vet and rank product name candidates in batch by checking domain availability, App Store and Google Play collisions, exact-phrase web results, GitHub handles and repos, and trademark register lookups.MIT
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to check and rank startup name candidates by domain availability, trademark conflicts, and social handle availability, with optional name generation and scoring profiles.36 PyPI4MIT
- AlicenseAqualityCmaintenanceEnables AI clients to generate strategic domain pricing tiers—buy-it-now anchors, make-offer floors, auction reserves, and lease prices—along with renewal ROI forecasts comparing holding costs against target flip multiples over 1, 3, and 5 year horizons.28 npmMIT
TDQS
Scored across 2 tools
The two tools target clearly distinct evaluation dimensions: brand quality heuristics versus category/trademark risk screening. There is no apparent overlap in purpose, so an agent can easily select the correct tool.
Both tool names use a consistent snake_case, verb-first convention: evaluate_brand_quality and screen_category_vs_trademark. The pattern is predictable and readable.
Two tools is thin for a domain evaluator, as it likely needs additional checks such as availability, length, TLD suitability, or SEO considerations. The count is borderline rather than clearly appropriate.
The surface covers brand quality and trademark screening but omits other common domain evaluation operations like availability, extension checks, length scoring, or bulk evaluation. These gaps are notable for the stated server purpose.