# @krovacloud/mcp

MCP server for Krova Cloud — let Claude, Cursor, and any MCP client provision and manage Cubes (Firecracker microVMs).

- **Type:** MCP server
- **Trust:** 85/100 (A), scored on the package rubric
- **Verification:** verified (build provenance)
- **Version:** 0.3.12
- **Author:** Krova Inc.
- **License:** MIT
- **npm:** @krovacloud/mcp
- **Source:** https://github.com/krovacloud/krova-node
- **Compatible clients:** claude-code, cursor, copilot, gemini (basis: transport)

## Trust

85/100 (A), scored on the package rubric
- Publisher verified: no
- Build provenance: verified attestation
- npm trusted publishing (OIDC): yes
- Install scripts: nothing suspicious found
- Prompt-injection scan: not run
- Obfuscation scan: not run
- Evidence age: 0 days

## Security scan

- **Status:** clean
- **Scanned:** 2026-09-08T11:12:26.140Z
- **Version scanned:** 0.3.12
- **CVEs:** none found by OSV at scan time

## Tools

23 declared. Statically extracted from the shipped source — a floor on the surface, not a census.
- `list_cubes` — List all Cubes (Firecracker microVMs) in a Krova Cloud Space.
- `get_cube` — Get details for a single Cube by id.
- `get_cube_ssh` — Everything needed to SSH into a Cube: host, port, the login USER, and any pinned host keys. Call this rather than guessing a username — it is `ubuntu` or `debia
- `create_cube` — Create (provision) a new Cube in a Space. Provisioning is asynchronous — the returned Cube begins in a pending state. Destructive/billable: creating a Cube star
- `power_off_cube` — Power off a running Cube (asynchronous). Compute + host RAM are released while disk is preserved; the Cube becomes stopped.
- `wake_cube` — Start a stopped Cube (asynchronous).
- `restart_cube` — Restart a running Cube — a COLD restart (asynchronous). The hypervisor process is stopped and relaunched, so the Cube boots against the host's current kernel. T
- `delete_cube` — Delete a Cube (asynchronous — deletion is enqueued). DESTRUCTIVE and irreversible: the Cube and its disk are torn down. Only call this when the user has explici
- `list_regions` — List Krova Cloud regions with available capacity.
- `list_images` — List available OS images for new Cubes.
- `get_pricing` — Get per-resource hourly rates and volume pricing tiers.
- `list_domains` — List the custom domains attached to a Cube.
- `get_domain_records`
- `create_domain` — Attach a custom domain to a Cube, routing it to an in-Cube port. Returns the domain AND the DNS records the user must publish — tell them the records verbatim, 
- `update_domain` — Change a custom domain's proxy settings. Currently exposes the origin scheme — the transport the edge uses to reach the Cube.
- `delete_domain` — Detach a custom domain from a Cube. Irreversible.
- `list_snapshots` — List a Cube's disk snapshots.
- `create_snapshot` — Create a snapshot of a Cube's disk. Asynchronous — the snapshot is enqueued.
- `delete_snapshot` — Delete a Cube snapshot. Irreversible.
- `restore_cube` — Restore a Cube's disk from one of its snapshots — REPLACES the current disk. Destructive and irreversible.
- `list_tcp_mappings` — List a Cube's TCP port mappings.
- `create_tcp_mapping` — Expose a Cube TCP port on the host, optionally restricted to specific IPs/CIDRs.
- `delete_tcp_mapping` — Remove a Cube TCP port mapping. Irreversible.

## Install

**Verdict: install** — No blocking findings and no open coverage gaps — safe to install as configured.
**Config** (claude-code):
```json
"{\n  \"mcpServers\": {\n    \"mcp\": {\n      \"command\": \"npx\",\n      \"args\": [\n        \"-y\",\n        \"@krovacloud/mcp\"\n      ],\n      \"env\": {\n        \"KROVA_API_KEY\": \"<YOUR_KROVA_API_KEY>\"\n      }\n    }\n  }\n}"
```
**Credentials it will ask for** (names only — Forge never holds a value):
- `KROVA_API_KEY` — Krova API Key (required)
Placeholders only. Forge never holds, brokers, or transmits a credential value — replace each <YOUR_NAME> in your own config file. Do not send a value back to Forge; no Forge endpoint accepts one.
- This entry needs 1 credential (1 required). The generated config carries placeholders, so it will fail in the editor rather than at runtime if they are left unset.

## Blast radius

Extensive blast radius — deletes data; holds an api key.
- Floor 55, ceiling 55 (tier: extensive)
- This is impact, not likelihood. A high radius is not a defect: a filesystem server is supposed to write files. It is never part of the trust score.

## Machine-readable views of this entry

- Signed JSON: https://forgeregistry.com/api/v1/packages/%40krovacloud%2Fmcp
- Install plan: https://forgeregistry.com/api/v1/packages/%40krovacloud%2Fmcp/install-plan
- Alternatives: https://forgeregistry.com/api/v1/alternatives/%40krovacloud%2Fmcp
- HTML page: https://forgeregistry.com/registry/%40krovacloud%2Fmcp
- MCP: POST https://forgeregistry.com/api/mcp → `forge_get_package` / `forge_install_plan`

## About this document

Generated by Forge (https://forgeregistry.com) — a compact rendering of the same record served, signed, at the JSON URL above. Trust and scan facts are the registry's own measurements; anything Forge did not measure is named as unmeasured rather than omitted.