katana-markdown-linter Python wrapper
katana-markdown-linter is a thin Python launcher over GitHub Release binary
archives. The package does not contain independent lint or MCP server logic. On
first use, it downloads the matching kml, kml-mcp, or kml-mcp-remote
binary archive, verifies the neighboring SHA-256 checksum, installs the binary
into the wrapper cache, and delegates to that binary.
Install
pipx install katana-markdown-linter
kml --version
Use uvx for one-off runs:
uvx --from katana-markdown-linter==0.19.5 kml --version
uvx --from katana-markdown-linter==0.19.5 kml check README.md
Basic Usage
# Run linting
kml check README.md
# Show help
kml help
kml --help
kml -h
kml check --help
# Localized help
kml --locale ja help
# Show version aliases
kml version
kml --version
kml -v
# Fix and Format
kml fix README.md
kml fmt
MCP server entrypoints
Use kml-mcp for local stdio MCP clients:
uvx --from katana-markdown-linter==0.19.5 kml-mcp --workspace-root /absolute/path/to/workspace
Use kml-mcp-remote only for self-hosted Streamable HTTP:
KML_MCP_REMOTE_TOKEN=change-me \
uvx --from katana-markdown-linter==0.19.5 kml-mcp-remote
Supported Platforms
The Python launcher uses the same binary archives as the GitHub Release channel. It currently supports:
- macOS arm64:
aarch64-apple-darwin - macOS x64:
x86_64-apple-darwin - Linux x64:
x86_64-unknown-linux-gnu - Windows x64:
x86_64-pc-windows-msvc
Unsupported platforms fail before download with an explicit platform error.
Wrapper Contract
- The package version selects the GitHub Release tag.
- The launcher downloads the matching
kml-vX.Y.Z-<target>,kml-mcp-vX.Y.Z-<target>, orkml-mcp-remote-vX.Y.Z-<target>archive. - The launcher downloads the matching
.sha256file and verifies the archive before extraction. - The installed binary is cached by version, platform, and executable role.
- MCP launchers do not write wrapper logs to stdout, preserving JSON-RPC stdio.
For full CLI usage, rule coverage, and other install channels, see the repository README. Report package issues through GitHub Issues.
1 maintainer
Release files for katana-markdown-linter 0.19.5
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| katana_markdown_linter-0.19.5.tar.gz | 5.7 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| katana_markdown_linter-0.19.5-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 11.8 kB
Release files / katana_markdown_linter-0.19.5.tar.gz
| Download URL | katana_markdown_linter-0.19.5.tar.gz |
|---|---|
| Size | 5.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
11ba4d2ccb405fa9d19309aa2ab824a097b8eca54fdc1c50db30add3f5cb9dc9
|
|
BLAKE2b-256 checksum How to use checksums |
40e914c06fd6f76c0438e40c86d289be30d03c53bc68fadbbe018f69e8f76f88
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 26, 2026.
Transparency logRelease files / katana_markdown_linter-0.19.5-py3-none-any.whl
| Download URL | katana_markdown_linter-0.19.5-py3-none-any.whl |
|---|---|
| Size | 6.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
bada58fd76c51823393c969262f6271d17f58f3d54386580372213fb76d11524
|
|
BLAKE2b-256 checksum How to use checksums |
e708fe86da553d431800f1d4208352ea3dd5a0d87dd7b3addcbed6b968b84d34
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 26, 2026.
Transparency log
