Genderize Mcp

io.github.mrfentmenPublished by GitHub account mrfentmenv1.0.0Updated Oct 24, 2026

Estimate gender from a first name. No key required.

VerifiedSTDIODesktop onlyData & Analytics

Overview

AI-generated overview

Lets an assistant estimate the likely gender associated with a first name, with no API key required.

What you can do
This local MCP server exposes a name-to-gender estimation capability to an assistant. Based on the registry description, it takes a first name and returns an estimated gender, and it states that no key is required. No tool list or README is available, so the exact tool names, inputs, and output fields are not documented here.
When to use it
Useful when an assistant needs a quick, low-stakes guess at the gender commonly associated with a first name, for example when enriching or formatting name lists. It is not a source of verified personal information about any individual.
Requirements
Runs as a local process on the user's machine, installed from the npm package genderize-mcp over stdio. Node.js is needed to run an npm package. No authentication, environment variables, or headers are declared.
Before you install
Gender inferred from a first name is a statistical guess and can be wrong, culturally biased, or inapplicable to a given person; avoid using it for decisions about individuals. The description does not state whether names are sent to an external service, so treat submitted names as potentially leaving the machine. No credentials are requested.

Installation

In SourceWeft

  1. Open Genderize Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.0.0LatestSep 22, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.