blastcheck-mcp 0.1.0__tar.gz

blastcheck_mcp-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 Kevin Proffitt
+
+   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.

blastcheck_mcp-0.1.0/MANIFEST.in

@@ -0,0 +1,2 @@
+prune tests
+prune docs

blastcheck_mcp-0.1.0/NOTICE

@@ -0,0 +1,8 @@
+blastcheck-mcp
+Copyright 2026 Kevin Proffitt / Proco Consulting
+
+This product includes test fixtures copied from the Impact Manifest
+specification repository (Apache-2.0):
+https://github.com/prococonsulting/impact-manifest
+
+Licensed under the Apache License, Version 2.0.

blastcheck_mcp-0.1.0/PKG-INFO

@@ -0,0 +1,219 @@
+Metadata-Version: 2.4
+Name: blastcheck-mcp
+Version: 0.1.0
+Summary: MCP server exposing blastcheck Impact Manifests to coding agents
+Author-email: Kevin Proffitt <kproffitt@prococonsulting.com>
+License: Apache-2.0
+Project-URL: Homepage, https://blastcheck.dev
+Project-URL: Source, https://github.com/prococonsulting/blastcheck-mcp
+Keywords: mcp,terraform,impact-manifest,blastcheck,change-safety
+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
+Requires-Python: >=3.10
+Description-Content-Type: text/markdown
+License-File: LICENSE
+License-File: NOTICE
+Requires-Dist: mcp<3,>=2
+Requires-Dist: blastcheck<0.8,>=0.7
+Requires-Dist: jsonschema>=4.18
+Provides-Extra: test
+Requires-Dist: pytest>=8; extra == "test"
+Dynamic: license-file
+
+# blastcheck-mcp
+
+An [MCP](https://modelcontextprotocol.io) server that gives coding
+agents (Claude Code, Claude Desktop, Cursor, and any other MCP client)
+the ability to assess Terraform plans with
+[blastcheck](https://blastcheck.dev): produce an
+[Impact Manifest](https://github.com/prococonsulting/impact-manifest) -
+a machine-readable change-safety assertion - and explain it in plain
+language.
+
+Read-only and propose-only. No tool applies Terraform, mutates a cloud
+resource, or accepts a credential. This release performs no network I/O
+at all: everything runs offline against the plan file.
+
+## Quickstart
+
+Requires Python 3.10+ and [uv](https://docs.astral.sh/uv/). No install
+step; the first run resolves everything:
+
+```
+uvx blastcheck-mcp
+```
+
+### Claude Code
+
+```
+claude mcp add blastcheck -- uvx blastcheck-mcp
+```
+
+### Claude Desktop
+
+Add to `claude_desktop_config.json` (Settings > Developer > Edit
+Config):
+
+```json
+{
+  "mcpServers": {
+    "blastcheck": {
+      "command": "uvx",
+      "args": ["blastcheck-mcp"]
+    }
+  }
+}
+```
+
+### Cursor
+
+Add to `~/.cursor/mcp.json` (or `.cursor/mcp.json` in a project):
+
+```json
+{
+  "mcpServers": {
+    "blastcheck": {
+      "command": "uvx",
+      "args": ["blastcheck-mcp"]
+    }
+  }
+}
+```
+
+## Using it
+
+Ask your agent to check a plan:
+
+```
+terraform plan -out plan.tfplan
+terraform show -json plan.tfplan > plan.json
+```
+
+Then: "run blastcheck on plan.json and explain what could go wrong."
+The agent will call impact_emit, get a manifest handle plus a verdict
+summary, and follow up with impact_explain for the full picture.
+(impact_emit also accepts the saved .tfplan directly and converts it.)
+
+## Tools
+
+### impact_emit
+
+Runs blastcheck's plan-only analysis on a `terraform show -json` file
+(or a saved .tfplan) and returns:
+
+- `manifest_handle` - a short reference to the full Impact Manifest,
+  written to a private temp file (0600, per-user 0700 directory, kept
+  at most 24h). Pass it to impact_explain instead of shuttling the
+  large document through model context.
+- `summary` - the verdict, per-severity counts, which changes drove it,
+  and the plan-only note.
+
+A plan-only run can never emit `safe` - it never verified live state,
+and blastcheck says so rather than guessing. That is the point of the
+format.
+
+### impact_explain
+
+Turns a manifest into markdown a human can act on: the verdict and why,
+each change's noteworthy findings with their rationales, a
+"safe if ..." checklist of unmet preconditions, and exactly what could
+not be verified. Deterministic local code; accepts a manifest_handle, a
+manifest_path, or the manifest inline (exactly one).
+
+Output is capped by a hard budget (BLASTCHECK_MCP_EXPLAIN_BUDGET env,
+default 32000 characters, about 8K tokens) so the tool can never
+consume a session's context in one call. Small plans render in full.
+Large plans get a compact view: dimensions identical across every
+change are stated once, changes with identical assessments are grouped
+with numeric indexes compressed to ranges (app[0..11]) - for_each
+string keys are never wildcarded, so which tenants or keys are
+affected stays visible - and blocking changes always keep their
+complete address list, dropping only per-change repetition. Whenever
+anything is grouped or cut, an explicit partial-view notice says so
+and shows the exact follow-up calls; all lists are lexically sorted
+before any cut, so the same plan always shows the same subset. Never
+a silent drop.
+
+Drill-down filters (optional, combined with AND):
+
+- `severity` - e.g. `["blocking"]` or `["blocking", "caution"]`
+- `module_prefix` - address prefix, e.g. `"module.tenants[\"contoso-prod\"]"`
+- `resource_type` - exact type, e.g. `"azurerm_managed_disk"`
+- `addresses` - exact addresses, always rendered in full detail; the
+  guaranteed path to any specific change
+
+## Compatibility
+
+Verified against real clients and across MCP protocol eras
+(v0.1.0-rc1, mcp SDK 2.x, macOS, Python 3.13):
+
+| Check | Result |
+|---|---|
+| Protocol 2024-11-05 (oldest era) | negotiated, tools list + calls work |
+| Protocol 2025-03-26 | negotiated, tools list + calls work |
+| Protocol 2025-06-18 | negotiated, tools list + calls work |
+| Unknown version offered | server answers with its latest, per spec |
+| Claude Code 2.0.76 (stdio) | connects; both tools exercised end to end in three separate headless runs. Investigated note: when driving headless `claude -p` sessions from INSIDE another Claude Code session (a nested test rig), intermittent multi-minute client startup stalls were observed; process inspection showed they occur before the MCP server process is even spawned, and the identical command succeeds on retry with no changes, so they are attributed to the nested test environment rather than this server. An ordinary interactive session has not yet been driven by a human; recommended as a final confirmation. |
+| Claude Desktop | config block above is the documented uvx form; not yet exercised on this machine |
+| Cursor | config block above is the documented uvx form; not yet exercised (Cursor not installed on the test machine) |
+| Large-plan compression | verified against a synthetic 288-change fixture ONLY (nested modules, for_each string keys, count indexes; 372KB full render compressed to a 12.5KB overview). NOT yet verified against a large real-world plan - if real changes fingerprint less uniformly, overviews will be larger; the hard output budget still caps them and the partial-view notice still applies. |
+
+## Errors
+
+Failures come back as `CODE: one clear sentence` - for example
+`FILE_NOT_FOUND: no such file: plan.json` or
+`MANIFEST_UNSUPPORTED_VERSION: ...` - never a stack trace.
+
+## Data boundary
+
+This release sends nothing anywhere: no telemetry, no API calls, no
+network I/O. Raw plan JSON never leaves the machine.
+
+A future release adds an optional CloudRift tier (live cost, dependency
+and tenant enrichment; see `docs/remote-tier.md`). Its boundary is
+already implemented and tested in this codebase, before any network
+code exists: if a manifest is ever scored remotely, what leaves the
+machine is an identity-only projection - per change: address, resource
+type, name, Terraform provider address, and actions; plus the
+manifest's schema_version, generated_at, producer name/version, and
+source type. Evidence, rationales, verdicts, attribute values (ports,
+CIDRs, sizes), and the plan itself are stripped by an explicit
+allowlist, so a future manifest field is excluded by default rather
+than leaked by default. That tier will require an explicit
+CLOUDRIFT_API_TOKEN; without one, the server registers the local tools
+only.
+
+## Environment variables
+
+| Variable | Effect |
+|---|---|
+| BLASTCHECK_MCP_EXPLAIN_BUDGET | Hard cap, in characters, on impact_explain output (default 32000, floor 4000). Over the cap, a compact grouped view with an explicit partial-view notice is returned instead - never a silent cut. |
+| CLOUDRIFT_API_TOKEN | Reserved for the future remote tier. If set today, the server notes on stderr that the remote tier is not in this release and runs the local tools only. Credentials are NEVER accepted as tool arguments. |
+
+## Development
+
+```
+python3 -m venv .venv
+.venv/bin/pip install -e ".[test]"
+.venv/bin/pytest
+```
+
+The suite is fully offline. `tests/test_project.py` holds the
+data-boundary tests; treat a failure there as a stop-ship.
+
+## Relationship to blastcheck and the spec
+
+blastcheck-mcp is a thin MCP layer over the
+[blastcheck](https://github.com/prococonsulting/blastcheck) library
+(pinned `>=0.7,<0.8`) and implements a consumer of the
+[Impact Manifest specification](https://github.com/prococonsulting/impact-manifest)
+(schema major version 0). The manifest schema is read from blastcheck's
+own vendored copy, so there is no second copy to drift.
+
+## License
+
+Apache-2.0. See [LICENSE](./LICENSE).

blastcheck_mcp-0.1.0/README.md

@@ -0,0 +1,193 @@
+# blastcheck-mcp
+
+An [MCP](https://modelcontextprotocol.io) server that gives coding
+agents (Claude Code, Claude Desktop, Cursor, and any other MCP client)
+the ability to assess Terraform plans with
+[blastcheck](https://blastcheck.dev): produce an
+[Impact Manifest](https://github.com/prococonsulting/impact-manifest) -
+a machine-readable change-safety assertion - and explain it in plain
+language.
+
+Read-only and propose-only. No tool applies Terraform, mutates a cloud
+resource, or accepts a credential. This release performs no network I/O
+at all: everything runs offline against the plan file.
+
+## Quickstart
+
+Requires Python 3.10+ and [uv](https://docs.astral.sh/uv/). No install
+step; the first run resolves everything:
+
+```
+uvx blastcheck-mcp
+```
+
+### Claude Code
+
+```
+claude mcp add blastcheck -- uvx blastcheck-mcp
+```
+
+### Claude Desktop
+
+Add to `claude_desktop_config.json` (Settings > Developer > Edit
+Config):
+
+```json
+{
+  "mcpServers": {
+    "blastcheck": {
+      "command": "uvx",
+      "args": ["blastcheck-mcp"]
+    }
+  }
+}
+```
+
+### Cursor
+
+Add to `~/.cursor/mcp.json` (or `.cursor/mcp.json` in a project):
+
+```json
+{
+  "mcpServers": {
+    "blastcheck": {
+      "command": "uvx",
+      "args": ["blastcheck-mcp"]
+    }
+  }
+}
+```
+
+## Using it
+
+Ask your agent to check a plan:
+
+```
+terraform plan -out plan.tfplan
+terraform show -json plan.tfplan > plan.json
+```
+
+Then: "run blastcheck on plan.json and explain what could go wrong."
+The agent will call impact_emit, get a manifest handle plus a verdict
+summary, and follow up with impact_explain for the full picture.
+(impact_emit also accepts the saved .tfplan directly and converts it.)
+
+## Tools
+
+### impact_emit
+
+Runs blastcheck's plan-only analysis on a `terraform show -json` file
+(or a saved .tfplan) and returns:
+
+- `manifest_handle` - a short reference to the full Impact Manifest,
+  written to a private temp file (0600, per-user 0700 directory, kept
+  at most 24h). Pass it to impact_explain instead of shuttling the
+  large document through model context.
+- `summary` - the verdict, per-severity counts, which changes drove it,
+  and the plan-only note.
+
+A plan-only run can never emit `safe` - it never verified live state,
+and blastcheck says so rather than guessing. That is the point of the
+format.
+
+### impact_explain
+
+Turns a manifest into markdown a human can act on: the verdict and why,
+each change's noteworthy findings with their rationales, a
+"safe if ..." checklist of unmet preconditions, and exactly what could
+not be verified. Deterministic local code; accepts a manifest_handle, a
+manifest_path, or the manifest inline (exactly one).
+
+Output is capped by a hard budget (BLASTCHECK_MCP_EXPLAIN_BUDGET env,
+default 32000 characters, about 8K tokens) so the tool can never
+consume a session's context in one call. Small plans render in full.
+Large plans get a compact view: dimensions identical across every
+change are stated once, changes with identical assessments are grouped
+with numeric indexes compressed to ranges (app[0..11]) - for_each
+string keys are never wildcarded, so which tenants or keys are
+affected stays visible - and blocking changes always keep their
+complete address list, dropping only per-change repetition. Whenever
+anything is grouped or cut, an explicit partial-view notice says so
+and shows the exact follow-up calls; all lists are lexically sorted
+before any cut, so the same plan always shows the same subset. Never
+a silent drop.
+
+Drill-down filters (optional, combined with AND):
+
+- `severity` - e.g. `["blocking"]` or `["blocking", "caution"]`
+- `module_prefix` - address prefix, e.g. `"module.tenants[\"contoso-prod\"]"`
+- `resource_type` - exact type, e.g. `"azurerm_managed_disk"`
+- `addresses` - exact addresses, always rendered in full detail; the
+  guaranteed path to any specific change
+
+## Compatibility
+
+Verified against real clients and across MCP protocol eras
+(v0.1.0-rc1, mcp SDK 2.x, macOS, Python 3.13):
+
+| Check | Result |
+|---|---|
+| Protocol 2024-11-05 (oldest era) | negotiated, tools list + calls work |
+| Protocol 2025-03-26 | negotiated, tools list + calls work |
+| Protocol 2025-06-18 | negotiated, tools list + calls work |
+| Unknown version offered | server answers with its latest, per spec |
+| Claude Code 2.0.76 (stdio) | connects; both tools exercised end to end in three separate headless runs. Investigated note: when driving headless `claude -p` sessions from INSIDE another Claude Code session (a nested test rig), intermittent multi-minute client startup stalls were observed; process inspection showed they occur before the MCP server process is even spawned, and the identical command succeeds on retry with no changes, so they are attributed to the nested test environment rather than this server. An ordinary interactive session has not yet been driven by a human; recommended as a final confirmation. |
+| Claude Desktop | config block above is the documented uvx form; not yet exercised on this machine |
+| Cursor | config block above is the documented uvx form; not yet exercised (Cursor not installed on the test machine) |
+| Large-plan compression | verified against a synthetic 288-change fixture ONLY (nested modules, for_each string keys, count indexes; 372KB full render compressed to a 12.5KB overview). NOT yet verified against a large real-world plan - if real changes fingerprint less uniformly, overviews will be larger; the hard output budget still caps them and the partial-view notice still applies. |
+
+## Errors
+
+Failures come back as `CODE: one clear sentence` - for example
+`FILE_NOT_FOUND: no such file: plan.json` or
+`MANIFEST_UNSUPPORTED_VERSION: ...` - never a stack trace.
+
+## Data boundary
+
+This release sends nothing anywhere: no telemetry, no API calls, no
+network I/O. Raw plan JSON never leaves the machine.
+
+A future release adds an optional CloudRift tier (live cost, dependency
+and tenant enrichment; see `docs/remote-tier.md`). Its boundary is
+already implemented and tested in this codebase, before any network
+code exists: if a manifest is ever scored remotely, what leaves the
+machine is an identity-only projection - per change: address, resource
+type, name, Terraform provider address, and actions; plus the
+manifest's schema_version, generated_at, producer name/version, and
+source type. Evidence, rationales, verdicts, attribute values (ports,
+CIDRs, sizes), and the plan itself are stripped by an explicit
+allowlist, so a future manifest field is excluded by default rather
+than leaked by default. That tier will require an explicit
+CLOUDRIFT_API_TOKEN; without one, the server registers the local tools
+only.
+
+## Environment variables
+
+| Variable | Effect |
+|---|---|
+| BLASTCHECK_MCP_EXPLAIN_BUDGET | Hard cap, in characters, on impact_explain output (default 32000, floor 4000). Over the cap, a compact grouped view with an explicit partial-view notice is returned instead - never a silent cut. |
+| CLOUDRIFT_API_TOKEN | Reserved for the future remote tier. If set today, the server notes on stderr that the remote tier is not in this release and runs the local tools only. Credentials are NEVER accepted as tool arguments. |
+
+## Development
+
+```
+python3 -m venv .venv
+.venv/bin/pip install -e ".[test]"
+.venv/bin/pytest
+```
+
+The suite is fully offline. `tests/test_project.py` holds the
+data-boundary tests; treat a failure there as a stop-ship.
+
+## Relationship to blastcheck and the spec
+
+blastcheck-mcp is a thin MCP layer over the
+[blastcheck](https://github.com/prococonsulting/blastcheck) library
+(pinned `>=0.7,<0.8`) and implements a consumer of the
+[Impact Manifest specification](https://github.com/prococonsulting/impact-manifest)
+(schema major version 0). The manifest schema is read from blastcheck's
+own vendored copy, so there is no second copy to drift.
+
+## License
+
+Apache-2.0. See [LICENSE](./LICENSE).

blastcheck_mcp-0.1.0/pyproject.toml

@@ -0,0 +1,42 @@
+[build-system]
+requires = ["setuptools>=68"]
+build-backend = "setuptools.build_meta"
+
+[project]
+name = "blastcheck-mcp"
+version = "0.1.0"
+description = "MCP server exposing blastcheck Impact Manifests to coding agents"
+readme = "README.md"
+requires-python = ">=3.10"
+license = { text = "Apache-2.0" }
+authors = [{ name = "Kevin Proffitt", email = "kproffitt@prococonsulting.com" }]
+keywords = ["mcp", "terraform", "impact-manifest", "blastcheck", "change-safety"]
+classifiers = [
+    "Development Status :: 3 - Alpha",
+    "Environment :: Console",
+    "Intended Audience :: Developers",
+    "Intended Audience :: System Administrators",
+    "Operating System :: OS Independent",
+    "Programming Language :: Python :: 3",
+]
+dependencies = [
+    "mcp>=2,<3",
+    "blastcheck>=0.7,<0.8",
+    "jsonschema>=4.18",
+]
+
+[project.optional-dependencies]
+test = ["pytest>=8"]
+
+[project.urls]
+Homepage = "https://blastcheck.dev"
+Source = "https://github.com/prococonsulting/blastcheck-mcp"
+
+[project.scripts]
+blastcheck-mcp = "blastcheck_mcp.server:main"
+
+[tool.setuptools.packages.find]
+where = ["src"]
+
+[tool.pytest.ini_options]
+testpaths = ["tests"]

blastcheck_mcp-0.1.0/setup.cfg

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