# io.github.mrfentmen/namsor-mcp (npm · namsor-mcp)

MCP server for NamSor: infer gender, country MCP: real tools for real work.

- Trust score: 71/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- npm · `namsor-mcp`: 71/100 (this document), [markdown](https://verifymcp.io/servers/mrfentmen-namsor-mcp/namsor-mcp.md), [page](https://verifymcp.io/servers/mrfentmen-namsor-mcp/namsor-mcp)

## Channel facts

- Registry: `npm`
- Package: `namsor-mcp`
- Version: `1.0.0`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Supply Chain Security**: 81/100
  - No malware found by supply-chain analysis.
  - CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available.
  - No install/post-install scripts declared.
  - 31 of 93 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 19 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 75/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 907 tokens (~53/item across 17 items; 17 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 43/100
  - Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 17 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 17 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the io.github.mrfentmen/namsor-mcp server?

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

### Claude

```bash
claude mcp add mrfentmen-namsor-mcp -- npx -y namsor-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "mrfentmen-namsor-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "namsor-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "mrfentmen-namsor-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "namsor-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add mrfentmen-namsor-mcp -- npx -y namsor-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "mrfentmen-namsor-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "namsor-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add mrfentmen-namsor-mcp --command npx --arg -y --arg namsor-mcp
```

### Hermes

```yaml
mcp_servers:
  mrfentmen-namsor-mcp:
    command: "npx"
    args: ["-y", "namsor-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "mrfentmen-namsor-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "namsor-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add mrfentmen-namsor-mcp -t stdio -c npx -a -y namsor-mcp
```

### Other

```json
{
  "mcpServers": {
    "mrfentmen-namsor-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "namsor-mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-21 (score 71, +1)

No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-19 (score 70, +1)

No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-16 (score 69, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-14 (score 68, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-13 (score 67, +2)

- [functional improvement] Stability: unverified → 0.17

### 2026-11-08 (score 65)

First indexed and scored.

## MCP tools (17)

### `get_api_status` (~26 tokens)

Check whether each NamSor classifier is currently up, plus its version and any downtime.

### `get_api_usage` (~27 tokens)

Show how many NamSor units your API key has used this period and how many remain.

### `get_api_key_info` (~24 tokens)

Show which NamSor plan and quota the configured API key belongs to.

### `list_api_services` (~23 tokens)

List the NamSor classification services available and the unit cost of each.

### `infer_gender` (~59 tokens)

Infer the likely gender of a first name, or of a first + last name pair.

Input parameters:

- `firstName` (string, required): First / given name, e.g. 'John'
- `lastName` (string): Last / family name — improves accuracy

### `infer_gender_full` (~53 tokens)

Infer the likely gender of a full name written as one string, e.g. 'John H. Smith'.

Input parameters:

- `fullName` (string, required): Full name in one string, e.g. 'John H. Smith'

### `infer_gender_full_geo` (~72 tokens)

Infer the likely gender of a full name using the cultural context of an ISO2 country.

Input parameters:

- `countryIso2` (string, required): ISO2 country giving the cultural context, e.g. 'US'
- `fullName` (string, required): Full name in one string, e.g. 'John H. Smith'

### `infer_gender_batch` (~48 tokens)

Infer the likely gender for up to 100 names in a single NamSor request.

Input parameters:

- `personalNames` (array, required): Names to classify in one request (NamSor allows up to 100)

### `infer_country` (~48 tokens)

Infer the likely country of residence or origin of a full name.

Input parameters:

- `personalNameFull` (string, required): Full name in one string, e.g. 'John Smith' or 'Wang Wei'

### `infer_country_batch` (~46 tokens)

Infer the likely country for up to 100 full names in one request.

Input parameters:

- `personalNames` (array, required): Names to classify in one request (NamSor allows up to 100)

### `infer_diaspora` (~73 tokens)

Infer the likely ethnicity/diaspora of a name, given the country the person lives in.

Input parameters:

- `countryIso2` (string, required): ISO2 country of residence, e.g. 'US'
- `firstName` (string, required): First / given name
- `lastName` (string, required): Last / family name

### `infer_diaspora_batch` (~50 tokens)

Infer the likely ethnicity/diaspora for up to 100 names in one request.

Input parameters:

- `personalNames` (array, required): Names to classify in one request (NamSor allows up to 100)

### `infer_us_race_ethnicity` (~92 tokens)

Infer US race/ethnicity probabilities from a name plus 5-digit ZIP code.

Input parameters:

- `countryIso2` (string, required): ISO2 country, normally 'US'
- `firstNameLastName` (string, required): First and last name separated by a space, e.g. 'John Smith'
- `zip5Code` (string, required): 5-digit US ZIP code, e.g. '90210'

### `infer_us_race_ethnicity_batch` (~51 tokens)

Infer US race/ethnicity for up to 100 names in one request.

Input parameters:

- `personalNames` (array, required): Names to classify in one request (NamSor allows up to 100)

### `chinese_name_candidates` (~65 tokens)

List Chinese characters that match a romanised (pinyin) surname and given name.

Input parameters:

- `chineseGivenNameLatin` (string, required): Romanised given name, e.g. 'Wei'
- `chineseSurnameLatin` (string, required): Romanised surname, e.g. 'Wang'

### `match_chinese_name` (~84 tokens)

Score how well a Chinese character name matches a romanised surname + given name.

Input parameters:

- `chineseGivenNameLatin` (string, required): Romanised given name, e.g. 'Wei'
- `chineseName` (string, required): Chinese name in characters, e.g. '王伟'
- `chineseSurnameLatin` (string, required): Romanised surname, e.g. 'Wang'

### `japanese_name_kanji_candidates` (~66 tokens)

List kanji candidates for a romanised Japanese surname and given name.

Input parameters:

- `japaneseGivenNameLatin` (string, required): Romanised given name, e.g. 'Akira'
- `japaneseSurnameLatin` (string, required): Romanised surname, e.g. 'Sato'

## Diagnostics

Captured diagnostic sections: Provenance, Vulnerabilities, Dependencies. The full working is on the page: https://verifymcp.io/servers/mrfentmen-namsor-mcp/namsor-mcp#diagnostics

## Score history

- 2026-11-21: 71
- 2026-11-20: 70
- 2026-11-19: 70
- 2026-11-18: 69
- 2026-11-17: 69
- 2026-11-16: 69
- 2026-11-15: 68
- 2026-11-14: 68
- 2026-11-13: 67
- 2026-11-12: 65
- 2026-11-11: 65
- 2026-11-10: 65
- 2026-11-09: 65
- 2026-11-08: 65

## Common questions

### What is the io.github.mrfentmen/namsor-mcp server?

io.github.mrfentmen/namsor-mcp is listed in the public MCP registry as io.github.mrfentmen/namsor-mcp. MCP server for NamSor: infer gender, country MCP: real tools for real work. This page covers its npm package (namsor-mcp).

### Is the io.github.mrfentmen/namsor-mcp server safe to use?

io.github.mrfentmen/namsor-mcp scores 71 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 21 November 2026. It declares no install or post-install scripts. 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.

### What tools does the io.github.mrfentmen/namsor-mcp server expose?

io.github.mrfentmen/namsor-mcp exposes 17 tools: get_api_status, get_api_usage, get_api_key_info, list_api_services, infer_gender, and 12 more. Their descriptions and schemas cost roughly 907 tokens of context every time the server is loaded.

### Is the io.github.mrfentmen/namsor-mcp server still maintained?

io.github.mrfentmen/namsor-mcp is still listed as active in the MCP registry. We last reached this channel on 21 November 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 io.github.mrfentmen/namsor-mcp server under?

io.github.mrfentmen/namsor-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

### What did VerifyMCP test on the io.github.mrfentmen/namsor-mcp server?

VerifyMCP ran 16 checks on io.github.mrfentmen/namsor-mcp, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- npm package: https://www.npmjs.com/package/namsor-mcp
- Socket report: https://socket.dev/npm/package/namsor-mcp
- Repository: https://github.com/mrfentmen/awesome-servers
- Changelog RSS feed: https://verifymcp.io/servers/mrfentmen-namsor-mcp/namsor-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/mrfentmen-namsor-mcp/namsor-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/mrfentmen-namsor-mcp/namsor-mcp.json
- HTML version of this page: https://verifymcp.io/servers/mrfentmen-namsor-mcp/namsor-mcp
