# Jitters the VibeCoder (pypi · jitters-cli)

How wrecked is your monkey? Jitters' mood from the hours of your own git commits this week.

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

## Components

- pypi · `jitters-cli`: 65/100 (this document), [markdown](https://verifymcp.io/servers/lol-vibeoverflow-jitters/jitters-cli.md), [page](https://verifymcp.io/servers/lol-vibeoverflow-jitters/jitters-cli)

## Channel facts

- Registry: `pypi`
- Package: `jitters-cli`
- Version: `0.1.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-04.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - Runs setuptools.build_meta at install time, a recognised build step with no custom scripting around it.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 19/100
  - Repository check failed: no source repository is declared.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 10 days ago).
  - Security-disclosure policy not yet verified: we couldn't inspect the source repository.
- **Schema Quality & AI Usability**: 75/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 105 tokens (~105/item across 1 items; 1 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **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 1 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 1 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.

**Unverified: 1 category.** A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

## Install

### How do I install the Jitters the VibeCoder MCP server?

Jitters the VibeCoder runs locally as a PyPI package, launched with uvx jitters-cli. 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 lol-vibeoverflow-jitters -- uvx jitters-cli
```

### Cursor

```json
{
  "mcpServers": {
    "lol-vibeoverflow-jitters": {
      "command": "uvx",
      "args": [
        "jitters-cli"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "lol-vibeoverflow-jitters": {
      "command": "uvx",
      "args": [
        "jitters-cli"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add lol-vibeoverflow-jitters -- uvx jitters-cli
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "lol-vibeoverflow-jitters": {
      "type": "local",
      "command": [
        "uvx",
        "jitters-cli"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add lol-vibeoverflow-jitters --command uvx --arg jitters-cli
```

### Hermes

```yaml
mcp_servers:
  lol-vibeoverflow-jitters:
    command: "uvx"
    args: ["jitters-cli"]
```

### Netclaw

```json
{
  "McpServers": {
    "lol-vibeoverflow-jitters": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "jitters-cli"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add lol-vibeoverflow-jitters -t stdio -c uvx -a jitters-cli
```

### Other

```json
{
  "mcpServers": {
    "lol-vibeoverflow-jitters": {
      "command": "uvx",
      "args": [
        "jitters-cli"
      ]
    }
  }
}
```

## 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-04 (score 65, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-11-03 (score 50, −15)

- [security regression] Malware scan: pass → unverified

### 2026-10-30 (score 65, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-10-29 (score 50, −15)

- [security regression] Malware scan: pass → unverified

### 2026-10-28 (score 65, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-10-25 (score 50, −15)

- [security regression] Malware scan: pass → unverified

### 2026-10-22 (score 65, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-10-21 (score 50)

First indexed and scored.

## MCP tools (1)

### `jitters_week` (~105 tokens)

How wrecked is the coder's monkey? Reads only the hours of the user's own commits in the last 7 days of a local git folder and answers Jitters' mood (sofa, groggy, wired, fit, steady or sleepy) with a small drawing and a link.

Input parameters:

- `all` (boolean): Count every author, not only the local git user.
- `path` (string): The git folder to read; the server's working folder when left out.

## Diagnostics

Captured diagnostic sections: Provenance, Install scripts, Dependencies. The full working is on the page: https://verifymcp.io/servers/lol-vibeoverflow-jitters/jitters-cli#diagnostics

## Score history

- 2026-11-04: 65
- 2026-11-03: 50
- 2026-11-02: 65
- 2026-11-01: 65
- 2026-10-31: 65
- 2026-10-30: 65
- 2026-10-29: 50
- 2026-10-28: 65
- 2026-10-27: 50
- 2026-10-26: 50
- 2026-10-25: 50
- 2026-10-24: 65
- 2026-10-23: 65
- 2026-10-22: 65
- 2026-10-21: 50

## Common questions

### What is the Jitters the VibeCoder MCP server?

Jitters the VibeCoder is an MCP server listed in the public MCP registry as lol.vibeoverflow/jitters. How wrecked is your monkey? Jitters' mood from the hours of your own git commits this week. This page covers its PyPI package (jitters-cli).

### Is the Jitters the VibeCoder MCP server safe to use?

Jitters the VibeCoder scores 65 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 November 2026. 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 Jitters the VibeCoder MCP server expose?

Jitters the VibeCoder exposes 1 tool: jitters_week. Their descriptions and schemas cost roughly 105 tokens of context every time the server is loaded.

### Is the Jitters the VibeCoder MCP server still maintained?

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

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

## Links

- PyPI project: https://pypi.org/project/jitters-cli/
- Socket report: https://socket.dev/pypi/package/jitters-cli
- Website: https://vibeoverflow.lol/week?src=registry
- Changelog RSS feed: https://verifymcp.io/servers/lol-vibeoverflow-jitters/jitters-cli.xml
- Changelog JSON feed: https://verifymcp.io/servers/lol-vibeoverflow-jitters/jitters-cli.json
- HTML version of this page: https://verifymcp.io/servers/lol-vibeoverflow-jitters/jitters-cli