Skip to main content
Glama
anpekesen

namegender-mcp

by anpekesen
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to namegender-mcp

  • mcp-genderize

    pipeworx-io
    A
    license
    Not graded
    quality
    C
    maintenance
    Enables gender prediction from a first name using genderize.io data, optionally for a specific country, returning gender, probability, and sample size.
    1 npm
    MIT

Related Servers

  • sabit-mcp

    ruwadgroup
    A
    license
    Not graded
    quality
    B
    maintenance
    Enables AI agents to verify email addresses through a multi-signal probabilistic pipeline, returning confidence scores and honest statuses (safe/risky/invalid/unknown) with evidence.
    Apache 2.0

  • RandomUser MCP Server

    rycid
    A
    license
    C
    quality
    D
    maintenance
    Provides enhanced access to the randomuser.me API with advanced features like custom formatting, password generation, and weighted nationality distribution.
    2
    MIT

  • mcp-randomuser

    pipeworx-io
    A
    license
    Not graded
    quality
    C
    maintenance
    Wraps the randomuser.me API to generate random user profiles with names, contact info, and demographics, optionally filtered by gender and count.
    2 npm
    MIT

  • Email Finder API

    Br0ski777
    A
    license
    Not graded
    quality
    C
    maintenance
    Find professional email addresses from name + company domain. Tests 15+ patterns against MX records with confidence scoring, with pay-per-call via x402.
    MIT
Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A4.2/5.0

Scored across 6 tools

Disambiguation5/5

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.

Naming Consistency4/5

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.

Tool Count5/5

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.

Completeness5/5

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.

Maintenance

ActivityMaintained
ResponsivenessNo issues

Resources