toolprint 0.1.0__tar.gz

toolprint-0.1.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 2026 Keith Foster
+
+   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.

toolprint-0.1.0/PKG-INFO

@@ -0,0 +1,208 @@
+Metadata-Version: 2.4
+Name: toolprint
+Version: 0.1.0
+Summary: What your agent's tool surface costs, and what it can do. Offline MCP assessment: context cost, capability risk, and definition drift.
+Author: Keith Foster
+License-Expression: Apache-2.0
+Project-URL: Homepage, https://github.com/dit4e/toolprint
+Project-URL: Repository, https://github.com/dit4e/toolprint
+Project-URL: Issues, https://github.com/dit4e/toolprint/issues
+Project-URL: Drift dataset, https://github.com/dit4e/toolprint-watch
+Keywords: mcp,model-context-protocol,security,ai-agents,llm,drift-detection,sarif,context-window,supply-chain
+Classifier: Development Status :: 3 - Alpha
+Classifier: Environment :: Console
+Classifier: Intended Audience :: Developers
+Classifier: Intended Audience :: System Administrators
+Classifier: Operating System :: OS Independent
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3 :: Only
+Classifier: Programming Language :: Python :: 3.9
+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: Topic :: Security
+Classifier: Topic :: Software Development :: Quality Assurance
+Classifier: Topic :: System :: Monitoring
+Classifier: Typing :: Typed
+Requires-Python: >=3.9
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Provides-Extra: tokens
+Requires-Dist: tiktoken>=0.5; extra == "tokens"
+Dynamic: license-file
+
+# toolprint
+
+**What your agent's tool surface costs, and what it can do.**
+
+Point it at a laptop and get back the number of tokens your MCP tools consume on
+every request before you type anything, how many of them can delete, send or
+spend, and how many of those sit behind no authentication.
+
+Offline. No account. Nothing is transmitted.
+
+```bash
+uvx toolprint scan                    # inventory, no network, no subprocesses
+uvx toolprint scan --connect          # retrieve live tool definitions
+uvx toolprint scan --connect --html report.html
+```
+
+---
+
+## Why the numbers are per-context
+
+A conversation loads exactly one client in exactly one project. That pairing is
+the only unit in which "what do my tools cost per conversation" has an answer.
+
+Scope precedence is real and mostly invisible: Claude Code resolves local over
+project over user, Cursor and VS Code resolve project over user, and in every
+case the *whole* entry from the winning scope is used — nothing is merged. So a
+machine with 19 configured entries may resolve to 11 distinct servers, of which
+one context loads 8. The other 11 entries are not a conservative overestimate;
+they describe no state the system is ever in. Entries that lose are reported as
+shadowed configuration, because editing one has no effect and produces no
+warning.
+
+## What it reports
+
+| | |
+|---|---|
+| **Cost** | Per-tool and per-context token counts, as a share of your window |
+| **Capability** | Every tool classified `read` / `write` / `external` / `irreversible` |
+| **Mislabelled tools** | Tools whose safety annotation their own name or schema contradicts |
+| **Auth posture** | `none`, `env_var`, `literal_secret`, `helper_command`, `oauth` |
+| **Hygiene** | Credentials stored literally in config files, shadowed entries, unreachable servers |
+
+Findings carry stable ids (`AUTH-001`, `COST-001`, `HYG-002`, …) with fixed
+titles and standard remediation, so two reports are comparable.
+
+## Output
+
+Everything renders from `findings.json`; nothing renders from raw collected data.
+
+```bash
+toolprint scan --connect --findings findings.json --html report.html
+toolprint viewer report.html      # empty viewer; drop any findings.json on it
+toolprint demo demo.html          # synthetic report, to see the output first
+```
+
+The HTML report is a single self-contained file. All CSS and JS inline, no CDN,
+no fonts, no analytics, and a Content-Security-Policy of `default-src 'none'`
+with `connect-src 'none'` — it has no capability to transmit what it displays.
+It opens from `file://` and prints cleanly to PDF.
+
+## Drift
+
+Once a baseline exists, `check` reports what changed without anyone reviewing it.
+
+```bash
+toolprint baseline --connect --by "$USER" --note "reviewed"
+toolprint check --connect --fail-on high
+toolprint approve --tool contact_delete --by "$USER" --note "expected in 4.2"
+```
+
+Ten rules, most severe first: effect-class escalation and revoked safety
+annotations are `critical`; a description that changed while its schema did not
+is `high`, because that is the rug-pull signature — an attacker rewriting a
+tool's instructions has to leave the schema alone or the tool stops working.
+Invisible characters and cross-server references appearing in text are `high`
+too. Breaking schema changes and new tools are `medium`; additive changes and
+removals are `low`.
+
+**Baselines refuse to bless a suspicious state.** Trust-on-first-use means a
+baseline approves whatever is in front of it, so `baseline` inspects the current
+surface for invisible characters, homoglyphs and cross-server shadowing first,
+and will not write a clean baseline over any of them without `--force`.
+
+**Exceptions require a reason and an expiry.** A suppression that cannot lapse
+becomes permanent by neglect, and then nobody reads the report at all. Expired
+exceptions stop suppressing and say so in the output.
+
+Hashes are per component — description, schema, annotations — rather than one
+blob, because only that split shows the description-moved-schema-didn't
+correlation. Canonicalisation normalises structure and never content:
+`transfer` and `transfеr` (Cyrillic е) hash differently on purpose, so a
+homoglyph substitution is caught rather than normalised away.
+
+## CI
+
+```bash
+toolprint scan --format json --fail-on high
+toolprint check --format sarif --out toolprint.sarif
+```
+
+Exit `0` below the threshold, `1` at or above it, `2` on execution error, `3`
+when the baseline is missing or was written by a different heuristics version.
+
+SARIF drops into GitHub code scanning, so findings land as annotations on the
+pull request. There is a ready-made action — see
+[docs/github-action.md](docs/github-action.md).
+
+## Assessment bundles
+
+`toolprint kit mcp_collect.py` writes a standalone, dependency-free script under
+400 lines that someone else can run on their own machine to produce a redacted
+bundle. It has exactly one outbound call — reachable only under `--connect`, and
+only to their own MCP servers. Redaction is an allowlist in one visible
+constant. See [docs/collection-kit-README.md](docs/collection-kit-README.md).
+
+## What it catches, and what it does not
+
+**Catches:** context cost and its distribution · unauthenticated servers exposing
+destructive capability · mislabelled tools · credentials in config files ·
+shadowed configuration · servers that fail to start.
+
+**Does not catch:** a server that is malicious from the first scan — this
+detects change and misconfiguration, not initial badness · a server doing
+exactly what it advertises · runtime behaviour that changes without the tool
+definition changing · whether a description will actually manipulate a given
+model.
+
+It composes with scanners that address the first case rather than replacing
+them.
+
+## Install
+
+```bash
+uvx toolprint scan          # no install
+pipx install toolprint
+pip install "toolprint[tokens]"   # optional tiktoken for exact token counts
+```
+
+Python 3.9+. The core has no required dependencies. Without `tiktoken`, token
+counts use a character ratio calibrated against real tool definitions (4.55
+chars/token, ~4% median error), and the method used is recorded per server.
+
+## Why it reports what it reports
+
+[DESIGN.md](DESIGN.md) covers the decisions most likely to surprise you: why
+cost is per context, why annotations give a floor and a ceiling, why
+canonicalisation refuses to normalise Unicode, and why the drift rules are
+ordered as they are.
+
+## Does drift actually happen?
+
+[dit4e/toolprint-watch](https://github.com/dit4e/toolprint-watch) checks 27
+public MCP servers daily against an approved baseline and commits what changed,
+so the git history of that baseline is an open record of how often tool
+definitions move. It is a separate repository so a year of observation commits
+does not bury this one.
+
+Worth knowing what it cannot see: of 18 well-known public remote MCP endpoints,
+**two** served `tools/list` without credentials. Remote servers are the category
+where a definition change is least visible to the people using them — no package
+update, no lockfile line — and also the category nobody outside the vendor can
+audit. That is an argument for running `toolprint check` in your own CI, where
+you already hold the credentials, rather than waiting for someone else to notice.
+
+## Status
+
+Early, but complete through drift. `scan`, `check`, baselines, approvals,
+bundles, the HTML viewer and SARIF are built and dogfooded. Opt-in peer
+benchmarking is next; `findings.json` already carries the `benchmark` field it
+will populate.
+
+## Licence
+
+Apache-2.0.

toolprint-0.1.0/README.md

@@ -0,0 +1,174 @@
+# toolprint
+
+**What your agent's tool surface costs, and what it can do.**
+
+Point it at a laptop and get back the number of tokens your MCP tools consume on
+every request before you type anything, how many of them can delete, send or
+spend, and how many of those sit behind no authentication.
+
+Offline. No account. Nothing is transmitted.
+
+```bash
+uvx toolprint scan                    # inventory, no network, no subprocesses
+uvx toolprint scan --connect          # retrieve live tool definitions
+uvx toolprint scan --connect --html report.html
+```
+
+---
+
+## Why the numbers are per-context
+
+A conversation loads exactly one client in exactly one project. That pairing is
+the only unit in which "what do my tools cost per conversation" has an answer.
+
+Scope precedence is real and mostly invisible: Claude Code resolves local over
+project over user, Cursor and VS Code resolve project over user, and in every
+case the *whole* entry from the winning scope is used — nothing is merged. So a
+machine with 19 configured entries may resolve to 11 distinct servers, of which
+one context loads 8. The other 11 entries are not a conservative overestimate;
+they describe no state the system is ever in. Entries that lose are reported as
+shadowed configuration, because editing one has no effect and produces no
+warning.
+
+## What it reports
+
+| | |
+|---|---|
+| **Cost** | Per-tool and per-context token counts, as a share of your window |
+| **Capability** | Every tool classified `read` / `write` / `external` / `irreversible` |
+| **Mislabelled tools** | Tools whose safety annotation their own name or schema contradicts |
+| **Auth posture** | `none`, `env_var`, `literal_secret`, `helper_command`, `oauth` |
+| **Hygiene** | Credentials stored literally in config files, shadowed entries, unreachable servers |
+
+Findings carry stable ids (`AUTH-001`, `COST-001`, `HYG-002`, …) with fixed
+titles and standard remediation, so two reports are comparable.
+
+## Output
+
+Everything renders from `findings.json`; nothing renders from raw collected data.
+
+```bash
+toolprint scan --connect --findings findings.json --html report.html
+toolprint viewer report.html      # empty viewer; drop any findings.json on it
+toolprint demo demo.html          # synthetic report, to see the output first
+```
+
+The HTML report is a single self-contained file. All CSS and JS inline, no CDN,
+no fonts, no analytics, and a Content-Security-Policy of `default-src 'none'`
+with `connect-src 'none'` — it has no capability to transmit what it displays.
+It opens from `file://` and prints cleanly to PDF.
+
+## Drift
+
+Once a baseline exists, `check` reports what changed without anyone reviewing it.
+
+```bash
+toolprint baseline --connect --by "$USER" --note "reviewed"
+toolprint check --connect --fail-on high
+toolprint approve --tool contact_delete --by "$USER" --note "expected in 4.2"
+```
+
+Ten rules, most severe first: effect-class escalation and revoked safety
+annotations are `critical`; a description that changed while its schema did not
+is `high`, because that is the rug-pull signature — an attacker rewriting a
+tool's instructions has to leave the schema alone or the tool stops working.
+Invisible characters and cross-server references appearing in text are `high`
+too. Breaking schema changes and new tools are `medium`; additive changes and
+removals are `low`.
+
+**Baselines refuse to bless a suspicious state.** Trust-on-first-use means a
+baseline approves whatever is in front of it, so `baseline` inspects the current
+surface for invisible characters, homoglyphs and cross-server shadowing first,
+and will not write a clean baseline over any of them without `--force`.
+
+**Exceptions require a reason and an expiry.** A suppression that cannot lapse
+becomes permanent by neglect, and then nobody reads the report at all. Expired
+exceptions stop suppressing and say so in the output.
+
+Hashes are per component — description, schema, annotations — rather than one
+blob, because only that split shows the description-moved-schema-didn't
+correlation. Canonicalisation normalises structure and never content:
+`transfer` and `transfеr` (Cyrillic е) hash differently on purpose, so a
+homoglyph substitution is caught rather than normalised away.
+
+## CI
+
+```bash
+toolprint scan --format json --fail-on high
+toolprint check --format sarif --out toolprint.sarif
+```
+
+Exit `0` below the threshold, `1` at or above it, `2` on execution error, `3`
+when the baseline is missing or was written by a different heuristics version.
+
+SARIF drops into GitHub code scanning, so findings land as annotations on the
+pull request. There is a ready-made action — see
+[docs/github-action.md](docs/github-action.md).
+
+## Assessment bundles
+
+`toolprint kit mcp_collect.py` writes a standalone, dependency-free script under
+400 lines that someone else can run on their own machine to produce a redacted
+bundle. It has exactly one outbound call — reachable only under `--connect`, and
+only to their own MCP servers. Redaction is an allowlist in one visible
+constant. See [docs/collection-kit-README.md](docs/collection-kit-README.md).
+
+## What it catches, and what it does not
+
+**Catches:** context cost and its distribution · unauthenticated servers exposing
+destructive capability · mislabelled tools · credentials in config files ·
+shadowed configuration · servers that fail to start.
+
+**Does not catch:** a server that is malicious from the first scan — this
+detects change and misconfiguration, not initial badness · a server doing
+exactly what it advertises · runtime behaviour that changes without the tool
+definition changing · whether a description will actually manipulate a given
+model.
+
+It composes with scanners that address the first case rather than replacing
+them.
+
+## Install
+
+```bash
+uvx toolprint scan          # no install
+pipx install toolprint
+pip install "toolprint[tokens]"   # optional tiktoken for exact token counts
+```
+
+Python 3.9+. The core has no required dependencies. Without `tiktoken`, token
+counts use a character ratio calibrated against real tool definitions (4.55
+chars/token, ~4% median error), and the method used is recorded per server.
+
+## Why it reports what it reports
+
+[DESIGN.md](DESIGN.md) covers the decisions most likely to surprise you: why
+cost is per context, why annotations give a floor and a ceiling, why
+canonicalisation refuses to normalise Unicode, and why the drift rules are
+ordered as they are.
+
+## Does drift actually happen?
+
+[dit4e/toolprint-watch](https://github.com/dit4e/toolprint-watch) checks 27
+public MCP servers daily against an approved baseline and commits what changed,
+so the git history of that baseline is an open record of how often tool
+definitions move. It is a separate repository so a year of observation commits
+does not bury this one.
+
+Worth knowing what it cannot see: of 18 well-known public remote MCP endpoints,
+**two** served `tools/list` without credentials. Remote servers are the category
+where a definition change is least visible to the people using them — no package
+update, no lockfile line — and also the category nobody outside the vendor can
+audit. That is an argument for running `toolprint check` in your own CI, where
+you already hold the credentials, rather than waiting for someone else to notice.
+
+## Status
+
+Early, but complete through drift. `scan`, `check`, baselines, approvals,
+bundles, the HTML viewer and SARIF are built and dogfooded. Opt-in peer
+benchmarking is next; `findings.json` already carries the `benchmark` field it
+will populate.
+
+## Licence
+
+Apache-2.0.

toolprint-0.1.0/pyproject.toml

@@ -0,0 +1,52 @@
+[build-system]
+requires = ["setuptools>=61"]
+build-backend = "setuptools.build_meta"
+
+[project]
+name = "toolprint"
+version = "0.1.0"
+description = "What your agent's tool surface costs, and what it can do. Offline MCP assessment: context cost, capability risk, and definition drift."
+readme = "README.md"
+requires-python = ">=3.9"
+license = "Apache-2.0"
+license-files = ["LICENSE"]
+authors = [{ name = "Keith Foster" }]
+keywords = ["mcp", "model-context-protocol", "security", "ai-agents", "llm",
+            "drift-detection", "sarif", "context-window", "supply-chain"]
+dependencies = []          # core is stdlib-only; this is a load-bearing claim, not an accident
+classifiers = [
+    "Development Status :: 3 - Alpha",
+    "Environment :: Console",
+    "Intended Audience :: Developers",
+    "Intended Audience :: System Administrators",
+    "Operating System :: OS Independent",
+    "Programming Language :: Python :: 3",
+    "Programming Language :: Python :: 3 :: Only",
+    "Programming Language :: Python :: 3.9",
+    "Programming Language :: Python :: 3.10",
+    "Programming Language :: Python :: 3.11",
+    "Programming Language :: Python :: 3.12",
+    "Programming Language :: Python :: 3.13",
+    "Topic :: Security",
+    "Topic :: Software Development :: Quality Assurance",
+    "Topic :: System :: Monitoring",
+    "Typing :: Typed",
+]
+
+[project.urls]
+Homepage = "https://github.com/dit4e/toolprint"
+Repository = "https://github.com/dit4e/toolprint"
+Issues = "https://github.com/dit4e/toolprint/issues"
+"Drift dataset" = "https://github.com/dit4e/toolprint-watch"
+
+[project.optional-dependencies]
+tokens = ["tiktoken>=0.5"] # optional accuracy upgrade only; never auto-installed
+
+[project.scripts]
+toolprint = "toolprint.cli:main"
+
+[tool.setuptools.packages.find]
+where = ["src"]
+
+[tool.setuptools.package-data]
+toolprint = ["viewer/*.html", "vendor/*.py", "py.typed"]

toolprint-0.1.0/setup.cfg

@@ -0,0 +1,4 @@
+[egg_info]
+tag_build = 
+tag_date = 0
+

toolprint-0.1.0/src/toolprint/__init__.py

@@ -0,0 +1,10 @@
+"""toolprint - what your agent's tool surface costs, and what it can do.
+
+Footprint: the tokens tool definitions consume on every request. Fingerprint:
+what those definitions are, and whether they changed without review.
+"""
+
+# The public name is spelled here and in cli.py's argparse prog only, which is
+# what made the rename from the mcpdrift placeholder a two-line change.
+TOOL_NAME = "toolprint"
+__version__ = "0.1.0"