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.

Thailand Data MCP

NPM · THAILAND-DATA-MCP

Thai data for AI agents: DBD company-registry lookup, address normalization, holidays, VAT/WHT.

Available components

−3 this week 74 Trust /100

Last scanned (36 minutes ago)

Scores higher than 48% of npm servers

Category Finance and Payments

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security81
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
  • No install/post-install scripts declared.Pass
  • 83 of 285 dependencies flagged as unhealthy (1 deprecated). View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability67
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1298 tokens (~259/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 Management77
  • Stability observed for 23 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 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.

  • 5 Nov 26 −3
    • Stability: pass → 0.77 functional
  • 31 Oct 26 0
    • CVE-2026-118764 affects this package: high ▼ security
  • 30 Oct 26 0
    • Stability: 0.97 → pass security
  • 29 Oct 26 0
    • Stability: pass → 0.97 functional
  • 28 Oct 26 0
    • Security disclosure: unverified → fail ▼ functional
  • 27 Oct 26 0
    • Security disclosure: fail → unverified ▼ functional
  • 24 Oct 26 −3
    • CVE-2023-54404 affects this package: high ▼ security
    • Known CVEs: CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. security
  • 23 Oct 26 +1
    • Stability: 0.97 → pass security
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 5 Nov 2026 · Analysed npm/thailand-data-mcp@0.1.2

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Vulnerabilities 3 findings
ID CVE Severity Vector Fix available
GHSA-c475-qrg2-pj4r CVE-2026-102990 high yes
GHSA-g3hv-75wg-m249 CVE-2026-118764 medium yes
GHSA-mrhx-c7xc-m3w5 CVE-2023-54404 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes

Background: What a vulnerability scan can and cannot prove →

Dependencies 285 packages
Packages resolved 285
Deprecated 1
Stale 83
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 5 exposed · ~1,298 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
thai_address_normalize ~437

Parse free-text Thai addresses (Thai or English) into the official administrative hierarchy: province (จังหวัด) → district (อำเภอ/เขต) → subdistrict (ตำบล/แขวง) → postal code, with bilingual names and official codes. Handles common written forms: abbreviations (ต./อ./จ., กทม.), Bangkok's แขวง/เขต terminology, missing components, and postcode-only inputs. Matching is dictionary-based against the complete official geography (77 provinces, 928 districts, 7,436 subdistricts). Args: - address (string): free-text address, 2-500 chars Returns structured JSON: { "province": { "code": number, "nameTh": string, "nameEn": string } | null, "district": { ... } | null, "subdistrict": { ... } | null, "postalCode": number | null, "confidence": "high" | "medium" | "low" | "ambiguous" | "none", "streetHint": string | null, // residual text after removing administrative parts (house no., road, soi) "warnings": string[], // e.g. postcode/subdistrict mismatch "candidates": [...] // present when confidence = "ambiguous"; add district/postcode and retry } Examples: - Use when: filling a shipping form from a customer's pasted address - Use when: validating that district/province/postcode in a record are consistent - Use when: deduplicating customer records with differently-written addresses - Don't use when: you need geocoding to lat/long (not provided) Error handling: confidence "none" means nothing matched — the text may not be a Thai address.

NameTypeReqDescription
addressstringyesFree-text Thai address in Thai or English, e.g. '400/22 ถ.พหลโยธิน แขวงสามเสนใน เขตพญาไท กทม 10400'. Partial addresses work — more components give higher confidence.

No output schema declared.

No examples provided.

thai_company_lookup ~460

Look up a Thai company (juristic person) in the official DBD (Department of Business Development) registry by its 13-digit registration number. Returns the official registry profile: Thai/English name, entity type, operating status, registration date, registered and paid-up capital (THB), business objective (bilingual, with TSIC-style code), and registered head-office address. Args: - juristic_id (string): exactly 13 digits, e.g. "0107536000315" Returns structured JSON: { "found": boolean, "company": { "juristicId": string, "nameTh": string, "nameEn": string, "type": string, // e.g. "บริษัทจำกัด" (Co., Ltd.), "บริษัทมหาชนจำกัด" (PCL) "status": string, // e.g. "ยังดำเนินกิจการอยู่" = still operating "registerDate": string, // YYYYMMDD "registeredCapitalBaht": number, "paidUpCapitalBaht": number, "objective": { "code": string, "textTh": string, "textEn": string }, "address": { ... } } | null, "fromCache": boolean, "attribution": string } Examples: - Use when: verifying a Thai supplier/counterparty exists and is still operating (KYB / due diligence) - Use when: fetching official registered capital or address for a contract - Don't use when: you only have a company NAME — this tool requires the 13-digit ID (ask the counterparty or check their invoice/website footer) Notes: - "found": false means the ID is not in the registry — it may be mistyped, or the entity may be a sole proprietor (not a juristic person). - Data is the live official registry, cached for 24h.

NameTypeReqDescription
juristic_idstringyes13-digit Thai juristic person registration number, e.g. '0107536000315'. Printed on invoices, contracts, and company documents; same number as the company's tax ID.

No output schema declared.

No examples provided.

thai_holidays ~188

List Thai public holidays for a given year (2025, 2026), with dates, Thai/English names, and a flag for lunar-calendar holidays. Args: - year (number): one of 2025, 2026 Returns structured JSON: { "year": number, "count": number, "holidays": [{ "date": "YYYY-MM-DD", "nameEn": string, "nameTh": string, "lunar": boolean }], "disclaimer": string } Use when scheduling anything in Thailand: payment due dates, meeting planning, delivery estimates, contract deadlines. Lunar holidays (lunar: true) are fixed by annual announcement — verify for critical deadlines. Bank holidays can differ slightly from public holidays (Bank of Thailand publishes its own list).

NameTypeReqDescription
yearintegeryesCalendar year. Available: 2025, 2026

No output schema declared.

No examples provided.

thai_list_provinces ~82

List all 77 Thai provinces with official codes and bilingual names. Returns structured JSON: { "count": 77, "provinces": [{ "code": number, "nameTh": string, "nameEn": string }] } Use when you need the canonical province list for validation, dropdowns, or mapping Thai/English province spellings.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

thai_vat_reference ~131

Reference card for Thai VAT and withholding tax (WHT) basics: standard VAT rate, registration threshold, filing forms and deadlines, and common WHT rates by payment category (services, rent, advertising, transport, dividends, etc.). No arguments. Returns structured JSON with "vat", "withholdingTax" (rates table + certificate requirement), and "disclaimers". Use when: computing invoice amounts involving Thai WHT deduction, checking whether a business must register for VAT, or explaining the 50 ทวิ withholding certificate. Reference only — NOT tax advice; verify with the Revenue Department for filings.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Install

How do I install the Thailand Data MCP server?

Thailand Data MCP runs locally as an npm package, launched with npx -y thailand-data-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · thailand-data-mcp

# add to Claude Code
claude mcp add narinthon-so-thailand-data-mcp -- npx -y thailand-data-mcp
Common questions

What is the Thailand Data MCP server?

Thailand Data MCP is listed in the public MCP registry as io.github.narinthon-so/thailand-data-mcp. Thai data for AI agents: DBD company-registry lookup, address normalization, holidays, VAT/WHT. This page covers its npm package (thailand-data-mcp).

Is the Thailand Data MCP server safe to use?

Thailand Data MCP scores 74 out of 100 on VerifyMCP. We recorded 3 known advisories against it as of 5 November 2026. It declares no install or post-install scripts. 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 Thailand Data MCP server expose?

Thailand Data MCP exposes 5 tools: thai_company_lookup, thai_address_normalize, thai_list_provinces, thai_holidays, thai_vat_reference. Their descriptions and schemas cost roughly 1,298 tokens of context every time the server is loaded.

Is the Thailand Data MCP server still maintained?

Thailand Data MCP is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the Thailand Data MCP server under?

Thailand Data MCP declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.