kaos-mcp 0.1.0__tar.gz

kaos_mcp-0.1.0/.gitignore

@@ -0,0 +1,11 @@
+.coverage
+.mypy_cache/
+.pytest_cache/
+.ruff_cache/
+.venv/
+__pycache__/
+*.pyc
+dist/
+*.egg-info/
+.mcp.json
+.kaos-vfs/

kaos_mcp-0.1.0/CHANGELOG.md

@@ -0,0 +1,276 @@
+# Changelog
+
+All notable changes to `kaos-mcp` are documented in this file.
+
+The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
+and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
+
+

+## [Unreleased]
+
+
+## [0.1.0] — 2026-05-20
+
+### Released
+
+- 0.1.0 GA — WU-L of GA plan. First stable release. Public API frozen.
+- Pin floor raised to `>=0.1.0,<0.2` across all kaos-* runtime and
+  optional dependencies. Refreshed `uv.lock` to pick up the 0.1.0
+  line of every upstream.
+
+### Internal
+
+- WU-L of the 0.1.0 GA plan
+  (`kaos-modules/docs/plans/2026-05-20-0.1.0-ga-plan.md`).
+
+
+## [0.1.0rc1] — 2026-05-20
+
+### Changed
+
+- Pin floor raised to `>=0.1.0rc1,<0.2` across kaos-* runtime
+  dependencies (`kaos-core`, `kaos-content[markdown]`). Refreshed
+  `uv.lock` to pick up the rc1 line of every upstream.
+
+### Internal
+
+- WU-J of the 0.1.0 GA plan
+  (`kaos-modules/docs/plans/2026-05-20-0.1.0-ga-plan.md`).
+  Release candidate; freezes the public API for `kaos-mcp`
+  ahead of 0.1.0 GA.
+
+
+## [0.1.0a5] — 2026-05-20
+
+### Changed
+
+- **kaos-core floor raised to `>=0.1.0a12`** (post-URI-redesign +
+  Capability type). WU-F.3 of the 0.1.0 GA plan; catch-up to
+  kaos-core 0.1.0a12.
+- `kaos_mcp.adapters.tool.ToolAdapter._annotation_for` now accepts
+  `str | list[str]` for the parameter schema type, matching the widened
+  `kaos_core.types.parameters.ParameterSchema.type` introduced in
+  kaos-core 0.1.0a12 (JSON-Schema-style type unions). The list form
+  falls back to `Any` for FastMCP signature generation.
+- `_KNOWN_TOOL_COUNTS['kaos-content']` bumped 9 -> 17. kaos-content
+  0.1.0a12 registers the date / money / percent / duration / number
+  sentence-extraction tools, plus the corpus summarize / narrow tools,
+  on top of the previously-known nine. The drift-guard test now passes
+  under the canonical lockfile pairing.
+- Refresh `uv.lock`: kaos-core 0.1.0a10 -> 0.1.0a12, kaos-content
+  0.1.0a4 -> 0.1.0a12, pydantic 2.12.5 -> 2.13.4, pydantic-core
+  2.41.5 -> 2.46.4, pydantic-settings 2.13.1 -> 2.14.1, ruff
+  0.15.7 -> 0.15.13, ty 0.0.34 -> 0.0.36.
+
+
+## [0.1.0a4] — 2026-05-16
+
+### Fixed
+
+- Drift-guard test (`test_known_tool_counts_match_live_register`)
+  now respects `KAOS_SKIP_TOOL_COUNT_DRIFT_GUARD=1`. The min-deps CI
+  job sets it because `--resolution=lowest-direct` drops every
+  dependency to its declared floor — including kaos-core — and the
+  older-kaos-core path makes kaos-content's `register_content_tools`
+  register more compatibility tools than the canonical lockfile
+  pairing does. The dict documents the count under the locked
+  cross-product; it doesn't claim to hold across every arbitrary
+  version pair. Real drift still gets caught by the regular matrix
+  legs, which don't set this skip variable.
+  (Supersedes an earlier in-this-release pass that wrongly bumped
+  the dict to 17 based on a force-upgraded local venv; the canonical
+  lockfile resolution gives 9 tools, not 17.) Files:
+  `kaos_mcp/management/status.py`, `tests/unit/test_management.py`,
+  `.github/workflows/ci.yml`.
+
+### Infrastructure
+
+- Public-PR CI workflows hardened (pinned actions, restricted token
+  scope) and dependabot migrated to the uv ecosystem with a 72-hour
+  cooldown matching the rest of the kaos-* org.
+- `pnpm setup` step in CI workflows defaults hardened.
+- CycloneDX SBOM ships as a release asset (F8).
+- CODEOWNERS expansion + OpenSSF Scorecard + Dependabot
+  governance rollup.
+
+
+## [0.1.0a3] — 2026-05-11
+
+### Fixed
+
+- Drift in `_KNOWN_TOOL_COUNTS["kaos-content"]`: bumped from 8 → 9 to match
+  `kaos-content` 0.1.0a4, which added `DedupSemanticTool`. The drift-guard
+  test (`tests/unit/test_management.py::TestStatus::test_known_tool_counts_match_live_register`)
+  was failing in the `min-deps` CI job. Files: `kaos_mcp/management/status.py`.
+### Security
+
+- **vulture (dead-code scan) now runs in pre-commit + CI alongside
+  the existing bandit job.** New `vulture` hook in
+  ``.pre-commit-config.yaml`` mirrored by a new ``vulture (dead-code
+  scan)`` job in ``security.yml``. `--min-confidence 100` with the
+  shared `--ignore-names` list for names vulture can't infer from
+  the import graph (framework callbacks, OAuth/OIDC field names,
+  signal handlers, MCP `_meta` keys). Also lands the existing
+  bandit hook in pre-commit (it was only in CI before). Both pass
+  clean. Mirrors the rollout from kaos-core.
+### Changed
+
+- **uv.lock bumped to ``kaos-core`` 0.1.0a4 → 0.1.0a5.** Pure
+  lockfile refresh; ``kaos-core`` 0.1.0a5 adds CLI verbs for
+  credential management (F2.5) + per-package compatibility fixes.
+  kaos-mcp's public API is unaffected. 143 unit tests pass.
+
+## [0.1.0a2] — 2026-05-08
+
+Patch release closing the eight findings in `docs/audit-02/kaos-mcp.md`
+(audit-02 F1–F8). No public-API removals; one new optional setting
+(`expose_server_config`) opts into the diagnostic config resource that
+was previously always-on. Existing `KaosMCPSettings` fields gained three
+DoS-cap defaults (`max_resource_bytes`, `max_range_length`,
+`max_table_rows`).
+
+### Security
+
+- **F1: per-session artifact isolation enforced at the MCP boundary.**
+  Every artifact / content / tabular / session resource handler now
+  derives the caller's session via `caller_session_id(ctx)` (prefers
+  `ctx.client_id`, falls back to `ctx.request_id`) and passes it as
+  `caller_session_id=` into `runtime.artifacts.*` reads. Cross-session
+  reads return a uniform `ResourceError("Unknown artifact")` so probing
+  cannot enumerate other sessions. `kaos://session/{session_id}/artifacts`
+  also refuses to enumerate any session other than the caller's.
+  Regression coverage: `tests/unit/test_session_enforcement.py` (10
+  tests). Files: `kaos_mcp/adapters/{session,resource,content,tabular,context}.py`.
+- **F3: `kaos://server/config` is opt-in and redaction is hardened.**
+  New `KaosMCPSettings.expose_server_config` (default `False`) gates
+  registration. When enabled, `_redact_value` always emits the constant
+  `"***"` (no `first4...last4` partial disclosure), and `_dump_settings`
+  redacts plain-`str` fields whose names match
+  `token|password|api_key|secret|credential|auth`. Regression coverage:
+  `tests/unit/test_config_resource.py` (15 tests including legacy
+  plain-`str` credential names). Files:
+  `kaos_mcp/{config,app}.py`, `kaos_mcp/adapters/config_resource.py`.
+- **F4: resource read DoS caps.** New settings
+  `max_resource_bytes` (10 MiB), `max_range_length` (10 MiB), and
+  `max_table_rows` (100 000) bound every artifact / content / tabular
+  read at the MCP boundary. `kaos://artifacts/{id}/range/{start}/{length}`
+  rejects oversize ranges; content-document and tabular-json reads
+  surface the artifact store's "Artifact exceeds inline read limit"
+  error; `kaos://tabular/{id}/table/{name}/rows/{start}/{count}`
+  rejects oversize row counts. Regression coverage:
+  `tests/unit/test_resource_caps.py`. Files:
+  `kaos_mcp/config.py`, `kaos_mcp/adapters/{resource,content,tabular}.py`.
+- **F5: `GOVINFO_API_KEY` written as env reference, not resolved value.**
+  `kaos_mcp/management/setup.py:_server_entries` now persists the
+  literal `${GOVINFO_API_KEY}` token into `.mcp.json`, `.codex/config.toml`,
+  `.gemini/settings.json`, `.vscode/mcp.json`, and `.cursor/mcp.json`.
+  Claude Code, Codex CLI, and Gemini CLI expand the reference at agent
+  launch — the project-local config never carries plaintext secrets.
+  Regression coverage: `tests/unit/test_management.py::TestSetup`
+  (`test_govinfo_*`, `test_setup_claude_writes_env_reference_not_secret`).
+- **F6: `kaos setup env` requires `--yes` for installer pipelines and
+  drops cwd-based script discovery.** `_find_setup_script` now walks
+  only from `__file__` (no more `Path.cwd()` fallback that would have
+  executed any nearby `scripts/setup-env.sh`). Direct
+  `curl … | sh` invocations against `https://astral.sh/uv/install.sh`
+  and `https://fnm.vercel.app/install` now require explicit
+  confirmation (CLI `--yes` flag, `confirm=True` from code); without
+  it the command is reported but not run. Regression coverage:
+  `tests/unit/test_management.py::TestSetup` (`test_setup_env_*`,
+  `test_find_setup_script_does_not_use_cwd`). Files:
+  `kaos_mcp/management/{env,cli}.py`.
+- **F7: CI supply-chain hardening.** `.github/workflows/security.yml`
+  pins the gitleaks Docker image to `v8.21.2` (no longer `:latest`),
+  adds a Bandit static-analysis job (medium severity / medium
+  confidence, AST-level), and runs the integration suite on
+  `schedule` and `workflow_dispatch`. SHA-pinning of GitHub Actions
+  themselves remains a follow-up; the existing
+  `.github/dependabot.yml` `github-actions` ecosystem PRs continue to
+  keep tag-pinned actions current.
+
+### Changed
+
+- **F2 + F8: `SECURITY.md` rewritten to match the actual surface.**
+  The previous file referenced `ProgramOfThought`, `batch_run`, the
+  semantic cache, and Program v3 — all of which live in
+  `kaos-llm-core` / `kaos-agents`, not `kaos-mcp`. The new file
+  documents the real boundaries (MCP transport, request validation,
+  per-session artifact enforcement, opt-in config resource, DoS caps,
+  setup helpers, OIDC release pipeline) and adds an explicit threat
+  model section explaining that per-request `_meta.kaos_config`
+  overrides are accepted as-is and that `kaos-mcp` should only be
+  exposed to trusted clients (stdio, or streamable HTTP behind an
+  authenticating proxy). Closes audit-02 F2 (documented threat model)
+  and F8 (scope alignment).
+
+## [0.1.0a1] — 2026-05-07
+
+First public alpha. FastMCP-native server bridge that wraps any
+`KaosRuntime` — tool registry plus content + tabular resource templates —
+and exposes them over stdio or streamable HTTP. Closes every finding in
+`docs/audit-01/kaos-mcp.md` (MCP-01..MCP-06).
+
+### Added
+
+- **`LICENSE`, `NOTICE`, `CHANGELOG.md`** seeded for the public release.
+  License flips from `LicenseRef-Proprietary` to Apache-2.0 via PEP 639
+  (`license = "Apache-2.0"`, `license-files = ["LICENSE", "NOTICE"]`).
+  PEP 639-superseded `License ::` classifier removed.
+
+- **`tests/unit/test_management.py::TestStatus::test_known_tool_counts_match_live_register`**
+  — drift guard that asserts every entry of `_KNOWN_TOOL_COUNTS` matches
+  what its module's `register_*_tools(KaosRuntime())` actually registers.
+  Catches audit-01 MCP-06 from recurring whenever a sibling adds tools.
+
+### Changed
+
+- **`KaosMCPSettings` now subclasses `kaos_core.config.ModuleSettings`**
+  instead of `pydantic_settings.BaseSettings` directly. Picks up the
+  KAOS settings hierarchy (per-request `_meta.kaos_config` overrides via
+  `from_context()`, `resolve()` classmethod for default-or-passed
+  resolution). Closes audit-01 MCP-04. No behavioural change for
+  callers; existing 23 unit tests in `test_config.py` /
+  `test_config_resource.py` continue to pass.
+
+- **`_KNOWN_TOOL_COUNTS` in `kaos_mcp/management/status.py` refreshed
+  to current platform reality** — kaos-content 7→8, kaos-nlp-core
+  10→17, kaos-web 31→42, kaos-office 14→17, kaos-source 22→30. The new
+  drift-guard test (above) stops these from going stale silently.
+  Closes audit-01 MCP-06.
+
+- **`_read_package_version()` in `kaos_mcp/management/doctor.py` now
+  reads Rust+PyO3 versions from `Cargo.toml` `[package].version`** and
+  applies the Cargo→PEP 440 normalization (`-alpha.N` → `aN`, `-beta.N`
+  → `bN`, `-rc.N` → `rcN`). Without this, packages whose version lives
+  in `Cargo.toml` (kaos-nlp-core, kaos-graph) reported as `?` in
+  `kaos doctor` when running from a separate venv. Closes audit-01
+  MCP-02. Regression coverage:
+  `tests/unit/test_management.py::TestDoctor::test_separate_venv_version_fallback_is_not_unknown`.
+
+- **`kaos_mcp/management/__init__.py` declares an explicit empty
+  `__all__`** per the platform's public-API discipline rule (every
+  `__init__.py` declares one). Closes audit-01 MCP-05.
+
+### Removed
+
+- **`kaos new` subcommand and `kaos_mcp/management/scaffold.py` shim**
+  — the project-scaffolding command upward-depended on `kaos-ui` (an
+  app-layer package), violating the architecture (kaos-mcp sits in Core
+  Infrastructure). The `kaos-ui` runtime dependency drove this; cutting
+  the subcommand removes the dep entirely. Project scaffolding moves to
+  `kaos-ui new <kind> <name>` (kaos-ui already owns its own console
+  script). Closes audit-01 MCP-03 — structurally rather than by
+  optional-extra workaround. The `module` and `workflow` non-UI
+  templates moved alongside, into `kaos-ui/kaos_ui/templates/`. The
+  `kaos` umbrella CLI keeps `doctor`, `status`, `setup`, `serve`.
+
+- **`kaos-ui>=0.1.0` removed from `[project.dependencies]`** and from
+  `[tool.uv.sources]`. `kaos-mcp` now depends only on `kaos-core`,
+  `kaos-content[markdown]`, `mcp[cli]`, `pydantic`, `pydantic-settings`,
+  `httpx`, and `starlette` — back to the documented `kaos-mcp ->
+  kaos-core, kaos-content` architecture edge.
+
+[Unreleased]: https://github.com/273v/kaos-mcp/compare/v0.1.0a3...HEAD
+[0.1.0a3]: https://github.com/273v/kaos-mcp/compare/v0.1.0a2...v0.1.0a3
+[0.1.0a2]: https://github.com/273v/kaos-mcp/compare/v0.1.0a1...v0.1.0a2
+[0.1.0a1]: https://github.com/273v/kaos-mcp/releases/tag/v0.1.0a1

kaos_mcp-0.1.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 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 273 Ventures LLC
+
+   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.

kaos_mcp-0.1.0/NOTICE

@@ -0,0 +1,8 @@
+kaos-mcp
+Copyright 2026 273 Ventures LLC.
+
+This product includes software developed at 273 Ventures LLC
+(https://273ventures.com).
+
+Licensed under the Apache License, Version 2.0. See the LICENSE file
+distributed with this software for the full text of the license.