mcp4api 0.1.0__tar.gz

mcp4api-0.1.0/.gitignore

@@ -0,0 +1,221 @@
+# Byte-compiled / optimized / DLL files
+__pycache__/
+*.py[codz]
+*$py.class
+
+# C extensions
+*.so
+
+# Distribution / packaging
+.Python
+build/
+develop-eggs/
+dist/
+downloads/
+eggs/
+.eggs/
+/lib/
+/lib64/
+parts/
+sdist/
+var/
+wheels/
+share/python-wheels/
+*.egg-info/
+.installed.cfg
+*.egg
+MANIFEST
+
+# PyInstaller
+#   Usually these files are written by a python script from a template
+#   before PyInstaller builds the exe, so as to inject date/other infos into it.
+*.manifest
+/*.spec
+
+# Installer logs
+pip-log.txt
+pip-delete-this-directory.txt
+
+# Unit test / coverage reports
+htmlcov/
+.tox/
+.nox/
+.coverage
+.coverage.*
+.cache
+nosetests.xml
+coverage.xml
+*.cover
+*.py.cover
+*.lcov
+.hypothesis/
+.pytest_cache/
+cover/
+
+# Translations
+*.mo
+*.pot
+
+# Django stuff:
+/*.log
+local_settings.py
+db.sqlite3
+db.sqlite3-journal
+
+# Flask stuff:
+instance/
+.webassets-cache
+
+# Scrapy stuff:
+.scrapy
+
+# Sphinx documentation
+docs/_build/
+
+# PyBuilder
+.pybuilder/
+target/
+
+# Jupyter Notebook
+.ipynb_checkpoints
+
+# IPython
+profile_default/
+ipython_config.py
+
+# pyenv
+#   For a library or package, you might want to ignore these files since the code is
+#   intended to run in multiple environments; otherwise, check them in:
+# .python-version
+
+# pipenv
+#   According to pypa/pipenv#598, it is recommended to include Pipfile.lock in version control.
+#   However, in case of collaboration, if having platform-specific dependencies or dependencies
+#   having no cross-platform support, pipenv may install dependencies that don't work, or not
+#   install all needed dependencies.
+# Pipfile.lock
+
+# uv
+#   Similar to Pipfile.lock, it is generally recommended to include uv.lock in version control.
+#   This is especially recommended for binary packages to ensure reproducibility, and is more
+#   commonly ignored for libraries.
+# uv.lock
+
+# poetry
+#   Similar to Pipfile.lock, it is generally recommended to include poetry.lock in version control.
+#   This is especially recommended for binary packages to ensure reproducibility, and is more
+#   commonly ignored for libraries.
+#   https://python-poetry.org/docs/basic-usage/#commit-your-poetrylock-file-to-version-control
+# poetry.lock
+# poetry.toml
+
+# pdm
+#   Similar to Pipfile.lock, it is generally recommended to include pdm.lock in version control.
+#   pdm recommends including project-wide configuration in pdm.toml, but excluding .pdm-python.
+#   https://pdm-project.org/en/latest/usage/project/#working-with-version-control
+# pdm.lock
+# pdm.toml
+.pdm-python
+.pdm-build/
+
+# pixi
+#   Similar to Pipfile.lock, it is generally recommended to include pixi.lock in version control.
+# pixi.lock
+#   Pixi creates a virtual environment in the .pixi directory, just like venv module creates one
+#   in the .venv directory. It is recommended not to include this directory in version control.
+.pixi/*
+!.pixi/config.toml
+
+# PEP 582; used by e.g. github.com/David-OConnor/pyflow and github.com/pdm-project/pdm
+__pypackages__/
+
+# Celery stuff
+celerybeat-schedule*
+celerybeat.pid
+
+# Redis
+*.rdb
+*.aof
+*.pid
+
+# RabbitMQ
+mnesia/
+rabbitmq/
+rabbitmq-data/
+
+# ActiveMQ
+activemq-data/
+
+# SageMath parsed files
+*.sage.py
+
+# Environments
+.env
+.envrc
+.venv
+/env/
+.mcp4api/
+venv/
+/ENV/
+env.bak/
+venv.bak/
+
+# Spyder project settings
+.spyderproject
+.spyproject
+
+# Rope project settings
+.ropeproject
+
+# mkdocs/Zensical documentation
+/site
+
+# mypy
+.mypy_cache/
+.dmypy.json
+dmypy.json
+
+# Pyre type checker
+.pyre/
+
+# pytype static type analyzer
+.pytype/
+
+# Cython debug symbols
+cython_debug/
+
+# PyCharm
+#   JetBrains specific template is maintained in a separate JetBrains.gitignore that can
+#   be found at https://github.com/github/gitignore/blob/main/Global/JetBrains.gitignore
+#   and can be added to the global gitignore or merged into this file.  For a more nuclear
+#   option (not recommended) you can uncomment the following to ignore the entire idea folder.
+# .idea/
+
+# Abstra
+#   Abstra is an AI-powered process automation framework.
+#   Ignore directories containing user credentials, local state, and settings.
+#   Learn more at https://abstra.io/docs
+.abstra/
+
+# Visual Studio Code
+#   Visual Studio Code specific template is maintained in a separate VisualStudioCode.gitignore that
+#   can be found at https://github.com/github/gitignore/blob/main/Global/VisualStudioCode.gitignore
+#   and can be added to the global gitignore or merged into this file. However, if you prefer, you
+#   could uncomment the following to ignore the entire vscode folder
+# .vscode/
+# Temporary file for partial code execution
+tempCodeRunnerFile.py
+
+# Ruff stuff:
+.ruff_cache/
+
+# PyPI configuration file
+.pypirc
+
+# Marimo
+marimo/_static/
+marimo/_lsp/
+__marimo__/
+
+# Streamlit
+.streamlit/secrets.toml

mcp4api-0.1.0/CHANGELOG.md

@@ -0,0 +1,21 @@
+# Changelog
+
+All notable changes to this project 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-10-28
+
+### Added
+
+- `mcp4api SPEC` runs ingest, curate, emit, and verify on an OpenAPI 3.0, 3.1, 3.2, or Swagger 2.0 document.
+- `mcp4api ingest` writes a deterministic `endpoints.json` with every schema in JSON Schema 2020-12.
+- `mcp4api curate` writes `tools.yaml` with Claude, a local heuristic, or a hand-edited manifest, within a token and USD budget.
+- `overrides.yaml` renames, describes, excludes, restores, or fixes inputs on curated tools without editing `tools.yaml`.
+- `mcp4api emit` writes a standalone Python MCP server to `generated/` and refuses to overwrite hand edits without `--force`.
+- `mcp4api verify` calls every generated tool behind a host allowlist, writes `report/`, and exits 3 on a known gap.
+- `mcp4api record` writes scrubbed cassettes from a sandbox, so later `--offline` verification needs no network.
+- The Shelf sample under `examples/sample-api` runs the whole pipeline offline.

mcp4api-0.1.0/CODE_OF_CONDUCT.md

@@ -0,0 +1,83 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our community a harassment-free experience for everyone, regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, caste, color, religion, or sexual identity and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our community include:
+
+* Demonstrating empathy and kindness toward other people
+* Being respectful of differing opinions, viewpoints, and experiences
+* Giving and gracefully accepting constructive feedback
+* Accepting responsibility and apologizing to those affected by our mistakes, and learning from the experience
+* Focusing on what is best not just for us as individuals, but for the overall community
+
+Examples of unacceptable behavior include:
+
+* The use of sexualized language or imagery, and sexual attention or advances of any kind
+* Trolling, insulting or derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or email address, without their explicit permission
+* Other conduct which could reasonably be considered inappropriate in a professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of acceptable behavior and will take appropriate and fair corrective action in response to any behavior that they deem inappropriate, threatening, offensive, or harmful.
+
+Community leaders have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, and will communicate reasons for moderation decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when an individual is officially representing the community in public spaces. Examples of representing our community include using an official e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to the community leaders responsible for enforcement through [GitHub security advisories](https://github.com/smusali/mcp4api/security/advisories/new). All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing clarity around the nature of the violation and an explanation of why the behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series of actions.
+
+**Consequence**: A warning with consequences for continued behavior. No interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, for a specified period of time. This includes avoiding interactions in community spaces as well as external channels like social media. Violating these terms may lead to a temporary or permanent ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public communication with the community for a specified period of time. No public or private interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, is allowed during this period. Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community standards, including sustained inappropriate behavior, harassment of an individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within the community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 2.1, available at [https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1].
+
+Community Impact Guidelines were inspired by [Mozilla's code of conduct enforcement ladder][Mozilla CoC].
+
+For answers to common questions about this code of conduct, see the FAQ at [https://www.contributor-covenant.org/faq][FAQ]. Translations are available at [https://www.contributor-covenant.org/translations][translations].
+
+[homepage]: https://www.contributor-covenant.org
+[v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html
+[Mozilla CoC]: https://github.com/mozilla/diversity
+[FAQ]: https://www.contributor-covenant.org/faq
+[translations]: https://www.contributor-covenant.org/translations

mcp4api-0.1.0/CONTRIBUTING.md

@@ -0,0 +1,26 @@
+# Contributing
+
+## Setup
+
+Python 3.11 or newer and [uv](https://docs.astral.sh/uv/).
+
+```bash
+uv sync --group dev
+```
+
+## Checks
+
+These commands stay offline and do not need an API key:
+
+```bash
+uv run ruff check .
+uv run ruff format --check .
+uv run mypy
+uv run pytest
+```
+
+`pytest` disables network sockets.
+
+## Demo recording
+
+`tools/record_demo.sh` rewrites `examples/demo.cast` and `examples/demo.gif`. It needs [asciinema](https://docs.asciinema.org/) and [agg](https://github.com/asciinema/agg). Run it when the CLI output changes.

mcp4api-0.1.0/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Samir Musali
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

mcp4api-0.1.0/PKG-INFO

@@ -0,0 +1,157 @@
+Metadata-Version: 2.5
+Name: mcp4api
+Version: 0.1.0
+Summary: Turn API docs into a working MCP server, then verify every generated tool against the real API.
+Project-URL: Homepage, https://github.com/smusali/mcp4api
+Project-URL: Repository, https://github.com/smusali/mcp4api
+Project-URL: Issues, https://github.com/smusali/mcp4api/issues
+Project-URL: Changelog, https://github.com/smusali/mcp4api/blob/main/CHANGELOG.md
+Project-URL: Documentation, https://github.com/smusali/mcp4api/blob/main/docs/USAGE.md
+Author-email: Samir Musali <samir.musali@gmail.com>
+License-Expression: MIT
+License-File: LICENSE
+Keywords: agentic-ai,ai-agents,ai-infrastructure,cli,code-generation,developer-tools,llm,mcp,model-context-protocol,openapi,python
+Classifier: Development Status :: 3 - Alpha
+Classifier: Environment :: Console
+Classifier: Intended Audience :: Developers
+Classifier: License :: OSI Approved :: MIT License
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Programming Language :: Python :: 3.14
+Classifier: Programming Language :: Python :: 3.15
+Classifier: Topic :: Software Development :: Code Generators
+Classifier: Topic :: Software Development :: Testing
+Classifier: Typing :: Typed
+Requires-Python: >=3.11
+Requires-Dist: anthropic<3,>=2.2.0
+Requires-Dist: httpx2<3,>=2.16.0
+Requires-Dist: hypothesis-jsonschema<1,>=0.23.1
+Requires-Dist: hypothesis<7,>=6.170.8
+Requires-Dist: jinja2<4,>=3.1.6
+Requires-Dist: jsonschema<5,>=4.26.0
+Requires-Dist: mcp<3,>=2.3
+Requires-Dist: openapi-spec-validator<1,>=0.9.0
+Requires-Dist: pydantic<3,>=2.14.1
+Requires-Dist: pyyaml<7,>=6.0.3
+Requires-Dist: rich<16,>=15.0.0
+Requires-Dist: typer<1,>=0.27.3
+Description-Content-Type: text/markdown
+
+# mcp4api
+
+mcp4api turns your API docs into a working MCP server, then calls every generated tool against your API and reports which ones work. Built for platform teams who want their product callable by agents.
+
+[![CI](https://github.com/smusali/mcp4api/actions/workflows/ci.yml/badge.svg)](https://github.com/smusali/mcp4api/actions/workflows/ci.yml)
+[![PyPI](https://img.shields.io/pypi/v/mcp4api.svg)](https://pypi.org/project/mcp4api/)
+[![License: MIT](https://img.shields.io/badge/License-MIT-blue.svg)](https://github.com/smusali/mcp4api/blob/main/LICENSE)
+[![Python versions](https://img.shields.io/pypi/pyversions/mcp4api.svg)](https://pypi.org/project/mcp4api/)
+
+![Offline run against the Shelf sample, from ingest through the verification summary](https://raw.githubusercontent.com/smusali/mcp4api/main/examples/demo.gif)
+
+[Recording](https://github.com/smusali/mcp4api/blob/main/examples/demo.cast)
+
+## Install
+
+```bash
+pip install mcp4api
+uvx mcp4api
+```
+
+## Quickstart
+
+These commands need no API key. They reuse the committed manifest and cassettes, regenerate the other artifacts in place, and exit 3. The sample's one known gap is `get_book`: `page_count` is a string in the API and an integer in the spec.
+
+```bash
+git clone https://github.com/smusali/mcp4api && cd mcp4api
+uvx mcp4api examples/sample-api/openapi.yaml --offline --out examples/sample-api
+cat examples/sample-api/report/verification.md
+```
+
+## Generated tool
+
+`upload_book_file` from the Shelf sample is four calls composed into one tool.
+
+```python
+@mcp.tool(
+    title="Upload Book File",
+    annotations=ToolAnnotations(
+        read_only_hint=False,
+        destructive_hint=False,
+        idempotent_hint=False,
+        open_world_hint=True,
+    ),
+)
+async def upload_book_file(
+    book_id: Annotated[str, Field(description="book id")],
+    content_type: Annotated[str, Field(description="content type")],
+    data: Annotated[str, Field(description="data")],
+    filename: Annotated[str, Field(description="filename")],
+) -> UploadBookFileResult:
+    """Upload a file and attach it to a book."""
+    create_upload = await api.request(
+        "POST",
+        "/uploads",
+        body={"content_type": content_type, "filename": filename},
+        auth=(("api_key", "header", "X-API-Key"),),
+    )
+    _upload_part = await api.request(
+        "PUT",
+        "/uploads/{upload_id}/parts/{part_number}",
+        path_params={
+            "part_number": UPLOAD_BOOK_FILE_PART_NUMBER,
+            "upload_id": api.pick(create_upload, "id"),
+        },
+        body={"data": data},
+        auth=(("api_key", "header", "X-API-Key"),),
+    )
+    _complete_upload = await api.request(
+        "POST",
+        "/uploads/{upload_id}/complete",
+        path_params={"upload_id": api.pick(create_upload, "id")},
+        auth=(("api_key", "header", "X-API-Key"),),
+    )
+    attach_book_file = await api.request(
+        "PUT",
+        "/books/{book_id}/file",
+        path_params={"book_id": book_id},
+        body={"upload_id": api.pick(create_upload, "id")},
+        auth=(("api_key", "header", "X-API-Key"),),
+    )
+
+    return UploadBookFileResult.model_validate(attach_book_file)
+```
+
+## Verification report
+
+![Verification report for the Shelf sample, with get_book as the known gap](https://raw.githubusercontent.com/smusali/mcp4api/main/examples/verification.png)
+
+## CI
+
+`mcp/` holds the committed `tools.yaml` and cassettes. Exit 3 fails the job.
+
+```yaml
+- uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1  # v7.0.1
+  with:
+    persist-credentials: false
+- uses: astral-sh/setup-uv@07a047e608db84b3d8c06cd9a7c7dcc9c355c18e  # v10.3.2
+- run: uvx mcp4api openapi.yaml --offline --out mcp/
+```
+
+## Limitations
+
+- OpenAPI 3.0, 3.1, 3.2, and Swagger 2.0 only.
+- API key or bearer token authentication only.
+- A failing tool is a known gap. It is not repaired.
+- Agent curation needs an Anthropic API key.
+
+The full list is in [Limitations](https://github.com/smusali/mcp4api/blob/main/docs/limitations.md).
+
+## Contributing
+
+See [Contributing](https://github.com/smusali/mcp4api/blob/main/CONTRIBUTING.md).
+
+## License
+
+[MIT](https://github.com/smusali/mcp4api/blob/main/LICENSE)

mcp4api-0.1.0/README.md

@@ -0,0 +1,116 @@
+# mcp4api
+
+mcp4api turns your API docs into a working MCP server, then calls every generated tool against your API and reports which ones work. Built for platform teams who want their product callable by agents.
+
+[![CI](https://github.com/smusali/mcp4api/actions/workflows/ci.yml/badge.svg)](https://github.com/smusali/mcp4api/actions/workflows/ci.yml)
+[![PyPI](https://img.shields.io/pypi/v/mcp4api.svg)](https://pypi.org/project/mcp4api/)
+[![License: MIT](https://img.shields.io/badge/License-MIT-blue.svg)](https://github.com/smusali/mcp4api/blob/main/LICENSE)
+[![Python versions](https://img.shields.io/pypi/pyversions/mcp4api.svg)](https://pypi.org/project/mcp4api/)
+
+![Offline run against the Shelf sample, from ingest through the verification summary](https://raw.githubusercontent.com/smusali/mcp4api/main/examples/demo.gif)
+
+[Recording](https://github.com/smusali/mcp4api/blob/main/examples/demo.cast)
+
+## Install
+
+```bash
+pip install mcp4api
+uvx mcp4api
+```
+
+## Quickstart
+
+These commands need no API key. They reuse the committed manifest and cassettes, regenerate the other artifacts in place, and exit 3. The sample's one known gap is `get_book`: `page_count` is a string in the API and an integer in the spec.
+
+```bash
+git clone https://github.com/smusali/mcp4api && cd mcp4api
+uvx mcp4api examples/sample-api/openapi.yaml --offline --out examples/sample-api
+cat examples/sample-api/report/verification.md
+```
+
+## Generated tool
+
+`upload_book_file` from the Shelf sample is four calls composed into one tool.
+
+```python
+@mcp.tool(
+    title="Upload Book File",
+    annotations=ToolAnnotations(
+        read_only_hint=False,
+        destructive_hint=False,
+        idempotent_hint=False,
+        open_world_hint=True,
+    ),
+)
+async def upload_book_file(
+    book_id: Annotated[str, Field(description="book id")],
+    content_type: Annotated[str, Field(description="content type")],
+    data: Annotated[str, Field(description="data")],
+    filename: Annotated[str, Field(description="filename")],
+) -> UploadBookFileResult:
+    """Upload a file and attach it to a book."""
+    create_upload = await api.request(
+        "POST",
+        "/uploads",
+        body={"content_type": content_type, "filename": filename},
+        auth=(("api_key", "header", "X-API-Key"),),
+    )
+    _upload_part = await api.request(
+        "PUT",
+        "/uploads/{upload_id}/parts/{part_number}",
+        path_params={
+            "part_number": UPLOAD_BOOK_FILE_PART_NUMBER,
+            "upload_id": api.pick(create_upload, "id"),
+        },
+        body={"data": data},
+        auth=(("api_key", "header", "X-API-Key"),),
+    )
+    _complete_upload = await api.request(
+        "POST",
+        "/uploads/{upload_id}/complete",
+        path_params={"upload_id": api.pick(create_upload, "id")},
+        auth=(("api_key", "header", "X-API-Key"),),
+    )
+    attach_book_file = await api.request(
+        "PUT",
+        "/books/{book_id}/file",
+        path_params={"book_id": book_id},
+        body={"upload_id": api.pick(create_upload, "id")},
+        auth=(("api_key", "header", "X-API-Key"),),
+    )
+
+    return UploadBookFileResult.model_validate(attach_book_file)
+```
+
+## Verification report
+
+![Verification report for the Shelf sample, with get_book as the known gap](https://raw.githubusercontent.com/smusali/mcp4api/main/examples/verification.png)
+
+## CI
+
+`mcp/` holds the committed `tools.yaml` and cassettes. Exit 3 fails the job.
+
+```yaml
+- uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1  # v7.0.1
+  with:
+    persist-credentials: false
+- uses: astral-sh/setup-uv@07a047e608db84b3d8c06cd9a7c7dcc9c355c18e  # v10.3.2
+- run: uvx mcp4api openapi.yaml --offline --out mcp/
+```
+
+## Limitations
+
+- OpenAPI 3.0, 3.1, 3.2, and Swagger 2.0 only.
+- API key or bearer token authentication only.
+- A failing tool is a known gap. It is not repaired.
+- Agent curation needs an Anthropic API key.
+
+The full list is in [Limitations](https://github.com/smusali/mcp4api/blob/main/docs/limitations.md).
+
+## Contributing
+
+See [Contributing](https://github.com/smusali/mcp4api/blob/main/CONTRIBUTING.md).
+
+## License
+
+[MIT](https://github.com/smusali/mcp4api/blob/main/LICENSE)

mcp4api-0.1.0/SECURITY.md

@@ -0,0 +1,26 @@
+# Security Policy
+
+## Supported versions
+
+Only the latest published release receives security fixes.
+
+| Version | Supported |
+| --- | --- |
+| Latest published release | Yes |
+| Older releases | No |
+
+## Reporting a vulnerability
+
+Report vulnerabilities privately through [GitHub security advisories](https://github.com/smusali/mcp4api/security/advisories/new). Do not open a public issue, and do not disclose the report before a fix is published. You can expect an initial response within 3 days.
+
+## Threat model
+
+mcp4api fetches documentation the operator did not write and passes that text to a model. A hostile page can attempt prompt injection. Curation wraps that text and then enforces exclusions in code. The tool generates code, executes it, and can call live APIs with real credentials. The methodology is in [Methodology](docs/METHODOLOGY.md).
+
+## Guarantees
+
+- Credentials are read from the environment and are not written into generated code, fixtures, or prompts.
+- Cassettes store no headers, and secret values are replaced before the file is written.
+- Verification dials only loopback or a host passed to `--allow-host`.
+- Destructive and non-idempotent tools are not called under `--live` unless `--allow-writes` is set.
+- Report excerpts are trimmed upstream bodies. Treat `report/` as sensitive when a live body may contain secrets.