Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Dorabot – Vietnam address after 2025 merger

REMOTE · DORABOT.IO

Convert old Vietnamese addresses to the 2025 format and check new ones, per official resolutions.

Available components

+3 this week 73 Trust /100

Last scanned (23 hours ago)

Scores higher than 59% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Maps and Location

Trust breakdown (7 categories)

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 Security74
  • 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
  • HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability63
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 1086 tokens (~217/item across 5 items; 5 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 Management43
  • Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

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 →

Changelog

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.

  • 19 Nov 26 +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.

  • 17 Nov 26 +1

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

  • 15 Nov 26 +1

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

  • 13 Nov 26 +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.

  • 11 Nov 26 +1

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

  • 9 Nov 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 8 Nov 26 67

    First indexed and scored.

Diagnostics

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://dorabot.io/dia-chi/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=dorabot.io CN=WE1,O=Google Trust Services,C=US 13 Oct 2026 11 Jan 2027 ECDSA 256 ECDSA-SHA256 7e897bbb5b5505c613154e7f1eef0695
SANs: dorabot.io, *.dorabot.io
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of dorabot.io. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
io. DS published 38690 8 Verified
dorabot.io. 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

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://dorabot.io/dia-chi/mcp Verified 200
http (plaintext) http://dorabot.io/dia-chi/mcp HTTPS enforced 301 https://dorabot.io/dia-chi/mcp
MCP tools · 5 exposed · ~992 tokens

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 →

Tool Tokens
danh_sach_tinh ~58

34 tỉnh, thành phố từ 01/7/2025, mỗi tỉnh gồm những tỉnh cũ nào (Nghị quyết 202/2025/QH15), và tỉnh nào đã có dữ liệu xã chi tiết.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

danh_sach_xa_moi ~100

Liệt kê các xã, phường, đặc khu mới của một tỉnh/thành sau sáp nhập 2025, mỗi đơn vị gồm những xã cũ nào. Miễn phí.

NameTypeReqDescription
timstring–Lọc theo tên xã mới hoặc xã cũ (tuỳ chọn)
tinhstringyesTên hoặc slug tỉnh mới, ví dụ "Hưng Yên" hoặc "hung-yen"

No output schema declared.

No examples provided.

doi_dia_chi ~265

Đổi một hoặc nhiều địa chỉ đầy đủ kiểu CŨ (số nhà/đường, phường/xã, quận/huyện, tỉnh) sang địa chỉ MỚI sau sáp nhập 2025 (bỏ cấp huyện, tỉnh và xã mới) cho cả 63 tỉnh cũ. Mỗi dòng có nhãn tin_cay: "cao" hoặc "kiem_tra" (xã cũ bị chia/trùng tên). Không khoá: 20 địa chỉ/ngày. Có khoá API (miễn phí 100/ngày, gói trả phí cao hơn): tối đa 200 địa chỉ/lần. Lấy khoá: https://dorabot.io/dia-chi/nha-phat-trien/

NameTypeReqDescription
addressesarray–Hoặc danh sách địa chỉ cũ, ví dụ ["Số 12 ngõ 5, phường Khâm Thiên, quận Đống Đa, Hà Nội"]
dia_chistring–Một địa chỉ cũ (hoặc nhiều địa chỉ, mỗi dòng một địa chỉ), ví dụ "Số 12 ngõ 5, phường Khâm Thiên, quận Đống Đa, Hà Nội"

No output schema declared.

No examples provided.

kiem_dia_chi ~214

Kiểm một hoặc nhiều địa chỉ ở Việt Nam đã đúng kiểu MỚI sau 01/7/2025 chưa (2 cấp: xã/phường/đặc khu + tỉnh/thành, không còn quận/huyện; xã có thật trong tỉnh). Dùng ở bước kiểm form địa chỉ, nhập dữ liệu khách hàng. Trả về trang_thai: "hop_le", "dia_chi_cu" (còn quận/huyện, tỉnh cũ hoặc xã cũ: gọi doi_dia_chi), "khong_thay_xa", "khong_thay_tinh". Miễn phí, không cần khoá, tối đa 200 địa chỉ/lần.

NameTypeReqDescription
addressesarray–Hoặc danh sách địa chỉ
dia_chistring–Một địa chỉ (hoặc nhiều, mỗi dòng một địa chỉ), ví dụ "12 Tạ Quang Bửu, Phường Bạch Mai, Thành phố Hà Nội"

No output schema declared.

No examples provided.

tra_cuu_xa_cu ~355

Tra một xã, phường, thị trấn CŨ (trước 01/7/2025) nay thuộc xã/phường MỚI nào sau sắp xếp đơn vị hành chính 2025 ở Việt Nam, theo đúng nghị quyết của Ủy ban Thường vụ Quốc hội (kèm số khoản, cho biết đơn vị bị chia). Miễn phí, không cần khoá. Hiện có các tỉnh: Hà Nội, Hồ Chí Minh, Hải Phòng, Đà Nẵng, Hưng Yên, Bắc Ninh, Ninh Bình, Thanh Hóa, An Giang, Cà Mau, Cao Bằng, Lai Châu, Lạng Sơn, Huế, Quảng Trị, Quảng Ngãi, Khánh Hòa, Gia Lai, Lâm Đồng, Đắk Lắk, Đồng Nai, Tây Ninh, Đồng Tháp, Điện Biên, Sơn La, Quảng Ninh, Nghệ An, Hà Tĩnh, Tuyên Quang, Lào Cai, Thái Nguyên, Phú Thọ, Cần Thơ, Vĩnh Long. Tỉnh khác: dùng doi_dia_chi.

NameTypeReqDescription
huyenstring–Quận/huyện cũ để lọc khi trùng tên, ví dụ "Đống Đa"
tinhstring–Tỉnh/thành (cũ hoặc mới), ví dụ "Hà Nội", "Thái Bình"
xastringyesTên xã/phường/thị trấn cũ, có hoặc không có chữ "phường/xã", ví dụ "Khâm Thiên"

No output schema declared.

No examples provided.

Install

How do I install the Dorabot – Vietnam address after 2025 merger MCP server?

Dorabot – Vietnam address after 2025 merger is a hosted endpoint at https://dorabot.io/dia-chi/mcp, 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 · dorabot.io

# add to Claude Code
claude mcp add --transport http io-dorabot-dia-chi 'https://dorabot.io/dia-chi/mcp'
Common questions

What is the Dorabot – Vietnam address after 2025 merger MCP server?

Dorabot – Vietnam address after 2025 merger is an MCP server listed in the public MCP registry as io.dorabot/dia-chi. Convert old Vietnamese addresses to the 2025 format and check new ones, per official resolutions. This page covers its hosted endpoint (https://dorabot.io/dia-chi/mcp).

Is the Dorabot – Vietnam address after 2025 merger MCP server safe to use?

Dorabot – Vietnam address after 2025 merger scores 73 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 Dorabot – Vietnam address after 2025 merger MCP server expose?

Dorabot – Vietnam address after 2025 merger exposes 5 tools: tra_cuu_xa_cu, doi_dia_chi, kiem_dia_chi, danh_sach_xa_moi, danh_sach_tinh. Their descriptions and schemas cost roughly 992 tokens of context every time the server is loaded.

Does the Dorabot – Vietnam address after 2025 merger MCP server require authentication?

No. We connected to Dorabot – Vietnam address after 2025 merger without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Dorabot – Vietnam address after 2025 merger MCP server still maintained?

Dorabot – Vietnam address after 2025 merger 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 Dorabot – Vietnam address after 2025 merger MCP server?

VerifyMCP ran 13 checks on Dorabot – Vietnam address after 2025 merger, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. 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.