# Anti-Vibe (npm · anti-vibe-mcp)

Read coding-agent output one sentence at a time, skim it by heading, or speed-read it.

- Trust score: 67/100 (medium)
- Change this week: +44
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-17

## Components

- npm · `anti-vibe-mcp`: 67/100 (this document), [markdown](https://verifymcp.io/servers/hellstellar-anti-vibe/anti-vibe-mcp.md), [page](https://verifymcp.io/servers/hellstellar-anti-vibe/anti-vibe-mcp)

## Channel facts

- Registry: `npm`
- Package: `anti-vibe-mcp`
- Version: `0.4.7`
- 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-10-17.

- **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.
  - 60 of 159 dependencies flagged as unhealthy.
- **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 8 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 66/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 881 tokens (~293/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**: 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.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "rsvpify_markdown" implies "send" and declares no destructiveHint at all, which the MCP spec reads as destructive by default.
  - An AI judge read all 3 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 Anti-Vibe MCP server?

Anti-Vibe runs locally as an npm package, launched with npx -y anti-vibe-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 hellstellar-anti-vibe -- npx -y anti-vibe-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "hellstellar-anti-vibe": {
      "command": "npx",
      "args": [
        "-y",
        "anti-vibe-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "hellstellar-anti-vibe": {
      "command": "npx",
      "args": [
        "-y",
        "anti-vibe-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add hellstellar-anti-vibe -- npx -y anti-vibe-mcp
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add hellstellar-anti-vibe --command npx --arg -y --arg anti-vibe-mcp
```

### Hermes

```yaml
mcp_servers:
  hellstellar-anti-vibe:
    command: "npx"
    args: ["-y", "anti-vibe-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "hellstellar-anti-vibe": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "anti-vibe-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add hellstellar-anti-vibe -t stdio -c npx -a -y anti-vibe-mcp
```

### Other

```json
{
  "mcpServers": {
    "hellstellar-anti-vibe": {
      "command": "npx",
      "args": [
        "-y",
        "anti-vibe-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-10-14 (score 67, +29)

- [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 Schema quality: excellent
- [functional] First check of Schema quality: fail
- [functional] First check of Destructive annotations: 0
- [functional] First check of Tool coverage: 100
- [functional] First check of Tool coverage: 100

### 2026-10-13 (score 38, 0)

- [functional regression] Security disclosure: unverified → fail

### 2026-10-12 (score 38, +15)

- [security improvement] Malware scan: unverified → pass
- [security improvement] Known CVEs: partial → pass
- [functional regression] Security disclosure: fail → unverified
- [functional] Dependency health: partial → 0.80

### 2026-10-09 (score 23)

First indexed and scored.

## MCP tools (3)

### `review_markdown` (~263 tokens)

Send markdown to Anti-Vibe for review

Send markdown to the Anti-Vibe reader so a human can review it without fatigue, moving heading-by-heading and optionally speed-reading each section. Provide your output as well-structured Markdown — use `#`/`##`/`###` headings to break it into sections (Anti-Vibe navigates by heading), plus normal Markdown for lists, tables, code blocks and emphasis. Pass the full content in `markdown`. For CODE REVIEW / diff content: one `###` heading per file, and NEVER paste a whole file or diff as a single fenced block — each fenced block is one atomic step in the reader, so an oversized block becomes an unreviewable wall. Split code into small fenced blocks (one function or one logical hunk, ~15 lines each) and precede each block with one line of prose saying WHY that piece exists. This applies doubly to NEW files: present them one function/section at a time, never verbatim top-to-bottom. Opens the Anti-Vibe tab on first use and live-updates it on later calls.

Input parameters:

- `markdown` (string, required): The full document as Markdown, ideally with #/## headings.
- `title` (string): Optional title; used as an H1 if the markdown has none.

Output parameters:

- `documentId` (string)
- `sectionCount` (number)
- `url` (string)
- `wordCount` (number)

### `rsvpify_markdown` (~287 tokens)

Rewrite agent output as RSVP prose and send to Anti-Vibe

Send an agent response to the Anti-Vibe reader OPTIMIZED for RSVP speed-reading, where one word is flashed at a time. Because raw agent output reads badly word-by-word, YOU must rewrite the content before passing it in `markdown`: (1) Rephrase into flowing, natural prose — full sentences, minimal symbols, no bullet fragments or telegraphic notes; write it as if it were read aloud. (2) Replace every code block with a short PROSE SUMMARY of what the code does (e.g. "A function that validates the token expiry using a strict less-than check."). Do not paste raw code into the prose — summarize it. (3) Keep `#`/`##` headings as the section spine. (4) When a TABLE or other structured element is essential to keep verbatim, include it as a normal Markdown table/code block — Anti-Vibe renders these as atomic blocks and AUTO-PAUSES the RSVP stream on them so the reader stops and studies them, then resumes. Use this tool for content a human will speed-read; use `review_markdown` to preserve the original code and structure verbatim.

Input parameters:

- `markdown` (string, required): Your rewritten prose: natural sentences, code replaced by summaries, tables kept verbatim.
- `title` (string): Optional title; used as an H1 if the prose has none.

Output parameters:

- `documentId` (string)
- `sectionCount` (number)
- `url` (string)
- `wordCount` (number)

### `review_flow` (~331 tokens)

Send a flow-ordered code review to Anti-Vibe

Push a FLOW-ORDERED code review to Anti-Vibe: the human walks the change in runtime execution order (like a sequence diagram), not file-by-file. Send ONLY the traversal STRUCTURE — never the diff text. Anti-Vibe resolves each hunk by running `git diff` in the repo and matching your locators. Order `flow` stops top→bottom in call order (entry → handler → service → effect); put models/schemas/contracts/types in `foundation` and list them bottom→up. Each stop maps to a FILE — the reviewer steps through all of that file's hunks one at a time. `locator` is an OPTIONAL hint (exact `hunkHeader` "@@ -a,b +c,d @@ ..." or `lineRange`) that just sets the match-confidence badge. Give each stop a one-line summary. For unchanged connective steps (a dispatcher/existing handler the flow passes through), add a stop with `context: true` and no locator so the sequence reads continuously. When a stop's file has several hunks, add `hunkFlow` to order them for reading in execution order (behavior change before plumbing) with a one-line note per hunk.

Input parameters:

- `diffBase` (string): git diff base, e.g. "HEAD~1" or "main...HEAD" (default: working tree).
- `repoPath` (string): Repo to run git diff in (defaults to ANTIVIBE_REPO_DIR or cwd).
- `stops` (array, required): Ordered traversal of the review.
- `title` (string): Title for the review.

Output parameters:

- `documentId` (string)
- `resolvedCount` (number)
- `stopCount` (number)
- `url` (string)

## Diagnostics

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

## Score history

- 2026-10-17: 67
- 2026-10-16: 67
- 2026-10-15: 67
- 2026-10-14: 67
- 2026-10-13: 38
- 2026-10-12: 38
- 2026-10-09: 23

## Common questions

### What is the Anti-Vibe MCP server?

Anti-Vibe is an MCP server listed in the public MCP registry as io.github.Hellstellar/anti-vibe. Read coding-agent output one sentence at a time, skim it by heading, or speed-read it. This page covers its npm package (anti-vibe-mcp).

### Is the Anti-Vibe MCP server safe to use?

Anti-Vibe scores 67 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 17 October 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 Anti-Vibe MCP server expose?

Anti-Vibe exposes 3 tools: review_markdown, rsvpify_markdown, review_flow. Their descriptions and schemas cost roughly 881 tokens of context every time the server is loaded.

### Is the Anti-Vibe MCP server still maintained?

Anti-Vibe is still listed as active in the MCP registry. We last reached this channel on 17 October 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 Anti-Vibe MCP server under?

Anti-Vibe 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

- npm package: https://www.npmjs.com/package/anti-vibe-mcp
- Socket report: https://socket.dev/npm/package/anti-vibe-mcp
- Repository: https://github.com/Hellstellar/anti-vibe
- Website: https://anti-vibe.pages.dev/
- Changelog RSS feed: https://verifymcp.io/servers/hellstellar-anti-vibe/anti-vibe-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/hellstellar-anti-vibe/anti-vibe-mcp.json
- HTML version of this page: https://verifymcp.io/servers/hellstellar-anti-vibe/anti-vibe-mcp