Installing packagetrackdev by hand

For a machine where the one-line installers cannot run. You check
each file against its published SHA256 yourself, then uv installs
the checked file. You need uv:
  https://docs.astral.sh/uv/getting-started/installation/

The current files:
  packagetrackdev
    https://packagetrack.dev/cli/packagetrackdev-0.5.0-py3-none-any.whl
  packagetrackdev-mcp
    https://packagetrack.dev/cli/packagetrackdev_mcp-0.3.0-py3-none-any.whl
Each checksum is at the same address with .sha256 added.

Windows (PowerShell)

  packagetrackdev
  1. Download the file and print its published checksum:
       Invoke-WebRequest -UseBasicParsing https://packagetrack.dev/cli/packagetrackdev-0.5.0-py3-none-any.whl -OutFile packagetrackdev-0.5.0-py3-none-any.whl
       Invoke-RestMethod https://packagetrack.dev/cli/packagetrackdev-0.5.0-py3-none-any.whl.sha256
  2. Print the file's own checksum. It must be the same line:
       (Get-FileHash -Algorithm SHA256 packagetrackdev-0.5.0-py3-none-any.whl).Hash.ToLower()
  3. Only if they match, install the checked file:
       uv tool install --force .\packagetrackdev-0.5.0-py3-none-any.whl

  packagetrackdev-mcp
  1. Download the file and print its published checksum:
       Invoke-WebRequest -UseBasicParsing https://packagetrack.dev/cli/packagetrackdev_mcp-0.3.0-py3-none-any.whl -OutFile packagetrackdev_mcp-0.3.0-py3-none-any.whl
       Invoke-RestMethod https://packagetrack.dev/cli/packagetrackdev_mcp-0.3.0-py3-none-any.whl.sha256
  2. Print the file's own checksum. It must be the same line:
       (Get-FileHash -Algorithm SHA256 packagetrackdev_mcp-0.3.0-py3-none-any.whl).Hash.ToLower()
  3. Only if they match, install the checked file:
       uv tool install --force .\packagetrackdev_mcp-0.3.0-py3-none-any.whl

Linux and macOS

  packagetrackdev
  1. Download the file and print its published checksum:
       curl -fsSLO https://packagetrack.dev/cli/packagetrackdev-0.5.0-py3-none-any.whl
       curl -fsSL https://packagetrack.dev/cli/packagetrackdev-0.5.0-py3-none-any.whl.sha256; echo
  2. Print the file's own checksum. It must be the same line:
       sha256sum packagetrackdev-0.5.0-py3-none-any.whl        (macOS: shasum -a 256 packagetrackdev-0.5.0-py3-none-any.whl)
  3. Only if they match, install the checked file:
       uv tool install --force ./packagetrackdev-0.5.0-py3-none-any.whl

  packagetrackdev-mcp
  1. Download the file and print its published checksum:
       curl -fsSLO https://packagetrack.dev/cli/packagetrackdev_mcp-0.3.0-py3-none-any.whl
       curl -fsSL https://packagetrack.dev/cli/packagetrackdev_mcp-0.3.0-py3-none-any.whl.sha256; echo
  2. Print the file's own checksum. It must be the same line:
       sha256sum packagetrackdev_mcp-0.3.0-py3-none-any.whl        (macOS: shasum -a 256 packagetrackdev_mcp-0.3.0-py3-none-any.whl)
  3. Only if they match, install the checked file:
       uv tool install --force ./packagetrackdev_mcp-0.3.0-py3-none-any.whl

On Windows, close any coding agent that runs packagetrackdev-mcp
first: Windows keeps a running tool's files locked.

uv records the file you installed from and reads it again for
`uv tool upgrade --all`: keep it where it is. To reinstall, or to
move to a newer release, repeat these steps with the files this page
lists then.

To uninstall:
  uv tool uninstall packagetrackdev packagetrackdev-mcp
then delete the wheels you installed from, and the folder the
one-line installers keep them in: ~/.packagetrack/wheels
(%USERPROFILE%\.packagetrack\wheels on Windows). Uninstall first:
while a tool is installed, `uv tool upgrade --all` reads its wheel.
The rest of ~/.packagetrack holds your settings and API key
(config.toml); delete the whole folder to remove everything.

Limits: the checksum covers these two files only. Their dependencies
(httpx; for the server also the MCP SDK and what it needs) are
downloaded by uv from PyPI and rest on PyPI's own checks, not ours.

For your coding agent: claude mcp add -s user packagetrackdev -- packagetrackdev-mcp