namegender-mcp
This server predicts gender from names, email addresses, and usernames, with evidence and country weighting.
gender_from_name: Predict gender from a first or full name, with probability, sample size, and match source; returns "unknown" when unsure.
gender_from_email: Extract a first name from an email's local part and predict its gender; handles role addresses like info@.
gender_from_username: Extract a first name from a username/handle and predict its gender.
gender_bulk: Resolve up to 100 names/emails/usernames in one request, with a match-rate summary.
name_countries: List countries where a name is recorded (not origin/ethnicity), with ranked counted countries and an unranked attested list.
account_status: Check remaining credits, daily free quota, and data version.
All gender tools accept an optional two-letter country code to weight results by that country's data.
Errors return isError with actionable messages and request IDs, without breaking the session.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@namegender-mcp What's the likely gender of the name Riley in the US?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
NameGender MCP server
Turns names, email addresses and usernames into a gender — with the evidence next to every answer: the probability, the sample size, the source and the name it matched.
Works in any client that speaks the Model Context Protocol: Claude Desktop, Claude Code, Cursor and others.
Setup
Get an API key from the namegender.com dashboard. Sign-up needs no card and comes with free credits every day.
Claude Desktop / Claude Code configuration:
{
"mcpServers": {
"namegender": {
"command": "npx",
"args": ["-y", "namegender-mcp"],
"env": { "NAMEGENDER_API_KEY": "ng_live_..." }
}
}
}Claude Code from the command line:
claude mcp add namegender -e NAMEGENDER_API_KEY=ng_live_... -- npx -y namegender-mcpRelated MCP server: Email Social Media Checker
Tools
Tool | What it does |
| Gender from a first or full name |
| Extracts a name from the local part of an email address |
| Extracts a name from a username or handle |
| Up to 100 values in one request, with a match-rate summary |
| Countries a name is recorded in — not a claim about origin |
| Remaining credits, daily free quota, data version |
The gender tools take an optional two-letter country code. The same name
can have a different gender from one country to the next; with a code, the
answer is weighted by that country's data.
What an answer looks like
Ayşe: female · probability 99% · sample 12,345 · source ssa · country TRAn answer from a source without counts says so:
Kamon: male · probability 95% · no sample (unverified) · source wgndThe distinction is deliberate. A 95% backed by counted people and a 95% backed by nothing are not the same thing and should not look the same.
Countries are not origin
name_countries keeps two lists apart. Counted birth registrations are
published for only seven countries (US, UK, France, Canada, Spain, Ireland,
Norway), so the ranked shares compare those seven only. Every other country
where the name is recorded appears in a separate, unranked list. Reading the
ranking as "where the name comes from" is wrong: Mehmet ranks first in
France there, and Turkey is not in the ranking at all.
Errors
Errors do not break the session. The tool returns isError and says what to
do — where to top up when credits run out, which variable to check when the
key is invalid — and includes the request ID so support can trace it.
Environment variables
Variable | Default |
| (required) |
|
|
Development
npm install
npm testMIT licensed.
Releasing
npm version patch # also updates server.json
git push --follow-tagsThe v* tag runs .github/workflows/release.yml: tests, then npm (trusted
publishing, no token), then the MCP registry (GitHub OIDC). Re-running the
workflow skips whatever is already published.
Available Tools
6 toolsaccount_statusAccount and remaining creditsA
Returns remaining credits, the daily free quota and the data version. When credits run out the other tools fail with 402; call this to find out why.
Inputs: no named parameters.
gender_bulkMany names at onceA
Resolves up to 100 values in one request and returns a summary with the match rate. Use this for more than one name: doing the same work one call at a time is slower and wasteful.
Inputs: names (required), type, country.
gender_from_emailGender from an email addressA
Extracts a first name from the local part of an email address and predicts its gender. Returns "unknown" when no name can be extracted — role addresses such as info@ or admin@ included.
Inputs: email (required), country.
gender_from_nameGender from a nameA
Predicts gender from a person's name. The answer carries more than the gender: the probability, how many people the sample is based on and how the name was matched. Names it cannot be sure about return "unknown" instead of a guess.
Inputs: name (required), country.
gender_from_usernameGender from a usernameA
Extracts a first name from a username or social media handle and predicts its gender.
Inputs: username (required), country.
name_countriesCountries a name appears inA
Returns the countries where a name is recorded. WARNING: this is NOT a claim about origin or ethnicity. Counted birth registrations are published for only seven countries (US, UK, France, Canada, Spain, Ireland, Norway), so the ranking compares those countries only; countries that publish no counts, such as Turkey or Japan, appear in the attested list, not in the ranking.
Inputs: name (required), limit.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 6 tools
Each tool targets a distinct input source or function: name, email, username, bulk processing, country lookup, and account status. No overlap in purpose, and the bulk tool is clearly differentiated as a batch alternative.
The gender_* tools share a consistent prefix and verb_from_source pattern (gender_from_name, gender_from_email, gender_from_username, gender_bulk). name_countries and account_status deviate from the verb_noun pattern but still use snake_case and are descriptive, so the naming is mostly consistent with minor exceptions.
Six tools is well-scoped for a gender prediction service: three single-input methods, a bulk method, a supplementary lookup, and a status/meta tool. Each tool serves a clear purpose without redundancy.
The surface covers all core operations: single prediction for name/email/username, bulk resolution, country information, and account status. There are no obvious missing operations for the domain, and the bulk tool addresses efficiency needs.
Related MCP Connectors
Detect gender and country of origin from first names, full names and email addresses.
Genderize MCP — gender prediction from first name (genderize.io, free, no auth)
Harness the power of names with our Name Demographics MCP. Using Agify, Genderize, and Nationalize
Keyless email checks: disposable, role, and free-provider detection, MX, and typo suggestions.
Related MCP Servers
- AlicenseCqualityDmaintenanceProvides enhanced access to the randomuser.me API with advanced features like custom formatting, password generation, and weighted nationality distribution.2MIT
- AlicenseCqualityDmaintenanceEnables checking email addresses through the Email Social Media Checker API to verify and validate email information.1MIT
- AlicenseNot gradedqualityCmaintenanceWraps the randomuser.me API to generate random user profiles with names, contact info, and demographics, optionally filtered by gender and count.278 npmMIT
- AlicenseNot gradedqualityCmaintenancePredicts nationality from a first name using the nationalize.io API. Requires no authentication.91 npmMIT