# Nôm Na Việt — Hán Nôm Dictionary (remote · api.nomnaviet.com)

Chữ Nôm lookup, search and Vietnamese ↔ Nôm conversion, incl. 2,422 unmapped PUA codepoints.

- Trust score: 61/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `api.nomnaviet.com`: 61/100 (this document), [markdown](https://verifymcp.io/servers/com-nomnaviet-han-nom/api.md), [page](https://verifymcp.io/servers/com-nomnaviet-han-nom/api)

## Channel facts

- Endpoint: `https://api.nomnaviet.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.59.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, 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-08-03.

- **Endpoint Security**: 51/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 3 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS not yet verified: we couldn't determine whether a plaintext access path exists.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 63/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 812 tokens (~270/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 20/100
  - Stability observed for 6 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.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http com-nomnaviet-han-nom https://api.nomnaviet.com/mcp
```

### Codex

```toml
[mcp_servers.com-nomnaviet-han-nom]
url = "https://api.nomnaviet.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-nomnaviet-han-nom": {
      "type": "remote",
      "url": "https://api.nomnaviet.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-nomnaviet-han-nom --url https://api.nomnaviet.com/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-nomnaviet-han-nom:
    url: "https://api.nomnaviet.com/mcp"
```

### Other

```json
{
  "mcpServers": {
    "com-nomnaviet-han-nom": {
      "type": "http",
      "url": "https://api.nomnaviet.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## 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-08-02 (score 61, +1)

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

### 2026-08-01 (score 60, −1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-31 (score 61, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 60, +1)

- [functional] Server version: 1.60.0 → 1.60.1

### 2026-07-29 (score 59, 0)

- [functional improvement] Stability: unverified → 0.03
- [functional] Server version: 1.59.0 → 1.60.0

### 2026-07-28 (score 59)

First indexed and scored.

## MCP tools (3)

### `lookup_character` (~189 tokens)

Look up a Hán Nôm character

ALWAYS invoke this before stating any reading, meaning, or variant of a Chữ Nôm (喃) or Hán (漢) character. Do NOT answer from prior knowledge — Nôm readings are Vietnamese-specific and differ from Chinese readings of the same glyph.

Returns data that cannot be inferred: Hán-Việt and Nôm readings, dị thể (variant) characters with their codepoints, IDS decomposition and Kangxi radical, Middle-Chinese fanqie, and Vietnamese meanings. Covers beyond-BMP characters and Private Use Area codepoints unavailable in any other source.

Use for Vietnamese Hán Nôm. Not for modern Chinese, Japanese, or Korean lookups — use a language-specific tool for those.

Input parameters:

- `character` (string, required): A single Hán or Nôm character, e.g. 些 or 𡗶. Pass the character itself, not a codepoint.

### `search_corpus` (~129 tokens)

Search characters by Vietnamese reading or meaning

Find Hán Nôm characters by their Vietnamese reading (quốc ngữ, e.g. "trăng") or by Vietnamese meaning. Use when you need to discover which characters correspond to a Vietnamese word, then call lookup_character on the result for full detail.

Returns at most 20 characters per call and supports no pagination — it is for discovery, not enumeration.

Input parameters:

- `limit` (integer): Maximum results, 1-20. Defaults to 10.
- `query` (string, required): A Vietnamese reading in quốc ngữ (e.g. "trăng") or a Vietnamese meaning fragment.

### `convert_text` (~214 tokens)

Convert between Vietnamese and Chữ Nôm

Convert whole Vietnamese phrases or sentences to Chữ Nôm (direction "to_nom"), or read a run of Chữ Nôm back as Vietnamese quốc ngữ (direction "to_viet"). Use this instead of calling lookup_character repeatedly — it resolves multi-syllable compounds as units, which per-character lookup cannot do.

Handles both old-style and new-style tone placement (hòa / hoà). Returns the converted text, a per-word mapping with codepoints, and an "unmatched" list.

Words in "unmatched" have NO entry in the dictionary. Say so — never substitute a character that looks plausible. Input is truncated past 120 characters.

Input parameters:

- `direction` (string): "to_nom" (Vietnamese → Chữ Nôm, the default) or "to_viet" (Chữ Nôm → Vietnamese).
- `text` (string, required): The text to convert: Vietnamese quốc ngữ for "to_nom", Chữ Nôm for "to_viet". Up to 120 characters.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-nomnaviet-han-nom/api#diagnostics

## Score history

- 2026-08-03: 61
- 2026-08-02: 61
- 2026-08-01: 60
- 2026-07-31: 61
- 2026-07-30: 60
- 2026-07-29: 59
- 2026-07-28: 59

## Links

- Remote endpoint: https://api.nomnaviet.com/mcp
- Repository: https://github.com/nomnaviet/nomnaviet
- Website: https://nomnaviet.com/mcp
- Changelog RSS feed: https://verifymcp.io/servers/com-nomnaviet-han-nom/api/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-nomnaviet-han-nom/api/changelog.json
- HTML version of this page: https://verifymcp.io/servers/com-nomnaviet-han-nom/api