# io.github.selvatuple/revibe-mcp (npm · revibe-mcp)

Analyze any codebase — get architecture, file roles, execution flows, and agent context.

- Trust score: 70/100 (medium)
- Change this week: +24
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- npm · `revibe-mcp`: 70/100 (this document), [markdown](https://verifymcp.io/servers/selvatuple-revibe-mcp/revibe-mcp.md), [page](https://verifymcp.io/servers/selvatuple-revibe-mcp/revibe-mcp)

## Channel facts

- Registry: `npm`
- Package: `revibe-mcp`
- Version: `0.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-08-03.

- **Supply Chain Security**: 87/100
  - No malware found by supply-chain analysis.
  - Only part of the dependency tree could be resolved (95 of 99), so this covers what we could see, not the whole tree.
  - No install/post-install scripts declared.
  - Only part of the dependency tree could be resolved (95 of 99), so this covers what we could see, not the whole tree.
- **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 139 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 81/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 507 tokens (~84/item across 6 items; 6 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 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.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add selvatuple-revibe-mcp -- npx -y revibe-mcp
```

### Codex

```bash
codex mcp add selvatuple-revibe-mcp -- npx -y revibe-mcp
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add selvatuple-revibe-mcp --command npx --arg -y --arg revibe-mcp
```

### Hermes

```yaml
mcp_servers:
  selvatuple-revibe-mcp:
    command: "npx"
    args: ["-y", "revibe-mcp"]
```

### Other

```json
{
  "mcpServers": {
    "selvatuple-revibe-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "revibe-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-08-03 (score 70, +1)

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

### 2026-08-02 (score 69, +48)

- [security regression] Provenance: unverified → fail
- [security improvement] Install scripts: unverified → pass
- [security improvement] Known CVEs: unverified → partial
- [security improvement] Malware scan: unverified → pass
- [functional regression] Tool coverage: 100 → unverified
- [functional improvement] Schema quality: unverified → excellent
- [functional improvement] Dependency health: unverified → partial
- [functional improvement] Stability: unverified → 0.20
- [functional improvement] Maintenance: unverified → pass
- [functional improvement] MCP protocol: unverified → pass
- [functional improvement] License: unverified → pass
- [functional] First check of Schema quality: unverified
- [functional] Licence: MIT

### 2026-07-31 (score 21, −25)

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

### 2026-07-27 (score 46)

First indexed and scored.

## MCP tools (6)

### `revibe_login` (~47 tokens)

Log in to Revibe via browser. Opens a browser window for authentication. After logging in and clicking Authorize, the API key is saved locally so all other Revibe tools work automatically.

### `analyze_repo` (~110 tokens)

Submit a GitHub repository for Revibe analysis. Analyzes architecture, file roles, execution flows, system design Q&A, and more. If no URL is provided, auto-detects from the current git remote. Analysis takes 3-7 minutes for most repos.

Input parameters:

- `github_url` (string): GitHub repository URL (e.g. https://github.com/owner/repo). Auto-detected if empty.
- `reanalyze` (boolean): Force re-analysis even if already analyzed.

### `check_status` (~33 tokens)

Check the status of a Revibe analysis job.

Input parameters:

- `job_id` (string, required): The job ID returned from analyze_repo.

### `get_summary` (~49 tokens)

Get a condensed summary of a completed Revibe analysis. Shows architecture pattern, language, file count, key modules, and available sections.

Input parameters:

- `job_id` (string, required): The job ID from analyze_repo.

### `get_section` (~189 tokens)

Get a specific analysis section from a completed Revibe analysis.

Available sections:
\- technical_architecture (or "architecture") — system layers, technologies, diagrams
\- file_roles — what each file does, importance, dependencies
\- system_design_qa — interview-style Q&A about design decisions
\- story_flow (or "execution_flows") — how the app starts up and handles requests
\- database_schema (or "database") — tables, relationships, ER diagrams
\- concepts_explanation (or "concepts") — key patterns and concepts used
\- modules — logical groupings of files
\- business_logic — core domain logic and rules
\- flow_implementation — detailed execution flow code traces

Input parameters:

- `job_id` (string, required): The job ID from analyze_repo.
- `section` (string, required): Section name (e.g. "architecture", "file_roles", "system_design_qa").

### `get_agent_context` (~79 tokens)

Get the full agent context JSON for a completed analysis. This is a structured format optimized for AI agents, containing file index, dependency graph, architecture layers, call chains, constraints, design decisions, and database schema. Save the output to agent_context.json for persistent codebase understanding.

Input parameters:

- `job_id` (string, required): The job ID from analyze_repo.

## Diagnostics

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

## Score history

- 2026-08-03: 70
- 2026-08-02: 69
- 2026-08-01: 21
- 2026-07-31: 21
- 2026-07-30: 46
- 2026-07-28: 46
- 2026-07-27: 46

## Links

- npm package: https://www.npmjs.com/package/revibe-mcp
- Socket report: https://socket.dev/npm/package/revibe-mcp
- Repository: https://github.com/selvatuple/revibe-mcp
- Changelog RSS feed: https://verifymcp.io/servers/selvatuple-revibe-mcp/revibe-mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/selvatuple-revibe-mcp/revibe-mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/selvatuple-revibe-mcp/revibe-mcp