Zalo Business Reference (ZBS Template Message, OA) MCP server
vn.since98/zalo-business-referencesince98.vnstreamable-httpv2026.11.21Scanned
ZBS (ZNS) message prices, OA plans, template checks, sending rules and Zalo error codes. Unofficial.
7 tools: 3 change things and 4 only read.
- Reads private data · 3
- Reads text others write · 3
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
3 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the Zalo Business Reference (ZBS Template Message, OA) MCP server can do
The Zalo Business Reference (ZBS Template Message, OA) MCP server is published by since98.vn, a domain the MCP Registry verified. It has 7 tools. It can create or change data (3 tools: estimate_message_cost, check_sending_rules and choose_channel), but cannot delete data. 4 tools only read.
3 tools read private data (oa_plan_compare, error_lookup and data_info); 3 tools bring in text other people can write (oa_plan_compare, error_lookup and data_info).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 21, 2026, version 2026.11.21.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
7 tools
Changes things 3Claude Code: ask
check_sending_rulesCheck 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…No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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}.
Annotations the server declares
- title: Check ZBS sending window, quota and promotion limits
- readOnlyHint: true
- idempotentHint: true
- destructiveHint: false
- openWorldHint: false
choose_channelSuggest 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 4…No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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}.
Annotations the server declares
- title: Choose a Zalo channel for a task
- readOnlyHint: true
- idempotentHint: true
- destructiveHint: false
- openWorldHint: false
estimate_message_costEstimate 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_r…No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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}.
Annotations the server declares
- title: ZBS template message cost (Zalo)
- readOnlyHint: true
- idempotentHint: true
- destructiveHint: false
- openWorldHint: false
Only reads 4Show 4 read-only tools
data_infoReturn 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, th…Reads private dataReads text others writeNo findings
Why it is in this group
- The description's first verb is "return": a word for reading.
What it can reach
- private-dataThe description's first sentence says "return" and "message": it reads messages.
- untrusted-inputThe description's first sentence says "return" and "message": it reads messages, which other people can write.
Description, as the server wrote it 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: {}.
Annotations the server declares
- title: Zalo reference data: sources and gaps
- readOnlyHint: true
- idempotentHint: true
- destructiveHint: false
- openWorldHint: false
error_lookupExplain 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 thi…Reads private dataReads text others writeNo findings
Why it is in this group
- The name "error_lookup" says "lookup": a word for reading.
What it can reach
- private-dataThe description's first sentence says "explain" and "table": it reads databases.
- private-dataThe input names a table (input.table), and the tool reads: it reads databases.
- untrusted-inputThe description's first sentence says "explain" and "message": it reads messages, which other people can write.
Description, as the server wrote it 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}.
Annotations the server declares
- title: Zalo error code lookup
- readOnlyHint: true
- idempotentHint: true
- destructiveHint: false
- openWorldHint: false
oa_plan_compareCompare 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 reque…Reads private dataReads text others writeNo findings
Why it is in this group
- The name "oa_plan_compare" says "compare": a word for reading.
What it can reach
- private-dataThe description's first sentence says "compare" and "message": it reads messages.
- untrusted-inputThe description's first sentence says "compare" and "message": it reads messages, which other people can write.
Description, as the server wrote it 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}.
Annotations the server declares
- title: Zalo OA plan comparison
- readOnlyHint: true
- idempotentHint: true
- destructiveHint: false
- openWorldHint: false
validate_templateCheck 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 …No findings
Why it is in this group
- The name "validate_template" says "validate": a word for reading.
Description, as the server wrote it 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}}.
Annotations the server declares
- title: Check a ZBS template draft (formal rules)
- readOnlyHint: true
- idempotentHint: true
- destructiveHint: false
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged outbound.
- Reads private data3
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write3
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 21, 2026, 19:24 UTC, unchanged since Nov 21, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 3
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 3 tools that change things (3 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://since98.vn/api/mcp/zalo: tools/list returned 7 tools to an anonymous client, including estimate_message_cost (write), check_sending_rules (write), choose_channel (write)
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 2026.11.21. Values in angle brackets are yours to fill in.
claude mcp add --transport http zalo-business-reference https://since98.vn/api/mcp/zaloclaude mcp add --transport http zalo-business-reference https://since98.vn/api/mcp/zaloRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__zalo-business-reference__oa_plan_compare",
"mcp__zalo-business-reference__validate_template",
"mcp__zalo-business-reference__error_lookup",
"mcp__zalo-business-reference__data_info"
],
"ask": [
"mcp__zalo-business-reference__estimate_message_cost",
"mcp__zalo-business-reference__check_sending_rules",
"mcp__zalo-business-reference__choose_channel"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as zalo-business-reference. Review it before you use it.
Capability tags behind 3 rules
- mcp__zalo-business-reference__oa_plan_compare private-data, untrusted-input
- mcp__zalo-business-reference__error_lookup private-data, untrusted-input
- mcp__zalo-business-reference__data_info private-data, untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/vn.since98/zalo-business-reference/verify?hash=4487661be74def80eb72968f15c2e062109f02d8ef75babed730c78ce513bbca" | jq -e '.changed == false'Pinned hash 4487661be74d, from Nov 21, 2026, 11:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/vn.since98/zalo-business-reference/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/vn.since98/zalo-business-reference)Source: MCP Registry · repository. Synced Nov 21, 2026, 11:17 UTC.
Zalo Business Reference (ZBS Template Message, OA) MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Zalo Business Reference (ZBS Template Message, OA) MCP server safe?
- No scan can promise that. What its definitions show: 7 tools, 3 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Zalo Business Reference (ZBS Template Message, OA) MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Zalo Business Reference (ZBS Template Message, OA) MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the Zalo Business Reference (ZBS Template Message, OA) MCP server have?
- 7 tools: 3 write, 4 read. estimate_message_cost, check_sending_rules, choose_channel, oa_plan_compare, validate_template, error_lookup and data_info.
Does the Zalo Business Reference (ZBS Template Message, OA) MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Zalo Business Reference (ZBS Template Message, OA) MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Zalo Business Reference (ZBS Template Message, OA) MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 21, 2026.