api-mcp-compiler 0.1.0__tar.gz

api_mcp_compiler-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 Subhadip Mitra
+
+   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.

api_mcp_compiler-0.1.0/NOTICE

@@ -0,0 +1,22 @@
+api-mcp-compiler
+Copyright 2026 Subhadip Mitra
+
+Licensed under the Apache License, Version 2.0. See LICENSE.
+
+This product includes no third-party source code.
+
+Benchmark specifications and task sets used to test this compiler are fetched at the point of
+use and are never redistributed here. Their licences are recorded in
+examples/benchmarks/manifest.json, alongside the attribution that would have to travel with
+each file were it ever included:
+
+  - RestBench specifications and task sets, from the RestGPT repository by Yifan Song and
+    colleagues (MIT).
+  - TextCasing and NumberConversion sample services, published by Data Access Worldwide as
+    free public samples.
+  - The SAWSDL test collection, from kmi/sws-test-collections (GPL-3.0), used only to measure
+    this compiler's coverage against documents it did not author.
+
+Servers generated by this compiler import the MCP Python SDK and an HTTP client. This
+compiler depends on neither, and generated files are the output of the tool rather than a
+derivative of it: they carry whatever licence their author chooses.

api_mcp_compiler-0.1.0/PKG-INFO

@@ -0,0 +1,304 @@
+Metadata-Version: 2.4
+Name: api-mcp-compiler
+Version: 0.1.0
+Summary: Semantic and safe compilation of enterprise APIs into MCP tool surfaces
+Author-email: Subhadip Mitra <contact@subhadipmitra.com>
+License-Expression: Apache-2.0
+Project-URL: Homepage, https://github.com/bassrehab/api-mcp-compiler
+Project-URL: Documentation, https://api-mcp.subhadipmitra.com/
+Project-URL: Source, https://github.com/bassrehab/api-mcp-compiler
+Project-URL: Issues, https://github.com/bassrehab/api-mcp-compiler/issues
+Project-URL: Changelog, https://github.com/bassrehab/api-mcp-compiler/blob/main/CHANGELOG.md
+Keywords: mcp,openapi,wsdl,soap,llm,agents,api,governance
+Classifier: Development Status :: 3 - Alpha
+Classifier: Intended Audience :: Developers
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Topic :: Software Development :: Code Generators
+Classifier: Typing :: Typed
+Requires-Python: >=3.11
+Description-Content-Type: text/markdown
+License-File: LICENSE
+License-File: NOTICE
+Requires-Dist: pydantic>=2.7
+Requires-Dist: typer>=0.12
+Requires-Dist: PyYAML>=6.0
+Requires-Dist: lxml>=5.2
+Requires-Dist: jsonschema>=4.22
+Provides-Extra: eval
+Requires-Dist: anthropic>=0.40; extra == "eval"
+Provides-Extra: dev
+Requires-Dist: pytest>=8; extra == "dev"
+Requires-Dist: anthropic>=0.40; extra == "dev"
+Requires-Dist: setuptools>=68; extra == "dev"
+Requires-Dist: wheel>=0.43; extra == "dev"
+Requires-Dist: ruff==0.16.2; extra == "dev"
+Requires-Dist: mypy==2.3.0; extra == "dev"
+Requires-Dist: types-PyYAML>=6.0.12; extra == "dev"
+Requires-Dist: types-jsonschema>=4.22; extra == "dev"
+Requires-Dist: lxml-stubs>=0.5.1; extra == "dev"
+Provides-Extra: docs
+Requires-Dist: mkdocs<2,>=1.6; extra == "docs"
+Requires-Dist: mkdocs-material<10,>=9.5; extra == "docs"
+Dynamic: license-file
+
+<div align="center">
+
+# api-mcp-compiler
+
+**Compile REST/OpenAPI and SOAP/WSDL services into agent-ready MCP tool surfaces**
+**that are semantically designed, policy-governed, and evaluation-backed.**
+
+[![CI](https://github.com/bassrehab/api-mcp-compiler/actions/workflows/ci.yml/badge.svg)](https://github.com/bassrehab/api-mcp-compiler/actions/workflows/ci.yml)
+[![Licence](https://img.shields.io/badge/licence-Apache--2.0-blue.svg)](https://github.com/bassrehab/api-mcp-compiler/blob/main/LICENSE)
+[![Python](https://img.shields.io/badge/python-3.11%20%7C%203.12-blue.svg)](https://www.python.org/downloads/)
+[![Typed](https://img.shields.io/badge/mypy-strict-blue.svg)](https://mypy.readthedocs.io/en/stable/)
+[![Contracts](https://img.shields.io/badge/contracts-JSON%20Schema%202020--12-blue.svg)](https://github.com/bassrehab/api-mcp-compiler/blob/main/src/api_mcp_compiler/schemas)
+[![Results](https://img.shields.io/badge/results-pre--registered-8A2BE2.svg)](https://github.com/bassrehab/api-mcp-compiler/tree/main/preregistrations)
+
+[Documentation](https://api-mcp.subhadipmitra.com/) &middot;
+[Notebook walkthrough](https://github.com/bassrehab/api-mcp-compiler/blob/main/notebooks/from_specification_to_server.ipynb) &middot;
+[Pre-registrations](https://github.com/bassrehab/api-mcp-compiler/tree/main/preregistrations) &middot;
+[Changelog](https://github.com/bassrehab/api-mcp-compiler/blob/main/CHANGELOG.md)
+
+</div>
+
+---
+
+Turning one API operation into one MCP tool is already commodity. The harder and more useful
+problem is deciding **which** tools should exist, what they should be called, what they should
+accept and return, and what may not be invoked without a human in the loop.
+
+This compiler answers that with provenance on every field, a safety gate that refuses to emit
+what it cannot justify, and governance derived separately from code.
+
+```
+specification -> ingestion -> API Semantic IR -> planner -> tool plan
+                                                    |
+                              overlay (human decisions)
+                                                    |
+                                              policy manifest
+                                                    |
+                                          generated tool surface
+                                                    |
+                                    runnable MCP server (HTTP or SOAP)
+```
+
+## Contents
+
+- [Status](#status)
+- [Install and verify](#install-and-verify)
+- [Try it](#try-it)
+- [How it works](#how-it-works)
+- [Design properties](#design-properties)
+- [Reproducibility](#reproducibility)
+- [Documentation](#documentation)
+- [Scope](#scope)
+- [Author](#author)
+- [Licence](#licence)
+
+## Status
+
+Working software, and recorded comparisons that did not find a difference.
+
+The compiler ingests OpenAPI 3.x, Swagger 2.0 and WSDL 1.1, produces an intermediate
+representation, plans a tool surface, derives a policy manifest, and generates a
+transport-independent surface that runs against a deterministic mock. An evaluation harness
+scores a surface against a task corpus using deterministic oracles over real service state,
+driven either by a replay of a recorded solution or by a model that sees only the goal and the
+tools. It emits a runnable MCP server for the approved part of a surface, over HTTP for
+OpenAPI and over SOAP envelopes for WSDL, while the compiler itself binds to no MCP SDK, never
+calls a model, and never reaches the network.
+
+The central question, whether a semantically planned surface beats one-tool-per-operation on
+task success, unsafe-action rate and cost, **has been measured four times and is still
+unanswered**.
+
+Every comparison was pre-registered: the hypothesis, corpus, arms, model, success definition
+and significance threshold were fixed in a digested document before the run, and each run
+records that digest. All returned inconclusive, and the nominal direction reversed between
+them. Nothing here should be read as evidence that the semantic surface performs better. It is
+an argued position that has so far survived no test capable of confirming it.
+
+What the runs did establish is mostly about the instrument. Several defects were found only by
+pointing the system at a specification and a task set written by other people: a parser that
+marked every optional argument required, generated schemas no client would load, a store in
+which a read mutated state and a bulk delete removed everything, and oracles that scored the
+route an annotator took rather than the outcome a goal asked for. Each is fixed, and the rules
+that would have prevented the last class now fail the build.
+
+The most distinctive claim, that operations should be composed into workflow tools, remains
+untested. The rule that proposes composites fires nowhere on the first benchmark API, and
+designing a better one after reading that benchmark's solution paths would fit the treatment
+to the test set. It needs a benchmark whose tasks have not been read here.
+
+## Install and verify
+
+```bash
+python -m venv .venv
+.venv/bin/python -m pip install -e '.[dev]'
+.venv/bin/python scripts/verify_repo.py
+```
+
+The gate runs pytest, ruff, mypy in strict mode, validates every committed example against its
+versioned JSON Schema, builds the wheel and sdist and proves an installed copy can validate its
+own artifacts, and re-executes the notebook to confirm its stored outputs still match. Lint and
+type-checker versions are pinned exactly, so the gate means the same thing on every machine.
+
+## Try it
+
+```bash
+# Normalize a specification into the intermediate representation
+.venv/bin/python -m api_mcp_compiler.cli inspect examples/openapi/order_service.yaml
+
+# Plan a tool surface, and read the review report a human would approve from
+.venv/bin/python -m api_mcp_compiler.cli review examples/openapi/order_service.yaml
+
+# Derive the governance manifest
+.venv/bin/python -m api_mcp_compiler.cli policy examples/openapi/inventory_service.yaml
+
+# Generate the surface, applying decisions a reviewer already recorded
+.venv/bin/python -m api_mcp_compiler.cli generate examples/openapi/order_service.yaml \
+  --overlay examples/overlays/order_service.overlay.json
+
+# Write the conversion report a reviewer reads. Never overwrites an earlier one.
+.venv/bin/python -m api_mcp_compiler.cli report examples/openapi/order_service.yaml
+
+# Approve by class, so nobody hand-edits an overlay
+.venv/bin/python -m api_mcp_compiler.cli approve examples/openapi/order_service.yaml \
+  --overlay build/order.overlay.json --risk read
+
+# Emit a runnable MCP server for the approved part of the surface
+.venv/bin/python -m api_mcp_compiler.cli serve examples/openapi/order_service.yaml \
+  --overlay examples/overlays/order_service.overlay.json --out build/order_server.py
+
+# The same for SOAP. A WSDL operation needs its side effect recorded by a reviewer first,
+# because WSDL carries no signal to infer one from.
+.venv/bin/python -m api_mcp_compiler.cli serve examples/wsdl/customer_service.wsdl \
+  --overlay examples/overlays/customer_service.overlay.json --out build/customer_server.py
+
+# Score a surface against a task corpus, using deterministic oracles over final state
+.venv/bin/python -m api_mcp_compiler.cli evaluate examples/openapi/order_service.yaml \
+  examples/evals/order_tasks.json
+
+# Check every artifact against its schema and list what is unresolved
+.venv/bin/python -m api_mcp_compiler.cli validate examples/openapi/inventory_service.yaml
+```
+
+To read the same walk with every intermediate value printed, the provenance on a field, the
+rationale behind a rename, the scope chosen over the union of its alternatives, the gate
+holding a destructive tool and the review decision that releases it, open
+[`notebooks/from_specification_to_server.ipynb`](https://github.com/bassrehab/api-mcp-compiler/blob/main/notebooks/from_specification_to_server.ipynb).
+Its stored outputs are re-executed and compared by the verification gate, so they cannot drift
+from the code that produced them.
+
+## How it works
+
+Ingestion, planning, policy synthesis and code generation are separate stages with separate
+contracts. Each contract is versioned independently and pinned, so a document written against
+one version fails validation loudly instead of being misread.
+
+| Stage | Input | Output | Contract |
+|---|---|---|---|
+| Ingestion | OpenAPI 3.x, Swagger 2.0, WSDL 1.1 | API Semantic IR | `api_semantic_ir.schema.json` |
+| Planning | IR, overlay | Tool plan | `tool_plan.schema.json` |
+| Policy | IR, plan | Policy manifest | `policy_manifest.schema.json` |
+| Generation | IR, plan, manifest | Tool surface | `mcp_tool_surface.schema.json` |
+| Review | Plan | Overlay | `tool_overlay.schema.json` |
+| Evaluation | Surface, corpus | Evaluation run | `evaluation_run.schema.json` |
+
+## Design properties
+
+**Every informative field carries provenance.** A record names the field, a pointer into the
+source document, how the value was derived (`source`, `normalized`, `inferred`, `default`) and
+a confidence. An inference cannot claim certainty and a source fact cannot express doubt; the
+contract rejects both.
+
+**Nothing is dropped silently.** Constructs that cannot be resolved become `Ambiguity` records,
+and a completeness sweep reports every key an adapter did not consume. Duplicate mapping keys
+are refused outright in YAML and JSON, because a dropped key never reaches the parser to be
+swept.
+
+**Ingestion never reaches the network.** `$ref` resolution defaults to deny. External files
+load only from directories you name with `--allow-dir`, checked against real paths so `../`
+cannot escape. Remote references are always refused. A specification is third-party input, and
+following its pointers is an action taken on its author's behalf.
+
+**Inference can only make an operation look less safe, never more.** Destructive wording raises
+a write to destructive; it never lowers a class, and a read described destructively is flagged
+for review rather than quietly reclassified. SOAP operations are never classified by inference
+at all, because WSDL carries no signal equivalent to an HTTP method.
+
+**Judgement never becomes silent action.** The planner proposes renames, omissions, groupings,
+output projections and composite workflows, each with a rationale and a confidence. Nothing it
+proposes changes the surface until a reviewer records the decision in an overlay, and an
+overlay is bound by digest to the specification revision it was reviewed against.
+
+**A tool is executable only if it earned it.** Reads pass automatically once validated. Write,
+destructive and privileged tools stay disabled until approved. A blocking ambiguity, an
+unclassified risk, or policy that could not be derived keeps a tool disabled regardless of
+approval. Refused tools are still emitted carrying the reason, so the surface never shrinks
+quietly.
+
+**Governance is derived, not assumed.** Policy is generated separately from code:
+least-privilege scopes chosen from the security alternatives rather than their union, approval
+and confirmation classes, retry rules from inferred idempotency, rate budgets, output ceilings,
+redaction and audit rules. A destructive action needs a confirmation token bound to the exact
+arguments it was issued for, so confirming one action cannot authorise another.
+
+**Evaluation is decided by state, never by a model.** A task names source operations rather
+than tool names, so one corpus scores both planners. Success is judged by the state the
+service ends in, together with oracles for absence of mutation, prohibited operations and
+confirmation adherence. No safety or success number depends on a judge, and latency and token
+cost are recorded as null rather than estimated, because a fabricated number sitting beside
+measured ones is indistinguishable from a measured one.
+
+**What the compiler cannot enforce, it says so.** Server-side authorization and protection
+against confused-deputy designs are properties of a deployed service, not of a generated
+artifact. The manifest records them as requirements and never reports them as satisfied.
+
+## Reproducibility
+
+Every document loaded during a compile is digested, not only the root, so an artifact stays
+tied to the exact bytes it came from. Golden IR, plan, policy, surface and review artifacts are
+committed. Regenerate them deliberately and review the diff:
+
+```bash
+.venv/bin/python scripts/regen_golden.py
+```
+
+## Documentation
+
+The full guide lives at **[api-mcp.subhadipmitra.com](https://api-mcp.subhadipmitra.com/)**:
+concepts, a command reference, the contract schemas, the SOAP path, and how evaluation and
+pre-registration work. Its source is in [`guide/`](https://github.com/bassrehab/api-mcp-compiler/tree/main/guide).
+
+## Scope
+
+Uses synthetic and public specifications only. No credentials, customer specifications or
+proprietary schemas belong in this repository.
+
+## Author
+
+**Subhadip Mitra**
+[subhadipmitra.com](https://subhadipmitra.com) &middot; contact@subhadipmitra.com
+
+If you use this in academic work, please cite it. [`CITATION.cff`](https://github.com/bassrehab/api-mcp-compiler/blob/main/CITATION.cff) has the
+metadata, and GitHub renders it as a citation block on the repository page.
+
+## Licence
+
+Apache-2.0. See [`LICENSE`](https://github.com/bassrehab/api-mcp-compiler/blob/main/LICENSE) and [`NOTICE`](https://github.com/bassrehab/api-mcp-compiler/blob/main/NOTICE).
+
+Apache rather than a copyleft licence, deliberately. The interesting part of this project is
+what it decides a good tool surface looks like and what it refuses to emit; restricting who
+may build on that would cost adoption without protecting anything worth protecting. The patent
+grant also matters for the enterprises most likely to have a specification estate that needs
+converting.
+
+Benchmark specifications and services used to test the compiler are fetched at the point of
+use and never redistributed here, so this repository carries no third-party source. Their
+licences and attributions are recorded in `examples/benchmarks/manifest.json`.
+
+Servers this compiler generates are its output, not a derivative of it. They carry whatever
+licence their author chooses.