# Nameclick: Email Finder & Lookup Tool (remote · mcp.nameclick.co)

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

- Trust score: 37/100 (low)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `mcp.nameclick.co`: 37/100 (this document), [markdown](https://verifymcp.io/servers/co-nameclick-nameclick/mcp.md), [page](https://verifymcp.io/servers/co-nameclick-nameclick/mcp)

## Channel facts

- Endpoint: `https://mcp.nameclick.co/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `0.1.2`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Endpoint Security**: 92/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - The endpoint enforces authorisation, advertised via RFC 9728 protected-resource metadata.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
  - The authorisation server supports Client ID Metadata Documents, the current MCP client-registration mechanism.
- **Transport & Reachability**: 0/100
  - Transport blocked by authentication: the endpoint requires auth we don't have to verify streamable-http.
- **Schema Quality & AI Usability**: 0/100
  - Schema blocked by authentication: the endpoint requires auth we don't have to read it.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 0/100
  - Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.
- **Tool Safety**: 0/100
  - Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.
- **Capabilities**: 0/100
  - Capabilities blocked by authentication: the endpoint requires auth we don't have to read them.

**Unverified: 6 categories.** Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

## Install

### How do I install the Nameclick: Email Finder & Lookup Tool MCP server?

Nameclick: Email Finder & Lookup Tool is a hosted endpoint at https://mcp.nameclick.co/mcp, 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.

### Claude

```bash
claude mcp add --transport http co-nameclick-nameclick 'https://mcp.nameclick.co/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "co-nameclick-nameclick": {
      "url": "https://mcp.nameclick.co/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "co-nameclick-nameclick": {
      "type": "http",
      "url": "https://mcp.nameclick.co/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.co-nameclick-nameclick]
url = "https://mcp.nameclick.co/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "co-nameclick-nameclick": {
      "type": "remote",
      "url": "https://mcp.nameclick.co/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add co-nameclick-nameclick --url 'https://mcp.nameclick.co/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  co-nameclick-nameclick:
    url: "https://mcp.nameclick.co/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "co-nameclick-nameclick": {
      "Transport": "http",
      "Url": "https://mcp.nameclick.co/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add co-nameclick-nameclick -t streamable-http -u 'https://mcp.nameclick.co/mcp'
```

### Other

```json
{
  "mcpServers": {
    "co-nameclick-nameclick": {
      "type": "http",
      "url": "https://mcp.nameclick.co/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-09 (score 37, −36)

- [security regression] Endpoint reachability: reachable → behind authorisation
- [security regression] Stability: 0.13 → unverified
- [security regression] Tool safety: pass → unverified
- [security regression] Transport: pass → unverified
- [security improvement] Authorization: partial → pass
- [security] First check of Authorization: pass
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional regression] Schema quality: 100 → unverified

### 2026-11-08 (score 73, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-07 (score 72, 0)

- [cosmetic] “find_contact” reworded the description of “name”

### 2026-11-06 (score 72, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-11-05 (score 71, 0)

- [security] Tool “find_contact” rewrote its description, which is the text the model reads
- [functional improvement] Stability: unverified → 0.03
- [functional] Server version: 0.1.0 → 0.1.1
- [cosmetic] “find_contact” reworded the description of “email”

### 2026-11-04 (score 71)

First indexed and scored.

## MCP tools (3)

### `find_contact` (~340 tokens)

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.

Input parameters:

- `company` (string): Where they work, by name.
- `domain` (string): A company's domain, such as anthropic.com.
- `email` (string): An email address, to find who holds it. From a key or the web finder, a personal address such as Gmail or Outlook needs a paid plan.
- `github` (string): A GitHub login; Nameclick reads the public profile and finds who it is.
- `linkedin` (string): A LinkedIn profile's address, such as https://www.linkedin.com/in/someone.
- `name` (string): The person's full name, with company or domain. In the extension, a name alone lists who holds it.
- `page` (object): A name selected on a page, with the text around it.

### `get_contact` (~97 tokens)

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.

Input parameters:

- `email` (string)
- `linkedin` (string): A LinkedIn profile's address, such as https://www.linkedin.com/in/someone.
- `person` (string): A person in Nameclick's store, as find_contact returns it.

### `get_services` (~32 tokens)

Nameclick's API and plans

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

Output parameters:

- `api` (string)
- `keys` (string)
- `lookup` (string)
- `mcp` (string)
- `openapi` (string)
- `plans` (array)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/co-nameclick-nameclick/mcp#diagnostics

## Score history

- 2026-11-21: 37
- 2026-11-20: 37
- 2026-11-19: 37
- 2026-11-18: 37
- 2026-11-17: 37
- 2026-11-16: 37
- 2026-11-15: 37
- 2026-11-14: 37
- 2026-11-13: 37
- 2026-11-12: 37
- 2026-11-11: 37
- 2026-11-10: 37
- 2026-11-09: 37
- 2026-11-08: 73
- 2026-11-07: 72
- 2026-11-06: 72
- 2026-11-05: 71
- 2026-11-04: 71

## Common questions

### What is the Nameclick: Email Finder & Lookup Tool MCP server?

Nameclick: Email Finder & Lookup Tool is an MCP server listed in the public MCP registry as co.nameclick/nameclick. Email finder and enrichment: LinkedIn, GitHub, or a person's name on any page, X and YouTube too. This page covers its hosted endpoint (https://mcp.nameclick.co/mcp).

### Is the Nameclick: Email Finder & Lookup Tool MCP server safe to use?

Nameclick: Email Finder & Lookup Tool scores 37 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 Nameclick: Email Finder & Lookup Tool MCP server expose?

Nameclick: Email Finder & Lookup Tool exposes 3 tools: find_contact, get_contact, get_services. Their descriptions and schemas cost roughly 469 tokens of context every time the server is loaded.

### Does the Nameclick: Email Finder & Lookup Tool MCP server require authentication?

Yes. Nameclick: Email Finder & Lookup Tool asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

### Is the Nameclick: Email Finder & Lookup Tool MCP server still maintained?

Nameclick: Email Finder & Lookup Tool is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the Nameclick: Email Finder & Lookup Tool MCP server?

VerifyMCP ran 5 checks on Nameclick: Email Finder & Lookup Tool, covering TLS certificate, Authorization, HTTPS, HSTS header and 1 more. 6 items could not be completed, a gap on our side rather than a finding about Nameclick: Email Finder & Lookup Tool: Transport, Schema quality, Stability, Tool coverage and 2 more. 6 categories score 0 for that reason, because we only credit what we can confirm. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://mcp.nameclick.co/mcp
- Repository: https://github.com/auscaster/nameclick
- Website: https://sourcey.com/nameclick
- Changelog RSS feed: https://verifymcp.io/servers/co-nameclick-nameclick/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/co-nameclick-nameclick/mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/co-nameclick-nameclick/mcp.json
- HTML version of this page: https://verifymcp.io/servers/co-nameclick-nameclick/mcp
