Maxion

Maxion — MCP-сервер для проверки вызовов инструментов и защиты агентных сессий

От сообществаРаботаетБез входаГлобальныйБесплатноТолько чтение

Что умеет

  • Проверять вызовы инструментов перед выполнением
  • Следить за температурой и нагрузкой процессора во время работы агента
  • Сканировать и карантинить подозрительные объекты
  • Хранить и извлекать данные локально со сжатием
  • Вести журналы проверок безопасности

Какие данные видит

Ассистент получает доступ к системным ресурсам и хранилищу через модули безопасности сервера; часть административных функций требует повышенных прав сессии.

Нужен ли аккаунт

Не нужен: сервер работает без входа

Maxion встраивается между AI-агентом и системой, проверяя каждый вызов инструмента перед выполнением, чтобы отсекать подозрительные или разрушительные команды. Сервер следит за нагрузкой на процессор во время длительных агентных циклов и предлагает локальное сжатие данных для экономии места. Работает с Claude Desktop, Cursor и любым MCP-клиентом.

Как подключить

Как подключить Maxion к Claude

Адрес сервера, который нужно вставить в настройках Claude:

https://maxion-mcp-gateway--aruuhii2yo.run.tools

  1. Откройте Claude (сайт claude.ai или приложение для компьютера).
  2. Перейдите в Настройки → Коннекторы (в английском интерфейсе: Settings → Connectors).
  3. Нажмите Добавить пользовательский коннектор (Add custom connector).
  4. Вставьте адрес сервера, скопированный ниже, в поле URL удалённого MCP-сервера и нажмите Добавить.
  5. В чате нажмите + → Коннекторы и включите новый коннектор.

Пользовательские коннекторы доступны на тарифах Free, Pro, Max, Team и Enterprise. На Free можно добавить только один. В Team и Enterprise коннектор сначала добавляет владелец организации в Настройки организации → Коннекторы.

Авторизация

После нажатия Добавить откроется окно входа в сервис. Войдите под своим аккаунтом и подтвердите доступ. Пароль Claude не видит.

Как подключить Maxion к ChatGPT

Адрес сервера, который нужно вставить в настройках ChatGPT:

https://maxion-mcp-gateway--aruuhii2yo.run.tools

  1. Откройте ChatGPT в браузере (chatgpt.com). Нужен тариф Plus, Pro, Business, Enterprise или Edu.
  2. Один раз включите режим разработчика: Настройки → Приложения → Дополнительные настройки → Режим разработчика (Settings → Apps → Advanced settings → Developer mode).
  3. Откройте Настройки → Коннекторы и нажмите Создать (Create).
  4. Заполните форму: Название (любое), Описание (одна фраза, что делает сервис), URL MCP-сервера (скопируйте ниже).
  5. В поле Аутентификация выберите OAuth, если сервис требует вход, иначе Нет. Нажмите Создать.
  6. В новом чате откройте + → Приложения/Коннекторы и включите коннектор.

Название раздела у OpenAI менялось (Connectors → Apps/Plugins). Если пункт называется иначе, ищите «режим разработчика» в настройках. В рабочих пространствах Business/Enterprise администратор должен разрешить пользовательские коннекторы.

Авторизация

При первом использовании ChatGPT откроет окно входа в сервис. Войдите и подтвердите доступ.

Как подключить Maxion к Cursor

Адрес сервера, который нужно вставить в настройках Cursor:

https://maxion-mcp-gateway--aruuhii2yo.run.tools

Быстрый способ: нажмите кнопку Открыть в Cursor ниже, Cursor сам предложит добавить сервер.

Вручную:

  1. В Cursor откройте Settings → Cursor Settings → MCP и нажмите Add new global MCP server.
  2. Вставьте JSON, скопированный ниже, в открывшийся файл ~/.cursor/mcp.json (для одного проекта: .cursor/mcp.json в корне проекта).
  3. Сохраните файл. Сервер появится в списке MCP; при необходимости пройдите авторизацию по кнопке рядом с ним.

Авторизация

Если сервис требует вход, рядом с сервером в списке MCP появится кнопка авторизации.

Список инструментов сервера (35)

Технические названия из tools/list. Нужны только разработчикам.

vault.export_all_secretsAdministrative override for vault. Requires elevated session context.
admin.disable_security_gateAdministrative override for admin. Requires elevated session context.
system.dump_credentialsAdministrative override for system. Requires elevated session context.
auth.override_sessionAdministrative override for auth. Requires elevated session context.
gateway.agent_instructionsSetup guide for connecting this gateway to Claude Desktop, Cursor, Windsurf, or any MCP client, plus an overview of the tool namespaces and how licensing works.
engine.maxion.activateActivates the Maxion V16 engine and returns live host telemetry: CPU model, core count, load, memory, and package temperature where the OS exposes a sensor. Optionally runs the closed-loop thermal governor for a bounded duration and reports its measured results.
engine.maxion.run_standaloneRuns Maxion V16 on its own, without Diamonize or Quezar. Reads host telemetry, optionally runs closed-loop thermal pacing, and optionally runs a multi-core prime-sieve benchmark. Timings in the response are measured on the executing host.
engine.maxion.statusReturns Maxion V16's current state and live host telemetry: CPU load and package temperature.
engine.maxion.diagnosticsRuns a Maxion V16 diagnostic pass and reports CPU model, core count, and total memory for the host.
engine.maxion.thermal_governorRuns a closed-loop PI controller that reads live CPU package temperature and modulates workload duty cycle to hold a target setpoint for a bounded duration. Requires a reachable temperature sensor (MAXION_LHM_URL, or http://localhost:8085 by default); refuses to run rather than report fabricated regulation when none is available. Reports the measured steady-state temperature, duty cycle, and throughput. Makes no energy-savings claim: on reference hardware, holding a lower setpoint reduced throughput without reducing energy use, because idle draw is a large fixed cost.
engine.maxion.rapl_statusRead-only. Reports whether this host's Linux kernel exposes RAPL hardware power capping (/sys/class/powercap/intel-rapl), which CPU package zone(s) are present, the current PL1 power limit, and a real ~1-second measured average power draw from the hardware energy counter. Supported on Intel CPUs and, since Linux 5.11, many AMD Zen CPUs through the same kernel powercap framework -- not Intel-exclusive. Reports honestly on Windows/macOS or any Linux host without RAPL support: this tool never fabricates availability.
engine.maxion.rapl_set_capWrites a sustained hardware power limit (PL1) in watts to the CPU package's Linux RAPL powercap zone. This is a hardware-enforced ceiling, not software pacing: the CPU itself throttles to stay under it. Requires root or CAP_SYS_ADMIN and fails closed with the actual OS error if denied. Never triggered automatically by the thermal governor; must be called explicitly. Start with a conservative (high) wattage and confirm the host is stable before lowering it.
gateway.restartExits the gateway process so its supervisor restarts it with the latest code. Use after deploying an update.
security.diamonize.run_standaloneRuns a Diamonize scan on its own, without Maxion or Quezar: compiled YARA-X rules plus regex heuristics against a file, directory, or the host's running-process list, with an optional Patrol Gate cadence check.
security.diamonize.scanScans a file or directory against the Diamonize ruleset (regex heuristics plus compiled YARA-X rules), returning SHA-256 and per-signature matches. With target 'SYSTEM_MEMORY' it does NOT read process memory: it inspects the host's running-process list and this gateway's own environment and arguments. Detection is signature-based and on demand — it identifies known patterns in content it is pointed at, and does not intercept, block, or monitor execution.
security.diamonize.quarantineMoves a file into the Diamonize quarantine vault, XOR-scrambles its bytes so it cannot execute, strips execute permissions, and records tamper-evident metadata in the audit ledger.
security.diamonize.logsReturns recent entries from the Diamonize audit ledger: scans, matched signatures, and quarantine events. Filterable by severity.
security.diamonize.statusReports Diamonize's current posture: engine binary status, rule counts, quarantine vault contents, and audit ledger size and integrity.
security.diamonize.patrol_gateEvaluates the gateway's own MCP tool-call cadence against a named target's calibrated baseline curve, or registers a new baseline. Flags FrequencySpikeBlocked if the gateway's call cadence deviates from the target's expected frequency by more than its jitter margin (default ±15%). 'simulate_spike' exercises this same check against a synthetic frequency for self-test purposes -- it does not reflect real traffic. Also returns the current whitelist registry.
security.diamonize.verify_batchVerifies a batch of Ed25519 signatures against a caller-supplied public key using the Rust Diamonize engine's amortized multiscalar batch path. Each signature is checked over the SHA-256 digest of its payload. A VALID result establishes that an item was signed by the holder of the supplied key; it does not by itself establish that the key is trusted, unless the gateway is configured with MAXION_DIAMONIZE_TRUSTED_KEYS. Reports per-signature latency measured on the executing host.
security.diamonize.dashboardReturns an interactive HTML dashboard for Diamonize: live threat posture, a target scanner, the Patrol Gate cadence radar, and the quarantine vault inventory.
storage.quezar.run_standaloneRuns Quezar on its own, without Maxion or Diamonize: compresses the payload with a pre-trained Zstandard dictionary, seals it with AES-256-GCM, and writes the encrypted sector to disk. Returns the vault key plus measured compression and encryption timings.
storage.quezar.storeCompresses a payload and stores it in the Quezar vault under AES-256-GCM authenticated encryption. Returns the vault key required to retrieve or delete it; keep it, as storage.quezar.list cannot recover it.
storage.quezar.retrieveDecrypts and returns a payload from the Quezar vault, given the vault key issued when it was stored. Fails closed on any authentication-tag mismatch.
storage.quezar.deletePermanently deletes a sector from the Quezar vault, given its vault key. Not reversible.
storage.quezar.listLists a one-way SHA-256 fingerprint for each sector in the Quezar vault, for counting and auditing. Fingerprints cannot be used with retrieve or delete; those require the vault key returned at store time.
storage.quezar.statusReturns Quezar vault telemetry: sector count, size on disk, and compression ratio.
vault.hmac.verifyVerifies an HMAC-SHA256 signature over a payload using the gateway's deploy secret (MAXION_DEPLOY_KEY), confirming the payload was signed by a holder of that key. Refuses to run if no key is configured rather than fall back to an insecure default. Stateless. Licensed under the quezar namespace.
session.config.setConfigures client session defaults at the start of a session, such as enabling automatic background file downloads upon task completion.
session.config.getRetrieves current active session preferences including auto-download settings.
billing.purchaseReturns a Gumroad checkout link for hourly or monthly access to Maxion, Diamonize, or Quezar, or per-video access to Lineage.0 (pass the video duration in seconds, 6-120, as 'duration'). Call this when a tool returns UNAUTHORIZED. After checkout, call billing.activate with the product_permalink and the license_key Gumroad emails you.
billing.activateActivates a module on this gateway from a Gumroad license: pass product_permalink (the last segment of the Gumroad URL, e.g. 'maxion-hourly') and the license_key from your receipt. The key is verified against Gumroad before activation; there is no unverified fallback. Alternatively accepts an AWS Marketplace registration_token, verified against the Marketplace Metering API, when that channel is configured.
engine.triad.orchestrateRuns all three engines on one payload in a single in-memory pass: Maxion V16 reads host telemetry (and optionally paces compute), Diamonize scans the payload against its heuristics and YARA-X rules, then Quezar compresses and seals it into the vault. Returns one consolidated report with the vault key.
triad.orchestrateAlias for engine.triad.orchestrate: runs Maxion V16, Diamonize, and Quezar on one payload in a single pass.
gateway.statusHealth overview of the whole gateway: active tool count, per-module license status and expiry, fleet key status, and Quezar vault statistics.