mcp-server-taxcode 0.7.1__tar.gz → 0.8.0__tar.gz

{mcp_server_taxcode-0.7.1 → mcp_server_taxcode-0.8.0}/.github/dependabot.yml

@@ -1,13 +1,4 @@
 version: 2
-# The Dockerfile pulls its base from public.ecr.aws. Declaring that host
-# under registries (no credentials; it allows anonymous pulls) lets the
-# docker update job reach it. See "Configuring access to private registries
-# for Dependabot" on docs.github.com.
-registries:
-  public-ecr:
-    type: docker-registry
-    url: https://public.ecr.aws
-
 updates:
   - package-ecosystem: "uv"
     directory: "/"
@@ -43,5 +34,3 @@ updates:
       time: "04:30"
       timezone: "Etc/UTC"
     open-pull-requests-limit: 10
-    registries:
-      - public-ecr

{mcp_server_taxcode-0.7.1 → mcp_server_taxcode-0.8.0}/.github/workflows/ci.yml

@@ -35,9 +35,11 @@ jobs:
           persist-credentials: false
 
       - name: Install uv
-        uses: astral-sh/setup-uv@c18668ad3cf93ea998bef934396af7bb5c839dc7  # v10.2.0
+        uses: astral-sh/setup-uv@1c37ad07a6a961277cf70c0d37d6f313000f5884  # v10.3.0
         with:
-          version: "latest"
+          # Newest uv that meets pyproject.toml's [tool.uv] required-version (>=0.13.4, from
+          # FastMCP's October 2026 certificate authority incident notice).
+          version-file: "pyproject.toml"
           enable-cache: true
 
       - name: Set up Python
@@ -63,7 +65,7 @@ jobs:
     strategy:
       fail-fast: false
       matrix:
-        python-version: ["3.10", "3.11", "3.12", "3.13"]
+        python-version: ["3.10", "3.11", "3.12", "3.13", "3.14"]
     steps:
       - uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1  # v7.0.1
         with:
@@ -71,9 +73,11 @@ jobs:
           persist-credentials: false
 
       - name: Install uv
-        uses: astral-sh/setup-uv@c18668ad3cf93ea998bef934396af7bb5c839dc7  # v10.2.0
+        uses: astral-sh/setup-uv@1c37ad07a6a961277cf70c0d37d6f313000f5884  # v10.3.0
         with:
-          version: "latest"
+          # Newest uv that meets pyproject.toml's [tool.uv] required-version (>=0.13.4, from
+          # FastMCP's October 2026 certificate authority incident notice).
+          version-file: "pyproject.toml"
           enable-cache: true
 
       - name: Set up Python ${{ matrix.python-version }}
@@ -101,9 +105,11 @@ jobs:
           persist-credentials: false
 
       - name: Install uv
-        uses: astral-sh/setup-uv@c18668ad3cf93ea998bef934396af7bb5c839dc7  # v10.2.0
+        uses: astral-sh/setup-uv@1c37ad07a6a961277cf70c0d37d6f313000f5884  # v10.3.0
         with:
-          version: "latest"
+          # Newest uv that meets pyproject.toml's [tool.uv] required-version (>=0.13.4, from
+          # FastMCP's October 2026 certificate authority incident notice).
+          version-file: "pyproject.toml"
           enable-cache: true
 
       - name: Set up Python
@@ -138,9 +144,11 @@ jobs:
           persist-credentials: false
 
       - name: Install uv
-        uses: astral-sh/setup-uv@c18668ad3cf93ea998bef934396af7bb5c839dc7  # v10.2.0
+        uses: astral-sh/setup-uv@1c37ad07a6a961277cf70c0d37d6f313000f5884  # v10.3.0
         with:
-          version: "latest"
+          # Newest uv that meets pyproject.toml's [tool.uv] required-version (>=0.13.4, from
+          # FastMCP's October 2026 certificate authority incident notice).
+          version-file: "pyproject.toml"
 
       - name: Set up Python
         uses: actions/setup-python@5fda3b95a4ea91299a34e894583c3862153e4b97  # v7.0.0
@@ -184,3 +192,29 @@ jobs:
             exit 1
           fi
           echo "Image label matches ${EXPECTED}"
+
+      - name: Builder fails below the ca-certificates floor
+        # Raising CA_CERTIFICATES_FLOOR above any real Debian version makes the installed
+        # package older than the floor, whatever version the base image or trixie-security
+        # ships, so this is deterministic. The build must fail at the builder's floor check,
+        # with its message, and before the pip bootstrap step starts.
+        run: |
+          set +e
+          docker build --target builder --progress=plain \
+            --build-arg CA_CERTIFICATES_FLOOR=99991231 . > ca-floor.log 2>&1
+          status=$?
+          set -e
+          cat ca-floor.log
+          if [ "$status" -eq 0 ]; then
+            echo "::error::builder built with a ca-certificates floor above the installed version"
+            exit 1
+          fi
+          if ! grep -q "is older than the floor 99991231" ca-floor.log; then
+            echo "::error::builder failed, but not at the ca-certificates floor check"
+            exit 1
+          fi
+          if grep -q -- "--require-hashes" ca-floor.log; then
+            echo "::error::the pip bootstrap step started before the ca-certificates floor check failed"
+            exit 1
+          fi
+          echo "Builder stops at the ca-certificates floor check before any pip step"

{mcp_server_taxcode-0.7.1 → mcp_server_taxcode-0.8.0}/.github/workflows/dependabot-automerge.yml

@@ -28,11 +28,25 @@ jobs:
         with:
           github-token: "${{ secrets.GITHUB_TOKEN }}"
 
+      # Docker base image updates never auto-merge. The docker ecosystem can move the tag
+      # (python:3.12-slim -> 3.14-slim is a Python runtime upgrade that Dependabot labels
+      # semver-minor), so these PRs stay open for a human review.
+      - name: Leave Docker base image updates for review
+        if: steps.metadata.outputs.package-ecosystem == 'docker'
+        run: echo "::notice title=Not auto-merged::Docker base image update ($DEPS $PREV -> $NEW). Docker updates always wait for a human review."
+        env:
+          DEPS: ${{ steps.metadata.outputs.dependency-names }}
+          PREV: ${{ steps.metadata.outputs.previous-version }}
+          NEW: ${{ steps.metadata.outputs.new-version }}
+
       # Allowlist, not a major-version denylist: update-type is the highest change in the PR
       # (a grouped PR with one major is skipped), and it is empty when the PR carries a
       # non-Dependabot commit, so only minor and patch updates are auto-merged.
       - name: Enable auto-merge for semver-minor and semver-patch updates
-        if: steps.metadata.outputs.update-type == 'version-update:semver-minor' || steps.metadata.outputs.update-type == 'version-update:semver-patch'
+        if: >-
+          steps.metadata.outputs.package-ecosystem != 'docker' &&
+          (steps.metadata.outputs.update-type == 'version-update:semver-minor' ||
+          steps.metadata.outputs.update-type == 'version-update:semver-patch')
         run: gh pr merge --auto --squash "$PR_URL"
         env:
           PR_URL: ${{ github.event.pull_request.html_url }}

{mcp_server_taxcode-0.7.1 → mcp_server_taxcode-0.8.0}/.github/workflows/drift-monitor.yml

@@ -28,9 +28,11 @@ jobs:
           persist-credentials: false
 
       - name: Install uv
-        uses: astral-sh/setup-uv@c18668ad3cf93ea998bef934396af7bb5c839dc7  # v10.2.0
+        uses: astral-sh/setup-uv@1c37ad07a6a961277cf70c0d37d6f313000f5884  # v10.3.0
         with:
-          version: "latest"
+          # Newest uv that meets pyproject.toml's [tool.uv] required-version (>=0.13.4, from
+          # FastMCP's October 2026 certificate authority incident notice).
+          version-file: "pyproject.toml"
           enable-cache: true
 
       - name: Set up Python

{mcp_server_taxcode-0.7.1 → mcp_server_taxcode-0.8.0}/.github/workflows/release.yml

@@ -28,7 +28,9 @@ jobs:
       - name: Install uv
         uses: astral-sh/setup-uv@1c37ad07a6a961277cf70c0d37d6f313000f5884  # v10.3.0
         with:
-          version: "latest"
+          # Newest uv that meets pyproject.toml's [tool.uv] required-version (>=0.13.4, from
+          # FastMCP's October 2026 certificate authority incident notice).
+          version-file: "pyproject.toml"
           enable-cache: false
 
       - name: Set up Python

{mcp_server_taxcode-0.7.1 → mcp_server_taxcode-0.8.0}/AGENTS.md

@@ -136,7 +136,10 @@ When translating an API documentation page, `llm.txt`, or OpenAPI specification
    - Tool execution errors reach the client as `tools/call` results with `isError: true` and the redacted message (`tool_error`, raised `from None` after the `except` block ends, so neither `__cause__` nor `__context__` holds the original exception); `ParentAuditMiddleware` logs the same redacted message. A batch tool's per-item errors and its `batch_failed` error (`tool_failure`, raised `from None` outside any `except` block) carry redacted messages too.
    - An unknown tool stays FastMCP 4.0.11's tool result (`isError: true`). The spec's JSON-RPC `-32602` (`Unknown tool: invalid_tool_name`) is a known gap; do not change the wire format. See `COOKBOOK.md` Recipe 12.
 3. **Multi-Stage Non-Root Containers**:
-   - The `Dockerfile` must use a multi-stage build (`python:3.12-slim AS builder` $\rightarrow$ runtime, pulled from the ECR Public mirror of Docker Official Images and pinned by digest) creating and executing under non-root `USER mcp` with virtual environment `/opt/venv`. The runtime stage carries `LABEL io.modelcontextprotocol.server.name` equal to the `server.json` `name` (MCP Registry OCI ownership check), and the default command stays stdio.
+   - The `Dockerfile` must use a multi-stage build (`python:3.14-slim AS builder` $\rightarrow$ runtime, pulled from Docker Hub and pinned by digest) creating and executing under non-root `USER mcp` with virtual environment `/opt/venv`. The runtime stage carries `LABEL io.modelcontextprotocol.server.name` equal to the `server.json` `name` (MCP Registry OCI ownership check), and the default command stays stdio.
+   - Trust stores follow FastMCP's [certificate authority incident notice (October 2026)](https://github.com/PrefectHQ/fastmcp/blob/main/SECURITY.md#certificate-authority-incident-october-2026): both stages upgrade the OS `ca-certificates` package and fail the build below the patched Debian version (`ARG CA_CERTIFICATES_FLOOR`, declared once), the builder does so before any pip runs because pip trusts the OS store as well as its bundled certifi, the builder bootstraps pip 26.2.2, and `certifi>=2026.10.19` is a direct dependency. `tests/test_dockerfile.py` and CI's `docker-build` job enforce the order and the floor.
+   - The pip bootstrap is hash-pinned in `docker/pip-bootstrap.txt` and installed with `--require-hashes`, so it does not depend on the TLS trust of the base image's older pip and certifi; whoever raises the pip floor updates that pin and its sha256 from PyPI (`https://pypi.org/pypi/pip/<version>/json`, the `py3-none-any` wheel's `digests.sha256`), because Dependabot does not track the file.
+   - Lowering `CA_CERTIFICATES_FLOOR` with `--build-arg` is unsupported; the build-arg exists only so CI can raise it for the negative floor check, and CI and the release workflow never pass it otherwise.
 4. **Registry Metadata Constraint**:
    - In `server.json`, the root `description` must be **strictly $\le$ 100 characters** to pass MCP Registry schema validation (longer strings trigger HTTP 422 errors).
    - The default package transport is `stdio`, and packages must specify `"runtimeHint": "uvx"`.
@@ -144,7 +147,7 @@ When translating an API documentation page, `llm.txt`, or OpenAPI specification
    - `<NAME>_MCP_AUTH_TOKEN` is read with `.strip()`; empty or whitespace-only means no auth plus a warning. When set, every HTTP entry point (`main()`, `fastmcp run`, `http_app()`) requires `Authorization: Bearer <token>` (`SharedTokenVerifier`: constant-time compare, token hidden from `repr`, blank tokens refused).
    - An HTTP transport on a host other than `127.0.0.1`, `::1` or `localhost` refuses to start without a token unless `<NAME>_MCP_ALLOW_UNAUTHENTICATED_BIND=1`. Stdio is unaffected and stays the image default (`COOKBOOK.md` Recipe 8).
 6. **SSRF & DNS Rebinding Defense**:
-   - Outbound requests must enforce HTTPS, disallow loopback/private/internal IP addresses, and offload DNS hostname verification to worker threads via `asyncio.to_thread` in `SSRFSafeAsyncTransport` to protect event loop responsiveness.
+   - Outbound requests must enforce HTTPS, disallow loopback/private/internal IP addresses, and offload DNS hostname verification to worker threads via `asyncio.to_thread` in `SSRFSafeAsyncTransport` to protect event loop responsiveness. The transport then connects only to an address it checked, trying the next checked address if a connect fails, and keeps the hostname in the URL for the Host header, TLS SNI, certificate verification and per-hostname connection pooling, so the name is never looked up a second time. The client, the drift fetch (`--spec-url`) and `ingest_statutes.py --check-upstream` all use it, and none follows redirects. httpx ignores env proxies whenever a transport is passed (`allow_env_proxies = trust_env and transport is None`), so connections always go direct through the pin; egress-proxy deployments need a proxy-aware transport, which isn't provided; `trust_env=False` on the drift fetch and the `--check-upstream` probe is belt-and-braces.
 7. **Defensive API Contracts & Payload Hardening**:
    - Guard against polymorphic nulls and missing keys with typed extraction helpers (`extract_dict`, `extract_list`); never chain naked `.get()` calls without type assertions. Status-classification and selection-loop patterns are in **`COOKBOOK.md`** Recipe 10.
 8. **Git Safety & Streamlined Releases**:
@@ -163,6 +166,8 @@ When translating an API documentation page, `llm.txt`, or OpenAPI specification
 
 ## 🛠️ Development & Verification Commands
 
+uv 0.13.4 or later is required (`[tool.uv] required-version` in `pyproject.toml`, from FastMCP's certificate authority incident notice); older uv refuses to run, and CI's `setup-uv` installs from that setting.
+
 ```bash
 # Install editable with dev dependencies
 uv sync --locked --extra dev
@@ -199,6 +204,6 @@ coderabbit review --agent --uncommitted
 
 ## 🔄 CI & Releases
 
-CI is defined in `.github/workflows/ci.yml` (jobs: `lint-and-types`, `test` on Python 3.10–3.13, `tool-contract`, `build-check`, `docker-build` (builds the image without pushing and checks its MCP server-name label against `server.json`)). It runs on pushes and pull requests to `main`, daily on `main` at 09:29 UTC (`schedule`), and on manual dispatch (`workflow_dispatch`); the daily run exists because merges by `dependabot-automerge.yml` use `GITHUB_TOKEN`, and pushes made with `GITHUB_TOKEN` don't trigger push workflows, so those merges get no `push` run. Run the commands above before opening a PR. Scheduled upstream drift runs in `drift-monitor.yml`. `dependabot-automerge.yml` turns on squash auto-merge only for Dependabot PRs whose highest update is minor or patch; major updates wait for a human review.
+CI is defined in `.github/workflows/ci.yml` (jobs: `lint-and-types`, `test` on Python 3.10–3.14, `tool-contract`, `build-check`, `docker-build` (builds the image without pushing, checks its MCP server-name label against `server.json`, and checks that the builder stage fails at its `ca-certificates` floor check, before any pip step, when the floor is above the installed version)). It runs on pushes and pull requests to `main`, daily on `main` at 09:29 UTC (`schedule`), and on manual dispatch (`workflow_dispatch`); the daily run exists because merges by `dependabot-automerge.yml` use `GITHUB_TOKEN`, and pushes made with `GITHUB_TOKEN` don't trigger push workflows, so those merges get no `push` run. Run the commands above before opening a PR. Scheduled upstream drift runs in `drift-monitor.yml`. `dependabot-automerge.yml` turns on squash auto-merge only for Dependabot PRs whose highest update is minor or patch; major updates wait for a human review. Docker base image updates (`package-ecosystem` `docker`) never auto-merge and always wait for a human review: Dependabot's docker ecosystem can move the image tag, not just its digest (for example `python:3.12-slim` to `python:3.14-slim`, a Python runtime upgrade that Dependabot labels a minor update), so the job logs a notice and leaves the PR open.
 
 `release.yml` runs on `v*` tag pushes only: it creates the GitHub Release, then builds the container image, pushes it to GHCR, attests it, and publishes to the MCP Registry. In the template repo the image is built only (no push), and the attest and registry jobs skip. Release procedure (tag-based versioning, release notes, pre-tag checks): **`COOKBOOK.md`** Recipes 1–2; product-repo migration steps: Recipe 9.

mcp_server_taxcode-0.8.0/Dockerfile

@@ -0,0 +1,83 @@
+# Multi-stage build for mcp-server-taxcode
+# Produces a minimal runtime image (~150MB) with no dev tooling.
+#
+# The base image is the Docker Official python image pulled from Docker Hub,
+# pinned by its multi-arch index digest. Dependabot's docker ecosystem keeps the
+# digest current.
+# No `# syntax=` line: the Dockerfile uses only features of BuildKit's built-in
+# frontend, so no frontend image is pulled.
+
+# FastMCP's October 2026 certificate authority incident notice says to update the
+# container's OS trust store: older base images ship a ca-certificates that predates the fix.
+# Debian shipped 20250419+deb13u1 in trixie-security. Both stages upgrade the package and
+# fail the build if the installed version is older than this floor, so a base image change
+# cannot drop the fix. The builder does it before any pip runs, because pip trusts the OS
+# store as well as its bundled certifi.
+# https://github.com/PrefectHQ/fastmcp/pull/5945 (notice) and
+# https://security-tracker.debian.org/tracker/DSA-6572-1 (Debian floor)
+ARG CA_CERTIFICATES_FLOOR=20250419+deb13u1
+
+# ─── Stage 1: Builder ─────────────────────────────────────────────────────────
+FROM python:3.14-slim@sha256:fbecd461fc72d21b2143c6eaba25143738079154a6d0ea3da3aec724f50eed4a AS builder
+
+ARG CA_CERTIFICATES_FLOOR
+RUN apt-get update && \
+    apt-get install -y --no-install-recommends --only-upgrade ca-certificates && \
+    rm -rf /var/lib/apt/lists/* && \
+    installed="$(dpkg-query -W -f='${Version}' ca-certificates)" && \
+    { dpkg --compare-versions "$installed" ge "$CA_CERTIFICATES_FLOOR" || \
+      { echo "ca-certificates $installed is older than the floor $CA_CERTIFICATES_FLOOR" >&2; exit 1; }; }
+
+WORKDIR /app
+
+# Install build deps in a virtualenv so we can copy it cleanly
+RUN python -m venv /opt/venv
+ENV PATH="/opt/venv/bin:$PATH"
+
+COPY docker/pip-bootstrap.txt /tmp/pip-bootstrap.txt
+COPY pyproject.toml README.md LICENSE ./
+COPY src/ src/
+
+# The build context has no .git, so uv-dynamic-versioning cannot read the tag and
+# falls back to 0.0.0. Release builds pass the tag version, for example
+# --build-arg UV_DYNAMIC_VERSIONING_BYPASS=1.3.1 (an unset or empty value keeps 0.0.0).
+ARG UV_DYNAMIC_VERSIONING_BYPASS
+ENV UV_DYNAMIC_VERSIONING_BYPASS=${UV_DYNAMIC_VERSIONING_BYPASS}
+
+# pip 26.2.2 updates the certificates pip bundles, per FastMCP's October 2026 certificate
+# authority incident notice. This image builds with pip, not uv, so pip carries the floor.
+# https://github.com/PrefectHQ/fastmcp/blob/main/SECURITY.md#certificate-authority-incident-october-2026
+# The bootstrap installs pip from a hash-pinned wheel (docker/pip-bootstrap.txt, --require-hashes),
+# so it does not depend on the TLS trust of the base image's older pip and certifi; the maintainer
+# who raises the pip floor updates that pin and its sha256 (Dependabot does not track the file).
+RUN pip install --no-cache-dir --require-hashes --only-binary=:all: -r /tmp/pip-bootstrap.txt && \
+    pip install --no-cache-dir .
+
+# ─── Stage 2: Runtime ─────────────────────────────────────────────────────────
+FROM python:3.14-slim@sha256:fbecd461fc72d21b2143c6eaba25143738079154a6d0ea3da3aec724f50eed4a AS runtime
+
+# MCP Registry ownership check for the OCI package: must equal server.json "name".
+# https://modelcontextprotocol.io/registry/package-types#docker%2Foci-images
+LABEL io.modelcontextprotocol.server.name="io.github.christianclaudio/taxcode"
+
+# OS trust store update and floor check, the same as the builder (see CA_CERTIFICATES_FLOOR).
+ARG CA_CERTIFICATES_FLOOR
+RUN apt-get update && \
+    apt-get install -y --no-install-recommends --only-upgrade ca-certificates && \
+    rm -rf /var/lib/apt/lists/* && \
+    installed="$(dpkg-query -W -f='${Version}' ca-certificates)" && \
+    { dpkg --compare-versions "$installed" ge "$CA_CERTIFICATES_FLOOR" || \
+      { echo "ca-certificates $installed is older than the floor $CA_CERTIFICATES_FLOOR" >&2; exit 1; }; }
+
+# Security: run as non-root
+RUN useradd --create-home --shell /bin/bash mcp
+USER mcp
+WORKDIR /home/mcp
+
+# Copy the pre-built virtualenv from builder
+COPY --from=builder /opt/venv /opt/venv
+ENV PATH="/opt/venv/bin:$PATH"
+
+# Default transport is stdio, so no port is exposed
+ENTRYPOINT ["taxcode-mcp"]
+

{mcp_server_taxcode-0.7.1 → mcp_server_taxcode-0.8.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: mcp-server-taxcode
-Version: 0.7.1
+Version: 0.8.0
 Summary: Enterprise Model Context Protocol (MCP) server for Tax Code
 Project-URL: Homepage, https://github.com/christianclaudio/mcp-server-taxcode
 Project-URL: Documentation, https://github.com/christianclaudio/mcp-server-taxcode#readme
@@ -20,18 +20,20 @@ Classifier: Programming Language :: Python :: 3.10
 Classifier: Programming Language :: Python :: 3.11
 Classifier: Programming Language :: Python :: 3.12
 Classifier: Programming Language :: Python :: 3.13
+Classifier: Programming Language :: Python :: 3.14
 Classifier: Topic :: Software Development :: Libraries :: Python Modules
 Requires-Python: >=3.10
+Requires-Dist: certifi>=2026.10.19
 Requires-Dist: duckdb>=1.5.6
-Requires-Dist: fastmcp>=4.1.0
+Requires-Dist: fastmcp>=4.1.3
 Requires-Dist: httpx>=0.28.1
 Requires-Dist: mcp>=2.3.0
 Requires-Dist: pydantic-settings>=2.15.0
 Requires-Dist: pydantic>=2.13.5
 Provides-Extra: code-mode
-Requires-Dist: fastmcp[code-mode]>=4.1.0; extra == 'code-mode'
+Requires-Dist: fastmcp[code-mode]>=4.1.3; extra == 'code-mode'
 Provides-Extra: dev
-Requires-Dist: fastmcp[code-mode]>=4.1.0; extra == 'dev'
+Requires-Dist: fastmcp[code-mode]>=4.1.3; extra == 'dev'
 Requires-Dist: mypy>=2.4.0; extra == 'dev'
 Requires-Dist: opentelemetry-sdk>=1.45.1; extra == 'dev'
 Requires-Dist: pytest-asyncio>=1.4.0; extra == 'dev'

mcp_server_taxcode-0.8.0/SECURITY.md

@@ -0,0 +1,18 @@
+# Security Policy
+
+## Supported Versions
+
+Only the latest release receives security fixes. Upgrade to the newest version on [Releases](https://github.com/christianclaudio/mcp-server-taxcode/releases).
+
+## Outbound Connections and Proxies
+
+Every outbound request (the upstream API client, the drift monitor's `--spec-url` fetch and `ingest_statutes.py --check-upstream`) goes through `SSRFSafeAsyncTransport`. It looks the host up once per request, checks every address against the private, loopback, link-local, reserved and metadata ranges, and connects only to a checked address, keeping the hostname for the Host header, TLS SNI and certificate verification. Redirects are not followed. httpx ignores env proxies whenever a transport is passed (httpx `AsyncClient`: `allow_env_proxies = trust_env and transport is None`), so connections always go direct through the pin; egress-proxy deployments need a proxy-aware transport, which isn't provided. `trust_env=False` on the drift fetch and the `--check-upstream` probe is belt-and-braces.
+
+## Reporting a Vulnerability
+
+If you discover a security vulnerability, please do NOT open a public GitHub issue.
+
+Please report vulnerabilities directly to the maintainer:
+* **Email**: `christianclaudio@mail.com`
+
+All reports will be acknowledged within 24 hours, and patches will be published with high priority.

mcp_server_taxcode-0.8.0/docker/pip-bootstrap.txt

@@ -0,0 +1,5 @@
+# pip for the Dockerfile builder's bootstrap, installed with --require-hashes so the install
+# does not depend on TLS trust. Hash of pip-26.2.2-py3-none-any.whl from PyPI's JSON API
+# (digests.sha256). Bump this pin and hash together with the pip floor; Dependabot does not.
+pip==26.2.2 \
+    --hash=sha256:fd7f4dfa8190e014013b9f08f3e973f4e4c26ffd179a204895533a7254813a70