Nameclick: Email Finder & Enrichment

co.nameclick/nameclicknameclick.costreamable-httpv0.1.0Scanned 4 hours ago

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

3 tools: 2 change things and 1 only read.

Reads private data · 3
Reads text others write · 2
Can send data out · 0
2 findings

Anlyon alternative

2 of these tools change something. Run those as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

3 tools

Changes things 2Creates or changes something that can be changed back.Claude Code: ask

find_contactFind 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 …Reads private dataReads text others write1 finding
Why it is in this group
- The name "find_contact" says "find": a word for reading.
- The server marks it as not read-only (readOnlyHint: false).
What it can reach
- private-dataThe name "find_contact" says "find" and "contact": it reads contacts.
- private-dataThe description's first sentence says "find" and "email": it reads mail.
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
- untrusted-inputThe description's first sentence says "find" and "email": it reads inbound email, which other people can write.
Findings
- Warn
  The server marks "find_contact" as not read-only (readOnlyHint: false), and its words say it reads.
  Matched text
  annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The name "find_contact" says "find": a word for reading.
  What this check looks for
Description, as the server wrote it
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; an address they publish themselves, 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.
Annotations the server declares
- title: Find an email address
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
get_contactReopen someone this account found before, by the person ID find_contact returned, their email or their LinkedIn address.Reads private dataReads text others write1 finding
Why it is in this group
- The name "get_contact" says "get": a word for reading.
- The description's first verb is "reopen": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- private-dataThe name "get_contact" says "get" and "contact": it reads contacts.
- private-dataThe description's first sentence says "contact": it reads contacts.
- untrusted-inputThe description's first sentence says "reopen" and "email": it reads inbound email, which other people can write.
Findings
- Warn
  The server marks "get_contact" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
  Matched text
  annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "get_contact" says "get": a word for reading.
  What this check looks for
Description, as the server wrote it
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.
Annotations the server declares
- title: Reopen a person you found
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false

Only reads 1Looks things up and changes nothing.Show 1 read-only tool

get_servicesThe lookup API, its OpenAPI document and the plans, for agents that call the API directly.Reads private dataNo findings
Why it is in this group
- The name "get_services" says "get": a word for reading.
What it can reach
- private-dataThe description's first sentence says "lookup" and "document": it reads documents.
Description, as the server wrote it
The lookup API, its OpenAPI document and the plans, for agents that call the API directly. Needs no key.
Annotations the server declares
- title: Nameclick's API and plans
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged outbound.

Reads private data3: Reads files, mail, messages, databases, secrets, calendars or repositories.; find_contact
get_contact
get_services
Reads text others write2: Brings in text someone else can write: web pages, inbound email, messages, issues and comments.; find_contact
get_contact
Can send data out0: Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Findings

Matches of fixed checks, with the text they matched.

2 warn

Warnfind_contact
The server marks "find_contact" as not read-only (readOnlyHint: false), and its words say it reads.
Matched text
annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The name "find_contact" says "find": a word for reading.
What this check looks for
Warnget_contact
The server marks "get_contact" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
Matched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "get_contact" says "get": a word for reading.
What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

All changes to this server

Install

Pinned to version 0.1.0. Values in angle brackets are yours to fill in.

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

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

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json

{
  "permissions": {
    "allow": [
      "mcp__nameclick__get_services"
    ],
    "ask": [
      "mcp__nameclick__find_contact",
      "mcp__nameclick__get_contact"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as nameclick. Review it before you use it.

Capability tags behind 3 rules

mcp__nameclick__find_contact private-data, untrusted-input
mcp__nameclick__get_contact private-data, untrusted-input
mcp__nameclick__get_services private-data

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://anlyon.dev/api/v1/servers/co.nameclick/nameclick/verify?hash=fcbbfe119080a47b5af004cd3d7172c308144999d4eb55fa39693fa39013241f" | jq -e '.changed == false'

Pinned hash fcbbfe119080, from Nov 4, 2026, 22:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://anlyon.dev/servers/co.nameclick/nameclick/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

[![anlyon.dev](https://anlyon.dev/badge/co.nameclick/nameclick.svg)](https://anlyon.dev/servers/co.nameclick/nameclick)

Source: MCP Registry · repository. Synced Nov 4, 2026, 22:17 UTC.