namegender-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NAMEGENDER_API_KEY | Yes | API key for the namegender.com service. Required. | |
| NAMEGENDER_BASE_URL | No | Base URL for the namegender API. | https://namegender.com/api/v1 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| gender_from_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. |
| gender_from_emailA | 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. |
| gender_from_usernameA | Extracts a first name from a username or social media handle and predicts its gender. |
| gender_bulkA | 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. |
| name_countriesA | 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. |
| account_statusA | 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. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.