trueppm-mcp 0.4.0__tar.gz

trueppm_mcp-0.4.0/.gitignore

@@ -0,0 +1,147 @@
+# Python
+__pycache__/
+*.py[cod]
+*.egg-info/
+*.egg
+.eggs/
+dist/
+build/
+.cache/pip/
+.venv
+venv/
+env/
+
+# Mypy / Ruff / Pytest / Hypothesis
+.mypy_cache/
+.ruff_cache/
+.pytest_cache/
+.hypothesis/
+.coverage
+htmlcov/
+
+# Node — no trailing slash so a worktree's `node_modules` *symlink*
+# (created by scripts/wt) is ignored too, not just real directories.
+node_modules
+
+# Coverage
+coverage/
+coverage.xml
+# Generated by scripts/sonar-scan.sh / the sonar:scan CI job: a copy of the API
+# coverage.xml with a resolvable <source> root injected for import (#2113).
+coverage.sonar.xml
+
+# uv lockfile. The api (APPLICATION), the scheduler (published LIBRARY), and the
+# mcp server (self-hostable app + published PyPI package) all commit a resolved
+# lock — for reproducible dev/CI installs and a scannable dependency surface: an
+# SCA tool (security:osv) can audit a committed lockfile but not the version
+# ranges a library declares. The published wheels still ship ranges from
+# pyproject.toml; the lock is a repo-side artifact only (#904 api supply-chain
+# hardening, #1153 scheduler OSV migration, #2122 mcp). Keep the blanket ignore
+# for everything else.
+uv.lock
+!packages/api/uv.lock
+!packages/scheduler/uv.lock
+!packages/mcp/uv.lock
+
+# Docker
+*.override.yml
+
+# OS
+.DS_Store
+Thumbs.db
+
+# Editor
+.idea/
+.vscode/
+*.swp
+*.swo
+
+# Docusaurus build cache
+.docusaurus/
+
+# Claude Code runtime state
+.claude/scheduled_tasks.lock
+.claude/worktrees/
+
+# Playwright test runtime output
+test-results/
+packages/web/test-results/
+packages/web/playwright-report/
+
+# Rendered by init-prod.sh from one of the nginx/*.conf.template files at first
+# run (#3189). A generated artifact, never committed.
+nginx/active.conf.template
+
+# Local dev attachment + media blobs (Closes #817)
+packages/api/attachments/
+packages/api/media/
+# Workspace logo blobs (#969) — local-disk storage root; prod uses object storage
+packages/api/branding/
+
+# Workspace export test/runtime artifacts (written by export tests; never committed)
+packages/api/workspace-exports/
+# Project export bundle test/runtime artifacts (ADR-0219; never committed)
+packages/api/project-exports/
+# Program export bundle test/runtime artifacts (ADR-0219, #1958; never committed)
+packages/api/program-exports/
+# Program seed import payload test/runtime artifacts (ADR-0726, #2574; never committed)
+packages/api/seed-imports/
+
+# Per-worktree harness files — auto-generated per worktree/machine by scripts/wt
+# (COMPOSE_PROJECT_NAME, isolated TRUEPPM_TEST_DB, owner marker, number reservation).
+# Regenerated on every `wt new`; never committed. Tracking them leaks machine-specific
+# data, collapses per-worktree test-DB isolation, and makes `wt prune` skip the
+# worktree as "has local work". See #1690.
+.envrc
+.wt-owner
+.wt-reservation
+
+# The operator's real secrets. init-prod.sh WRITES this file at the repo root —
+# SECRET_KEY (which is also the JWT signing key), DB_PASSWORD, REDIS_PASSWORD —
+# and nothing else stopped `git add -A` from committing it. .env.example is the
+# tracked template; .env never is (#3183).
+.env
+.env.*
+!.env.example
+
+# SonarCloud / sonar-scanner scratch output
+.scannerwork/
+.sonar/
+
+# Schemathesis API-fuzz crash cache — one JSON record per crash fingerprint,
+# written by the `fuzz` extra (packages/api/pyproject.toml) on every local run.
+# Generated, machine-local, and large (289 files in one observed run); each
+# record embeds the request headers and curl repro for its target. Never
+# committed. See #2794.
+.schemathesis/
+
+# Captured docs-build output (#2797). website:build / pages redirect `npm run
+# build` here so the exit code stays honest (a `| tee` would report tee's
+# status), then check-mermaid-rendered.sh scans it for the [ERROR] lines Astro
+# logs while still exiting 0. CI-local scratch; never committed.
+website-build.log
+
+# k6 perf/load metrics blob (#2816). `packages/api/perf/load.js` writes it to the
+# working directory on every run — a CI artifact there, repo-root scratch when the
+# harness is run locally per packages/api/perf/README.md. Machine-local and
+# meaningless off the run that produced it; never committed.
+perf-summary.json
+
+# TLS material generated by init-prod.sh (#2829). `TLS_MODE=selfsigned` mints a
+# lineage into certbot/conf/live/$DOMAIN/, and letsencrypt writes the real one to
+# the same place — so this directory holds a PRIVATE KEY on any host that has run
+# the documented production entrypoint, including a developer trying the prod
+# compose drill locally. The drill removes it on teardown; this is the guard for
+# the run that fails before teardown.
+certbot/
+
+# Local audit reports (docs/audit/). Generated by /pre-release, red-team, and
+# state-of-repo runs; kept on the machine that produced them and never committed.
+#
+# This repo is PUBLIC. These reports enumerate unfixed defects with file:line
+# detail — red-team-2026-08-06.md alone carries two CRITICAL and three HIGH
+# findings, and C1 (no working way to revoke a stolen refresh token) is still
+# live on main as of 2026-08-21. Committing them here publishes a working
+# exploit description ahead of the fix. File the findings as issues instead —
+# a tracker entry is the disclosure channel, a checked-in audit report is not.
+docs/audit/

trueppm_mcp-0.4.0/Dockerfile

@@ -0,0 +1,156 @@
+# Read-only TruePPM MCP server (ADR-0186).
+#
+# A pure HTTP client of the TruePPM REST API — no Django, no database driver, no
+# system libraries beyond the Python runtime. stdio is the primary transport (an
+# AI client spawns the container and speaks MCP over the pipe); pass
+# `--transport http` to serve the network transport for web assistants.
+#
+# Build context is this package directory:
+#   docker build -t trueppm-mcp packages/mcp/
+# Run (stdio):
+#   docker run --rm -i -e TRUEPPM_API_URL=... -e TRUEPPM_API_TOKEN=... trueppm-mcp
+# Run (HTTP, port 8000):
+#   docker run --rm -p 127.0.0.1:8000:8000 -e TRUEPPM_API_URL=... \
+#     -e TRUEPPM_API_TOKEN=... trueppm-mcp --transport http --host 0.0.0.0 --port 8000
+#   WARNING: the HTTP/SSE transport has no client-side auth — anyone who can reach
+#   the published port acts as the token owner. Publish on the host loopback only
+#   (`127.0.0.1:` prefix; a bare `-p 8000:8000` binds every host interface), or put
+#   it behind an authenticated, TLS-terminating ingress and name that hostname with
+#   `--allowed-host`. Host/Origin validation (DNS-rebinding protection) is always
+#   on, even when binding 0.0.0.0. See administration/mcp-server.md.
+
+# ---------------------------------------------------------------------------
+# Stage 1: builder — install the package into an isolated virtualenv
+# ---------------------------------------------------------------------------
+# CI overrides this with the GitLab Dependency Proxy prefix so dind builds
+# don't pull Docker Hub anonymously (#4201); the default keeps local and
+# release builds unchanged.
+ARG DOCKERHUB_PREFIX=docker.io
+
+FROM ${DOCKERHUB_PREFIX}/python:3.11-slim@sha256:b7a9e5f6a93d6d4a31f129bbd4bdee69efccb6ded0fb230d78aafaf37af98377 AS builder
+
+# `apt-get upgrade` (not just `update`) so this layer carries the Debian
+# security team's latest point-release patches even when the pinned
+# `python:3.11-slim` digest above hasn't been rebuilt since the last CVE
+# disclosure — the same rationale as the api image's equivalent comment
+# (packages/api/Dockerfile), and the same bug class as #4335 (the web
+# image's Alpine base had no upgrade step at all). This image installs no
+# apt packages of its own (pure HTTP client, no build-essential/libpq-dev
+# needed), so there is nothing to `apt-get install` here — just the
+# upgrade and the list cleanup. Build-stage CVEs never ship (this stage is
+# discarded), so this line matters only for the runtime stage below — kept
+# here too so both stages patch identically.
+RUN apt-get update -qq && \
+    apt-get upgrade -y -qq && \
+    rm -rf /var/lib/apt/lists/*
+
+ENV VIRTUAL_ENV=/venv
+RUN python -m venv "$VIRTUAL_ENV"
+ENV PATH="$VIRTUAL_ENV/bin:$PATH"
+
+# pip >= 26.2.2 (emSign CA incident, #4642): pip always trusts its OWN vendored
+# certifi bundle and cannot be told otherwise, so any pip older than 26.2.2 still
+# trusts the emSign roots that certifi dropped, whatever the OS trust store says.
+# Install the wheel by direct URL with a hash so the upgrade does not depend on
+# the bundle it is replacing. Keep this even once the base image ships a newer
+# pip: it is the pin that makes the floor explicit. The runtime stage later
+# uninstalls pip entirely; this protects the build-time fetches (uv, wheel).
+RUN printf '%s\n' 'pip @ https://files.pythonhosted.org/packages/3f/06/3e4420302363fbb71be3c7f35ce042f54bfca330e3e66b3a2e3c4cca579f/pip-26.2.2-py3-none-any.whl --hash=sha256:fd7f4dfa8190e014013b9f08f3e973f4e4c26ffd179a204895533a7254813a70' > /tmp/pip-req.txt \
+ && pip install --no-cache-dir --require-hashes -r /tmp/pip-req.txt \
+ && rm /tmp/pip-req.txt
+# Fail the build if the pin above ever stops taking effect (#4642).
+RUN /venv/bin/python -c "import pip,sys; v=tuple(int(x) for x in pip.__version__.split('.')[:3]); sys.exit(0 if v>=(26,2,2) else 'pip %s < 26.2.2' % pip.__version__)"
+
+# Patch the venv-seeded build tooling forward before installing so the published
+# image scans clean (mirrors the api image hardening, #1388): 3.11's ensurepip
+# seeds an old `wheel` that trips Trivy on CVE-2026-24049.
+# --only-binary :all: keeps this a wheel-only install so no sdist setup script
+# runs during the build (wheel ships a manylinux wheel, so the flag is safe here
+# — unlike the local source install of /build/mcp below).
+RUN pip install --only-binary :all: --no-cache-dir --upgrade "wheel>=0.46.2"
+
+# `uv` is a build-only tool used below to resolve dependencies from the
+# checked-in lockfile instead of `pip`'s live-PyPI resolution (#4184, same
+# class as #4078 on the api image). It installs into this SAME venv (there is
+# no separate build-tool venv) and this venv is copied wholesale into the
+# runtime stage, so it is `pip uninstall`ed explicitly right after its last
+# use below, before any runtime-stage COPY can pick it up. Pinned exact (not
+# a floor) and matched to the api image's pin: `uv export`'s output shape is
+# a build input, not a runtime dependency, so a version drift here should be
+# a deliberate bump, not something that silently changes on the next
+# `docker build`.
+RUN pip install --only-binary :all: --no-cache-dir "uv==0.9.5"
+
+# Resolve every runtime dependency from packages/mcp/uv.lock — the lock CI
+# tested against — instead of a fresh `pip` resolution against whatever PyPI
+# serves on the day of the build (same structural gap #4078 fixed for the api
+# image, here for the smaller `mcp[cli]` / `httpx` / `cryptography` set).
+# `trueppm-mcp` itself is excluded from the export (--no-emit-project): the
+# LOCAL source copied in below is what must ship, not whatever version the
+# lock happens to record.
+#
+# --require-hashes verifies every downloaded artifact against the hash uv
+# recorded at lock time — the supply-chain hardening the previous unpinned
+# `pip install` had no way to do. This requires every entry in the export to
+# carry a hash, which holds here since the only hash-less member of the
+# dependency graph (trueppm-mcp itself) is excluded above.
+COPY pyproject.toml uv.lock /build/mcp-lock/
+WORKDIR /build/mcp-lock
+RUN uv export --frozen --no-dev --no-emit-project \
+      -o /build/requirements.txt && \
+    pip uninstall -y uv && \
+    pip install --no-cache-dir --require-hashes -r /build/requirements.txt
+
+# Install the mcp package itself. Its dependencies were all installed from
+# the lock above, so --no-deps stops pip from re-resolving them against
+# PyPI — the exact step that reopens the gap this fix closes if it is ever
+# dropped.
+COPY . /build/mcp
+RUN pip install --no-cache-dir --no-deps /build/mcp
+
+# Prove the image can actually boot before it ships: import the CLI entry
+# point module (the console script's target, `trueppm_mcp.cli:main`), which
+# transitively imports the server, client, and config modules and would fail
+# the same way a live-PyPI-resolved dependency mismatch would (mirrors the
+# api image's `django.setup()` boot smoke from #4078). Runs in every build —
+# local `docker build` and any future CI job — not only a later automated
+# gate, so a regression is caught at the earliest possible point.
+RUN /venv/bin/python -c "import trueppm_mcp.cli; print('boot smoke: OK')"
+
+# ---------------------------------------------------------------------------
+# Stage 2: runtime — lean image with only the venv
+# ---------------------------------------------------------------------------
+FROM ${DOCKERHUB_PREFIX}/python:3.11-slim@sha256:b7a9e5f6a93d6d4a31f129bbd4bdee69efccb6ded0fb230d78aafaf37af98377 AS runtime
+
+# See the matching comment in the builder stage above — this is the stage
+# that actually ships, so this `upgrade` is the one that matters for a
+# pre-publish Trivy gate (none exists for this image today, but the
+# Dockerfile's own header documents `docker build ... packages/mcp/` as a
+# supported self-host path, so an operator building it locally gets the
+# same patch posture as the api/web images).
+RUN apt-get update -qq && \
+    apt-get upgrade -y -qq && \
+    rm -rf /var/lib/apt/lists/*
+
+COPY --from=builder /venv /venv
+
+# Drop the Python build tools (pip/setuptools/wheel) from both the base image's
+# system Python and the app venv: the server runs entirely from the venv console
+# script and never invokes them at runtime, but Trivy scans them and fails the
+# release on their fixable CVEs (mirrors the api image, #1388).
+RUN python -m pip uninstall -y wheel setuptools pip \
+ && /venv/bin/python -m pip uninstall -y wheel setuptools pip \
+ && rm -f /usr/local/lib/python3.11/ensurepip/_bundled/*.whl
+# The base image's ensurepip carries its own pip wheel (24.0 here, with the same
+# vendored certifi); deleted so `python -m ensurepip` cannot resurrect an old pip (#4642).
+
+# Non-root runtime user.
+RUN useradd --uid 1000 --no-create-home --shell /sbin/nologin trueppm
+
+ENV PATH="/venv/bin:$PATH"
+WORKDIR /app
+USER trueppm
+
+# stdio by default; override CMD args for http/sse, e.g.
+#   docker run -p 127.0.0.1:8000:8000 ... trueppm-mcp --transport http --host 0.0.0.0
+ENTRYPOINT ["trueppm-mcp"]

trueppm_mcp-0.4.0/LICENSE

@@ -0,0 +1,201 @@
+                                 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.

trueppm_mcp-0.4.0/NOTICE

@@ -0,0 +1,7 @@
+TruePPM
+Copyright 2026 MacroDream, LLC and contributors
+
+This product is licensed under the Apache License, Version 2.0 (see LICENSE).
+
+Third-party components that TruePPM redistributes, and the notices their
+licenses require to travel with them, are listed in NOTICES.

trueppm_mcp-0.4.0/NOTICES

@@ -0,0 +1,49 @@
+TruePPM MCP Server — Third-Party Notices
+=========================================
+
+This file is scoped to what `trueppm-mcp` itself redistributes — it is NOT a
+byte-identical copy of the repository-root `NOTICES` (unlike this package's
+`LICENSE`/`NOTICE`, which are). The root file also covers psycopg, which
+`trueppm-mcp` never depends on (it is a pure HTTP client of the TruePPM REST
+API — ADR-0186 — with no Django, no ORM, no database driver), so copying it
+verbatim here would misstate what this package distributes. If TruePPM's
+third-party dependency set changes, keep this file and the root `NOTICES` in
+sync by hand for the components both packages actually ship.
+
+TruePPM's own source code is licensed under the Apache License 2.0 (see
+`LICENSE` in this directory, and the repository-root `LICENSE`). This file
+records the third-party components that `trueppm-mcp` redistributes — in its
+Docker image (`packages/mcp/Dockerfile`, via the installed wheel's
+`dist-info/licenses/`) and in its own published PyPI sdist/wheel — and whose
+licenses require a notice to travel with every distributed copy.
+
+
+certifi — Mozilla's curated bundle of root certificates
+--------------------------------------------------------
+
+  Component:   certifi
+  Version:     unpinned (resolved transitively; see below)
+  License:     Mozilla Public License 2.0 (SPDX: MPL-2.0)
+  Upstream:    https://github.com/certifi/python-certifi
+  License text: licenses/MPL-2.0.txt
+
+  How it arrives, and the obligation we satisfy:
+
+  certifi is not a direct dependency of trueppm-mcp — it arrives transitively
+  via `httpx`, this package's HTTP client. It is redistributed unmodified,
+  installed from PyPI as an ordinary wheel.
+
+  MPL-2.0 is file-level copyleft: the obligations attach to modifications of
+  the *licensed files themselves*, not to software that merely depends on or
+  links against them (§1.4, §3.1-3.3). We do not modify certifi's source, so
+  no source-disclosure obligation is triggered — only the Notice preservation
+  and license-availability requirements that apply to any Covered Software we
+  redistribute (§3.2, §3.3), both satisfied here: this NOTICES entry plus
+  `licenses/MPL-2.0.txt` travel with every copy of this package (image and
+  PyPI artifact alike), and certifi's own unmodified source remains available
+  from its canonical PyPI/GitHub location at all times.
+
+  No version is pinned deliberately: certifi ships a rolling CA bundle update,
+  and pinning a version would eventually distribute stale root certificates.
+  See the repository-root `NOTICES` for the full rationale (shared verbatim
+  with this package's own copy of the certifi entry).