Company Profile by Domain

io.github.BerrkaydevPublished by GitHub account Berrkaydevv1.0.0Updated Nov 22, 2026

Company profile from a domain: legal data, emails, tech stack, open jobs and social links.

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

An Apify-hosted remote MCP server that builds a company profile from a domain: legal data, emails, tech stack, open jobs and social links.

What you can do
  • Look up a company by its domain and return a consolidated profile.
  • Retrieve legal and registration details, contact emails and social links.
  • Surface the company's detected tech stack and currently open job postings.
  • Runs are executed on the Apify platform and billed to the connected Apify account.
When to use it
Useful when you want an assistant to enrich a lead or prospect list, qualify a company before outreach, or gather background on a business from just its website domain.
Requirements
Remote streamable HTTP endpoint at mcp.apify.com with OAuth authentication. An Apify account and an Apify API token sent as an Authorization header in the form Bearer token are required; runs are billed to that Apify account.
Before you install
The Authorization header carries an Apify API token, so treat it as a secret. Lookups consume Apify credits and are billed to your account. Submitted domains are sent to Apify and its data sources, and returned emails and contact details may be personal data subject to privacy rules.

Installation

In SourceWeft

  1. Open Company Profile by Domain 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.Berrkaydev%2Fcompany-profile-by-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": {
    "company-profile-by-domain": {
      "type": "http",
      "url": "https://mcp.apify.com/?tools=berkaydev/company-profile-by-domain"
    }
  }
}

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.0LatestNov 22, 2026

Score

67% 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.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.