Zalo Business Reference (ZBS Template Message, OA)
REMOTE · SINCE98.VN
ZBS (ZNS) message prices, OA plans, template checks, sending rules and Zalo error codes. Unofficial.
Available components
Last scanned (10 hours ago)
Scores higher than 54% 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 Usability57
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 2805 tokens (~400/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
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- 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 70
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/zalo
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/zalo | Verified | 200 | |
| http (plaintext) | http://since98.vn/api/mcp/zalo | HTTPS enforced | 301 | https://since98.vn/api/mcp/zalo |
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 →
check_sending_rules Check ZBS sending window, quota and promotion limits ~464
Check whether a ZBS template send is allowed: the sending window by tag in Vietnam time (Tag 1 round the clock, Tag 2 and 3 07:00-22:00; for Tag 1 at night a warning notes the -133 wording; the conflicting announcement dates are named), the OA daily quota (levels 1000, 5000, 20000, 50000, unlimited; default 20000), Tag 3 limits per user (1 per day, 30 per month), and the quota upgrade conditions (Good quality over 7 days and 2 x the daily quota sent in 7 days). Reference only, nothing is sent. Examples: {"tag":3,"send_time":"21:30","daily_volume":15000}; {"tag":2,"send_time":"06:30"}; {"tag":3,"promo_sent_to_user_today":1}; {"tag":1,"quota_level":20000,"sent_last_7_days":45000}.
| Name | Type | Req | Description |
|---|---|---|---|
| daily_volume | integer | – | Template messages the OA plans to send that day (all templates). |
| delivery | string | – | How messages are addressed: "phone" (phone number, default) or "uid" (Zalo user ID for this OA; cheaper, not for OTP, quick response, journey or carousel). |
| promo_sent_to_user_this_month | integer | – | Tag 3 messages this OA has already sent to the same user this month (before this one). |
| promo_sent_to_user_today | integer | – | Tag 3 messages this OA has already sent to the same user today (before this one). |
| quota_level | – | – | OA daily quota level for template messages: 1000, 5000, 20000, 50000, unlimited (default 20000, where a new OA starts; 1000 and 5000 are penalty levels). |
| send_time | string | – | Planned send time, HH:MM in Vietnam time (UTC+7). |
| sent_last_7_days | integer | – | Messages sent successfully in the last 7 days (to check the quota upgrade volume condition). |
| tag | – | yes | Template tag: 1 transaction, 2 customer care, 3 promotion. |
| Name | Type | Req | Description |
|---|---|---|---|
| affiliation | string | yes | – |
| allowed | boolean | yes | – |
| data_version | string | yes | – |
| disclaimer | string | yes | – |
| quota | object | yes | – |
| tag | number | yes | – |
| violations | array | yes | – |
| warnings | array | yes | – |
| window | object | yes | – |
No examples provided.
choose_channel Choose a Zalo channel for a task ~261
Suggest which Zalo channel fits a business task, by simple published rules: ZBS template message (with the template type, tag, price and window), a free consultation reply within 48 hours of the user's last interaction (paid outside 48 hours, not allowed after 7 days), an OA broadcast to followers, or a Mini App. Tasks: otp, order_status, delivery_tracking, payment_request, appointment_reminder, customer_reply, service_rating, promotion, voucher, birthday_greeting, news_to_followers, catalog_checkout. Optional: last_interaction_hours, is_follower. Reference only. Examples: {"task":"order_status"}; {"task":"customer_reply","last_interaction_hours":30}; {"task":"promotion","is_follower":true}.
| Name | Type | Req | Description |
|---|---|---|---|
| is_follower | boolean | – | The user follows the OA. |
| last_interaction_hours | integer | – | Hours since the user's last interaction with the OA (message, call, menu tap...). Decides whether a free reply is possible. |
| task | string | yes | What you need to send: otp, order_status, delivery_tracking, payment_request, appointment_reminder, customer_reply, service_rating, promotion, voucher, birthday_greeting, news_to_followers, catalog_c… |
| Name | Type | Req | Description |
|---|---|---|---|
| affiliation | string | yes | – |
| alternatives | array | yes | – |
| data_version | string | yes | – |
| disclaimer | string | yes | – |
| notes | array | yes | – |
| recommended | object | yes | – |
| task | string | yes | – |
No examples provided.
data_info Zalo reference data: sources and gaps ~113
Return the data version and retrieval date, the official Zalo pages used, what Zalo does not publish (Cơ bản plan price, broadcast price above the free allowance, Mini App fees, the VAT rate for template messages, and others), where Zalo's own pages disagree (maximum buttons, night window, OTP by UID, old fallback prices) and how this tool resolves it, the change log and the worked example. Use when the user asks how current or reliable the figures are. Takes no arguments: {}.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| affiliation | string | yes | – |
| data_date | string | yes | – |
| data_version | string | yes | – |
| disclaimer | string | yes | – |
| discrepancies | array | yes | – |
| not_published | array | yes | – |
| sources | array | yes | – |
No examples provided.
error_lookup Zalo error code lookup ~153
Explain a Zalo error code in plain words: which table it comes from (ZBS Template Message, the archived ZNS table, or the Official Account API; the same code can mean different things in different tables) and what to check. A positive number is also tried as negative. Examples: {"code":-133}; {"code":-100,"table":"oa_api"}; {"code":249}.
| Name | Type | Req | Description |
|---|---|---|---|
| code | integer | yes | Error code returned by Zalo, e.g. -133 (a positive number is also tried as negative). |
| table | string | – | Limit to one table: zbs (ZBS Template Message), zns_archive (old ZNS), oa_api (Official Account API). |
| Name | Type | Req | Description |
|---|---|---|---|
| affiliation | string | yes | – |
| code | number | yes | – |
| data_version | string | yes | – |
| disclaimer | string | yes | – |
| found | boolean | yes | – |
| matches | array | yes | – |
No examples provided.
estimate_message_cost ZBS template message cost (Zalo) ~706
Estimate what Zalo charges for ZBS template messages (formerly ZNS): base price by template type (otp, voucher, payment_request, bus_ticket, custom = "other types", rating, quick_response, carousel, journey "from" price) for phone or UID sending, plus buttons by category (the first button to the OA page/Mini App/OA article and the first to an e-invoice page are free, others paid from the first), image module and quick reply. Returns the price per message with a line breakdown, the total if all messages are delivered, the estimate for delivery_rate (only delivered messages are charged), totals with VAT if you pass vat_rate (Zalo names no rate), the OA plan needed to send through the API, and days needed at the daily quota (default 20000, a new OA). OTP, quick response, journey and carousel by UID are rejected. Prices exclude VAT. Reference only, no messages are sent. Examples: {"template_type":"custom","buttons":["business_website"],"count":10000}; {"template_type":"custom","delivery":"uid","buttons":["oa_profile_page"],"count":5000,"delivery_rate":0.9,"vat_rate":0.1}; {"template_type":"otp","count":20000}.
| Name | Type | Req | Description |
|---|---|---|---|
| buttons | array | – | Extra buttons by category, one item per button (repeat a category for two buttons): oa_profile_page, business_mini_app, oa_article_or_other_zalo_asset, e_invoice_lookup, business_website, call_phone,… |
| count | integer | – | Number of messages (1-100000000). Default 1. |
| delivery | string | – | How messages are addressed: "phone" (phone number, default) or "uid" (Zalo user ID for this OA; cheaper, not for OTP, quick response, journey or carousel). |
| delivery_rate | number | – | Expected share of messages that get delivered and charged, 0-1 (default 1 = all). Only delivered messages are charged. |
| image | boolean | – | Image module (1-3 images) included. Default false. Not allowed on OTP. |
| quick_reply | boolean | – | Quick reply (response) buttons activated. Default false; always on for quick_response. |
| quota_level | – | – | OA daily quota level for template messages: 1000, 5000, 20000, 50000, unlimited (default 20000, where a new OA starts; 1000 and 5000 are penalty levels). |
| template_type | string | – | ZBS template type: otp, payment_request, voucher, bus_ticket, custom (the "other types" row: order status, reminders, notices), rating, quick_response, carousel, journey (special industries, price "f… |
| vat_rate | number | – | Optional VAT rate as a share (e.g. 0.1) to add to the totals. Zalo's ZBS page says prices exclude VAT but names no rate, so the rate is yours. |
| Name | Type | Req | Description |
|---|---|---|---|
| affiliation | string | yes | – |
| count | number | yes | – |
| data_version | string | yes | – |
| delivered_estimate | number | yes | – |
| delivery | string | yes | – |
| disclaimer | string | yes | – |
| lines | array | yes | – |
| notes | array | yes | – |
| per_message | number | yes | – |
| plan_required | object | yes | – |
| quota | object | yes | – |
| sources | array | yes | – |
| template_type | string | yes | – |
| total_estimated | number | yes | – |
| total_max | number | yes | – |
| warnings | array | yes | – |
No examples provided.
oa_plan_compare Zalo OA plan comparison ~394
Compare the Zalo Official Account plans in force from 1 June 2026 (Cơ bản, Tiêu chuẩn, Tăng trưởng, Toàn diện) with prices including 10% VAT, staff accounts, Open API and its requests-per-minute limit, consultation messages outside the 48-hour window and features, and pick the smallest plan that meets your needs (needs_api, api_requests_per_minute, replies_outside_48h_per_month, staff, features, term_months 6 or 12), with the reason and the paid-reply overage. The Cơ bản price is not published by Zalo. Reference only. Examples: {}; {"needs_api":true,"staff":8}; {"replies_outside_48h_per_month":3000,"features":["chatbot"],"term_months":6}.
| Name | Type | Req | Description |
|---|---|---|---|
| api_requests_per_minute | integer | – | Peak OA API requests per minute (implies needs_api when above 0). |
| features | array | – | Required features: chat_basic, chat_advanced_labels_assign_notes, group_chat_gmf, voice_call_basic, voice_call_advanced, mobile_chat_tool, basic_automation, chat_menu, chatbot, extensions, articles_c… |
| needs_api | boolean | – | The OA needs the Open API (for integrations or sending template messages through the API). Default false. |
| replies_outside_48h_per_month | integer | – | Consultation messages per month sent more than 48 hours after the user's last interaction (paid replies). |
| staff | integer | – | Staff accounts that will work in the OA. Default 1. |
| term_months | – | – | Plan term: 12 (default) or 6 months (6 months only for Tăng trưởng and Toàn diện). |
| Name | Type | Req | Description |
|---|---|---|---|
| affiliation | string | yes | – |
| data_version | string | yes | – |
| disclaimer | string | yes | – |
| notes | array | yes | – |
| plans | array | yes | – |
| reason | string | yes | – |
| recommended | – | yes | – |
No examples provided.
validate_template Check a ZBS template draft (formal rules) ~487
Check a ZBS template draft against the formal technical rules Zalo publishes: template name, title and text block lengths and parameter counts, table rows and cell lengths, number of buttons (2 vs 3 conflict reported as a warning), button text and URL length, parameters only in the URL path, one OA page button, logo PNG 400x96, image module 1-3 images 16:9 up to 500 KB, parameter types and sample lengths, and formal content hints (links or phone numbers in the text, icons, "anh/chị", superlatives in Tag 3). Types: custom, otp, rating, quick_response. Returns errors and warnings with the rule and the official page. Content is reviewed by Zalo, not here; the text is not stored. Example: {"template_type":"custom","tag":1,"title":"Order <order_code> confirmed","paragraphs":["Hello <customer_name>, your order <order_code> is on its way."],"buttons":[{"category":"business_website","text":"Track order","url":"https://shop.example.vn/track/<order_code>"}],"logo":{"format":"PNG","width":400,"height":96}}.
| Name | Type | Req | Description |
|---|---|---|---|
| buttons | array | – | CTA buttons. |
| images | array | – | Image module files: width, height (px), size_kb. |
| logo | object | – | Logo file facts: format (PNG), width and height in px. |
| name | string | – | Template name (visible only to the business). |
| paragraphs | array | – | Text blocks (custom: 1-4; OTP and rating: one). |
| params | array | – | Declared parameters: name, Zalo type (customer_name, phone_number, address, code, custom_label, transaction_status, contact, personal_title, product_name, amount, time, bank_transfer_note, url_in_but… |
| quick_replies | array | – | Quick reply button texts (quick_response templates). |
| table | array | – | Table rows {name, value}. |
| tag | – | – | Template tag: 1 transaction, 2 customer care, 3 promotion. |
| template_type | string | – | Template to check: custom (default), otp, rating, quick_response. |
| title | string | – | Title; parameters as <param_name>. |
| Name | Type | Req | Description |
|---|---|---|---|
| affiliation | string | yes | – |
| data_version | string | yes | – |
| disclaimer | string | yes | – |
| errors | number | yes | – |
| issues | array | yes | – |
| moderation | string | yes | – |
| valid | boolean | yes | – |
| warnings | number | yes | – |
No examples provided.
How do I install the Zalo Business Reference (ZBS Template Message, OA) MCP server?
Zalo Business Reference (ZBS Template Message, OA) is a hosted endpoint at https://since98.vn/api/mcp/zalo, 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-zalo-business-reference 'https://since98.vn/api/mcp/zalo'
What is the Zalo Business Reference (ZBS Template Message, OA) MCP server?
Zalo Business Reference (ZBS Template Message, OA) is an MCP server listed in the public MCP registry as vn.since98/zalo-business-reference. ZBS (ZNS) message prices, OA plans, template checks, sending rules and Zalo error codes. Unofficial. This page covers its hosted endpoint (https://since98.vn/api/mcp/zalo).
Is the Zalo Business Reference (ZBS Template Message, OA) MCP server safe to use?
Zalo Business Reference (ZBS Template Message, OA) scores 70 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 Zalo Business Reference (ZBS Template Message, OA) MCP server expose?
Zalo Business Reference (ZBS Template Message, OA) exposes 7 tools: estimate_message_cost, oa_plan_compare, validate_template, check_sending_rules, choose_channel, and 2 more. Their descriptions and schemas cost roughly 2,578 tokens of context every time the server is loaded.
Does the Zalo Business Reference (ZBS Template Message, OA) MCP server require authentication?
No. We connected to Zalo Business Reference (ZBS Template Message, OA) without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Zalo Business Reference (ZBS Template Message, OA) MCP server still maintained?
Zalo Business Reference (ZBS Template Message, OA) 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 Zalo Business Reference (ZBS Template Message, OA) MCP server?
VerifyMCP ran 12 checks on Zalo Business Reference (ZBS Template Message, OA), 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 Zalo Business Reference (ZBS Template Message, OA): 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.