Vietnam Address Converter (2025 reform) MCP server
vn.since98/vietnam-addresssince98.vnstreamable-httpv2026.11.20Scanned
Convert old Vietnamese addresses to the post-2025 34 provinces and 3,321 communes. Official data.
7 tools: 3 change things and 4 only read.
- Reads private data · 1
- Reads text others write · 1
- Can send data out · 0
- 2 findings
Tools listed without sign-in. Remote posture
With Anlyon
3 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
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 Vietnam Address Converter (2025 reform) MCP server can do
The Vietnam Address Converter (2025 reform) MCP server is published by since98.vn, a domain the MCP Registry verified. It has 7 tools. It can create or change data (3 tools: convert_old_to_new, explain_merge and normalize_address), but cannot delete data. 4 tools only read.
1 tool reads private data (data_info); 1 tool brings in text other people can write (data_info).
The fixed checks matched 2 findings (annotation-conflict). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 21, 2026, version 2026.11.20.
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.
7 tools
Changes things 3Claude Code: ask
convert_old_to_newConvert a Vietnamese administrative address from BEFORE 1 July 2025 (old province, district, commune) to the unit(s) valid AFTER the 2025 reform.1 finding
Why it is in this group
- The name "convert_old_to_new" 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_old_to_new" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "convert_old_to_new" says "convert": a word for a change.
Description, as the server wrote it Convert a Vietnamese administrative address from BEFORE 1 July 2025 (old province, district, commune) to the unit(s) valid AFTER the 2025 reform. Use when the user has an old address, an old ID card or registration address, or asks "what is my ward called now". Pass the parts you have; names may be written with or without diacritics, with prefixes or abbreviations, or as official codes. Returns the old unit, the new commune and province, the new address line, transition type (merge, unchanged, rename, retype, special_zone), partial=true when only part of the old commune went there, and resolution numbers. If the old commune was split between several new communes, ALL of them are returned and ambiguous=true: do not pick one, ask for the street or hamlet. Examples: {"province":"TP.HCM","district":"Quận 8","ward":"Phường 16"}; {"province":"Bình Dương","district":"Thủ Dầu Một","ward":"Phú Cường"}; {"ward":"27430"}.
Annotations the server declares
- title: Convert old address to new (2025 reform)
- readOnlyHint: true
- idempotentHint: true
- destructiveHint: false
- openWorldHint: false
explain_mergeExplain what a NEW (post-1 July 2025) commune or province was formed from: the old communes or provinces merged into it, whether each came whole or partially (split communes list t…1 finding
Why it is in this group
- The name "explain_merge" says "explain": a word for reading.
- The input takes a statement or command to run (input.code), which can change anything it can reach.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
The server marks "explain_merge" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "explain_merge" says "explain": a word for reading.
Description, as the server wrote it Explain what a NEW (post-1 July 2025) commune or province was formed from: the old communes or provinces merged into it, whether each came whole or partially (split communes list the other new units their parts went to), the transition type and the resolution numbers. Use when the user asks "which wards were merged into X" or needs the legal basis. Takes the new unit code (5 digits for a commune, 2 for a province); get it from find_units or convert_old_to_new. Examples: {"code":"26734"}; {"code":"79"}.
Annotations the server declares
- title: Explain how a new unit was formed
- readOnlyHint: true
- idempotentHint: true
- destructiveHint: false
- openWorldHint: false
normalize_addressParse a free-form Vietnamese address line (street, commune, district, province; with or without diacritics, commas or abbreviations) and rewrite it with the post-reform units: drop…No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it Parse a free-form Vietnamese address line (street, commune, district, province; with or without diacritics, commas or abbreviations) and rewrite it with the post-reform units: drops the district and replaces the old commune and province. Returns status (converted, already_new, province_level when only a province was given, ambiguous, partial when the commune is missing, e.g. a district alone, not_found), confidence, the rewritten address, all candidates when ambiguous, which parts were recognised and which were not. Never invents a unit. Examples: {"address":"12 Nguyễn Huệ, P. Bến Nghé, Q.1, TP.HCM"}; {"address":"so 1 phu cuong thu dau mot binh duong"}.
Annotations the server declares
- title: Rewrite a free-form address to the new units
- readOnlyHint: true
- idempotentHint: true
- destructiveHint: false
- openWorldHint: false
Only reads 4Show 4 read-only tools
data_infoReturn the dataset version, the official source (National Statistics Office of Viet Nam transition table, with checksum and fetch date), the list of resolutions with issue and effe…Reads private dataReads text others writeNo findings
Why it is in this group
- The description's first verb is "return": a word for reading.
What it can reach
- private-dataThe description's first sentence says "return" and "table": it reads databases.
- untrusted-inputThe description's first sentence says "return" and "issue": it reads issues, which other people can write.
Description, as the server wrote it Return the dataset version, the official source (National Statistics Office of Viet Nam transition table, with checksum and fetch date), the list of resolutions with issue and effective dates (2025 reform and 2026 changes), unit counts and the coverage note. Use when the user asks how current or reliable the data is. Takes no arguments: {}.
Annotations the server declares
- title: Dataset version and sources
- readOnlyHint: true
- idempotentHint: true
- destructiveHint: false
- openWorldHint: false
find_unitsSearch Vietnamese administrative units by name or code, ignoring case and diacritics.No findings
Why it is in this group
- The name "find_units" says "find": a word for reading.
Description, as the server wrote it Search Vietnamese administrative units by name or code, ignoring case and diacritics. scope "new" (default) searches the post-reform units (34 provinces, 3,321 communes); scope "old" searches units as of 30 June 2025 (63 provinces, districts, communes). Use to check spelling, get a code, or see every place with the same name before converting. Returns code, full name, level, match quality (code, exact, partial) and parent district/province. Examples: {"query":"Bến Nghé","scope":"old"}; {"query":"thu duc"}; {"query":"Tân Phú","scope":"old","level":"ward","province":"79","limit":20}.
Annotations the server declares
- title: Find administrative units by name
- readOnlyHint: true
- idempotentHint: true
- destructiveHint: false
- openWorldHint: false
list_provincesList Vietnam's provinces and centrally-run cities.No findings
Why it is in this group
- The name "list_provinces" says "list": a word for reading.
Description, as the server wrote it List Vietnam's provinces and centrally-run cities. scope "new" (default): the 34 provinces in force since 1 July 2025, each with its code, number of communes and the old provinces merged into it. scope "old": the 63 provinces before the reform, each with the new province it became part of. Use for overviews or to answer "which provinces were merged into X". Example: {"scope":"old"}.
Annotations the server declares
- title: List provinces (34 new or 63 old)
- readOnlyHint: true
- idempotentHint: true
- destructiveHint: false
- openWorldHint: false
list_wardsList all commune-level units (phường, xã, đặc khu) of one province.No findings
Why it is in this group
- The name "list_wards" says "list": a word for reading.
Description, as the server wrote it List all commune-level units (phường, xã, đặc khu) of one province. scope "new" (default): communes after the reform with codes and any 2026 changes; scope "old": communes as of 30 June 2025 with their district. The province may be a 2-digit code or a name. Example: {"province":"79"}; {"province":"Đà Nẵng","scope":"old"}. Output can be long (up to a few hundred entries); prefer find_units for a single name.
Annotations the server declares
- title: List communes of a province
- readOnlyHint: true
- idempotentHint: true
- destructiveHint: false
- openWorldHint: false
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 outbound.
- Reads private data1
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write1
- 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.
Looked at Nov 21, 2026, 19:20 UTC, unchanged since Nov 21, 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
- 3
- 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 3 tools that change things (3 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://since98.vn/api/mcp/address: tools/list returned 7 tools to an anonymous client, including convert_old_to_new (write), explain_merge (write), normalize_address (write)
Findings
Matches of fixed checks, with the text they matched.
The server marks "convert_old_to_new" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "convert_old_to_new" says "convert": a word for a change.
- Warnexplain_merge
The server marks "explain_merge" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "explain_merge" says "explain": a word for reading.
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 2026.11.20. Values in angle brackets are yours to fill in.
claude mcp add --transport http vietnam-address https://since98.vn/api/mcp/addressclaude mcp add --transport http vietnam-address https://since98.vn/api/mcp/addressRun 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.
{
"permissions": {
"allow": [
"mcp__vietnam-address__find_units",
"mcp__vietnam-address__list_provinces",
"mcp__vietnam-address__list_wards",
"mcp__vietnam-address__data_info"
],
"ask": [
"mcp__vietnam-address__convert_old_to_new",
"mcp__vietnam-address__explain_merge",
"mcp__vietnam-address__normalize_address"
],
"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 vietnam-address. Review it before you use it.
Capability tags behind 1 rule
- mcp__vietnam-address__data_info private-data, untrusted-input
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/vn.since98/vietnam-address/verify?hash=b471bb604135a627a38c6a2e45105d8b5d4009b273636a8cc16947d97e923fae" | jq -e '.changed == false'Pinned hash b471bb604135, from Nov 21, 2026, 11:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/vn.since98/vietnam-address/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/vn.since98/vietnam-address)Source: MCP Registry · repository. Synced Nov 21, 2026, 11:17 UTC.
Vietnam Address Converter (2025 reform) MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Vietnam Address Converter (2025 reform) MCP server safe?
- No scan can promise that. What its definitions show: 7 tools, 3 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 Vietnam Address Converter (2025 reform) MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Vietnam Address Converter (2025 reform) 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 Vietnam Address Converter (2025 reform) MCP server have?
- 7 tools: 3 write, 4 read. convert_old_to_new, explain_merge, normalize_address, find_units, list_provinces, list_wards and data_info.
Does the Vietnam Address Converter (2025 reform) MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Vietnam Address Converter (2025 reform) MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Vietnam Address Converter (2025 reform) MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 21, 2026.