io.github.qingkuai-js/qingkuai-mcp-server
NPM · QINGKUAI-MCP-SERVER
MCP server for Qingkuai (.qk) — docs search, syntax check, compilation, and formatting tools.
Available components
Last scanned (2 hours ago)
Scores higher than 99% of npm 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 Security99
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 2 of 11 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to qingkuai-js/language-features). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 3 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability85
- 97% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Partial
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 4262 tokens (~60/item across 70 items; 6 tools + 64 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
- Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 4 Nov 26 −1
- Stability: pass → 0.93 functional
- 1 Nov 26 +10
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Provenance: fail → pass ▲ security
- The attested source repository moved: qingkuai-js/language-features security
- Schema quality: 40 → 60 ▼ functional
- Capabilities: pass → unverified ▼ functional
- Schema quality: 92 → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Schema quality: 92% → 97% ▲ functional
- Package version: 1.0.2 → 1.0.13 functional
- 31 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- 29 Oct 26 +1
- Stability: 0.97 → pass security
- Security disclosure: fail → unverified ▼ functional
- 27 Oct 26 −1
- Stability: pass → 0.93 functional
- 21 Oct 26 +1
- Stability: 0.97 → pass security
- 20 Oct 26 −1
- Stability: pass → 0.97 functional
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 npm/qingkuai-mcp-server@1.0.13
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | qingkuai-js/language-features |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/qingkuai-js/language-features/.github/workflows/release.yml@refs/tags/mcp-v1.0.13 |
| Rekor log index | 3631805155 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:be7d12bb43c8d495d9b493843041ab62050107b34cce8cc6d252affb7f6756e42cdb728515644422a197a8ddedee8d79a52c8a6325e53ef5a3ef949f1 |
Background: How many MCP packages publish verified provenance →
Dependencies 11 packages
| Packages resolved | 11 |
|---|---|
| Stale | 2 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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_qingkuai_syntax Check Qingkuai Syntax ~140
Check Qingkuai (.qk) source code syntax without full compilation. Performs early stage compilation (template parsing, script analysis) to validate: - Template structure and tag nesting - Script syntax errors - Directive usage and attributes Returns syntax errors, warnings, and type information without code generation. Use this when the user wants to validate or check .qk code syntax, or reports a syntax error in a .qk file.
| Name | Type | Req | Description |
|---|---|---|---|
| allowConstReactive | boolean | – | Allow constant declarations to be marked as reactive. Default: true |
| source | string | yes | Qingkuai (.qk) source code to check |
No output schema declared.
No examples provided.
compile_qingkuai Compile Qingkuai Code ~286
Compile Qingkuai (.qk) source code to JavaScript. Performs full compilation pipeline: - Syntax validation (parsing, analysis) - Template compilation to render functions - Reactivity detection and optimization - Source map generation Returns compiled JavaScript code, error messages, and source mappings. Use this when the user wants to compile or transpile .qk source code to JavaScript, or asks about the compilation result.
| Name | Type | Req | Description |
|---|---|---|---|
| allowConstReactive | boolean | – | Allow constant declarations to be marked as reactive. Default: true |
| debug | boolean | – | Enable debug mode. Default: false |
| hashId | string | – | Hash ID for the component. Default: auto-generated |
| interpretiveComments | boolean | – | Preserve interpretive comments. Default: false |
| preserveHtmlComments | boolean | – | Preserve HTML comments in template. Default: false |
| reactivityMode | string | – | Default reactivity mode for variables. Default: 'reactive' |
| requireReactivityMark | boolean | – | Require top-level variable declarations to be explicitly marked with reactivity built-ins. Default: false |
| source | string | yes | Qingkuai (.qk) source code to compile |
| sourcemap | boolean | – | Generate source map. Default: false |
| whitespace | string | – | Whitespace handling in templates. Default: 'trim' |
No output schema declared.
No examples provided.
format_qingkuai_code Format Qingkuai Code ~158
Format a Qingkuai (.qk) file using Prettier with the Qingkuai plugin. Applies consistent code style and formatting: - Indentation and spacing normalization - Line breaking and wrapping - Consistent quote styles (template literals, single quotes, etc.) - Component attribute formatting Input is a file path. The tool reads file contents, loads Prettier config with that path, formats, and writes back to the same file. Returns write result and any formatting errors. Use this when the user wants to format, reformat, or fix the styling of a .qk file.
| Name | Type | Req | Description |
|---|---|---|---|
| filePath | string | yes | Absolute or workspace-relative path to the .qk file to format and write back |
No output schema declared.
No examples provided.
get_qingkuai_project_bootstrap_guide Get Qingkuai Project Bootstrap Guide ~80
Use this first when user asks to create/init a Qingkuai project in a new or empty folder. Returns authoritative install/scaffold docs URIs and snippets.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum number of results. Default is 4. |
| query | string | – | Optional keywords. Default: getting started installation create. |
No output schema declared.
No examples provided.
read_qingkuai_doc Read Qingkuai Doc ~100
Read a Qingkuai doc by its docs:// URI (as returned by search_qingkuai_docs). Supports an #section anchor to read a single section; without an anchor the full document is returned. Unknown URIs return the closest valid URIs.
| Name | Type | Req | Description |
|---|---|---|---|
| uri | string | yes | Doc URI returned by search_qingkuai_docs, e.g. docs://basic/forms.md or docs://basic/forms.md#two-way-binding |
No output schema declared.
No examples provided.
search_qingkuai_docs Search Qingkuai Syntax Docs ~220
Search the official Qingkuai reference docs for .qk files. This is the AUTHORITATIVE source for Qingkuai syntax, directives, attributes, events, reactivity, and components. Accepts English, Chinese, or syntax tokens (e.g. #for, &value, qk:spread). ALWAYS call this tool when the user asks about Qingkuai syntax, grammar, directives, attributes, events, interpolation, reactivity, components, compiler rules, or how to write .qk code — do NOT answer from memory. Results include matched doc sections with full content inline. Base answers on these sections; call read_qingkuai_doc for a full document or a specific section. Verify generated .qk code with check_qingkuai_syntax afterwards.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum number of result groups. Default is 4. |
| query | string | yes | Keywords, a natural-language question (English or Chinese), or syntax tokens like #for / &value / qk:spread. |
No output schema declared.
No examples provided.
How do I install the io.github.qingkuai-js/qingkuai-mcp-server server?
io.github.qingkuai-js/qingkuai-mcp-server runs locally as an npm package, launched with npx -y qingkuai-mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · qingkuai-mcp-server
claude mcp add qingkuai-js-qingkuai-mcp-server -- npx -y qingkuai-mcp-server
What is the io.github.qingkuai-js/qingkuai-mcp-server server?
io.github.qingkuai-js/qingkuai-mcp-server is listed in the public MCP registry as io.github.qingkuai-js/qingkuai-mcp-server. MCP server for Qingkuai (.qk), docs search, syntax check, compilation, and formatting tools. This page covers its npm package (qingkuai-mcp-server).
Is the io.github.qingkuai-js/qingkuai-mcp-server server safe to use?
io.github.qingkuai-js/qingkuai-mcp-server scores 96 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 io.github.qingkuai-js/qingkuai-mcp-server server expose?
io.github.qingkuai-js/qingkuai-mcp-server exposes 6 tools: format_qingkuai_code, check_qingkuai_syntax, compile_qingkuai, get_qingkuai_project_bootstrap_guide, search_qingkuai_docs, read_qingkuai_doc. Their descriptions and schemas cost roughly 984 tokens of context every time the server is loaded.
Is the io.github.qingkuai-js/qingkuai-mcp-server server still maintained?
io.github.qingkuai-js/qingkuai-mcp-server is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.qingkuai-js/qingkuai-mcp-server server under?
io.github.qingkuai-js/qingkuai-mcp-server declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.