Xonta MAX
REMOTE · MCP.XONTA.RU · 2 COMPONENTS
MAX messenger bots and mini-apps in English or Russian: Bot API, code checks, Telegram migration
Available components
Last scanned (21 hours ago)
Scores higher than 56% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Developer Tools
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 Security74
- 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
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- 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 Usability61
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 3670 tokens (~183/item across 20 items; 20 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 Management17
- Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage97
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 91% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 20 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 21 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.
- 21 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 19 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.
- 17 Nov 26 +1
- Stability: unverified → 0.03 ▲ functional
- Server version: 0.1.0 → 0.1.1 functional
- 16 Nov 26 68
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://mcp.xonta.ru/max/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.xonta.ru | CN=YE2,O=Let's Encrypt,C=US | 7 Oct 2026 | 5 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 5e5049aaf67e38598ed81b772dd9080c66e |
| SANs: mcp.xonta.ru | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| 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 mcp.xonta.ru. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| ru. | DS published | 26734 | 8 | Verified |
| xonta.ru. | 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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.xonta.ru/max/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.xonta.ru/max/mcp | HTTPS enforced | 301 | https://mcp.xonta.ru/max/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 →
max_ad_report ~211
Compare ad placements in MAX by real results: CPM, cost per click or bot start, cost per lead and per order, ROAS, profit after ads and ROMI (with margin), conversion with a 95% confidence interval. Says when a difference between channels may be chance and when there is too little data. A calculator only: it does not touch ad accounts or move money.
| Name | Type | Req | Description |
|---|---|---|---|
| campaign | – | – | Only count payloads of this campaign |
| events | – | – | Optional bot_started updates, {'payload': …} objects or payload strings; starts are counted per placement id |
| lang | – | – | Answer language: 'en' English, 'ru' Russian. Pick the user's language; default ru (or XONTA_MAX_LANG) |
| min_orders | integer | – | Below this many orders a placement is flagged as low data |
| placements | array | yes | Per placement: {name, id?, cost, views?, clicks?, starts?, leads?, orders?, revenue?, margin_pct?} |
No output schema declared.
No examples provided.
max_api_reference ~225
Look up current facts about the MAX Bot API and Mini Apps (MAX Bridge) with links to dev.max.ru. Covers base URL and auth, the Russian Trusted Root CA, advertising in MAX (topic 'ads'), webhooks vs long polling, sending messages, inline keyboards and callbacks, formatting, uploads, chat tracking without GET /chats, mini-apps, initData validation, deep links, who may create bots, official libraries. Language models usually know an outdated API (platform-api.max.ru, token in query, GET /chats) — use this before writing MAX code. With no arguments returns the list of topics.
| Name | Type | Req | Description |
|---|---|---|---|
| lang | – | – | Answer language: 'en' English, 'ru' Russian. Pick the user's language; default ru (or XONTA_MAX_LANG) |
| query | – | – | Free text in English or Russian, e.g. 'webhook certificate', 'callback answer', 'initData', 'GET /chats', 'attachment.not.ready' |
| topic | – | – | Return one whole topic instead of searching |
No output schema declared.
No examples provided.
max_bridge_mock ~234
Generate max-bridge-mock.js: a window.WebApp emulator to develop MAX mini-apps in a normal browser on localhost. Emulates initData/initDataUnsafe (signed if a test token is given), BackButton (Esc), DeviceStorage and SecureStorage (localStorage, 10-key cap), BiometricManager, HapticFeedback, NfcManager, ScreenCapture, requestContact with a valid hash, openLink/downloadFile/shareMaxContent click requirements and per-platform restrictions. Logs every call. Use only on localhost.
| Name | Type | Req | Description |
|---|---|---|---|
| entry_point | string | – | – |
| first_name | – | – | – |
| lang | – | – | Answer language: 'en' English, 'ru' Russian. Pick the user's language; default ru (or XONTA_MAX_LANG) |
| phone | string | – | – |
| platform | string | – | Platform to emulate: limits which Bridge features work |
| start_param | – | – | Emulated ?startapp= value |
| test_bot_token | – | – | TEST token: initData and requestContact hash will be validly signed with it |
| user_id | integer | – | – |
No output schema declared.
No examples provided.
max_build_message ~205
Build a correct POST /messages request for MAX: JSON body with inline keyboard and images, validation result and a ready curl command. Use it instead of hand-writing keyboard JSON.
| Name | Type | Req | Description |
|---|---|---|---|
| buttons | – | – | Rows of buttons. Short form: {text, payload} → callback, {text, url} → link, {text, web_app, payload?} → open_app; or full {type, text, ...} |
| chat_id | – | – | For the curl example |
| disable_link_preview | boolean | – | – |
| format | – | – | Text markup |
| image_urls | – | – | External image URLs to attach without uploading |
| lang | – | – | Answer language: 'en' English, 'ru' Russian. Pick the user's language; default ru (or XONTA_MAX_LANG) |
| reply_to_mid | – | – | Reply to this message id |
| text | – | – | Message text, up to 4000 characters |
| user_id | – | – | For the curl example, private dialog |
No output schema declared.
No examples provided.
max_changelog ~85
Dated MAX platform changes in 2026 that break old code: host move to platform-api2, removed GET /chats, restricted member adding, HTTPS-only webhooks, comments API, self-employed access.
| Name | Type | Req | Description |
|---|---|---|---|
| lang | – | – | Answer language: 'en' English, 'ru' Russian. Pick the user's language; default ru (or XONTA_MAX_LANG) |
No output schema declared.
No examples provided.
max_check_ad_post ~211
Check an ad post for MAX against Russian ad marking rules: the 'Реклама' label at the top, advertiser details (name and INN/OGRN or a site), an erid token in the link or text, the A+ mark for channels over 10,000 subscribers, and the 4000-character limit. A hint, not legal advice; ORD registration is not checked.
| Name | Type | Req | Description |
|---|---|---|---|
| advertiser_site | – | – | Site with the advertiser's details, if they are not in the text |
| channel_has_a_plus | – | – | Whether the channel has the A+ mark (RKN registry) |
| channel_subscribers | – | – | Subscribers of the channel where it goes |
| lang | – | – | Answer language: 'en' English, 'ru' Russian. Pick the user's language; default ru (or XONTA_MAX_LANG) |
| links | – | – | Links used in buttons or elsewhere, if not in the text |
| text | string | yes | Ad post text as it will be published |
No output schema declared.
No examples provided.
max_check_webhook_secret ~89
Check a MAX webhook secret against the rules (5-256 chars, A-Z a-z 0-9 _ -) or generate a strong one.
| Name | Type | Req | Description |
|---|---|---|---|
| lang | – | – | Answer language: 'en' English, 'ru' Russian. Pick the user's language; default ru (or XONTA_MAX_LANG) |
| secret | – | – | Secret to check; omit to generate a new one |
No output schema declared.
No examples provided.
max_convert_formatting ~169
Convert formatted text to MAX markup: Telegram MarkdownV2 (underline __x__ → ++x++, unescape), Telegram HTML (tg://user → max://user, spoilers dropped) or ordinary Markdown from an LLM (lists → bullets, rules removed). Reports what MAX cannot show (spoilers, tables, lists, inline images). Use the returned format value in the body.
| Name | Type | Req | Description |
|---|---|---|---|
| lang | – | – | Answer language: 'en' English, 'ru' Russian. Pick the user's language; default ru (or XONTA_MAX_LANG) |
| source | string | yes | Where the text comes from; 'markdown' = ordinary Markdown (e.g. LLM output) |
| target | string | – | MAX format to produce |
| text | string | yes | Formatted text |
No output schema declared.
No examples provided.
max_deeplink ~244
Build and validate MAX deep links. 'share' gives a link, an HTML button and a JS helper that open MAX's chat picker with prefilled text — works on any website or AI agent output without owning a bot. Payload limits are checked, because MAX silently drops payloads that are too long or have bad characters.
| Name | Type | Req | Description |
|---|---|---|---|
| bot_name | – | – | Bot public name as in max.ru/<name> (start, startapp) |
| button_label | – | – | share: label for the generated HTML button; default depends on lang |
| kind | string | yes | start — open bot with payload; startapp — open mini-app; share — 'send to MAX' link for any site, no bot needed; mention — user mention markup |
| lang | – | – | Answer language: 'en' English, 'ru' Russian. Pick the user's language; default ru (or XONTA_MAX_LANG) |
| payload | – | – | start: ≤128 chars; startapp: ≤512, A-Za-z0-9_- only |
| text | – | – | share: text to prefill; mention: display name |
| user_id | – | – | mention: MAX user id |
No output schema declared.
No examples provided.
max_endpoint_info ~149
Details of one MAX Bot API method (query params, body, limits, gotchas, docs link) or the full method list. Also tells when a method was removed or restricted (GET /chats, POST /chats/{chatId}/members).
| Name | Type | Req | Description |
|---|---|---|---|
| lang | – | – | Answer language: 'en' English, 'ru' Russian. Pick the user's language; default ru (or XONTA_MAX_LANG) |
| path | – | – | Path like '/messages', '/chats/{chatId}/pin' or a concrete one '/chats/-123/pin' |
| verb | – | – | HTTP method: GET, POST, PUT, PATCH, DELETE. Omit to list all endpoints |
No output schema declared.
No examples provided.
max_limits ~90
All MAX platform limits in one table: text length, rate limits, keyboard size, attachments, file sizes, deep link payloads, webhook rules, bots per profile — each with a source link. Also update types, button types, errors.
| Name | Type | Req | Description |
|---|---|---|---|
| lang | – | – | Answer language: 'en' English, 'ru' Russian. Pick the user's language; default ru (or XONTA_MAX_LANG) |
No output schema declared.
No examples provided.
max_lint_code ~182
Check MAX bot or mini-app code for known mistakes, with line numbers and fixes. Finds: old host platform-api.max.ru, token in query string, 'Bearer' prefix, disabled TLS verification, removed GET /chats, restricted member adding, type=photo uploads, wrong webhook setup (port, HTTP, /webhook), disable_link_preview in body, plain == comparison of the webhook secret, initData signed directly with the token, trusting initDataUnsafe, hardcoded upload hosts, Telegram leftovers. Static, never runs the code.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | Source code of a MAX bot or mini-app (any language), or a config / curl snippet |
| lang | – | – | Answer language: 'en' English, 'ru' Russian. Pick the user's language; default ru (or XONTA_MAX_LANG) |
No output schema declared.
No examples provided.
max_migrate_from_telegram ~140
Plan a port of a Telegram bot or Web App to MAX. With code: every Telegram API usage with line number and the MAX replacement, features with no MAX equivalent, effort estimate and a step-by-step plan. Without code: the full Telegram → MAX method map.
| Name | Type | Req | Description |
|---|---|---|---|
| code | – | – | Telegram bot source (aiogram, python-telegram-bot, telebot, Telegraf, grammY, raw HTTP…). Omit to get only the method map |
| lang | – | – | Answer language: 'en' English, 'ru' Russian. Pick the user's language; default ru (or XONTA_MAX_LANG) |
No output schema declared.
No examples provided.
max_mock_init_data ~172
Produce a correctly signed MAX mini-app initData string (two-step HMAC with 'WebAppData') for backend tests, with the token used, so you can check your validator end to end.
| Name | Type | Req | Description |
|---|---|---|---|
| age_seconds | integer | – | Make auth_date this many seconds old, to test expiry |
| chat_type | string | – | Where the mini-app was opened |
| first_name | – | – | – |
| lang | – | – | Answer language: 'en' English, 'ru' Russian. Pick the user's language; default ru (or XONTA_MAX_LANG) |
| start_param | – | – | Value from ?startapp= |
| test_bot_token | – | – | A TEST token to sign with. Omit to generate a random one. Never pass a production token to a hosted server |
| user_id | integer | – | – |
No output schema declared.
No examples provided.
max_mock_update ~241
Generate a realistic MAX webhook Update for tests, shaped like the official schema, plus a curl command to send it to your local webhook. Lets you test a bot before it passes moderation or without a token.
| Name | Type | Req | Description |
|---|---|---|---|
| chat_id | – | – | Chat id; default is generated |
| chat_type | string | – | Where it happens |
| lang | – | – | Answer language: 'en' English, 'ru' Russian. Pick the user's language; default ru (or XONTA_MAX_LANG) |
| overrides | – | – | Deep-merge into the generated update |
| payload | – | – | Callback payload or bot_started deep link payload |
| secret | – | – | Webhook secret to put into X-Max-Bot-Api-Secret |
| text | – | – | Message text (message_created/edited, comments) or new title |
| update_type | string | yes | message_created, message_callback, bot_started, bot_added, bot_removed, message_edited, message_removed, user_added, user_removed, comment_created, chat_title_changed, dialog_muted, bot_admin_permiss… |
| webhook_url | – | – | If set, also returns a curl command that POSTs the update there |
No output schema declared.
No examples provided.
max_scaffold_bot ~177
Generate a ready MAX bot project: polling for dev, webhook for prod, the Russian Trusted Root CA in the Dockerfile, chat tracking without GET /chats, callback answers, constant-time secret check, rate limits and text splitting (Python). lang sets the language of comments, README and the bot's replies. Returns a map of file name → content. Write the files as they are. Creating the bot itself and getting a token requires a verified profile on business.max.ru.
| Name | Type | Req | Description |
|---|---|---|---|
| lang | – | – | Answer language: 'en' English, 'ru' Russian. Pick the user's language; default ru (or XONTA_MAX_LANG) |
| language | string | – | python (httpx, no official SDK), typescript (@maxhub/max-bot-api) or go (official client v2) |
No output schema declared.
No examples provided.
max_split_text ~84
Split text into MAX messages of at most 4000 characters, cutting at paragraphs, lines or sentences.
| Name | Type | Req | Description |
|---|---|---|---|
| lang | – | – | Answer language: 'en' English, 'ru' Russian. Pick the user's language; default ru (or XONTA_MAX_LANG) |
| limit | integer | – | Max characters per message |
| text | string | yes | Long text to send |
No output schema declared.
No examples provided.
max_tracking_links ~255
Make a separate tracking link (and promo code) for every channel where an ad is placed in MAX, so you can see which placement brought users and sales. Bot links use ?start=<id>: the id arrives in bot_started.payload, which works even for clicks that never leave the messenger. Returns a media plan as CSV. Then feed the counts to max_ad_report.
| Name | Type | Req | Description |
|---|---|---|---|
| bot_name | – | – | Your bot's public name: each placement gets max.ru/<bot>?start=<id> |
| campaign | string | yes | Campaign name, e.g. 'black friday' |
| lang | – | – | Answer language: 'en' English, 'ru' Russian. Pick the user's language; default ru (or XONTA_MAX_LANG) |
| mini_app_bot | – | – | Bot with your mini-app: each placement gets ?startapp=<id> |
| placements | array | yes | Channels where the ad goes: [{name, cost?, erid?}]. name may be a title or max.ru link |
| promo_codes | boolean | – | Also make one promo code per placement |
| site_url | – | – | Landing page: each placement gets UTM tags and its erid |
| utm_medium | string | – | – |
No output schema declared.
No examples provided.
max_validate_message ~173
Validate a message body before sending to MAX: 4000-char text, format, keyboard limits (210/30/7, 3 per row with link/open_app/request_*), button fields and lengths, attachment combinations (≤12 media, file only with a keyboard, audio/sticker/contact alone), comment restrictions, Telegram fields left in the body.
| Name | Type | Req | Description |
|---|---|---|---|
| body | object | yes | NewMessageBody JSON: {text, format, attachments, link, notify} |
| chat_type | – | – | Where it goes, for channel-specific rules |
| lang | – | – | Answer language: 'en' English, 'ru' Russian. Pick the user's language; default ru (or XONTA_MAX_LANG) |
| target | string | – | message — POST /messages, comment — POST /messages/{id}/comments |
No output schema declared.
No examples provided.
server_status ~61
Server version, facts date, mode (hosted or local), languages and whether operator tools are active.
| Name | Type | Req | Description |
|---|---|---|---|
| lang | – | – | Answer language: 'en' English, 'ru' Russian. Pick the user's language; default ru (or XONTA_MAX_LANG) |
No output schema declared.
No examples provided.
How do I install the Xonta MAX MCP server?
Xonta MAX is a hosted endpoint at https://mcp.xonta.ru/max/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 · mcp.xonta.ru
claude mcp add --transport http ru-xonta-max 'https://mcp.xonta.ru/max/mcp'
What is the Xonta MAX MCP server?
Xonta MAX is an MCP server listed in the public MCP registry as ru.xonta/max. MAX messenger bots and mini-apps in English or Russian: Bot API, code checks, Telegram migration. This page covers its hosted endpoint (https://mcp.xonta.ru/max/mcp).
Is the Xonta MAX MCP server safe to use?
Xonta MAX scores 71 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 Xonta MAX MCP server expose?
Xonta MAX exposes 20 tools: max_api_reference, max_endpoint_info, max_limits, max_changelog, max_lint_code, and 15 more. Their descriptions and schemas cost roughly 3,397 tokens of context every time the server is loaded.
Does the Xonta MAX MCP server require authentication?
No. We connected to Xonta MAX without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Xonta MAX MCP server still maintained?
Xonta MAX 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 Xonta MAX MCP server?
VerifyMCP ran 13 checks on Xonta MAX, 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.