Cổng Luật Việt
REMOTE · CONGLUATVIET.VN
Vietnamese law: search documents, check legal effect, read articles, verify citations.
Available components
Last scanned (19 hours ago)
Scores higher than 65% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Education and Research
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 Security83
- 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 is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability72
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 575 tokens (~143/item across 4 items; 4 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 Management13
- Stability observed for 4 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 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
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 →
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.
- 20 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.
- 18 Nov 26 +1
- Stability: unverified → 0.03 ▲ functional
- 17 Nov 26 74
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://congluatviet.vn/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=congluatviet.vn | CN=WE1,O=Google Trust Services,C=US | 9 Oct 2026 | 7 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 61389ca2d62e8f141318c31f94be2de7 |
| SANs: congluatviet.vn, *.congluatviet.vn | ||||||
| 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 secure
Validation of congluatviet.vn. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| vn. | DS published | 16196, 16196 | 8, 8 | Verified |
| congluatviet.vn. | DS published | 2371 | 13 | Verified |
| congluatviet.vn. | Verified address RRset verified with the apex keys |
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; includeSubDomains |
| content-security-policy | default-src 'self'; script-src 'self' 'unsafe-inline' https://hcaptcha.com https://*.hcaptcha.com; style-src 'self' 'unsafe-inline' https://hcaptcha.com https://*.hcaptcha.com; img-src 'self' data: blob:; font-src 'self' data: blob:; connect-src 'self' https://hcaptcha.com https://*.hcaptcha.com; media-src 'self' data:; frame-src 'self' https://hcaptcha.com https://*.hcaptcha.com; worker-src 'self' blob:; frame-ancestors 'self'; object-src 'none'; base-uri 'self'; form-action 'self' |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://congluatviet.vn/mcp | Verified | 200 | |
| http (plaintext) | http://congluatviet.vn/mcp | HTTPS enforced | 301 | https://congluatviet.vn/mcp |
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 →
doc_dieu Đọc nguyên văn một điều ~94
Nguyên văn một điều của một văn bản, kèm hiệu lực văn bản và số lần điều đó đã bị sửa đổi. Dùng khi cần trích chính xác câu chữ của luật thay vì nhớ lại.
| Name | Type | Req | Description |
|---|---|---|---|
| dieu | string | yes | Số điều, ví dụ "468" hoặc "12a" |
| guid | string | yes | Mã văn bản lấy từ tim_kiem hoặc tra_van_ban |
No output schema declared.
No examples provided.
kiem_trich_dan Kiểm các chỗ viện dẫn luật trong một đoạn văn ~162
Dán một văn bản tiếng Việt (bài viết, hợp đồng, công văn…); công cụ tìm mọi chỗ viện dẫn ("Điều N + tên hoặc số hiệu văn bản") rồi đối chiếu từng chỗ: điều đó có tồn tại không, văn bản còn hiệu lực không, điều đã bị sửa đổi chưa và từ ngày nào, kèm câu mở đầu của điều và liên kết nguồn. Cần khoá tài khoản Cổng Luật Việt (header Authorization: Bearer); mỗi chỗ viện dẫn hoặc số hiệu tính một lượt.
| Name | Type | Req | Description |
|---|---|---|---|
| noi_dung | string | yes | Đoạn văn cần kiểm (kiểm 20.000 ký tự đầu, tối đa 15 chỗ viện dẫn mỗi lượt) |
No output schema declared.
No examples provided.
tim_kiem Tìm văn bản và điều luật Việt Nam ~121
Tìm trong kho văn bản quy phạm pháp luật Việt Nam (luật, nghị định, thông tư…). Nhận từ khoá, tên văn bản, số hiệu, hoặc câu dạng "điều 468 bộ luật dân sự 2015". Trả văn bản và điều khớp kèm tình trạng hiệu lực, guid và liên kết congluatviet.vn.
| Name | Type | Req | Description |
|---|---|---|---|
| gioi_han | integer | – | Số kết quả mỗi nhóm, mặc định 5 |
| q | string | yes | Câu tìm bằng tiếng Việt |
No output schema declared.
No examples provided.
tra_van_ban Tra hiệu lực một văn bản ~118
Tình trạng hiệu lực, ngày ban hành, ngày có và hết hiệu lực, số điều của MỘT văn bản. Ưu tiên truyền `guid`; `so_hieu` có thể trùng nhiều văn bản, khi đó trả danh sách để chọn.
| Name | Type | Req | Description |
|---|---|---|---|
| guid | string | – | Mã văn bản lấy từ tim_kiem |
| muc_luc | boolean | – | true để kèm danh sách điều |
| so_hieu | string | – | Ví dụ 100/2019/NĐ-CP |
No output schema declared.
No examples provided.
How do I install the Cổng Luật Việt MCP server?
Cổng Luật Việt is a hosted endpoint at https://congluatviet.vn/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 · congluatviet.vn
claude mcp add --transport http vn-congluatviet-phap-luat 'https://congluatviet.vn/mcp'
What is the Cổng Luật Việt MCP server?
Cổng Luật Việt is an MCP server listed in the public MCP registry as vn.congluatviet/phap-luat. Vietnamese law: search documents, check legal effect, read articles, verify citations. This page covers its hosted endpoint (https://congluatviet.vn/mcp).
Is the Cổng Luật Việt MCP server safe to use?
Cổng Luật Việt scores 76 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 Cổng Luật Việt MCP server expose?
Cổng Luật Việt exposes 4 tools: tim_kiem, tra_van_ban, doc_dieu, kiem_trich_dan. Their descriptions and schemas cost roughly 495 tokens of context every time the server is loaded.
Does the Cổng Luật Việt MCP server require authentication?
No. We connected to Cổng Luật Việt without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Cổng Luật Việt MCP server still maintained?
Cổng Luật Việt 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 Cổng Luật Việt MCP server?
VerifyMCP ran 13 checks on Cổng Luật Việt, 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.