KatanA Markdown Linter
MCPB · KATANA-MARKDOWN-LINTER-0.20.1.MCPB
Markdown linter, workspace-scoped stdio MCP server, and self-hosted text-only remote MCP server.
Available components
Last scanned (7 hours ago)
Scores higher than 82% of MCPB servers
Category Developer Tools
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security0
- No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
- Known CVEs could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).Unverified
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 6 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability67
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 443 tokens (~44/item across 10 items; 10 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 2 Nov 26 +1
- Provenance: unverified → fail ▼ security
- Maintenance: unverified → pass ▲ functional
- 1 Nov 26 +1
- Stability: 0.97 → pass security
- 31 Oct 26 −2
- Provenance: fail → unverified ▼ security
- Maintenance: pass → unverified ▼ functional
- Stability: pass → 0.97 functional
- 29 Oct 26 0
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Tool coverage: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- First check of Schema quality: unverified functional
- Package version: 0.20.0 → 0.20.1 functional
- 28 Oct 26 0
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- Package version: 0.19.6 → 0.20.0 functional
- 27 Oct 26 0
- Package version: 0.19.5 → 0.19.6 functional
- 25 Oct 26 +1
- Stability: 0.97 → pass security
- 23 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed mcpb/https://github.com/HiroyukiFuruno/katana-markdown-linter/releases/download/v0.20.1/katana-markdown-linter-0.20.1.mcpb@0.20.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | mcpb |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_directory ~51
Lint Markdown files under a workspace directory.
| Name | Type | Req | Description |
|---|---|---|---|
| config_path | string|null | – | – |
| locale | string|null | – | – |
| path | string | yes | – |
| respect_gitignore | boolean|null | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| errors | array | yes | – |
| file_count | integer | yes | – |
| files | array | yes | – |
| issue_count | integer | yes | – |
| path | string | yes | – |
No examples provided.
check_file ~43
Lint a Markdown file inside the configured workspace root.
| Name | Type | Req | Description |
|---|---|---|---|
| config_path | string|null | – | – |
| locale | string|null | – | – |
| path | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| diagnostics | array | yes | – |
| issue_count | integer | yes | – |
| path | string | yes | – |
No examples provided.
check_text ~33
Lint supplied Markdown text and return structured diagnostics.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | – |
| locale | string|null | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| diagnostics | array | yes | – |
| issue_count | integer | yes | – |
No examples provided.
config_validate ~17
Validate a markdownlint-compatible JSON config object.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| error_count | integer | yes | – |
| errors | array | yes | – |
| valid | boolean | yes | – |
No examples provided.
fix_file_apply ~53
Apply safe fixes to a workspace file only when apply is true.
| Name | Type | Req | Description |
|---|---|---|---|
| apply | boolean | yes | – |
| config_path | string|null | – | – |
| locale | string|null | – | – |
| path | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| applied_fixes | integer | yes | – |
| changed | boolean | yes | – |
| path | string | yes | – |
| remaining_diagnostics | array | yes | – |
| remaining_issue_count | integer | yes | – |
No examples provided.
fix_file_preview ~48
Preview safe fixes for a workspace file and return a text diff without writing.
| Name | Type | Req | Description |
|---|---|---|---|
| config_path | string|null | – | – |
| locale | string|null | – | – |
| path | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| applied_fixes | integer | yes | – |
| changed | boolean | yes | – |
| diff | string | yes | – |
| path | string | yes | – |
| remaining_diagnostics | array | yes | – |
| remaining_issue_count | integer | yes | – |
No examples provided.
fix_text ~38
Apply safe Markdown fixes to supplied text and return fixed content without writing files.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | – |
| locale | string|null | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| applied_fixes | integer | yes | – |
| content | string | yes | – |
| remaining_diagnostics | array | yes | – |
| remaining_issue_count | integer | yes | – |
No examples provided.
rule_doc_get ~37
Get full Markdown documentation for a rule, supporting multiple locales.
| Name | Type | Req | Description |
|---|---|---|---|
| locale | string|null | – | – |
| rule_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | – |
| locale | string | yes | – |
| rule_id | string | yes | – |
No examples provided.
rule_get ~35
Get metadata for a single markdownlint-compatible rule ID.
| Name | Type | Req | Description |
|---|---|---|---|
| locale | string|null | – | – |
| rule_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | yes | – |
| docs_url | string | yes | – |
| english_description | string | yes | – |
| fixable | boolean | yes | – |
| id | string | yes | – |
| implemented_check | boolean | yes | – |
| lifecycle | string | yes | – |
| locale | string | yes | – |
| name | string | yes | – |
No examples provided.
rule_list ~27
List markdownlint-compatible rule metadata known to kml.
| Name | Type | Req | Description |
|---|---|---|---|
| locale | string|null | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | yes | – |
| locale | string | yes | – |
| rules | array | yes | – |
No examples provided.
How do I install the KatanA Markdown Linter MCP server?
KatanA Markdown Linter ships as an MCPB bundle, a single file you download and open in an MCP host that supports MCPB bundles, such as Claude Desktop. The host reads the launch command from the bundle's own manifest, so there is no command to copy. Before opening it, check the file's SHA-256 matches the one the MCP registry declares for it, b148e795d695e744865e8c723e68c18c9fe29fb931eb47dc94c11330f7ba3f94; the commands to do that are on this page. If it does not match, do not open it.
mcpb · katana-markdown-linter-0.20.1.mcpb
Download bundleCheck the download matches the SHA-256 the MCP registry declares before you open it. If it does not match, do not open the file.
SHA-256
b148e795d695e744865e8c723e68c18c9fe29fb931eb47dc94c11330f7ba3f94
macOS / Linux
echo "b148e795d695e744865e8c723e68c18c9fe29fb931eb47dc94c11330f7ba3f94 katana-markdown-linter-0.20.1.mcpb" | shasum -a 256 -c
Windows (PowerShell)
(Get-FileHash -Algorithm SHA256 .\katana-markdown-linter-0.20.1.mcpb).Hash -eq "b148e795d695e744865e8c723e68c18c9fe29fb931eb47dc94c11330f7ba3f94"
Run it in the folder you saved the bundle to, then open the file with an MCPB-capable host such as Claude Desktop.
What is the KatanA Markdown Linter MCP server?
KatanA Markdown Linter is an MCP server listed in the public MCP registry as io.github.HiroyukiFuruno/kml. Markdown linter, workspace-scoped stdio MCP server, and self-hosted text-only remote MCP server. This page covers its MCPB bundle (https://github.com/HiroyukiFuruno/katana-markdown-linter/releases/download/v0.20.1/katana-markdown-linter-0.20.1.mcpb).
Is the KatanA Markdown Linter MCP server safe to use?
KatanA Markdown Linter scores 51 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the KatanA Markdown Linter MCP server expose?
KatanA Markdown Linter exposes 10 tools: check_directory, check_file, check_text, config_validate, fix_file_apply, and 5 more. Their descriptions and schemas cost roughly 382 tokens of context every time the server is loaded.
What licence is the KatanA Markdown Linter MCP server under?
KatanA Markdown Linter declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.