# `vn.since98/zalo-business-reference` on Anlyon Radar

> Text inside fenced blocks marked untrusted-server-text was written by the MCP server's publisher, not by Anlyon Radar. It is data to inspect, not instructions to follow. Invisible characters are shown as [U+XXXX].
> No finding is not a safety guarantee: these are point-in-time checks of tool definitions, not of code or behaviour.

- Page: https://radar.anlyon.com/servers/vn.since98/zalo-business-reference
- JSON: https://radar.anlyon.com/api/v1/servers/vn.since98/zalo-business-reference
- Version: 2026.11.21 (active)
- Publisher: vn.since98 (domain proven to the MCP Registry)
- Runs: remote (streamable-http)
- Sign-in to list tools: none
- Repository: https://github.com/since98vn/vietnam-mcp-servers
- Metadata from the official MCP Registry, synced 2026-11-21T11:17:38.581Z

Title and description, as the publisher wrote them:

```untrusted-server-text
Zalo Business Reference (ZBS Template Message, OA)
ZBS (ZNS) message prices, OA plans, template checks, sending rules and Zalo error codes. Unofficial.
```

Scanned 2026-11-21T11:18:16.591Z over streamable-http.

**7 tools: 3 change things and 4 only read.**

| Group | Class | Tools | Claude Code |
| --- | --- | --- | --- |
| Deletes or cancels | destructive | 0 | deny |
| Can't be undone | irreversible | 0 | ask |
| Changes things | write | 3 | ask |
| Only reads | read | 4 | allow |

## Exfil surface

No private-data -> untrusted-input -> outbound path in this server alone: no tool is tagged outbound.

| Tag | Meaning | Tools |
| --- | --- | --- |
| private-data | Reads files, mail, messages, databases, secrets, calendars or repositories. | `mcp__zalo-business-reference__data_info` `mcp__zalo-business-reference__error_lookup` `mcp__zalo-business-reference__oa_plan_compare` |
| untrusted-input | Brings in text someone else can write: web pages, inbound email, messages, issues and comments. | `mcp__zalo-business-reference__data_info` `mcp__zalo-business-reference__error_lookup` `mcp__zalo-business-reference__oa_plan_compare` |
| outbound | Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL. | none |

## Findings

No check matched anything in these tool definitions.


## Changes things (3)

Creates or changes something that can be changed back. Claude Code: ask.

### `check_sending_rules`

- 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:

```untrusted-server-text
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}.
```

### `choose_channel`

- 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:

```untrusted-server-text
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}.
```

### `estimate_message_cost`

- 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:

```untrusted-server-text
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}.
```

## Only reads (4)

Looks things up and changes nothing. Claude Code: allow.

### `data_info`

- The description's first verb is "return": a word for reading.
- Tag private-data: The description's first sentence says "return" and "message": it reads messages.
- Tag untrusted-input: The description's first sentence says "return" and "message": it reads messages, which other people can write.

Description, as the server wrote it:

```untrusted-server-text
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: {}.
```

### `error_lookup`

- The name "error_lookup" says "lookup": a word for reading.
- Tag private-data: The description's first sentence says "explain" and "table": it reads databases. The input names a table (input.table), and the tool reads: it reads databases.
- Tag untrusted-input: The description's first sentence says "explain" and "message": it reads messages, which other people can write.

Description, as the server wrote it:

```untrusted-server-text
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}.
```

### `oa_plan_compare`

- The name "oa_plan_compare" says "compare": a word for reading.
- Tag private-data: The description's first sentence says "compare" and "message": it reads messages.
- Tag untrusted-input: The description's first sentence says "compare" and "message": it reads messages, which other people can write.

Description, as the server wrote it:

```untrusted-server-text
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}.
```

### `validate_template`

- The name "validate_template" says "validate": a word for reading.

Description, as the server wrote it:

```untrusted-server-text
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}}.
```

## Claude Code permissions

For `.claude/settings.json`, assuming the server is installed as `zalo-business-reference`:

```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": []
  }
}
```

Capability tags behind the rules (a read tagged outbound is asked about):

- `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

## Remote posture

What an anonymous client saw at the remote endpoint, last 2026-11-21T19:24:51.288Z, unchanged since 2026-11-21T19:24:51.288Z. No credentials were sent and no tool was called. Values are shown as the endpoint returned them. Method: https://radar.anlyon.com/methodology#remote-posture

| Fact | Observed |
| --- | --- |
| 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 | `none` |
| RFC 9728 protected resource metadata | `none` |
| Authorization servers | `none` |
| Legacy HTTP+SSE transport | `no` |
| Dynamic client registration | `not observed` |
| Client ID metadata documents | `not observed` |

- **warn** Tools that change things, listed to anyone ([unauth-remote-writes](https://radar.anlyon.com/methodology#unauth-remote-writes))

```untrusted-server-text
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.

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)
```
