Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Tenki Sandbox MCP

NPM · @TENKICLOUD/MCP · SCANNED SEP 20

Disposable microVM sandboxes for AI agents: run code, read/write files, git, preview URLs.

Available components

npm · @tenkicloud/mcp 97
+3 this week 97 Trust /100
Trust breakdown (7 categories)

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 Security98
  • 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
  • 31 of 95 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 LuxorLabs/tenki-mcp). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 2 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability86
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 86 tokens (~86/item across 1 items; 1 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 Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 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 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 1 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
Install

How do I install the Tenki Sandbox MCP server?

Tenki Sandbox MCP runs locally as an npm package, launched with npx -y @tenkicloud/mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @tenkicloud/mcp

# add to Claude Code
claude mcp add luxorlabs-tenki-mcp -- npx -y @tenkicloud/mcp
// .cursor/mcp.json
{
  "mcpServers": {
    "luxorlabs-tenki-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@tenkicloud/mcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "luxorlabs-tenki-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@tenkicloud/mcp"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add luxorlabs-tenki-mcp -- npx -y @tenkicloud/mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "luxorlabs-tenki-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@tenkicloud/mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add luxorlabs-tenki-mcp --command npx --arg -y --arg @tenkicloud/mcp
# ~/.hermes/config.yaml
mcp_servers:
  luxorlabs-tenki-mcp:
    command: "npx"
    args: ["-y", "@tenkicloud/mcp"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "luxorlabs-tenki-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@tenkicloud/mcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add luxorlabs-tenki-mcp -t stdio -c npx -a -y @tenkicloud/mcp
// mcp.json
{
  "mcpServers": {
    "luxorlabs-tenki-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@tenkicloud/mcp"
      ]
    }
  }
}
Changelog

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.

  • 20 Sept 26 +1
    • Stability: 0.97 → pass security
  • 18 Sept 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.

  • 17 Sept 26 0
    • Stability: 0.87 → 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.2.0 → 0.3.0 functional
  • 15 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.

  • 13 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.

  • 11 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.

  • 9 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.

  • 7 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

Diagnostics

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 20 Sept 2026 · Analysed npm/@tenkicloud/mcp@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 LuxorLabs/tenki-mcp
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/LuxorLabs/tenki-mcp/.github/workflows/npm-publish.yml@refs/tags/v0.3.0
Rekor log index 2879492318
Predicate type https://slsa.dev/provenance/v1
Subject digest sha512:bbc6a5ac7fad5196f83fb8dec2ad5bc5a6746b163a461d30597c8c5c43ad09ee9c1c911051c55545516d12a56c25261338adc5452184f96a4cc063d4a

Background: How many MCP packages publish verified provenance →

Dependencies 95 packages
Packages resolved 95
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 1 exposed · ~86 tokens

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 →

Tool Tokens
tenki_auth_status ~86

Report whether the server has a usable Tenki credential, which kind (API key vs OAuth session token), and the endpoint it targets — verified with a live identity probe. Call this first when other tools fail with auth errors, or when this is the only tool available (which means no credential is configured). Reports status only; it does not log in and never returns the token.

Input schema present but exposes no named parameters.

NameTypeReqDescription
authenticatedbooleanyesTrue only when a credential is present AND a live identity probe succeeded.
credentialstringyesKind of credential the server is running with. Never includes the token itself.
detailstringyesHuman-readable status plus, when unauthenticated, how to supply a credential.
endpointstringyesControl-plane base URL the server is pointed at.
errorstring–Why the probe failed, when a credential is present but unusable (expired, revoked, wrong endpoint).
identityobject–Identity returned by the live probe, when it succeeded.
sourcestring–Environment variable the credential came from (TENKI_AUTH_TOKEN takes precedence over TENKI_API_KEY).
toolsRegisteredintegeryesHow many tools this server registered. Without a credential only this one is registered.

No examples provided.

Common questions

What is the Tenki Sandbox MCP server?

Tenki Sandbox MCP is listed in the public MCP registry as io.github.LuxorLabs/tenki-mcp. Disposable microVM sandboxes for AI agents: run code, read/write files, git, preview URLs. This page covers its npm package (@tenkicloud/mcp).

Is the Tenki Sandbox MCP server safe to use?

Tenki Sandbox MCP scores 97 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 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 Tenki Sandbox MCP server expose?

Tenki Sandbox MCP exposes 1 tool: tenki_auth_status. Their descriptions and schemas cost roughly 86 tokens of context every time the server is loaded.

Is the Tenki Sandbox MCP server still maintained?

Tenki Sandbox MCP is still listed as active in the MCP registry. We last reached this channel on 20 September 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 Tenki Sandbox MCP server under?

Tenki Sandbox MCP declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.