asm-mcp 1.0.0__tar.gz

asm_mcp-1.0.0/.dockerignore

@@ -0,0 +1,13 @@
+.git
+.github
+.gitlab-ci.yml
+venv
+.venv
+__pycache__
+*.py[cod]
+.ruff_cache
+.env
+opencode.json
+tests
+Dockerfile
+.dockerignore

asm_mcp-1.0.0/.github/dependabot.yml

@@ -0,0 +1,20 @@
+version: 2
+updates:
+  # Actions are pinned by commit SHA; Dependabot moves them deliberately, grouped.
+  - package-ecosystem: github-actions
+    directory: /
+    schedule:
+      interval: monthly
+    groups:
+      actions:
+        patterns: ["*"]
+    commit-message:
+      prefix: ci
+
+  # Version updates are off: Dependabot edits pyproject.toml but cannot
+  # regenerate requirements.lock. Security alerts keep working with a limit of 0.
+  - package-ecosystem: pip
+    directory: /
+    schedule:
+      interval: monthly
+    open-pull-requests-limit: 0

asm_mcp-1.0.0/.github/workflows/ci.yml

@@ -0,0 +1,76 @@
+name: CI
+
+on:
+  push:
+    branches: [main, master]
+  pull_request:
+
+permissions:
+  contents: read
+
+jobs:
+  test:
+    runs-on: ubuntu-latest
+    strategy:
+      fail-fast: false
+      matrix:
+        python-version: ["3.10", "3.11", "3.12", "3.13"]
+    steps:
+      - uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1  # v7.0.1
+
+      - uses: actions/setup-python@6d4fd22b20465ccc0f7354476588e8df7c9ca0e0  # v7.1.0
+        with:
+          python-version: ${{ matrix.python-version }}
+
+      # Hash-pinned: the server holds a live ASM API token, so a substituted
+      # dependency is a credential compromise, not just a broken build.
+      - name: Install locked dependencies
+        run: pip install --require-hashes -r requirements.lock
+
+      - name: Install the package without touching the locked tree
+        run: pip install --no-deps -e .
+
+      - name: Run tests
+        run: python -m unittest discover -s tests -v
+
+      - name: Check the lock satisfies what the package declares
+        run: pip check
+
+  lint:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1  # v7.0.1
+
+      - uses: actions/setup-python@6d4fd22b20465ccc0f7354476588e8df7c9ca0e0  # v7.1.0
+        with:
+          python-version: "3.12"
+
+      # --group needs pip 25.1 or newer.
+      - run: |
+          python -m pip install --upgrade pip
+          pip install --group dev
+
+      - run: ruff check .
+
+  lock:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1  # v7.0.1
+
+      - uses: astral-sh/setup-uv@68559e99cc807c1eb7e9238fd43a15bba460eec2  # v10.3.3
+        with:
+          version: "0.12.10"
+
+      # Fails if pyproject.toml and requirements.lock have drifted apart. The lock
+      # is copied first because uv seeds the resolution from an existing output
+      # file: this asks "does the lock still match pyproject", not "is it the
+      # newest resolve".
+      - name: Verify the lock is current
+        run: |
+          mkdir -p /tmp/lockcheck
+          cp requirements.lock /tmp/lockcheck/requirements.lock
+          uv pip compile pyproject.toml --universal --python-version 3.10 \
+            --generate-hashes -o /tmp/lockcheck/requirements.lock --quiet
+          diff -u \
+            <(grep -v '^#    uv pip compile' requirements.lock) \
+            <(grep -v '^#    uv pip compile' /tmp/lockcheck/requirements.lock)

asm_mcp-1.0.0/.github/workflows/publish.yml

@@ -0,0 +1,49 @@
+name: Publish
+
+on:
+  release:
+    types: [published]
+
+permissions:
+  contents: read
+
+jobs:
+  # A release whose tag does not match __version__ would upload nothing new to
+  # PyPI (skip-existing) and leave the release pointing at the wrong code.
+  version:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1  # v7.0.1
+      - name: Check the release tag matches the package version
+        run: |
+          version=$(sed -n 's/^__version__ = "\(.*\)"$/\1/p' src/asm_mcp/__init__.py)
+          if [ "${GITHUB_REF_NAME#v}" != "$version" ]; then
+            echo "::error::release tag $GITHUB_REF_NAME does not match __version__ $version"
+            exit 1
+          fi
+
+  publish:
+    needs: version
+    runs-on: ubuntu-latest
+    environment: pypi
+    permissions:
+      # A job-level permissions block replaces the workflow-level one, so
+      # checkout's contents: read has to be repeated here.
+      contents: read
+      # PyPI trusted publishing: no long-lived API token in repository secrets.
+      id-token: write
+    steps:
+      - uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1  # v7.0.1
+
+      - uses: actions/setup-python@6d4fd22b20465ccc0f7354476588e8df7c9ca0e0  # v7.1.0
+        with:
+          python-version: "3.12"
+
+      - run: pip install build==1.3.0
+
+      - run: python -m build
+
+      - uses: pypa/gh-action-pypi-publish@7245906fb61fa33a13554f9d5fb856fe61758086  # v1.14.3
+        with:
+          # a version published by hand earlier must not fail the release
+          skip-existing: true

asm_mcp-1.0.0/.gitignore

@@ -0,0 +1,10 @@
+venv/
+.venv/
+/dist/
+*.egg-info/
+__pycache__/
+*.py[cod]
+.ruff_cache/
+.env
+opencode.json
+.DS_Store

asm_mcp-1.0.0/CONTRIBUTING.md

@@ -0,0 +1,89 @@
+# Участие в разработке
+
+## Окружение
+
+Нужен Python 3.10+.
+
+```sh
+python3 -m venv venv
+./venv/bin/pip install --require-hashes -r requirements.lock
+./venv/bin/pip install --no-deps -e .
+./venv/bin/pip install --group dev
+```
+
+Зависимости ставятся из лока с проверкой хешей. Сервер держит живой API-токен,
+поэтому подменённая зависимость здесь означает утечку доступа, а не просто
+сломанную сборку. Для `--group` нужен pip 25.1 или новее.
+
+## Тесты и линт
+
+```sh
+./venv/bin/python -m unittest discover -s tests -v
+./venv/bin/ruff check .
+```
+
+Сеть тестам не нужна. HTTP-клиент подменяется через `httpx.MockTransport`.
+`tests/support.py` содержит `FakeASM` — эмулятор `/assets/updated` и
+`/issues/updated` с особенностями настоящего API:
+
+- утечка фильтра статуса;
+- пустые страницы при маленьком `count`;
+- таймауты на больших страницах;
+- ответ активов в виде массива.
+
+Handshake по stdio проверяется на установленной команде `asm-mcp`.
+
+## Зависимости
+
+Версии задаются в `pyproject.toml`, а `requirements.lock` генерируется из них.
+После правки зависимостей пересоберите лок, иначе CI это заметит:
+
+```sh
+uv pip compile pyproject.toml --universal --python-version 3.10 --generate-hashes -o requirements.lock
+```
+
+## Проверить сервер вручную
+
+```sh
+printf '%s\n' \
+  '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-06-18","capabilities":{},"clientInfo":{"name":"probe","version":"0"}}}' \
+  '{"jsonrpc":"2.0","method":"notifications/initialized"}' \
+  '{"jsonrpc":"2.0","id":2,"method":"tools/list"}' \
+  | ASM_BASE_URL=https://asm.example.com ASM_API_TOKEN=<token> asm-mcp
+```
+
+## Структура кода
+
+| Модуль | Содержимое |
+| --- | --- |
+| `settings.py` | `Settings`: переменные окружения, читаются и проверяются один раз при запуске |
+| `catalog.py` | Справочник: типы и статусы, severity, поля, особенности API, список read-only маршрутов `ROUTES` |
+| `params.py` | Проверки аргументов: id, курсор, фильтры, маршруты `asm_request` |
+| `arguments.py` | Модели аргументов тулов на pydantic. Из одной модели получаются и проверка, и `inputSchema` |
+| `client.py` | `ASMClient`: пул соединений, Bearer, троттлинг, ретраи, подсказки по статусам, лимиты ответа |
+| `paging.py` | Обход по `seqUpdate`, адаптивный размер страницы, компактный вид записей |
+| `summary.py` | Счётчики сводок и фоновые задачи в памяти |
+| `server.py` | Тулы (`@tool`), состояние сервера (`AppState`), точка входа `cli` |
+
+Глобального состояния нет. Настройки, клиент, троттлер и фоновые задачи
+создаются при старте сервера и живут, пока он работает.
+
+Новый тул добавляется в `server.py`: это функция-обработчик с декоратором
+`@tool(имя, модель, описание)`. Модель аргументов описывается классом в
+`arguments.py`. Новый read-only эндпоинт подключается записью `Route(...)` в
+`catalog.ROUTES`. Эндпоинты, которые меняют данные, туда не добавляются.
+
+## Документация
+
+`README.md` и `README.en.md` должны совпадать по содержанию, раздел в раздел.
+Правьте оба файла.
+
+## Релиз
+
+Версия задаётся в `src/asm_mcp/__init__.py` и оттуда попадает в метаданные
+пакета, версию MCP-сервера и User-Agent. Публикация на PyPI запускается
+публикацией GitHub Release (`.github/workflows/publish.yml`, trusted publishing,
+без токенов в секретах). Тег релиза (`vX.Y.Z`) должен совпадать с версией
+пакета, иначе публикация остановится.
+
+Ссылки в README абсолютные: PyPI не резолвит относительные пути.

asm_mcp-1.0.0/Dockerfile

@@ -0,0 +1,29 @@
+# Build the wheel separately so the runtime image carries no build toolchain.
+FROM python:3.12-slim AS build
+
+WORKDIR /build
+RUN pip install --no-cache-dir build==1.3.0
+
+COPY pyproject.toml README.md LICENSE NOTICE ./
+COPY src ./src
+RUN python -m build --wheel --outdir /dist
+
+
+FROM python:3.12-slim
+
+# Dependencies come from the hash-pinned lock, the package itself without
+# resolving anything further, so the image matches what CI tested.
+COPY requirements.lock /tmp/requirements.lock
+RUN pip install --no-cache-dir --require-hashes -r /tmp/requirements.lock \
+    && rm /tmp/requirements.lock
+
+COPY --from=build /dist/*.whl /tmp/
+RUN pip install --no-cache-dir --no-deps /tmp/*.whl && rm /tmp/*.whl
+
+# The process holds a live ASM API token; it has no reason to run as root.
+RUN useradd --create-home --uid 10001 asm
+USER asm
+
+# stdio transport: the MCP client talks to this process over stdin/stdout,
+# so the container must be run with -i and must print nothing else to stdout.
+ENTRYPOINT ["asm-mcp"]

asm_mcp-1.0.0/LICENSE

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

asm_mcp-1.0.0/NOTICE

@@ -0,0 +1,5 @@
+F6 ASM MCP Server
+Copyright 2026 F6 JSC
+
+This product includes software developed at F6 JSC
+(https://f6.security).