# Rivet (npm · @rivet-dev/mcp)

Manage Rivet Cloud namespaces and actors, run Code Mode, and open the Rivet Actor Inspector.

- Trust score: 64/100 (medium)
- Change this week: +5
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-26

## Components

- remote · `mcp.rivet.dev`: 36/100, [markdown](https://verifymcp.io/servers/dev-rivet-mcp/mcp.md), [page](https://verifymcp.io/servers/dev-rivet-mcp/mcp)
- npm · `@rivet-dev/mcp`: 64/100 (this document), [markdown](https://verifymcp.io/servers/dev-rivet-mcp/rivet-dev-mcp.md), [page](https://verifymcp.io/servers/dev-rivet-mcp/rivet-dev-mcp)

## Channel facts

- Registry: `npm`
- Package: `@rivet-dev/mcp`
- Version: `2.3.17`
- 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-09-26.

- **Supply Chain Security**: 94/100
  - No malware found by supply-chain analysis.
  - CVE check failed: a known low-severity CVE affects esbuild 0.27.7, a direct dependency. A fixed version is available.
  - No install/post-install scripts declared.
  - 127 of 317 dependencies flagged as unhealthy (1 deprecated).
- **Provenance & Transparency**: 6/100
  - Repository check failed: no source repository is declared.
  - Provenance check failed: no build-provenance attestation is published.
  - License check failed: the license (SEE LICENSE IN LICENSE) isn't a recognized OSI-approved license.
  - Actively maintained (last published 1 days ago).
  - Security-disclosure policy not yet verified: we couldn't inspect the source repository.
- **Schema Quality & AI Usability**: 77/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1085 tokens (~155/item across 7 items; 6 tools + 1 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 33/100
  - Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 90/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 69% of tool parameters carry a description.
- **Tool Safety**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 0 of 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "execute" implies "execute" and declares no destructiveHint at all, which the MCP spec reads as destructive by default.
  - An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.
  - Supports UI / widget rendering.

## Install

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

Rivet runs locally as an npm package, launched with npx -y @rivet-dev/mcp. 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 dev-rivet-mcp -- npx -y @rivet-dev/mcp
```

### Cursor

```json
{
  "mcpServers": {
    "dev-rivet-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@rivet-dev/mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "dev-rivet-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@rivet-dev/mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add dev-rivet-mcp -- npx -y @rivet-dev/mcp
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add dev-rivet-mcp --command npx --arg -y --arg @rivet-dev/mcp
```

### Hermes

```yaml
mcp_servers:
  dev-rivet-mcp:
    command: "npx"
    args: ["-y", "@rivet-dev/mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "dev-rivet-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@rivet-dev/mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add dev-rivet-mcp -t stdio -c npx -a -y @rivet-dev/mcp
```

### Other

```json
{
  "mcpServers": {
    "dev-rivet-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@rivet-dev/mcp"
      ]
    }
  }
}
```

## 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-09-26 (score 64, +1)

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

### 2026-09-25 (score 63, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-24 (score 63, +4)

- [functional improvement] Stability: unverified → 0.27

### 2026-09-16 (score 59)

First indexed and scored.

## MCP tools (6)

### `search` (~78 tokens)

Search the Rivet Cloud, Engine, actor, and inspector Code Mode API. Returns the call signature and a runnable example for each matching operation, to be pasted into the execute tool. Call this before execute whenever the exact argument shape is not already known. An empty query lists everything.

Input parameters:

- `limit` (integer)
- `query` (string)

### `execute` (~259 tokens)

Execute JavaScript in Secure Exec against the live Rivet namespace, using the `rivet` library bound as a global.
This is the tool that reads and mutates real Rivet state; the other tools only describe or embed it.
Top-level await is available. Return the final JSON-serializable result, or call globalThis.__return(value) from a nested scope.
Direct network, environment, and filesystem access are disabled, so `rivet` is the only way out.
Use the search tool to look up an operation signature instead of guessing it.

To find actors when no name is known yet:
  const { names } = await rivet.actors.names.list();
  return await rivet.actors.list({ filters: { name: names[0] } });

Name the organization, project, and namespace to act on. Levels the connection URL already pins are fixed and cannot be overridden; levels with a single option are filled in for you. Use target_list to discover the names.

Input parameters:

- `code` (string, required)
- `namespace` (string): Rivet namespace this call acts on
- `organization` (string): Rivet organization slug this call acts on
- `project` (string): Rivet project slug this call acts on

### `rivet.actor.inspect` (~345 tokens)

Resolve one Rivet Actor and return its id, name, key, status, region, and inspector capabilities, with an embedded Inspector on MCP Apps hosts. Read-only. To find an actor id first, use the execute tool with rivet.actors.names.list() and rivet.actors.list().
Name the organization, project, and namespace to act on. Levels the connection URL already pins are fixed and cannot be overridden; levels with a single option are filled in for you. Use target_list to discover the names.

Input parameters:

- `actor` (required): Selects exactly one actor. Must be an object, in one of three forms: 1. By id: { "actorId": "1knr9w8pjyaz6ntfubbfiwpmlacl00" } 2. An existing actor by name: { "name": "counter", "key": ["demo"] } 3.…
- `namespace` (string): Rivet namespace this call acts on
- `organization` (string): Rivet organization slug this call acts on
- `project` (string): Rivet project slug this call acts on

### `rivet.ui.actor.session.create` (~333 tokens)

Create a temporary single-actor Inspector proxy session for the embedded Inspector UI. Returns a short-lived token used by rivet.ui.actor.session.renew and revoke. Not needed to read actor data; use the execute tool for that.
Name the organization, project, and namespace to act on. Levels the connection URL already pins are fixed and cannot be overridden; levels with a single option are filled in for you. Use target_list to discover the names.

Input parameters:

- `actor` (required): Selects exactly one actor. Must be an object, in one of three forms: 1. By id: { "actorId": "1knr9w8pjyaz6ntfubbfiwpmlacl00" } 2. An existing actor by name: { "name": "counter", "key": ["demo"] } 3.…
- `namespace` (string): Rivet namespace this call acts on
- `organization` (string): Rivet organization slug this call acts on
- `project` (string): Rivet project slug this call acts on

### `rivet.ui.actor.session.renew` (~29 tokens)

Rotate and renew a temporary Inspector proxy session.

Input parameters:

- `token` (string, required)

### `rivet.ui.actor.session.revoke` (~28 tokens)

Revoke a temporary Inspector proxy session.

Input parameters:

- `token` (string, required)

## Diagnostics

Captured diagnostic sections: Provenance, Vulnerabilities, Dependencies. The full working is on the page: https://verifymcp.io/servers/dev-rivet-mcp/rivet-dev-mcp#diagnostics

## Score history

- 2026-09-26: 64
- 2026-09-25: 63
- 2026-09-24: 63
- 2026-09-23: 59
- 2026-09-22: 59
- 2026-09-21: 59
- 2026-09-20: 59
- 2026-09-19: 59
- 2026-09-18: 59
- 2026-09-17: 59
- 2026-09-16: 59

## Common questions

### What is the Rivet MCP server?

Rivet is an MCP server listed in the public MCP registry as dev.rivet/mcp. Manage Rivet Cloud namespaces and actors, run Code Mode, and open the Rivet Actor Inspector. This page covers its npm package (@rivet-dev/mcp).

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

Rivet scores 64 out of 100 on VerifyMCP. We recorded 2 known advisories against it as of 26 September 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.

### What tools does the Rivet MCP server expose?

Rivet exposes 6 tools: search, execute, rivet.actor.inspect, rivet.ui.actor.session.create, rivet.ui.actor.session.renew, rivet.ui.actor.session.revoke. Their descriptions and schemas cost roughly 1,072 tokens of context every time the server is loaded.

### Is the Rivet MCP server still maintained?

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

## Links

- npm package: https://www.npmjs.com/package/@rivet-dev/mcp
- Socket report: https://socket.dev/npm/package/@rivet-dev/mcp
- Website: https://rivet.dev/docs
- Changelog RSS feed: https://verifymcp.io/servers/dev-rivet-mcp/rivet-dev-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/dev-rivet-mcp/rivet-dev-mcp.json
- HTML version of this page: https://verifymcp.io/servers/dev-rivet-mcp/rivet-dev-mcp