MCP Servers · Communication
anpekesen/namegender-mcp
Model Context Protocol server for the NameGender API: gender from names, emails and usernames, with probability, sample size and source on every answer.
Our verdict
We have not reviewed anpekesen/namegender-mcp yet
No one at Enterprise DNA has checked this listing against its sources. The description comes from public listings gathered automatically. Any fact below shows where it came from and when it was last checked.
From the listing
About anpekesen/namegender-mcp
Model Context Protocol server that wraps the NameGender API to infer gender from names, emails, and usernames. Every result includes a probability score, sample size, and source. Written in JavaScript for MCP-compatible clients.
Best for
Developers who need quick name-based gender guesses inside MCP-compatible AI tools.
Use cases
- Enrich CRM records with gender predictions
- Resolve gender from user emails in chatbot flows
- Add gender context to lead scoring pipelines
Notes
0 stars on GitHub. Last updated 2026-09-21. Licensed MIT.
Pros
- Works across names, emails, and usernames
- Provides probability, sample size, and source for transparency
- Simple MCP integration for JavaScript projects
Cons
- No stars or community adoption yet
- Depends on an external API, adding a third-party call
- Name-based inference is not a reliable measure of gender identity
Key facts
What we have checked
Not checked yet. Dated facts such as prices, releases and repository activity appear here once we have confirmed them from a source.
How to use
How to set it up
As the listing publishes it. We have not run this install.
Install
claude mcp add namegender -e NAMEGENDER_API_KEY=ng_live_... -- npx -y namegender-mcpTools exposed
gender_from_namegender_from_emailgender_from_usernamegender_bulkname_countriesaccount_statusNAMEGENDER_API_KEYNAMEGENDER_BASE_URL
Clients the listing names (not checked here)
Claude Desktop, Claude Code, Cursor
Example client config
{
"mcpServers": {
"namegender": {
"command": "npx",
"args": [
"-y",
"namegender-mcp"
],
"env": {
"NAMEGENDER_API_KEY": "ng_live_..."
}
}
}
}Install
Add anpekesen/namegender-mcp to your client
Our lab has not run this server yet. "Config checked" on a client means the recipe matches that client's documented config format; it does not mean we ran it.
Claude Code
Config checkedRun in your terminal (runs on your computer)
claude mcp add --env NAMEGENDER_API_KEY=YOUR_NAMEGENDER_API_KEY --transport stdio anpekesen-namegender-mcp -- npx -y namegender-mcp@0.3.0Needs NAMEGENDER_API_KEY: replace each YOUR_ value with your own.
Claude Desktop
Config checkedAdd to claude_desktop_config.json (runs on your computer)
{
"mcpServers": {
"anpekesen-namegender-mcp": {
"command": "npx",
"args": [
"-y",
"namegender-mcp@0.3.0"
],
"env": {
"NAMEGENDER_API_KEY": "YOUR_NAMEGENDER_API_KEY"
}
}
}
}Needs NAMEGENDER_API_KEY: replace each YOUR_ value with your own.
Cursor
Config checkedAdd to .cursor/mcp.json (runs on your computer)
{
"mcpServers": {
"anpekesen-namegender-mcp": {
"command": "npx",
"args": [
"-y",
"namegender-mcp@0.3.0"
],
"env": {
"NAMEGENDER_API_KEY": "YOUR_NAMEGENDER_API_KEY"
}
}
}
}Needs NAMEGENDER_API_KEY: replace each YOUR_ value with your own.
VS Code
Config checkedAdd to .vscode/mcp.json (runs on your computer)
{
"inputs": [
{
"type": "promptString",
"id": "namegender-api-key",
"description": "API key from the namegender.com dashboard",
"password": true
}
],
"servers": {
"anpekesen-namegender-mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"namegender-mcp@0.3.0"
],
"env": {
"NAMEGENDER_API_KEY": "${input:namegender-api-key}"
}
}
}
}Needs NAMEGENDER_API_KEY: replace each YOUR_ value with your own.
Codex
Config checkedAdd to ~/.codex/config.toml (runs on your computer)
[mcp_servers.anpekesen-namegender-mcp]
command = "npx"
args = ["-y", "namegender-mcp@0.3.0"]
env_vars = ["NAMEGENDER_API_KEY"]Needs NAMEGENDER_API_KEY: replace each YOUR_ value with your own.
- ChatGPT: ChatGPT connects only to remote servers that need no API key.
Recipes come from the server's entry in the official MCP registry. Check the package name before you run it, and keep keys out of shared files.
Works with
What anpekesen/namegender-mcp connects to
5 clients, each with how we know and when we checked.
| Works with | Type | How we know | Checked |
|---|---|---|---|
| Claude Code | Client | Install recipe matches the client's documented formatRuns locally, version 0.3.0Config checked | Claude Code docs |
| Claude Desktop | Client | Install recipe matches the client's documented formatRuns locally, version 0.3.0Config checked | Claude Desktop docs |
| Cursor | Client | Install recipe matches the client's documented formatRuns locally, version 0.3.0Config checked | Cursor docs |
| VS Code | Client | Install recipe matches the client's documented formatRuns locally, version 0.3.0Config checked | VS Code docs |
| Codex | Client | Install recipe matches the client's documented formatRuns locally, version 0.3.0Config checked | Codex docs |
Sources
Where this comes from
No sources recorded yet. Each source we check is listed here with the date we checked it.
A source shows what was published when we checked it. It does not certify security, performance or a working installation. Read our method.
Changelog
What changed
No changes recorded yet. Releases, price changes and deprecations appear here, with their dates, once we track them for this record.
Get the free Developer’s Field Guide
A 27-page field guide to the AI coding workflow with Claude. Claude Code, MCP servers, the prompt patterns that work, and what to delegate. Free.
Enter your work email. We send it straight over, plus a few short notes worth knowing. Unsubscribe any time.