Nameclick: Email Finder & Lookup Tool

co.nameclickPublished by nameclick.coOfficial publisherv0.1.1Updated Nov 5, 2026

Email finder and enrichment: LinkedIn, GitHub, or a person's name on any page, X and YouTube too.

VerifiedStreamable HTTPWeb executableWeb Search & ScrapingBusiness & Commerce

Overview

AI-generated overview

Nameclick by Sourcey finds a person's email address and enriches the contact with roles and company, from LinkedIn, GitHub, X, YouTube or a name on a page.

What you can do
  • Find a person and their email from a LinkedIn address, an email, a GitHub login, or a full name with a company or domain
  • Reopen a previously found contact by person ID, email or LinkedIn address, at no cost
  • Report lookup status such as needs_employer or candidates when the identifier is ambiguous
  • Retrieve the lookup API description, OpenAPI document and plans for direct API use
When to use it
Useful when an assistant needs to turn a profile, login or name into a verified email address and company context, for example while researching people or preparing outreach. It is aimed at lookups the user explicitly asks for, not bulk enrichment.
Requirements
Remote hosted MCP endpoint; no local package. A Nameclick key is required for find_contact and get_contact, sent as a Bearer token in the Authorization header, taken from the extension's settings. get_services needs no key.
Before you install
Lookups consume paid credits: one lookup is spent the first time an email address on record is shown for someone, so repeated or broad searches cost money. The server receives the identifiers and page text you send, and the privacy policy governs what is kept. Only look up people the user asks about.

Installation

In SourceWeft

  1. Open Nameclick: Email Finder & Lookup Tool in the dashboard and add it to a workspace.
  2. 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/co.nameclick%2Fnameclick/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.

{
  "mcpServers": {
    "nameclick-email-finder-lookup-tool": {
      "type": "http",
      "url": "https://mcp.nameclick.co/mcp"
    }
  }
}

README

Nameclick by Sourcey

Find a person's email address from their LinkedIn profile, their GitHub login, or their name on any page, X and YouTube included, enriched with their roles and company. The card shows who matched, so you know it is the right person before you write.

  • Extension: on the Chrome Web Store, which Brave, Arc and Opera install from too; Edge and Firefox list it once their stores approve it. On the web, the LinkedIn email finder does the same lookup from a profile's address.
  • Agents: the hosted MCP server at https://mcp.nameclick.co/mcp, registry name co.nameclick/nameclick.
  • API: described at api.nameclick.co/openapi.json.

The MCP server

ToolDoes
find_contactFinds who a person is and their email address, from a LinkedIn address, an email, a GitHub login, a full name with their company or its domain, or their name on a page. One lookup is spent only the first time an email address on record is shown for someone.
get_contactReopens a person you found before, free.
get_servicesThe lookup API, for agents that call it directly. Free, no key.

The find_email prompt gives clients a slash command. find_contact and get_contact take a key in the Authorization header, as Bearer <key>, from the extension's settings under "Use Nameclick in your agent".

json
{  "mcpServers": {    "nameclick": {      "type": "http",      "url": "https://mcp.nameclick.co/mcp",      "headers": { "Authorization": "Bearer <your Nameclick key>" }    }  }}

The skill teaches an agent to resolve the person first and to look up only the person the user asked about.

Privacy

Nameclick reads a profile's address, or a selected name and the text around it, only when you press. The privacy policy says what is kept, and anyone in it can ask to be removed.

Licence

Apache-2.0. See LICENSE.

Source: README.md at commit dbf4308

Tools

3

find_contact

Find an email address

Find who a person is and their email address, from a LinkedIn profile address, an email, a GitHub login, a full name with their company or its domain, or a name selected on a page with the text around it, a profile on X or a YouTube channel included. Resolve the person first: use the profile or employer the user gave you, never a guess. One lookup is spent only when Nameclick finds an email address on record for them, once per person for good; a personal address such as Gmail needs a paid plan, and the card says when one is held back; a miss, a record with no email or an ambiguous identity costs nothing. The record also carries their roles, location and links, and their company's size, funding and site. Look up the person the user asked about, never people in bulk.

Parametersnamepageemaildomaingithubcompanylinkedin

get_contact

Reopen a person you found

Reopen someone this account found before, by the person ID find_contact returned, their email or their LinkedIn address. Free. Answers not_found for anyone the account has not found.

Parametersemailpersonlinkedin

get_services

Nameclick's API and plans

The lookup API, its OpenAPI document and the plans, for agents that call the API directly. Needs no key.

Takes no parameters.

Version history

2
  1. v0.1.1LatestNov 5, 2026
  2. v0.1.0Nov 4, 2026

Score

100% 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 listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts