Vietnam Address Converter (2025 reform)
REMOTE · SINCE98.VN
Convert old Vietnamese addresses to the post-2025 34 provinces and 3,321 communes. Official data.
Available components
Last scanned (10 hours ago)
Scores higher than 56% of remote servers
Reachable. Last reached 21 Nov 2026.
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. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability68
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1622 tokens (~231/item across 7 items; 7 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "explain_merge" implies "merge" and declares readOnlyHint instead, contradicting what its own name says it does. See how to fix → Fail
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Unverified: 1 category
A category scored 0 because we could not verify it: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
Checks we ran (12)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 21 Nov 26 71
First indexed and scored.
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 21 Nov 2026 · Probed https://since98.vn/api/mcp/address
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=since98.vn | CN=YE1,O=Let's Encrypt,C=US | 17 Nov 2026 | 15 Feb 2027 | ECDSA 256 | ECDSA-SHA384 | 516661a5f073aa828863fb6784c1843e2cd |
| SANs: *.since98.vn, since98.vn | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of since98.vn. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| vn. | DS published | 16196, 16196 | 8, 8 | Verified |
| since98.vn. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000 |
| content-security-policy | default-src 'self'; script-src 'self' 'unsafe-inline' https://*.googletagmanager.com; style-src 'self' 'unsafe-inline'; img-src 'self' data: https://*.google-analytics.com https://*.googletagmanager.com; font-src 'self'; connect-src 'self' https://*.google-analytics.com https://*.analytics.google.com https://*.googletagmanager.com; frame-ancestors 'none'; base-uri 'self'; form-action 'self'; object-src 'none' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(), interest-cohort=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://since98.vn/api/mcp/address | Verified | 200 | |
| http (plaintext) | http://since98.vn/api/mcp/address | HTTPS enforced | 301 | https://since98.vn/api/mcp/address |
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 →
convert_old_to_new Convert old address to new (2025 reform) ~361
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"}.
| Name | Type | Req | Description |
|---|---|---|---|
| district | string | – | Old district (quận / huyện / thị xã / thành phố): name, abbreviation (Q.1, H. Củ Chi) or 3-digit code. |
| province | string | – | Old (pre-1 July 2025) province or city: name with or without diacritics, abbreviation (TP.HCM, HN) or 2-digit code. A post-reform province name is also accepted. |
| ward | string | – | Old commune-level unit (phường / xã / thị trấn): name, abbreviation (P.16) or 5-digit code. |
No output schema declared.
No examples provided.
data_info Dataset version and sources ~77
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: {}.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
explain_merge Explain how a new unit was formed ~165
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"}.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | Code of a NEW unit: 5-digit commune code (e.g. "26734") or 2-digit province code (e.g. "79"). |
No output schema declared.
No examples provided.
find_units Find administrative units by name ~313
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}.
| Name | Type | Req | Description |
|---|---|---|---|
| level | string | – | Restrict to one level. "district" exists only with scope "old". |
| limit | integer | – | Maximum results, 1-50, default 10. |
| province | string | – | Optional province filter in the same scope: code or name. |
| query | string | yes | Unit name or code to look up, e.g. "Bến Nghé", "ben nghe", "Thủ Đức", "26734". Case and diacritics are ignored. |
| scope | string | – | "new" (default): units after the 2025 reform (34 provinces, 3,321 communes). "old": units as of 30 June 2025 (63 provinces, districts, 10,035 communes). |
No output schema declared.
No examples provided.
list_provinces List provinces (34 new or 63 old) ~150
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"}.
| Name | Type | Req | Description |
|---|---|---|---|
| scope | string | – | "new" (default): 34 provinces after 1 July 2025, with the old provinces merged into each. "old": 63 provinces before the reform, with the new province each went into. |
No output schema declared.
No examples provided.
list_wards List communes of a province ~189
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.
| Name | Type | Req | Description |
|---|---|---|---|
| province | string | yes | Province: 2-digit code (e.g. "79") or name (e.g. "Hồ Chí Minh", "Ha Noi"). |
| scope | string | – | "new" (default): communes after the reform. "old": communes as of 30 June 2025, with their district. |
No output schema declared.
No examples provided.
normalize_address Rewrite a free-form address to the new units ~223
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"}.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Free-form Vietnamese address, with or without diacritics, e.g. "12 Nguyễn Huệ, P. Bến Nghé, Q.1, TP.HCM" or "so 1 phu cuong thu dau mot binh duong". |
No output schema declared.
No examples provided.
How do I install the Vietnam Address Converter (2025 reform) MCP server?
Vietnam Address Converter (2025 reform) is a hosted endpoint at https://since98.vn/api/mcp/address, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · since98.vn
claude mcp add --transport http vn-since98-vietnam-address 'https://since98.vn/api/mcp/address'
What is the Vietnam Address Converter (2025 reform) MCP server?
Vietnam Address Converter (2025 reform) is an MCP server listed in the public MCP registry as vn.since98/vietnam-address. Convert old Vietnamese addresses to the post-2025 34 provinces and 3,321 communes. Official data. This page covers its hosted endpoint (https://since98.vn/api/mcp/address).
Is the Vietnam Address Converter (2025 reform) MCP server safe to use?
Vietnam Address Converter (2025 reform) scores 71 out of 100 on VerifyMCP. 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 Vietnam Address Converter (2025 reform) MCP server expose?
Vietnam Address Converter (2025 reform) exposes 7 tools: convert_old_to_new, find_units, list_provinces, list_wards, explain_merge, and 2 more. Their descriptions and schemas cost roughly 1,478 tokens of context every time the server is loaded.
Does the Vietnam Address Converter (2025 reform) MCP server require authentication?
No. We connected to Vietnam Address Converter (2025 reform) without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Vietnam Address Converter (2025 reform) MCP server still maintained?
Vietnam Address Converter (2025 reform) 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 did VerifyMCP test on the Vietnam Address Converter (2025 reform) MCP server?
VerifyMCP ran 12 checks on Vietnam Address Converter (2025 reform), covering TLS certificate, Authorization, HTTPS, HSTS header and 8 more. One item could not be completed, a gap on our side rather than a finding about Vietnam Address Converter (2025 reform): Stability. One category scores 0 for that reason, because we only credit what we can confirm. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.