Namewhere: Company Name to Domain & Website Finder

io.github.CyberMax-toolsPublished by GitHub account CyberMax-toolsv1.0.0Updated Oct 24, 2026

Namewhere: company name to official website domain, confidence, evidence, socials.

The publisher's own server: Finder Jobs

VerifiedStreamable HTTPWeb executableWeb Search & ScrapingBusiness & Commerce

Overview

AI-generated overview

A remote Apify-hosted MCP server that turns a company name into its official website domain, with confidence, evidence and social profiles.

What you can do
Resolve a company name to its official website domain, with a confidence score and supporting evidence for the match. Return associated social profiles alongside the domain result. Look up official web addresses for companies during research or data enrichment.
When to use it
Useful when an assistant needs to find or verify a company's official website and social profiles from just its name, for example in lead research, data enrichment or due diligence.
Requirements
A remote MCP endpoint at mcp.apify.com, reached over streamable HTTP. OAuth authentication is required, supplied through the Authorization header. No local runtime or package is needed.
Before you install
Requires OAuth credentials via the Authorization header; keep that token private. Results are third-party lookups, so verify the returned domain and confidence before relying on them. Usage may be subject to Apify account limits or billing.

Installation

In SourceWeft

  1. Open Namewhere: Company Name to Domain & Website Finder in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.CyberMax-tools%2Fcompany-to-domain/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "namewhere-company-name-to-domain-website": {
      "type": "http",
      "url": "https://mcp.apify.com/?tools=cybermax/company-to-domain"
    }
  }
}

README

This repository has no README.

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestSep 26, 2026

Score

60% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.

Other Finder integrations