ais-webmcp 0.1.0__tar.gz

ais_webmcp-0.1.0/.gitignore

@@ -0,0 +1,27 @@
+.venv/
+__pycache__/
+.pytest_cache/
+.ruff_cache/
+.mypy_cache/
+.playwright-cli/
+build/
+dist/
+*.egg-info/
+*.pyc
+*.pyo
+*.pyd
+.Python
+*.so
+.coverage
+htmlcov/
+.tox/
+.nox/
+output/
+staticfiles/
+node_modules/
+.DS_Store
+*.log
+.env
+.env.*
+!.env.example
+_wt/

ais_webmcp-0.1.0/LICENSE

@@ -0,0 +1,204 @@
+Copyright (c) 2026 Alpin Insight Solutions GmbH & Co. KG
+
+
+                                 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 [yyyy] [name of copyright owner]
+
+   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.

ais_webmcp-0.1.0/NOTICE

@@ -0,0 +1,33 @@
+insight-ui-webmcp
+Copyright (c) 2026 Alpin Insight Solutions GmbH & Co. KG
+
+This product includes software developed by
+Alpin Insight Solutions GmbH & Co. KG.
+
+Product: insight-ui-webmcp
+Repository: https://github.com/alpininsight/insight-ui-webmcp
+
+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.
+
+Packages: ais-webmcp, insight-ui-webmcp
+
+Third-party software bundled in the browser helper (register.js, built from
+js/register.source.cjs by scripts/build-js.cjs) remains under its own license:
+
+- Ajv JSON schema validator (https://github.com/ajv-validator/ajv),
+  MIT License, Copyright (c) 2015-2021 Evgeny Poberezkin.
+- fast-deep-equal (https://github.com/epoberezkin/fast-deep-equal),
+  MIT License, Copyright (c) 2017 Evgeny Poberezkin.
+
+This NOTICE file is provided for attribution as contemplated by the Apache
+License, Version 2.0. It does not modify the License.

ais_webmcp-0.1.0/PKG-INFO

@@ -0,0 +1,221 @@
+Metadata-Version: 2.5
+Name: ais-webmcp
+Version: 0.1.0
+Summary: Create, validate and manage WebMCP manifests for any kind of website
+Project-URL: Homepage, https://github.com/alpininsight/ais-webmcp
+Project-URL: Documentation, https://github.com/alpininsight/ais-webmcp#readme
+Project-URL: Issues, https://github.com/alpininsight/ais-webmcp/issues
+Author: Alpin Insight Solutions GmbH & Co. KG
+License-Expression: Apache-2.0
+License-File: LICENSE
+License-File: NOTICE
+Classifier: Development Status :: 3 - Alpha
+Classifier: Environment :: Console
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Programming Language :: Python :: 3.14
+Requires-Python: >=3.12
+Requires-Dist: jsonschema<5,>=4.23
+Requires-Dist: pyyaml<7,>=6.0.2
+Description-Content-Type: text/markdown
+
+# AIS WebMCP — manage WebMCP for any website
+
+Make your website's capabilities clear to AI agents. `ais-webmcp` is the
+framework-independent PyPI command for creating, validating and maintaining
+WebMCP descriptions in the context of your website.
+
+Use it with static sites, CMS websites, documentation portals or custom web
+applications. Work with local JSON and YAML manifests, then connect the shared
+browser helper to your website's own content and actions.
+
+**DE:** Das frameworkunabhängige PyPI-Kommando, mit dem Sie WebMCP-Beschreibungen
+für jede Art von Webseite erstellen, prüfen und sinnvoll pflegen können.
+
+## Background
+
+[Insight UI](https://pypi.org/project/insight-ui/) is our open-source,
+WCAG-focused UI package, which we presented at the September meetup of the
+Berlin Python User Group, hosted at our office. Our work on WebMCP grew out
+of it as an extension, which is why we built insight-ui-webmcp first. At the
+meetup, people asked whether we could offer it without the Django layer we
+use for all our production-critical applications. That question is how
+ais-webmcp came about: the same WebMCP core, without the framework. We look
+forward to hearing what you think, and we warmly welcome contributions; see
+[how to contribute](CONTRIBUTING.md).
+
+## Packages at a glance
+
+One browser runtime, `register.js`, ships in the Python package and the npm
+package.
+
+```mermaid
+flowchart LR
+  Core["ais-webmcp (PyPI)<br/>manifest, CLI, register.js"]
+  Django["insight-ui-webmcp (PyPI)<br/>Django adapter"]
+  NPM["@alpininsightsolutions/webmcp (npm)<br/>register.js only"]
+  Core --> Django
+  Core --> NPM
+  Django --> S1["Django sites"]
+  NPM --> S2["other websites"]
+```
+
+- `ais-webmcp` on PyPI is the core: manifests, the CLI, and `register.js`.
+  The Django adapter `insight-ui-webmcp` installs that core.
+- `@alpininsightsolutions/webmcp` (coming soon) on npm is `register.js` only,
+  for other websites.
+
+The npm package is pending its first release and is not live yet. The
+unscoped npm package `webmcp` is unrelated.
+
+```bash
+pip install ais-webmcp
+ais-webmcp init --output manifest.yaml --static
+ais-webmcp validate manifest.yaml
+ais-webmcp list manifest.yaml
+ais-webmcp doctor manifest.yaml --html index.html
+ais-webmcp export manifest.yaml --output webmcp.manifest.json
+ais-webmcp export manifest.yaml --kind tools --output tools.json
+ais-webmcp export manifest.yaml --kind snippet --output snippet.html
+ais-webmcp diff manifest.yaml webmcp.manifest.json
+```
+
+Python 3.12+; Django is not required. `doctor` and `status` report local
+configuration and refuse remote URLs; browser support is verified separately.
+CSP is noted and not rewritten. Origin Trial tokens are redacted to character
+lengths. `export` can write a canonical manifest, a JSON tools list, or a
+static snippet with no token. Existing files are protected unless you pass
+`--force`. Consequential tools stay disabled in scaffolds until the host
+explicitly enables and implements them.
+
+## Output schemas
+
+Declare a [Draft 2020-12 JSON Schema](https://json-schema.org/draft/2020-12)
+for each tool result next to its input schema. The canonical key is
+`outputSchema`; `output_schema` is an alias, and only one of them may be set.
+`ToolSpec.output_schema` writes `outputSchema`.
+
+`ais-webmcp validate` checks a present output schema: it must be a JSON object
+and a valid [Draft 2020-12](https://json-schema.org/draft/2020-12) schema. An
+invalid schema fails validation. Omitting the schema does not. The result stays
+`ok`, the exit code stays 0, and each tool without a schema adds a finding:
+
+<!-- markdownlint-disable MD013 -->
+
+```json
+{
+  "path": "tools[0]",
+  "code": "missing_output_schema",
+  "severity": "low",
+  "message": "missing outputSchema (also accepts output_schema). Optional for existing hosts; absence is a low-severity finding."
+}
+```
+
+<!-- markdownlint-enable MD013 -->
+
+Check engines can treat `missing_output_schema` as a low-severity finding.
+Existing hosts keep validating until they declare output schemas. Text reports
+print `finding:` lines and still start with `ok:` when there are no errors.
+
+For Django and [Insight UI](https://pypi.org/project/insight-ui/) applications,
+add the insight-ui-webmcp adapter. The core owns the shared schema and browser
+runtime; the adapter uses the installed core rather than shipping a second
+copy.
+
+Development preview; the first public release is pending.
+
+## Public npm package
+
+The browser runtime is prepared as the public package
+`@alpininsightsolutions/webmcp` (coming soon). Enterprise code never goes to
+npm. The tarball is only the built `register.js`, its types, this README,
+`LICENSE`, and `NOTICE` (`package.json` is included because npm always packs
+it). A path under `enterprise/`, a path containing `webmcp_check`, or a `.env`
+file fails the tarball guard.
+
+|            |                                 |
+| ---------- | ------------------------------- |
+| PyPI / CLI | `ais-webmcp`                    |
+| npm        | `@alpininsightsolutions/webmcp` |
+| global     | `InsightUiWebmcp`               |
+
+```bash
+npm install @alpininsightsolutions/webmcp
+```
+
+```ts
+import InsightUiWebmcp from "@alpininsightsolutions/webmcp";
+
+const status = InsightUiWebmcp.status();
+if (status.supported) {
+  await InsightUiWebmcp.registerFromManifest(
+    {
+      profile: "webpage",
+      version: "1",
+      tools: [
+        {
+          id: "search",
+          name: "Search",
+          description: "Search this page",
+          inputSchema: {
+            type: "object",
+            properties: { q: { type: "string" } },
+          },
+        },
+      ],
+    },
+    {
+      search(input: { q?: string }) {
+        return { results: [] };
+      },
+    },
+  );
+}
+```
+
+A `<script>` tag assigns that same object to `window.InsightUiWebmcp`.
+
+The committed npm version is the `0.0.0` placeholder. Publish stamps the
+`vX.Y.Z` tag into `package.json` when the name stays in the
+`@alpininsightsolutions` scope, the license is `Apache-2.0`, the files
+allowlist includes `LICENSE` and `NOTICE`, and the repository URL is
+`git+https://github.com/alpininsight/ais-webmcp.git`. `npm run build:release`
+then injects that version into `register.js`. The workflow packs that build
+and publishes the tarball with provenance. `prepublishOnly` rejects a local
+`npm publish` while the version is still `0.0.0`. Publishing runs from
+`.github/workflows/npm-publish.yml`, a manual dispatch from `main` with that
+tag. Trusted Publishing attaches provenance. The trusted publisher is bound
+to `alpininsight/ais-webmcp`, workflow `npm-publish.yml`, and environment
+`npm-ais-webmcp`. A release goes out only with Peter's go. The first publish
+is the manual bootstrap.
+One-time npmjs.com setup is in [docs/release.md](docs/release.md).
+
+## Development
+
+```bash
+uv sync --locked --all-groups
+npm ci
+npm run check:js-build
+npm test
+uv run --locked pytest
+uv run --locked pre-commit run --all-files
+```
+
+See [how to contribute](CONTRIBUTING.md).
+
+Python 3.12–3.14 and Node 24 are the versions this repository tests. Node 24
+is the repo pin (`.nvmrc` and `devEngines`); the published package does not
+set `engines`, so installing the browser runtime does not warn on other Node
+versions. Each release contains exactly one wheel and one sdist.
+
+License: Apache-2.0 with NOTICE. Bundled dependencies retain their own licenses
+in the generated runtime banner.
+
+## Split provenance
+
+Core history was extracted from
+[insight-ui-webmcp at d6ead80843dbe42096791dd6688ed58a35dc3291](https://github.com/alpininsight/insight-ui-webmcp/tree/d6ead80843dbe42096791dd6688ed58a35dc3291).
+See [the implementation tracker](https://github.com/alpininsight/insight-ui-webmcp/issues/63)
+for the architecture decision, adapter/publisher/host migration and separate
+release evidence. The original repository history and existing host pins are
+preserved.

ais_webmcp-0.1.0/README.md

@@ -0,0 +1,200 @@
+# AIS WebMCP — manage WebMCP for any website
+
+Make your website's capabilities clear to AI agents. `ais-webmcp` is the
+framework-independent PyPI command for creating, validating and maintaining
+WebMCP descriptions in the context of your website.
+
+Use it with static sites, CMS websites, documentation portals or custom web
+applications. Work with local JSON and YAML manifests, then connect the shared
+browser helper to your website's own content and actions.
+
+**DE:** Das frameworkunabhängige PyPI-Kommando, mit dem Sie WebMCP-Beschreibungen
+für jede Art von Webseite erstellen, prüfen und sinnvoll pflegen können.
+
+## Background
+
+[Insight UI](https://pypi.org/project/insight-ui/) is our open-source,
+WCAG-focused UI package, which we presented at the September meetup of the
+Berlin Python User Group, hosted at our office. Our work on WebMCP grew out
+of it as an extension, which is why we built insight-ui-webmcp first. At the
+meetup, people asked whether we could offer it without the Django layer we
+use for all our production-critical applications. That question is how
+ais-webmcp came about: the same WebMCP core, without the framework. We look
+forward to hearing what you think, and we warmly welcome contributions; see
+[how to contribute](CONTRIBUTING.md).
+
+## Packages at a glance
+
+One browser runtime, `register.js`, ships in the Python package and the npm
+package.
+
+```mermaid
+flowchart LR
+  Core["ais-webmcp (PyPI)<br/>manifest, CLI, register.js"]
+  Django["insight-ui-webmcp (PyPI)<br/>Django adapter"]
+  NPM["@alpininsightsolutions/webmcp (npm)<br/>register.js only"]
+  Core --> Django
+  Core --> NPM
+  Django --> S1["Django sites"]
+  NPM --> S2["other websites"]
+```
+
+- `ais-webmcp` on PyPI is the core: manifests, the CLI, and `register.js`.
+  The Django adapter `insight-ui-webmcp` installs that core.
+- `@alpininsightsolutions/webmcp` (coming soon) on npm is `register.js` only,
+  for other websites.
+
+The npm package is pending its first release and is not live yet. The
+unscoped npm package `webmcp` is unrelated.
+
+```bash
+pip install ais-webmcp
+ais-webmcp init --output manifest.yaml --static
+ais-webmcp validate manifest.yaml
+ais-webmcp list manifest.yaml
+ais-webmcp doctor manifest.yaml --html index.html
+ais-webmcp export manifest.yaml --output webmcp.manifest.json
+ais-webmcp export manifest.yaml --kind tools --output tools.json
+ais-webmcp export manifest.yaml --kind snippet --output snippet.html
+ais-webmcp diff manifest.yaml webmcp.manifest.json
+```
+
+Python 3.12+; Django is not required. `doctor` and `status` report local
+configuration and refuse remote URLs; browser support is verified separately.
+CSP is noted and not rewritten. Origin Trial tokens are redacted to character
+lengths. `export` can write a canonical manifest, a JSON tools list, or a
+static snippet with no token. Existing files are protected unless you pass
+`--force`. Consequential tools stay disabled in scaffolds until the host
+explicitly enables and implements them.
+
+## Output schemas
+
+Declare a [Draft 2020-12 JSON Schema](https://json-schema.org/draft/2020-12)
+for each tool result next to its input schema. The canonical key is
+`outputSchema`; `output_schema` is an alias, and only one of them may be set.
+`ToolSpec.output_schema` writes `outputSchema`.
+
+`ais-webmcp validate` checks a present output schema: it must be a JSON object
+and a valid [Draft 2020-12](https://json-schema.org/draft/2020-12) schema. An
+invalid schema fails validation. Omitting the schema does not. The result stays
+`ok`, the exit code stays 0, and each tool without a schema adds a finding:
+
+<!-- markdownlint-disable MD013 -->
+
+```json
+{
+  "path": "tools[0]",
+  "code": "missing_output_schema",
+  "severity": "low",
+  "message": "missing outputSchema (also accepts output_schema). Optional for existing hosts; absence is a low-severity finding."
+}
+```
+
+<!-- markdownlint-enable MD013 -->
+
+Check engines can treat `missing_output_schema` as a low-severity finding.
+Existing hosts keep validating until they declare output schemas. Text reports
+print `finding:` lines and still start with `ok:` when there are no errors.
+
+For Django and [Insight UI](https://pypi.org/project/insight-ui/) applications,
+add the insight-ui-webmcp adapter. The core owns the shared schema and browser
+runtime; the adapter uses the installed core rather than shipping a second
+copy.
+
+Development preview; the first public release is pending.
+
+## Public npm package
+
+The browser runtime is prepared as the public package
+`@alpininsightsolutions/webmcp` (coming soon). Enterprise code never goes to
+npm. The tarball is only the built `register.js`, its types, this README,
+`LICENSE`, and `NOTICE` (`package.json` is included because npm always packs
+it). A path under `enterprise/`, a path containing `webmcp_check`, or a `.env`
+file fails the tarball guard.
+
+|            |                                 |
+| ---------- | ------------------------------- |
+| PyPI / CLI | `ais-webmcp`                    |
+| npm        | `@alpininsightsolutions/webmcp` |
+| global     | `InsightUiWebmcp`               |
+
+```bash
+npm install @alpininsightsolutions/webmcp
+```
+
+```ts
+import InsightUiWebmcp from "@alpininsightsolutions/webmcp";
+
+const status = InsightUiWebmcp.status();
+if (status.supported) {
+  await InsightUiWebmcp.registerFromManifest(
+    {
+      profile: "webpage",
+      version: "1",
+      tools: [
+        {
+          id: "search",
+          name: "Search",
+          description: "Search this page",
+          inputSchema: {
+            type: "object",
+            properties: { q: { type: "string" } },
+          },
+        },
+      ],
+    },
+    {
+      search(input: { q?: string }) {
+        return { results: [] };
+      },
+    },
+  );
+}
+```
+
+A `<script>` tag assigns that same object to `window.InsightUiWebmcp`.
+
+The committed npm version is the `0.0.0` placeholder. Publish stamps the
+`vX.Y.Z` tag into `package.json` when the name stays in the
+`@alpininsightsolutions` scope, the license is `Apache-2.0`, the files
+allowlist includes `LICENSE` and `NOTICE`, and the repository URL is
+`git+https://github.com/alpininsight/ais-webmcp.git`. `npm run build:release`
+then injects that version into `register.js`. The workflow packs that build
+and publishes the tarball with provenance. `prepublishOnly` rejects a local
+`npm publish` while the version is still `0.0.0`. Publishing runs from
+`.github/workflows/npm-publish.yml`, a manual dispatch from `main` with that
+tag. Trusted Publishing attaches provenance. The trusted publisher is bound
+to `alpininsight/ais-webmcp`, workflow `npm-publish.yml`, and environment
+`npm-ais-webmcp`. A release goes out only with Peter's go. The first publish
+is the manual bootstrap.
+One-time npmjs.com setup is in [docs/release.md](docs/release.md).
+
+## Development
+
+```bash
+uv sync --locked --all-groups
+npm ci
+npm run check:js-build
+npm test
+uv run --locked pytest
+uv run --locked pre-commit run --all-files
+```
+
+See [how to contribute](CONTRIBUTING.md).
+
+Python 3.12–3.14 and Node 24 are the versions this repository tests. Node 24
+is the repo pin (`.nvmrc` and `devEngines`); the published package does not
+set `engines`, so installing the browser runtime does not warn on other Node
+versions. Each release contains exactly one wheel and one sdist.
+
+License: Apache-2.0 with NOTICE. Bundled dependencies retain their own licenses
+in the generated runtime banner.
+
+## Split provenance
+
+Core history was extracted from
+[insight-ui-webmcp at d6ead80843dbe42096791dd6688ed58a35dc3291](https://github.com/alpininsight/insight-ui-webmcp/tree/d6ead80843dbe42096791dd6688ed58a35dc3291).
+See [the implementation tracker](https://github.com/alpininsight/insight-ui-webmcp/issues/63)
+for the architecture decision, adapter/publisher/host migration and separate
+release evidence. The original repository history and existing host pins are
+preserved.