# Jotbus (npm · jotbus)

End-to-end encrypted scratchpad for coding agents across machines, vendors and people.

- Trust score: 79/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- npm · `jotbus`: 79/100 (this document), [markdown](https://verifymcp.io/servers/com-jotbus-jotbus/jotbus.md), [page](https://verifymcp.io/servers/com-jotbus-jotbus/jotbus)

## Channel facts

- Registry: `npm`
- Package: `jotbus`
- Version: `0.11.0`
- 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-05.

- **Supply Chain Security**: 100/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.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 27 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 68/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 439 tokens (~146/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 73/100
  - Stability observed for 22 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 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.

## Install

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

Jotbus runs locally as an npm package, launched with npx -y jotbus. 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 com-jotbus-jotbus -- npx -y jotbus
```

### Cursor

```json
{
  "mcpServers": {
    "com-jotbus-jotbus": {
      "command": "npx",
      "args": [
        "-y",
        "jotbus"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-jotbus-jotbus": {
      "command": "npx",
      "args": [
        "-y",
        "jotbus"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add com-jotbus-jotbus -- npx -y jotbus
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add com-jotbus-jotbus --command npx --arg -y --arg jotbus
```

### Hermes

```yaml
mcp_servers:
  com-jotbus-jotbus:
    command: "npx"
    args: ["-y", "jotbus"]
```

### Netclaw

```json
{
  "McpServers": {
    "com-jotbus-jotbus": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "jotbus"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-jotbus-jotbus -t stdio -c npx -a -y jotbus
```

### Other

```json
{
  "mcpServers": {
    "com-jotbus-jotbus": {
      "command": "npx",
      "args": [
        "-y",
        "jotbus"
      ]
    }
  }
}
```

## 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-03 (score 79, +1)

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

### 2026-11-01 (score 78, +1)

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

### 2026-10-30 (score 77, +1)

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

### 2026-10-28 (score 76, +1)

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

### 2026-10-26 (score 75, +1)

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

### 2026-10-24 (score 74, +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-10-22 (score 73, +4)

- [functional improvement] Stability: unverified → 0.27

### 2026-10-14 (score 69, +30)

- [security improvement] Injection markers: unverified → pass
- [security] First check of Judged manipulation: pass
- [security] Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window).
- [functional improvement] Tool coverage: unverified → 100
- [functional improvement] MCP protocol: unverified → pass
- [functional] First check of Schema quality: fail
- [functional] First check of Destructive annotations: pass
- [functional] First check of Schema quality: fail
- [functional] First check of Schema quality: good
- [functional] First check of Tool coverage: 100

## MCP tools (3)

### `list_workspaces` (~78 tokens)

List the Jotbus workspaces connected on this machine. No Jotbus workspaces are connected on this machine yet. Create one with create_workspace, or ask the user to run `npx jotbus` (new temporary workspace) or `npx jotbus join <invite>` in a terminal; it becomes available here right away.

### `jotbus_help` (~21 tokens)

How Jotbus works and how to connect a workspace.

### `create_workspace` (~183 tokens)

Create a new Jotbus workspace and connect it on this machine. Use this when the user asks you to start, create or make a Jotbus workspace (then pass its name as `workspace` to write_workspace). If this machine is signed in to a Jotbus account (npx jotbus login), it is persistent on that account; otherwise, or with persistent: false, it is a free temporary workspace that lasts 60 minutes. Returns its name and how to share it.

Input parameters:

- `description` (string): Optional description (persistent workspaces).
- `name` (string): Optional name (lowercase letters, digits, ".", "_", "-"). Persistent workspaces only; random otherwise.
- `persistent` (boolean): Default: true when this machine is signed in, false otherwise. Persistent workspaces need `npx jotbus login` and a subscription.

## Diagnostics

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

## Score history

- 2026-11-05: 79
- 2026-11-04: 79
- 2026-11-03: 79
- 2026-11-02: 78
- 2026-11-01: 78
- 2026-10-31: 77
- 2026-10-30: 77
- 2026-10-29: 76
- 2026-10-28: 76
- 2026-10-27: 75
- 2026-10-26: 75
- 2026-10-25: 74
- 2026-10-24: 74
- 2026-10-23: 73
- 2026-10-22: 73
- 2026-10-21: 69
- 2026-10-20: 69
- 2026-10-19: 69
- 2026-10-18: 69
- 2026-10-17: 69
- 2026-10-16: 69
- 2026-10-15: 69
- 2026-10-14: 69
- 2026-10-13: 39
- 2026-10-12: 39
- 2026-10-11: 39

## Common questions

### What is the Jotbus MCP server?

Jotbus is an MCP server listed in the public MCP registry as com.jotbus/jotbus. End-to-end encrypted scratchpad for coding agents across machines, vendors and people. This page covers its npm package (jotbus).

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

Jotbus scores 79 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 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.

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

Jotbus exposes 3 tools: list_workspaces, jotbus_help, create_workspace. Their descriptions and schemas cost roughly 282 tokens of context every time the server is loaded.

### Is the Jotbus MCP server still maintained?

Jotbus is still listed as active in the MCP registry. We last reached this channel on 5 November 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 Jotbus MCP server under?

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

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

VerifyMCP ran 16 checks on Jotbus, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. 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/jotbus
- Socket report: https://socket.dev/npm/package/jotbus
- Repository: https://github.com/Launchable-AI-Inc/jotbus
- Website: https://jotbus.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-jotbus-jotbus/jotbus.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-jotbus-jotbus/jotbus/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-jotbus-jotbus/jotbus.json
- HTML version of this page: https://verifymcp.io/servers/com-jotbus-jotbus/jotbus