Skip to content

MCP servers › ru.xonta › max

MCP server · registry snapshot 2026-11-16 · last tested 2026-11-16

max MCP server

Registry name ru.xonta/max

Xonta MAX — the publisher's title

by xonta.ru · domain (the registry's namespace rule)repository owner on GitHub: mrsergeiluzhnov (personal account)Source ↗PyPI ↗Website ↗

MAX messenger bots and mini-apps in English or Russian: Bot API, code checks, Telegram migration — the publisher's description

7 of 8 record checks metRead-only · tools listed 2026-11-16version 0.1.0PythonMITstandard input/output, streamable HTTP20 tools

Summary

ru.xonta/max is a remote and local MCP server listed in the official MCP registry at version 0.1.0, under the namespace of the domain xonta.ru. Its linked repository is github.com/mrsergeiluzhnov/xonta-max-mcp; GitHub reports its owner as mrsergeiluzhnov, a personal account. On 2026-11-16 ProtocolProbe connected to it in read-only mode and read its inventory: 20 tools, 0 resources and 0 prompts.

Record checks

7 of 8 record checks met · 1 does not apply

  • met: Registry entry is active and says how to run it
  • met: Source repository link opens
  • met: Repository is not archived
  • met: Code pushed to the repository in the 90 days before our check
  • not met: Repository publishes a security policy (SECURITY.md)
  • met: Package names its licence with a standard (SPDX) identifier
  • met: The version the registry lists can be installed and is not withdrawn
  • not applicable: npm package carries build provenance (attestation)
  • met: No known critical or high advisory in the package or its dependencies
  • Not ranked by downloads: no download figure available
  • Not ranked by stars: 0 stars (ranked from 10)

From public records, not a safety rating. Each check with its reason · Is it safe to install?

Operate this server? Correct a fact · README badge · Run the checks yourself · Claim it

Key facts

Runs
remote and local package
Transport
standard input/output, streamable HTTP
Your own values
none declared (not a guarantee)
Sign-in
none needed to open a session
Package
PyPI · listed version current
License
MIT
Dependencies
no known high or critical advisories
Repository
public
Tools
20
Last tested
2026-11-16

Tool list size

10,538 tokens on Claude Opus 5.5

Added to every request that loads this server's tools (20 tools). Counted with Anthropic's token counter on 2026-11-16, from the tool list we read on 2026-11-16. Median across 28,560 counted servers: 2,657 tokens. How it is counted

How a client gets in

Connects without signing in

Read from the server's public metadata on 2026-11-16 (mcp.xonta.ru), in our read-only connection; no tool was called. It may have changed since. How it is read

Tool list at the three APIs

Not sent yet for this version (0.1.0).

Add to your client

How fresh this is

Live-tested
yes, a real session (not a text-only review)
Last tested
2026-11-16
Mode
read-only (no tool calls)
Latest version
0.1.0, published 2026-11-16 (registry, as of the 2026-11-16 snapshot)
First listed version
2026-11-16 (earliest version still in the registry; older removed versions would be earlier)
Registry data
snapshot 2026-11-16
Package and repository
checked 2026-11-16
Engine
mcp-runtime-engine@0.1.0 · sdk@1.32.0

Dead or stale signals

None found in the records we hold

Looked for and not found: deprecated in the registry; listed version cannot be installed or is withdrawn; repository link does not open; repository archived; no push in over 365 days. Each line is a dated fact from a public record. It does not say whether the server still works, and a record can change after the date shown.

Changes since the last refresh

New in the registry: not in the list of 2026-11-15, listed on 2026-11-16 with version 0.1.0 (published 2026-11-16).

Source: the official MCP Registry list on 2026-11-15 and on 2026-11-16.

What it is

What does this server offer?

Observed inventory
20tools
0resources
0prompts

None of its 20 tools are described as changing anything. For 20 the reading was uncertain, so no mark is shown.

  • max_api_reference

    “Look up current facts about the MAX Bot API and Mini Apps (MAX Bridge) with links to dev.max.ru.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    3 inputs
    • querystring or null“Free text in English or Russian, e.g.”
    • topicstring or null“Return one whole topic instead of searching”
    • langstring or null“Answer language: 'en' English, 'ru' Russian.”
  • max_endpoint_info

    “Details of one MAX Bot API method (query params, body, limits, gotchas, docs link) or the full method list.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    3 inputs
    • verbstring or null“HTTP method: GET, POST, PUT, PATCH, DELETE.”
    • pathstring or null“Path like '/messages', '/chats/{chatId}/pin' or a concrete one '/chats/-123/pin'”
    • langstring or null“Answer language: 'en' English, 'ru' Russian.”
  • max_limits

    “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.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    1 input
    • langstring or null“Answer language: 'en' English, 'ru' Russian.”
  • max_changelog

    “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.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    1 input
    • langstring or null“Answer language: 'en' English, 'ru' Russian.”
  • max_lint_code

    “Check MAX bot or mini-app code for known mistakes, with line numbers and fixes.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    2 inputs, 1 required
    • codestringrequired“Source code of a MAX bot or mini-app (any language), or a config / curl snippet”
    • langstring or null“Answer language: 'en' English, 'ru' Russian.”
  • max_migrate_from_telegram

    “Plan a port of a Telegram bot or Web App to MAX.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    2 inputs
    • codestring or null“Telegram bot source (aiogram, python-telegram-bot, telebot, Telegraf, grammY, raw HTTP…).”
    • langstring or null“Answer language: 'en' English, 'ru' Russian.”
  • max_scaffold_bot

    “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, rat…”

    Publisher declares: read-only yes · destructive no · idempotent no · open-world no

    2 inputs
    • languagestring“python (httpx, no official SDK), typescript (@maxhub/max-bot-api) or go (official client v2)”
    • langstring or null“Answer language: 'en' English, 'ru' Russian.”
  • max_validate_message

    “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 medi…”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    4 inputs, 1 required
    • bodyobjectrequired“NewMessageBody JSON: {text, format, attachments, link, notify}”
    • targetstring“message — POST /messages, comment — POST /messages/{id}/comments”
    • chat_typestring or null“Where it goes, for channel-specific rules”
    • langstring or null“Answer language: 'en' English, 'ru' Russian.”
  • max_build_message

    “Build a correct POST /messages request for MAX: JSON body with inline keyboard and images, validation result and a ready curl command.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    9 inputs
    • textstring or null“Message text, up to 4000 characters”
    • formatstring or null“Text markup”
    • buttonsarray or null“Rows of buttons.”
    • image_urlsarray or null“External image URLs to attach without uploading”
    • reply_to_midstring or null“Reply to this message id”
    • chat_idinteger or null“For the curl example”
    • user_idinteger or null“For the curl example, private dialog”
    • disable_link_previewboolean
    • langstring or null“Answer language: 'en' English, 'ru' Russian.”
  • max_split_text

    “Split text into MAX messages of at most 4000 characters, cutting at paragraphs, lines or sentences.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    3 inputs, 1 required
    • textstringrequired“Long text to send”
    • limitinteger“Max characters per message”
    • langstring or null“Answer language: 'en' English, 'ru' Russian.”
  • max_convert_formatting

    “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 → bulle…”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    4 inputs, 2 required
    • textstringrequired“Formatted text”
    • sourcestringrequired“Where the text comes from; 'markdown' = ordinary Markdown (e.g.”
    • targetstring“MAX format to produce”
    • langstring or null“Answer language: 'en' English, 'ru' Russian.”
  • max_deeplink

    “Build and validate MAX deep links.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    7 inputs, 1 required
    • kindstringrequired“start — open bot with payload; startapp — open mini-app; share — 'send to MAX' link for any site, no bot needed; mention — user mention markup”
    • bot_namestring or null“Bot public name as in max.ru/<name> (start, startapp)”
    • payloadstring or null“start: ≤128 chars; startapp: ≤512, A-Za-z0-9_- only”
    • textstring or null“share: text to prefill; mention: display name”
    • user_idinteger or null“mention: MAX user id”
    • button_labelstring or null“share: label for the generated HTML button; default depends on lang”
    • langstring or null“Answer language: 'en' English, 'ru' Russian.”
Show 8 more tools
  • max_mock_update

    “Generate a realistic MAX webhook Update for tests, shaped like the official schema, plus a curl command to send it to your local webhook.”

    Publisher declares: read-only yes · destructive no · idempotent no · open-world no

    9 inputs, 1 required
    • update_typestringrequired“message_created, message_callback, bot_started, bot_added, bot_removed, message_edited, message_removed, user_added, user_removed, comment_created, chat_title_…”
    • textstring or null“Message text (message_created/edited, comments) or new title”
    • payloadstring or null“Callback payload or bot_started deep link payload”
    • chat_typestring“Where it happens”
    • chat_idinteger or null“Chat id; default is generated”
    • overridesobject or null“Deep-merge into the generated update”
    • webhook_urlstring or null“If set, also returns a curl command that POSTs the update there”
    • secretstring or null“Webhook secret to put into X-Max-Bot-Api-Secret”
    • langstring or null“Answer language: 'en' English, 'ru' Russian.”
  • max_mock_init_data

    “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.”

    Publisher declares: read-only yes · destructive no · idempotent no · open-world no

    7 inputs
    • test_bot_tokenstring or null“A TEST token to sign with.”
    • user_idinteger
    • first_namestring or null
    • chat_typestring“Where the mini-app was opened”
    • start_paramstring or null“Value from ?startapp=”
    • age_secondsinteger“Make auth_date this many seconds old, to test expiry”
    • langstring or null“Answer language: 'en' English, 'ru' Russian.”
  • max_bridge_mock

    “Generate max-bridge-mock.js: a window.WebApp emulator to develop MAX mini-apps in a normal browser on localhost.”

    Publisher declares: read-only yes · destructive no · idempotent no · open-world no

    8 inputs
    • platformstring“Platform to emulate: limits which Bridge features work”
    • start_paramstring or null“Emulated ?startapp= value”
    • test_bot_tokenstring or null“TEST token: initData and requestContact hash will be validly signed with it”
    • user_idinteger
    • first_namestring or null
    • phonestring
    • entry_pointstring
    • langstring or null“Answer language: 'en' English, 'ru' Russian.”
  • max_check_webhook_secret

    “Check a MAX webhook secret against the rules (5-256 chars, A-Z a-z 0-9 _ -) or generate a strong one.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    2 inputs
    • secretstring or null“Secret to check; omit to generate a new one”
    • langstring or null“Answer language: 'en' English, 'ru' Russian.”
  • server_statuson 12 other servers

    “Server version, facts date, mode (hosted or local), languages and whether operator tools are active.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    1 input
    • langstring or null“Answer language: 'en' English, 'ru' Russian.”
  • max_tracking_links

    “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.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    8 inputs, 2 required
    • campaignstringrequired“Campaign name, e.g.”
    • placementsarrayrequired“Channels where the ad goes: [{name, cost?, erid?}].”
    • bot_namestring or null“Your bot's public name: each placement gets max.ru/<bot>?start=<id>”
    • mini_app_botstring or null“Bot with your mini-app: each placement gets ?startapp=<id>”
    • site_urlstring or null“Landing page: each placement gets UTM tags and its erid”
    • utm_mediumstring
    • promo_codesboolean“Also make one promo code per placement”
    • langstring or null“Answer language: 'en' English, 'ru' Russian.”
  • max_ad_report

    “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.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    5 inputs, 1 required
    • placementsarrayrequired“Per placement: {name, id?, cost, views?, clicks?, starts?, leads?, orders?, revenue?, margin_pct?}”
    • eventsarray or null“Optional bot_started updates, {'payload': …} objects or payload strings; starts are counted per placement id”
    • campaignstring or null“Only count payloads of this campaign”
    • min_ordersinteger“Below this many orders a placement is flagged as low data”
    • langstring or null“Answer language: 'en' English, 'ru' Russian.”
  • max_check_ad_post

    “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 channel…”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    6 inputs, 1 required
    • textstringrequired“Ad post text as it will be published”
    • linksarray or null“Links used in buttons or elsewhere, if not in the text”
    • channel_subscribersinteger or null“Subscribers of the channel where it goes”
    • channel_has_a_plusboolean or null“Whether the channel has the A+ mark (RKN registry)”
    • advertiser_sitestring or null“Site with the advertiser's details, if they are not in the text”
    • langstring or null“Answer language: 'en' English, 'ru' Russian.”

Each quoted sentence is the first sentence of the publisher’s own description. The kind of tool and the “changes data” mark are our AI model’s reading of that description, not something we tested: two differently worded runs had to agree, otherwise no label is shown, and nobody has checked them by hand. A tool without the “changes data” mark is described as only reading, searching or calculating, or the two runs did not agree. No tool was called. Read the publisher’s full description before relying on it. “Publisher declares” lists the hints the server itself sends with the tool (MCP annotations: read-only, destructive, idempotent, open-world); they are the publisher's claims, not checked by us. Inputs are the parameters in the tool's own input schema: name, declared type, whether it is required, and the first sentence of its description. Read 2026-11-16.

How well are its tools described?

Features #4 and #5

How clearly this server's own tool descriptions say what a tool does, and how consistent its tool list is. The first part is an AI model's yes/no reading of each description; the second part is counted. We do not turn it into a grade.

Descriptions

AI reading of each description

No AI reading was available for this server's tools (the two runs did not agree, or the listing was not reviewed).

Counted from the listing

Parameters with a description
91% of 87
Tools with a description
100% of 20
Typical description length
285 characters

The tool set

Counted from the listing

Tools
20
Size of the list
about 6,460 tokens for an agent to load (characters ÷ 4)
Naming
20 of 20 names use snake_case

AI reading: easy to mix up

No pair found.

The AI items cover 0 of 20 tools: for a tool where two differently worded runs disagreed, that item is left out. They were not checked by hand, and no tool was called. “Easy to mix up” means two tools whose names or descriptions overlap without saying how they differ; the AI found none. We do not rate whether the tool set is complete or whether side effects are spelled out, because our AI reading of those was not reliable enough.

How do I add it to my client?

Config from the registry entry

From the PyPI package xonta-max-mcp

Add to CursorAn install link in the format Cursor documents, holding the Cursor config below. The command runs the publisher’s code on your machine.

Claude Desktop · claude_desktop_config.json (Settings → Developer → Edit Config)
{
  "mcpServers": {
    "max": {
      "command": "uvx",
      "args": [
        "xonta-max-mcp==0.1.0"
      ]
    }
  }
}
Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json
{
  "mcpServers": {
    "max": {
      "command": "uvx",
      "args": [
        "xonta-max-mcp==0.1.0"
      ]
    }
  }
}
VS Code · .vscode/mcp.json
{
  "servers": {
    "max": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "xonta-max-mcp==0.1.0"
      ]
    }
  }
}
VS Code (command line) · Bash or zsh terminal (macOS, Linux)
code --add-mcp '{"name":"max","type":"stdio","command":"uvx","args":["xonta-max-mcp==0.1.0"]}'
Claude Code
claude mcp add --transport stdio max -- uvx xonta-max-mcp==0.1.0
Cline · cline_mcp_settings.json (Cline CLI: ~/.cline/data/settings/; in the editor: MCP Servers → Configure → Configure MCP Servers)
{
  "mcpServers": {
    "max": {
      "command": "uvx",
      "args": [
        "xonta-max-mcp==0.1.0"
      ],
      "disabled": false,
      "autoApprove": []
    }
  }
}
Gemini CLI · ~/.gemini/settings.json, or .gemini/settings.json in a project
{
  "mcpServers": {
    "max": {
      "command": "uvx",
      "args": [
        "xonta-max-mcp==0.1.0"
      ]
    }
  }
}
OpenAI Codex · ~/.codex/config.toml, or .codex/config.toml in a trusted project
[mcp_servers.max]
command = "uvx"
args = ["xonta-max-mcp==0.1.0"]
Zed · Zed settings file (command: zed: open settings file)
{
  "context_servers": {
    "max": {
      "command": "uvx",
      "args": [
        "xonta-max-mcp==0.1.0"
      ]
    }
  }
}
Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+
npx @modelcontextprotocol/inspector@2.11.0 -- uvx xonta-max-mcp==0.1.0
  • Optional settings the entry also lists (left out above): MAX_BOT_TOKEN, MAX_CA_FILE, XONTA_MAX_LANG.
  • This runs the publisher's code on your machine (uvx). Read its README first.
  • The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.

From the remote endpoint (Streamable HTTP)

We connected to this URL on 2026-11-16 (a read-only session: no tool was called).

Add to CursorAn install link in the format Cursor documents, holding the Cursor config below.

Claude Desktop or claude.ai
Settings → Connectors → Add custom connector, then paste:
https://mcp.xonta.ru/max/mcp
Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json
{
  "mcpServers": {
    "max": {
      "url": "https://mcp.xonta.ru/max/mcp"
    }
  }
}
VS Code · .vscode/mcp.json
{
  "servers": {
    "max": {
      "type": "http",
      "url": "https://mcp.xonta.ru/max/mcp"
    }
  }
}
VS Code (command line) · Bash or zsh terminal (macOS, Linux)
code --add-mcp '{"name":"max","type":"http","url":"https://mcp.xonta.ru/max/mcp"}'
Claude Code
claude mcp add --transport http max https://mcp.xonta.ru/max/mcp
Cline · cline_mcp_settings.json (Cline CLI: ~/.cline/data/settings/; in the editor: MCP Servers → Configure → Configure MCP Servers)
{
  "mcpServers": {
    "max": {
      "type": "streamableHttp",
      "url": "https://mcp.xonta.ru/max/mcp",
      "disabled": false,
      "autoApprove": []
    }
  }
}
Gemini CLI · ~/.gemini/settings.json, or .gemini/settings.json in a project
{
  "mcpServers": {
    "max": {
      "httpUrl": "https://mcp.xonta.ru/max/mcp"
    }
  }
}
OpenAI Codex · ~/.codex/config.toml, or .codex/config.toml in a trusted project
[mcp_servers.max]
url = "https://mcp.xonta.ru/max/mcp"
Zed · Zed settings file (command: zed: open settings file)
{
  "context_servers": {
    "max": {
      "url": "https://mcp.xonta.ru/max/mcp"
    }
  }
}
Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+
npx @modelcontextprotocol/inspector@2.11.0 --server-url https://mcp.xonta.ru/max/mcp --transport http
  • The server runs on the operator's infrastructure; it may ask you to sign in when you first connect.
  • Zed's docs we read on 2026-10-26 describe remote servers by URL and do not name the transport.
  • The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.

Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21; Cline, Gemini CLI, OpenAI Codex and Zed 2026-10-26). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.

Can it be installed, and is it up to date?

Version pin · advisories

Listed version

Registry lists
0.1.0
Latest stable
0.1.0
Status
current
Withdrawn
no

Source: pypi.org · 2026-11-16. About the version the registry lists; a manual install may resolve to a different one.

Dependency advisories

critical0high0moderate0low0

Counted in the full dependency tree as resolved on 2026-11-16 (OSV.dev; each bar counts advisories). Bars share one scale. The package itself has no known vulnerability (OSV.dev).

Integrity, provenance, license

Integrity
sha256-b4ac9ce51ac39fa06…
License
MIT

Source: the package registry · 2026-11-16.

What do the published files and outside lists say?

Read as text · nothing run · no tool called

Package files

Registry entry

  • Same package in other registry entries. No other registry entry lists this entry's npm or PyPI package at a newer version. Source: own registry snapshot · read 2026-11-16.

Outside lists

  • CVE records (NVD). No CVE record in the NVD feeds we read links this server's repository. Source: read 2026-11-16. This product uses the NVD API but is not endorsed or certified by the NVD.
  • GitHub advisories. No GitHub advisory names this entry's listed package. Source: read 2026-11-16. GitHub Advisory Database, CC BY 4.0
  • Docker MCP catalogue. Not in the Docker MCP catalogue on 2026-11-16. Source: read 2026-11-16.
  • Cline marketplace. Not in the Cline marketplace on 2026-11-16. Source: read 2026-11-16.

Own host

  • security.txt. No security.txt at https://mcp.xonta.ru/.well-known/ (HTTP 404, 2026-11-16). No security.txt at https://xonta.ru/.well-known/ (HTTP 404, 2026-11-16). Source: mcp.xonta.ru/.well-known/security.txt · read 2026-11-16.
  • A2A agent card. No A2A agent card at https://mcp.xonta.ru/.well-known/ (HTTP 404, 2026-11-16). No A2A agent card at https://xonta.ru/.well-known/ (HTTP 404, 2026-11-16). Source: mcp.xonta.ru/.well-known/agent-card.json · read 2026-11-16.

Read as text from published files and outside lists. Nothing was installed or run, and no tool was called. A fact, not a rating. How each fact is read

Does the registry listing match what we found?

Feature #6

The registry checks an entry when it is published (each new version), and nothing re-checks it on a schedule. A difference below is about the listing, not a judgement of the publisher.

Registry saysWe foundResultSource · date
Remote endpoint mcp.xonta.ru/max/mcpSession openedmatchesour test · 2026-11-16
No credential declared as requiredOpened a session without any credentialmatchesour test · 2026-11-16
Version 0.1.0 on PyPIExists and can be installedmatchesPyPI · 2026-11-16
Repository github.com/mrsergeiluzhnov/xonta-max-mcpOpens publiclymatchesapi.github.com · 2026-11-16

Who made it?

Feature #7 · lineage

Facts about the publisher. We do not turn them into a trust score.

Namespace
ru.xonta · 2 servers
GitHub owner
a personal account (mrsergeiluzhnov)
Repository
github.com/mrsergeiluzhnov/xonta-max-mcp
Stars
0
Repository age
0–30 days
Last push
0–30 days ago
Archived
no
Security policy
none found (we looked for SECURITY.md in the repository and in its owner’s .github repository)

Source: the registry entry and api.github.com · 2026-11-16; security policy read from GitHub · 2026-11-16.

Publish this server? Run these checks against it yourself before release, from your own machine: a server the command starts, or your own server at its URL after a one-time proof that you control it: npx protocolprobe-selftest.

Choosing

Record checks

Public records · not a safety rating

7 of 8 record checks met · 1 does not apply

  • Not ranked by downloads: no download figure available
  • Not ranked by stars: 0 stars (ranked from 10)
  • MetRegistry entry is active and says how to run itActive, with a package or a remote address.
  • MetSource repository link opensThe linked GitHub repository is public.
  • MetRepository is not archivedNot archived.
  • MetCode pushed to the repository in the 90 days before our checkLast push 0-30 days before our check.
  • Not metRepository publishes a security policy (SECURITY.md)No SECURITY.md in the places GitHub reads it from.What changes this check: GitHub's documentation describes adding a SECURITY.md from the repository's security settings: under Reporting, Security policy, Start setup. GitHub: adding a security policy
  • MetPackage names its licence with a standard (SPDX) identifierMIT
  • MetThe version the registry lists can be installed and is not withdrawnThe listed version exists and is current.
  • Does not applynpm package carries build provenance (attestation)PyPI packages have no npm-style attestation.
  • MetNo known critical or high advisory in the package or its dependenciesNone known in the package or its dependency tree.

Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-11-16 (security policy 2026-11-16). No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating, and the same rules apply to every server. How each check works · Leaderboards · How we stay neutral

Common questions about ru.xonta/max

Answered from the data above

Who publishes ru.xonta/max?

The registry ties the namespace ru.xonta to the domain xonta.ru; only its owner can publish under it. Its linked repository is github.com/mrsergeiluzhnov/xonta-max-mcp; GitHub reports its owner as mrsergeiluzhnov, a personal account. These are facts from the registry and GitHub, not a rating.

Is ru.xonta/max safe to install?

We do not rate servers as safe or unsafe. 7 of its 8 applicable record checks are met (facts from public records, each listed on this page). What the records show: Its source repository opens publicly. Its repository had a push in the last 90 days. The listed version is the latest stable release. The package itself has no known vulnerability (OSV.dev). Its full dependency tree has no known advisory. These are facts with their sources on this page, not a safety guarantee, and we did not run its tools.

Does ru.xonta/max need an API key or sign-in?

It opened a session without any credential on 2026-11-16. The registry entry declares no required credential; no declaration is not a guarantee.

Has ru.xonta/max been security tested?

Partly. 2 of the 14 checks that apply to it were exercised. We connected and read what the server declares, but did not call its tools: ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so). This is our choice, not a block by the server. ProtocolProbe publishes no security verdict for a named server.

Does ru.xonta/max publish a security policy?

We found no SECURITY.md in its repository (root, .github/ or docs/) or in its owner's .github repository.

Is the listed version current?

Yes. The registry lists 0.1.0, the latest stable release on PyPI.

Where is the source code of ru.xonta/max?

In github.com/mrsergeiluzhnov/xonta-max-mcp, which opens publicly.

Found this page useful?

Anonymous · no sign-in

A quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.

Compare with another server

Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.

Security testing

What did we test, and what did we leave out?

18 checks · features #1, #2

Not probed (no operator permission)

We connected and read what the server declares, but did not call its tools: ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so). This is our choice, not a block by the server. No security score is given; a check we did not run is never counted as passed.

The 18 checks at a glanceour test · 2026-11-16
  1. Inventory: exercised
  2. Hidden instructions: exercised
  3. Real execution: not run · our policy
  4. Secret leak: not run · nothing to check it against
  5. Internal addresses: not run · our policy
  6. Unconfirmed changes: not run · our policy
  7. Bad input: not run · our policy
  8. Model requests: not run · nothing to check it against
  9. Sensitive questions: not run · nothing to check it against
  10. Folder boundary: not run · our policy
  11. Log leaks: not run · nothing to check it against
  12. Hidden content: not run · nothing to check it against
  13. Fake assistant turns: not applicable
  14. Token passthrough: not applicable
  15. Token audience: not applicable
  16. Sign-in redirect: not run · our policy
  17. Consent handling: not testable from outside
  18. Sign-in metadata: not applicable

2 exercised12 not run (reason given)4 not applicable

Each check ends in exactly one state: exercised, not run (with the reason), or not applicable (with the reason). 2 of the 14 checks that apply to it were exercised. We do not publish security-check outcomes for named servers. These 18 checks are separate from the record checks at the top of this page, which read public records only.

Exercised · 2
  • 1Inventory
    tool-list
    Reads the declared tools, resources and prompts.exercised
  • 2Hidden instructions
    description-poisoning
    Looks for hidden instructions in tool descriptions.exercised
Not run, with the reason · 12
  • 3Real execution
    real-execution
    Calls a tool and checks what really happens.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy
  • 4Secret leak
    canary-leak
    Plants a fake secret and checks whether it leaks.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 5Internal addresses
    ssrf
    Checks whether a tool can be steered to internal addresses.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy
  • 6Unconfirmed changes
    write-without-confirmation
    Checks whether tools that change data act without asking.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy
  • 7Bad input
    error-handling
    Sends bad input and watches how the server answers.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy
  • 8Model requests
    sampling
    Checks whether the server asks the client's model to act for it.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 9Sensitive questions
    elicitation-sensitive-data
    Checks whether the server asks users for sensitive data.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 10Folder boundary
    root-boundary
    Checks whether the server reaches outside the folders it was given.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy
  • 11Log leaks
    logging-side-channel
    Checks whether log messages carry data they should not.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 12Hidden content
    audience-hiding
    Checks resources that hide content from the user.This check needs content the server returns, and nothing was read or called.not run · nothing to check it against
  • 16Sign-in redirect
    open-redirect
    Checks the sign-in redirect for abuse.Testing the sign-in redirect means sending probes to the operator's sign-in service, which we do not do.not run · our policy
  • 17Consent handling
    confused-deputy
    Checks consent handling when one service acts for another.Depends on the operator's own consent screen, which differs per server and cannot be tested from outside.not testable from outside
Does not apply to this server · 4
  • 13Fake assistant turns
    fake-assistant-turn
    Checks prompts that pose as the assistant's own words.The server exposes no prompts.not applicable
  • 14Token passthrough
    token-passthrough
    Checks whether the server forwards a user's token to other services.The server opened a session without sign-in, so there is no token flow to check.not applicable
  • 15Token audience
    token-audience-validation
    Checks whether tokens meant for another service are accepted.The server opened a session without sign-in, so there is no token flow to check.not applicable
  • 18Sign-in metadata
    oauth-url-scheme
    Checks the published sign-in metadata for unsafe URLs.No sign-in (OAuth) metadata is published, so there are no sign-in addresses to check.not applicable

Source: our own test, 2026-11-16, mcp-runtime-engine@0.1.0. Which checks count and why follows our published scoring model.

What happened during the test?

Feature #8

The steps in order, as the test record holds them.

  1. 0 msStarted a read-only session with the server's remote endpoint
  2. 449 msConnected after 0 redirects. No credential was sent or needed.
  3. Read the inventory: 20 tools, 0 resources, 0 prompts.
  4. 3,917 msFinished: 2 checks exercised.

Reference

How is it classified?

18 fields

One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.

TopicAI-classified
pending: added at the next monthly refresh
listed 2026-11-16; not classified yet
Pricing modelAI-classified
pending: added at the next monthly refresh
the website is not read yet
Programming language
api.github.com · 2026-11-16
Hosting type
registry · 2026-11-16
MCP capability
prompts, resources, tools
our test · 2026-11-16
Transport
standard input/output, streamable HTTP
registry · 2026-11-16
Required credentials
none declared
registry · 2026-11-16 · no declaration is not a guarantee
Package registry
registry · 2026-11-16
Freshness
0–30 days
registry updatedAt · 2026-11-16
Lifecycle status
registry · 2026-11-16
License class
package registry · 2026-11-16
Integrity hash
declared (sha256)
package registry · 2026-11-16
Signature / provenance
does not apply
PyPI publishes no registry signature or attestation equivalent to npm dist.signatures
Dependency advisories
none known
OSV.dev · 2026-11-16
Popularity
not stated
pypistats.org gave no number (404); PyPI info.downloads is a -1 placeholder and is not used
Publisher signals
owner: a personal account · repository age: 0–30 days · stars: 0–9
api.github.com · 2026-11-16
Maintenance
api.github.com · 2026-11-16
Environment
either (remote or your machine)
where it runs, from the hosting type · 2026-11-16

“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.

Cite or correct this page

Sources and corrections

Suggested citation

ProtocolProbe. “ru.xonta/max: MCP server record.” Data checked 2026-11-16. https://protocolprobe.com/mcp/servers/ru.xonta/max

Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.

As JSON: this record in the API · API documentation.

Badge for your README

ProtocolProbe: 7 of 8 record checks met

[![ProtocolProbe](https://protocolprobe.com/api/v1/badge/ru.xonta/max)](https://protocolprobe.com/mcp/servers/ru.xonta/max)

It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.

Something wrong, or is this yours?

If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here, except for a server whose operator has claimed it and given permission (that server's page says so).

Write to hello@protocolprobe.com · corrections log · methodology