io.github.KilaWattCloud/kilawatt-mcp-server
NPM · KILAWATT-MCP-SERVER
Kilawatt Cloud MCP server: request GPU compute with account or x402 payments.
Available components
Last scanned (22 hours ago)
Scores higher than 92% of npm servers
Category Cloud Infrastructure
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 Security90
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, reached via @x402/core > zod. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 30 of 113 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to KilaWattCloud/kilawatt-mcp-server). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 14 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability69
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 805 tokens (~89/item across 9 items; 9 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 Coverage81
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 43% of tool parameters carry a description.Partial
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "deploy_gpu_node" implies "deploy" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 9 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.
- 3 Nov 26 0
- Stability: 0.97 → pass security
- 2 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.
- 1 Nov 26 −1
- Stability: pass → 0.93 functional
- 26 Oct 26 0
- Stability: 0.97 → pass security
- 25 Oct 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.
- 24 Oct 26 −3
- CVE-2023-54404 affects this package: high ▼ security
- Known CVEs: pass → fail ▼ security
- Package version: 0.1.1 → 0.3.0 functional
- 23 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Oct 26 +16
- Malware scan: unverified → pass ▲ security
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 4 Nov 2026 · Analysed npm/kilawatt-mcp-server@0.3.0
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 | KilaWattCloud/kilawatt-mcp-server |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/KilaWattCloud/kilawatt-mcp-server/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3342870215 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:8822ebc031df20f32c1a131df4dfdbfa42c262c0afd5efd6b97bce207c16080db4b89eaba413165f4d451730a637706205c57f442a269efbdf5fc90ba |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 113 packages
| Packages resolved | 113 |
|---|---|
| Stale | 30 |
| 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 →
deploy_gpu_node ~173
Provision real GPU compute on Kilawatt Cloud. Charges the caller's Kilawatt wallet and starts an actual machine. Set dry_run to true to price the run and check balance, spend caps, rate limits and concurrency without provisioning or charging anything.
| Name | Type | Req | Description |
|---|---|---|---|
| card_count | integer | – | Number of GPUs to provision. |
| dry_run | boolean | – | Price and pre-authorize only. Returns the cost estimate, the routing order and whether the account is authorized, without provisioning or charging. |
| duration_seconds | number | – | How long the node is needed, in seconds. Billed up front. |
| gpu_type | string | – | GPU model identifier, e.g. nvidia-h100, nvidia-h200, nvidia-b200. |
| routing_policy | string | – | How the smart order router picks a node. |
No output schema declared.
No examples provided.
get_capacity ~49
Read current GPU capacity data from Kilawatt Cloud. Read-only: no API key is needed and nothing is provisioned or charged. If capacity data is not available right now, the tool says so.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_platform_status ~65
Read the current Kilawatt Cloud platform status: status (operational, degraded, incident or unknown), a status note, when it was last checked, and links to the status page and the latest test summary. Read-only: no API key is needed and nothing is charged.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_pricing ~59
Read indicative USD prices per GPU hour for each GPU tier. Read-only: no API key is needed and nothing is charged. These prices are indicative only. The exact price for a job comes from an unpaid x402 request (use x402_quote).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_resume_info ~84
Check whether a job can be resumed from its last checkpoint. Returns the checkpoint count, the last checkpoint time, can_resume, the reason when it cannot be resumed, and the resume action. Read-only: nothing is started or charged. Needs KILAWATT_API_KEY.
| Name | Type | Req | Description |
|---|---|---|---|
| job_id | string | yes | The job ID (36 characters, hex digits and dashes). |
No output schema declared.
No examples provided.
resume_job ~183
Start a NEW PAID run that resumes a job from its last checkpoint on a different supplier. This spends money. It requires confirm set to true and a spend cap in max_spend_usd. Call get_resume_info first, show the user what it returns, and ask the user before calling this tool with confirm true. The request is never retried automatically. Needs KILAWATT_API_KEY.
| Name | Type | Req | Description |
|---|---|---|---|
| confirm | boolean | yes | Must be exactly true, and only after the user has agreed to start a paid run. |
| duration_seconds | integer | – | Optional run length in seconds, a whole number from 60 to 86400. |
| job_id | string | yes | The job ID (36 characters, hex digits and dashes). |
| max_spend_usd | number | yes | Required spend cap in USD for the new run. Must be a positive number. |
No output schema declared.
No examples provided.
x402_job_status ~37
Get the status of a job created through x402 using this server's locally saved API key.
| Name | Type | Req | Description |
|---|---|---|---|
| job_id | string | yes | – |
No output schema declared.
No examples provided.
x402_quote ~66
Get the current price and Base USDC payment details for a GPU job without paying.
| Name | Type | Req | Description |
|---|---|---|---|
| card_count | integer | – | – |
| duration_seconds | number | – | – |
| gpu_type | string | – | – |
| routing_policy | string | – | – |
| workload_type | string | – | – |
No output schema declared.
No examples provided.
x402_run_job ~89
Quote and, only with confirm=true and all spend caps passing, pay for one GPU job in Base USDC.
| Name | Type | Req | Description |
|---|---|---|---|
| card_count | integer | – | – |
| confirm | boolean | yes | – |
| duration_seconds | number | – | – |
| gpu_type | string | – | – |
| max_usd | number | yes | – |
| routing_policy | string | – | – |
| workload_type | string | – | – |
No output schema declared.
No examples provided.
How do I install the io.github.KilaWattCloud/kilawatt-mcp-server server?
io.github.KilaWattCloud/kilawatt-mcp-server runs locally as an npm package, launched with npx -y kilawatt-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 · kilawatt-mcp-server
claude mcp add kilawattcloud-kilawatt-mcp-server -- npx -y kilawatt-mcp-server
What is the io.github.KilaWattCloud/kilawatt-mcp-server server?
io.github.KilaWattCloud/kilawatt-mcp-server is listed in the public MCP registry as io.github.KilaWattCloud/kilawatt-mcp-server. Kilawatt Cloud MCP server: request GPU compute with account or x402 payments. This page covers its npm package (kilawatt-mcp-server).
Is the io.github.KilaWattCloud/kilawatt-mcp-server server safe to use?
io.github.KilaWattCloud/kilawatt-mcp-server scores 88 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 4 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.KilaWattCloud/kilawatt-mcp-server server expose?
io.github.KilaWattCloud/kilawatt-mcp-server exposes 9 tools: deploy_gpu_node, x402_quote, x402_run_job, x402_job_status, get_capacity, and 4 more. Their descriptions and schemas cost roughly 805 tokens of context every time the server is loaded.
Is the io.github.KilaWattCloud/kilawatt-mcp-server server still maintained?
io.github.KilaWattCloud/kilawatt-mcp-server is still listed as active in the MCP registry. We last reached this channel on 4 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.KilaWattCloud/kilawatt-mcp-server server under?
io.github.KilaWattCloud/kilawatt-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.