Skip to content

Nôm Na Việt — Hán Nôm Dictionary MCP server

com.nomnaviet/han-nomnomnaviet.comstreamable-httpv1.68.0Scanned

Vietnamese Chữ Nôm & Hán: lookup, search, conversion, and original Đại Nam Quấc âm tự vị entries.

4 tools: 1 change things and 3 only read.

Tools: 0 delete, 0 irreversible, 1 write, 3 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 0
  • 2 findings

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here changes things. Govern it.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Nôm Na Việt — Hán Nôm Dictionary MCP server can do

The Nôm Na Việt — Hán Nôm Dictionary MCP server is published by nomnaviet.com, a domain the MCP Registry verified. It has 4 tools. It can create or change data (1 tool: convert_text), but cannot delete data. 3 tools only read.

None of its tools reads private data, brings in text other people write, or sends data out.

The fixed checks matched 2 findings (long-description and annotation-conflict). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 10, 2026, version 1.68.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

4 tools

Changes things 1Claude Code: ask
  • convert_textConvert 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").1 finding

    Why it is in this group

    • The name "convert_text" says "convert": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "convert_text" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true}; The name "convert_text" says "convert": a word for a change.

      What this check looks for
    Description, as the server wrote it
    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 500 characters.

    Annotations the server declares

    • title: Convert between Vietnamese and Chữ Nôm
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
Only reads 3Show 3 read-only tools
  • lookup_characterALWAYS invoke this before stating any reading, meaning, or variant of a Chữ Nôm (喃) or Hán (漢) character.No findings

    Why it is in this group

    • The name "lookup_character" says "lookup": a word for reading.
    Description, as the server wrote it
    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. Each meaning carries the dictionary it came from and the reading it belongs to, so senses under different readings are never confused. Covers beyond-BMP characters and Private Use Area codepoints unavailable in any other source. "historicalEntries" lists entries in historical dictionaries (e.g. Đại Nam Quấc âm tự vị, 1895) that print this character — summaries only. Pass an entryId to lookup_dictionary_entry for the original wording and its subentries. Use for Vietnamese Hán Nôm. Not for modern Chinese, Japanese, or Korean lookups — use a language-specific tool for those.

    Annotations the server declares

    • title: Look up a Hán Nôm character
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
  • lookup_dictionary_entryUse this to retrieve an original entry from a historical Vietnamese dictionary such as Đại Nam Quấc âm tự vị (Huình-Tịnh Paulus Của, 1895–96).1 finding

    Why it is in this group

    • The name "lookup_dictionary_entry" says "lookup": a word for reading.

    Findings

    • Info

      The description is 2,594 characters long, over the 2,000 this check looks for.

      Matched text

      description ends: "...ves you. Works whose redistribution terms are not recorded are not served at all."

      What this check looks for
    Description, as the server wrote it
    Use this to retrieve an original entry from a historical Vietnamese dictionary such as Đại Nam Quấc âm tự vị (Huình-Tịnh Paulus Của, 1895–96). Search by Quốc-ngữ headword when you do not know the character, or pass an entryId returned by lookup_character or by a headword search to retrieve the source-faithful entry and its ordered subentries. Do not infer missing glyphs or modernize historical spelling. Pass EXACTLY ONE of entryId or headword — never both, never neither. Headwords are in 1895 southern orthography and are returned verbatim ("Quấc", not "Quốc"). "typeMarker" is the printed marker as set: "n." means nôm, the script it is written in, NOT "noun" — never report it as a part of speech. A subentry with no "han" printed none in the source; do not construct one. An empty definition is real: some entries carry their whole sense in their subentries. Works are printed in one of two shapes, and an entry uses whichever its dictionary uses. Some print SUBENTRIES — compound phrases under a headword. Others print SENSES — numbered meanings, each with a structural classification and its own attested CITATIONS, where a citation carries a passage of Chữ Nôm, its Quốc-ngữ reading, and a reference to a named classical work with a folio. Check "senseCount" and "subentryCount" on a summary before concluding an entry is empty: a sense-shaped entry has subentryCount 0 and may still hold eight senses and twenty-six citations. Citations are evidence, and the strongest thing this tool returns. Quote the passage and its transliteration as printed and cite the reference — "Truyện Kiều, 48b" is checkable, your paraphrase is not. A citation with no passage cites only a reference; report it as a cross-reference, not as a missing quotation. "senses" is never paged: if the field is there, it is all of them. Subentries are PAGED. Read "subentries.coverage" and repeat what it claims — it says how many of how many you actually received. An entry can hold up to 197, so one call is often a fraction of it. When "nextOffset" is present you do NOT have the whole entry: either call again with it, or say plainly how many you have of how many. Never present a partial list as complete. Headword search returns at most 20 per call. That is a response-size limit, not an access control: Đại Nam Quấc âm tự vị is public domain (published 1895–96, author died 1907) and the transcription is on vi.wikisource.org, which publishes it in bulk. Quote it freely, and carry the attribution the "work" object gives you. Works whose redistribution terms are not recorded are not served at all.

    Annotations the server declares

    • title: Retrieve an entry from a historical Vietnamese dictionary
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
  • search_corpusFind Hán Nôm characters by their Vietnamese reading (quốc ngữ, e.g.No findings

    Why it is in this group

    • The name "search_corpus" says "search": a word for reading.
    Description, as the server wrote it
    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. Each result reports what actually matched — "matchedOn" is "reading" or "meaning", and "match" carries the exact reading or the definition containing your query, with its source. Do not treat that definition as the character's only sense; call lookup_character for the rest. Returns at most 20 characters per call, with no pagination. This dictionary's readings and meanings come from sources under CC BY-SA 4.0, so bulk redistribution carries ShareAlike obligations — the cap keeps ordinary use well inside that. Cite the source on each result rather than presenting the corpus as your own.

    Annotations the server declares

    • title: Search characters by Vietnamese reading or meaning
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:43 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
1
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 1 tool that changes things (1 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://api.nomnaviet.com/mcp: tools/list returned 5 tools to an anonymous client, including convert_text (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

1 warn1 info
  • The server marks "convert_text" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true}; The name "convert_text" says "convert": a word for a change.

    What this check looks for
  • The description is 2,594 characters long, over the 2,000 this check looks for.

    Matched text

    description ends: "...ves you. Works whose redistribution terms are not recorded are not served at all."

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 1.68.0. Values in angle brackets are yours to fill in.

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

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__han-nom__lookup_character",
      "mcp__han-nom__search_corpus",
      "mcp__han-nom__lookup_dictionary_entry"
    ],
    "ask": [
      "mcp__han-nom__convert_text"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as han-nom. Review it before you use it.

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/com.nomnaviet/han-nom/verify?hash=b02386e96eecdeed1fcadfb530c2e9d888af6294077142fe6e05e71597f7d721" | jq -e '.changed == false'

Pinned hash b02386e96eec, from Nov 10, 2026, 22:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/com.nomnaviet/han-nom/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for com.nomnaviet/han-nom
[![Anlyon Radar](https://radar.anlyon.com/badge/com.nomnaviet/han-nom.svg)](https://radar.anlyon.com/servers/com.nomnaviet/han-nom)

Source: MCP Registry · repository. Synced Oct 21, 2026, 17:59 UTC.

Nôm Na Việt — Hán Nôm Dictionary MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Nôm Na Việt — Hán Nôm Dictionary MCP server safe?

No scan can promise that. What its definitions show: 4 tools, 1 of which can change, send or delete something, and 2 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Nôm Na Việt — Hán Nôm Dictionary MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Nôm Na Việt — Hán Nôm Dictionary MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Nôm Na Việt — Hán Nôm Dictionary MCP server have?

4 tools: 1 write, 3 read. convert_text, lookup_character, search_corpus and lookup_dictionary_entry.

Does the Nôm Na Việt — Hán Nôm Dictionary MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Nôm Na Việt — Hán Nôm Dictionary MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Nôm Na Việt — Hán Nôm Dictionary MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 10, 2026.