Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

NameGender

NPM · NAMEGENDER-MCP · SCANNED SEP 27

Gender from names, emails and usernames, with probability, sample size and source on every answer.

Available components

npm · namegender-mcp 49
0 this week 49 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security98
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 31 of 95 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to anpekesen/namegender-mcp). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 10 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability0
  • Schema quality not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we have no schema to assess.Unverified
Stability & Change Management0
  • Stability not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we have no schema to compare.Unverified
Tool Coverage0
  • Tool coverage not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we have no tool definitions to assess.Unverified
Tool Safety0
  • Tool safety not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we have no tool text to scan.Unverified
Capabilities0
  • Protocol version not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we never saw its MCP handshake.Unverified

Unverified: 5 categories

Categories scored 0 because our sandbox has not given us the schema these checks need to read. That is a gap on our side rather than a finding about the package, and we only credit what we can confirm, so the score stands at 0 until the capture succeeds. We are working through the fleet, so this normally clears without any action from you. How we score packages →

Install

How do I install the NameGender MCP server?

NameGender runs locally as an npm package, launched with npx -y namegender-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · namegender-mcp

# add to Claude Code
claude mcp add anpekesen-namegender -- npx -y namegender-mcp
// .cursor/mcp.json
{
  "mcpServers": {
    "anpekesen-namegender": {
      "command": "npx",
      "args": [
        "-y",
        "namegender-mcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "anpekesen-namegender": {
      "command": "npx",
      "args": [
        "-y",
        "namegender-mcp"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add anpekesen-namegender -- npx -y namegender-mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "anpekesen-namegender": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "namegender-mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add anpekesen-namegender --command npx --arg -y --arg namegender-mcp
# ~/.hermes/config.yaml
mcp_servers:
  anpekesen-namegender:
    command: "npx"
    args: ["-y", "namegender-mcp"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "anpekesen-namegender": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "namegender-mcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add anpekesen-namegender -t stdio -c npx -a -y namegender-mcp
// mcp.json
{
  "mcpServers": {
    "anpekesen-namegender": {
      "command": "npx",
      "args": [
        "-y",
        "namegender-mcp"
      ]
    }
  }
}
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 16 Sept 26 49

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 27 Sept 2026 · Analysed npm/namegender-mcp@0.1.2

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo anpekesen/namegender-mcp
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/anpekesen/namegender-mcp/.github/workflows/release.yml@refs/tags/v0.1.2
Rekor log index 2864279692
Predicate type https://slsa.dev/provenance/v1
Subject digest sha512:1f56db3e5c460e0203144178bee5e999f1653871161a030989327d8f0f1514b7fea67c75e008619ae862d2776639eb9477e7e4ea0109eb63886eb5084

Background: How many MCP packages publish verified provenance →

Dependencies 95 packages
Packages resolved 95
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tools for package channels are captured by running the package in an isolated sandbox. The most recent sandbox run could not capture a tool list from this package.

Common questions

What is the NameGender MCP server?

NameGender is an MCP server listed in the public MCP registry as io.github.anpekesen/namegender. Gender from names, emails and usernames, with probability, sample size and source on every answer. This page covers its npm package (namegender-mcp).

Is the NameGender MCP server safe to use?

NameGender scores 49 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 27 September 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

Is the NameGender MCP server still maintained?

NameGender is still listed as active in the MCP registry. We last reached this channel on 27 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the NameGender MCP server under?

NameGender declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.