# TurboSteed MCP (npm · @turbosteed/cli)

Exposes TurboSteed web-hosting, site generation, and library features to AI coding agents.

- Trust score: 36/100 (low)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- npm · `@turbosteed/cli`: 36/100 (this document), [markdown](https://verifymcp.io/servers/vivek-turbosteed-turbosteed-cli/turbosteed-cli.md), [page](https://verifymcp.io/servers/vivek-turbosteed-turbosteed-cli/turbosteed-cli)

## Channel facts

- Registry: `npm`
- Package: `@turbosteed/cli`
- Version: `1.1.1`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Supply Chain Security**: 98/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 61 of 156 dependencies flagged as unhealthy (2 deprecated).
- **Provenance & Transparency**: 32/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Licence could not be checked: the licence is shipped as a file inside the package, not declared as a standard (SPDX) licence identifier, so we cannot tell whether it is OSI-approved.
  - Actively maintained (last published 49 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 0/100
  - Schema quality not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no schema to assess.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no schema to compare.
- **Tool Coverage**: 0/100
  - Tool coverage not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no tool definitions to assess.
- **Tool Safety**: 0/100
  - Tool safety not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no tool text to scan.
- **Capabilities**: 0/100
  - Protocol version not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we never saw its MCP handshake.

**Unverified: 5 categories.** Categories scored 0 because our sandbox has not given us the schema these checks need to read. That is a gap on our side rather than a finding about the package, and we only credit what we can confirm, so the score stands at 0 until the capture succeeds. We are working through the fleet, so this normally clears without any action from you.

## Install

### How do I install the TurboSteed MCP server?

TurboSteed MCP runs locally as an npm package, launched with npx -y @turbosteed/cli. The registry lists launch arguments for this package that we cannot show safely, so they are left out. Check the registry entry for what the server needs. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add vivek-turbosteed-turbosteed-cli -- npx -y @turbosteed/cli
```

The registry lists launch arguments for this package that we cannot show safely, so they are left out. Check the registry entry for what the server needs.

### Cursor

```json
{
  "mcpServers": {
    "vivek-turbosteed-turbosteed-cli": {
      "command": "npx",
      "args": [
        "-y",
        "@turbosteed/cli"
      ]
    }
  }
}
```

The registry lists launch arguments for this package that we cannot show safely, so they are left out. Check the registry entry for what the server needs.

### VS Code

```json
{
  "servers": {
    "vivek-turbosteed-turbosteed-cli": {
      "command": "npx",
      "args": [
        "-y",
        "@turbosteed/cli"
      ]
    }
  }
}
```

The registry lists launch arguments for this package that we cannot show safely, so they are left out. Check the registry entry for what the server needs.

### Codex

```bash
codex mcp add vivek-turbosteed-turbosteed-cli -- npx -y @turbosteed/cli
```

The registry lists launch arguments for this package that we cannot show safely, so they are left out. Check the registry entry for what the server needs.

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "vivek-turbosteed-turbosteed-cli": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@turbosteed/cli"
      ],
      "enabled": true
    }
  }
}
```

The registry lists launch arguments for this package that we cannot show safely, so they are left out. Check the registry entry for what the server needs.

### OpenClaw

```bash
openclaw mcp add vivek-turbosteed-turbosteed-cli --command npx --arg -y --arg @turbosteed/cli
```

The registry lists launch arguments for this package that we cannot show safely, so they are left out. Check the registry entry for what the server needs.

### Hermes

```yaml
mcp_servers:
  vivek-turbosteed-turbosteed-cli:
    command: "npx"
    args: ["-y", "@turbosteed/cli"]
```

The registry lists launch arguments for this package that we cannot show safely, so they are left out. Check the registry entry for what the server needs.

### Netclaw

```json
{
  "McpServers": {
    "vivek-turbosteed-turbosteed-cli": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@turbosteed/cli"
      ]
    }
  }
}
```

The registry lists launch arguments for this package that we cannot show safely, so they are left out. Check the registry entry for what the server needs.

### Vellum

```bash
assistant mcp add vivek-turbosteed-turbosteed-cli -t stdio -c npx -a -y @turbosteed/cli
```

The registry lists launch arguments for this package that we cannot show safely, so they are left out. Check the registry entry for what the server needs.

### Other

```json
{
  "mcpServers": {
    "vivek-turbosteed-turbosteed-cli": {
      "command": "npx",
      "args": [
        "-y",
        "@turbosteed/cli"
      ]
    }
  }
}
```

The registry lists launch arguments for this package that we cannot show safely, so they are left out. Check the registry entry for what the server needs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 36, +2)

- [security improvement] CVE-2026-118764 no longer affects this package
- [security improvement] Known CVEs: fail → pass

### 2026-10-31 (score 34, −2)

- [security regression] CVE-2026-118764 affects this package: medium
- [security regression] Known CVEs: pass → fail

### 2026-10-19 (score 0)

- [functional regression] Security disclosure: unverified → fail

### 2026-10-18 (score 0)

- [functional regression] Security disclosure: fail → unverified

### 2026-10-12 (score 0)

- [functional regression] Security disclosure: unverified → fail

### 2026-10-11 (score 0)

- [functional regression] Security disclosure: fail → unverified

### 2026-10-03 (score 0)

- [security improvement] Malware scan: unverified → pass

### 2026-10-02 (score 0)

First indexed and scored.

## MCP tools (0)

Tools for package channels are captured by running the package in an isolated sandbox. The most recent sandbox run could not capture a tool list from this package.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/vivek-turbosteed-turbosteed-cli/turbosteed-cli#diagnostics

## Score history

- 2026-11-21: 36
- 2026-11-20: 36
- 2026-11-19: 36
- 2026-11-18: 36
- 2026-11-17: 36
- 2026-11-16: 36
- 2026-11-15: 36
- 2026-11-14: 36
- 2026-11-13: 36
- 2026-11-12: 36
- 2026-11-11: 36
- 2026-11-10: 36
- 2026-11-09: 36
- 2026-11-08: 36
- 2026-11-07: 36
- 2026-11-06: 36
- 2026-11-05: 36
- 2026-11-04: 34
- 2026-11-03: 34
- 2026-11-02: 34
- 2026-11-01: 34
- 2026-10-31: 34
- 2026-10-30: 36
- 2026-10-29: 36
- 2026-10-28: 36
- 2026-10-27: 36
- 2026-10-26: 36
- 2026-10-25: 36
- 2026-10-24: 36
- 2026-10-23: 36

## Common questions

### What is the TurboSteed MCP server?

TurboSteed MCP is listed in the public MCP registry as io.github.vivek-turbosteed/turbosteed-cli. Exposes TurboSteed web-hosting, site generation, and library features to AI coding agents. This page covers its npm package (@turbosteed/cli).

### Is the TurboSteed MCP server safe to use?

TurboSteed MCP scores 36 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. It declares no install or post-install scripts. 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.

### Is the TurboSteed MCP server still maintained?

TurboSteed MCP is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the TurboSteed MCP server?

VerifyMCP ran 8 checks on TurboSteed MCP, covering Malware scan, Known CVEs, Install scripts, Dependency health and 4 more. 6 items could not be completed, a gap on our side rather than a finding about TurboSteed MCP: License, Schema quality, Stability, Tool coverage and 2 more. 5 categories score 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- npm package: https://www.npmjs.com/package/@turbosteed/cli
- Socket report: https://socket.dev/npm/package/@turbosteed/cli
- Repository: https://github.com/Turbosteed/turbosteed-cli
- Website: https://turbosteed.com/
- Changelog RSS feed: https://verifymcp.io/servers/vivek-turbosteed-turbosteed-cli/turbosteed-cli.xml
- Changelog JSON feed: https://verifymcp.io/servers/vivek-turbosteed-turbosteed-cli/turbosteed-cli/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/vivek-turbosteed-turbosteed-cli/turbosteed-cli.json
- HTML version of this page: https://verifymcp.io/servers/vivek-turbosteed-turbosteed-cli/turbosteed-cli
