MCP.Market

Krova MCP server

by krova.cloud·cloud.krova/mcp·v0.3.19

Provision and manage Krova Cloud Cubes — Firecracker microVMs with root access and no public IP.

B80/100grade B
What users say
No reviews yet
Be the first
Safety scan
B80/100

not scanned yet

Adoption
Growing

0 stars372 downloads/wk

Reviews

Write one

Nobody has reviewed Krova yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Krova tools

No tool declarations could be read from the package source. They show once the server is installed.

Not scanned yet. New listings are scanned within a day or two of arriving.

How Krova compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
80/100
higher than 60% of 48,255 servers
Downloads a week
372
more than 84% of 12,191 servers with a package

Release history: 3 versions in the registry since 2026-09-17, latest 2026-11-03, typically one every 37 days.

Install Krova in Claude Code, Cursor or VS Code

Runs npx -y @krovacloud/mcp on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add mcp -- npx -y @krovacloud/mcp
Add to Cursor

What the publisher says

From the Krova repository's README, as published. We do not edit it. Read it on GitHub

krova-node

The single home for the Krova Cloud JavaScript / TypeScript packages — SDK, CLI, MCP server, webhook verifier, and the n8n node. A pnpm-workspace monorepo: the CLI/MCP consume the SDK via workspace:*, so everything stays in sync and a cross-package change is one PR.

Develop

pnpm install
pnpm -r build      # topological — the SDK builds before its consumers
pnpm -r test
pnpm -r typecheck

Releasing (automatic, no manual version bumps)

Every push to main runs scripts/release.mjs: for each package that changed since its last release tag, it patch-increments the latest version on npm, publishes it (with provenance), and records a @ git tag + GitHub release. Unchanged packages are skipped. An explicit higher version in a package's package.json is honored as-is.

Publishing uses npm trusted publishing (OIDC) — the release workflow has id-token: write and runs pnpm publish --provenance, so no NPMTOKEN** (or any long-lived npm token) is required. See "How releases work" in CONTRIBUTING.md.

Nothing above is checked by us. What we check is on the safety report.

Krova: common questions

Is Krova MCP server safe?
Mostly: it is graded B (80/100). Read the Krova safety report
How do I install Krova?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Krova need an API key?
Yes. The registry entry asks for KROVA_API_KEY.
Is Krova maintained?
The last commit was 37 days ago (2026-09-28). The latest release is v0.3.19.
What can I use instead of Krova?
Servers from other publishers that do the same job: Superserve MCP server.
How does Krova compare with other MCP servers?
safety score 80/100 (higher than 60% of 48,255 servers); downloads a week 372 (more than 84% of 12,191 servers with a package). Full comparison.

Alternatives to Krova

Same job from other publishers: the closest match first, then the best rated.

  • Superserve
    MCP server for Superserve sandboxes: create, exec, and manage Firecracker microVMs
    A