# VibeDoctor (remote · vibedoctor.io)

Lets coding agents check their own code for leaked secrets, risky dependencies and AI-code mistakes

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

## Components

- remote · `vibedoctor.io`: 75/100 (this document), [markdown](https://verifymcp.io/servers/io-vibedoctor-vibedoctor/vibedoctor.md), [page](https://verifymcp.io/servers/io-vibedoctor-vibedoctor/vibedoctor)

## Channel facts

- Endpoint: `https://vibedoctor.io/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, 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.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 64/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 307 tokens (~307/item across 1 items; 1 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 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 1 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

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

VibeDoctor is a hosted endpoint at https://vibedoctor.io/mcp, so there is nothing to install locally. 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 --transport http io-vibedoctor-vibedoctor 'https://vibedoctor.io/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "io-vibedoctor-vibedoctor": {
      "url": "https://vibedoctor.io/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "io-vibedoctor-vibedoctor": {
      "type": "http",
      "url": "https://vibedoctor.io/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.io-vibedoctor-vibedoctor]
url = "https://vibedoctor.io/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-vibedoctor-vibedoctor": {
      "type": "remote",
      "url": "https://vibedoctor.io/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add io-vibedoctor-vibedoctor --url 'https://vibedoctor.io/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  io-vibedoctor-vibedoctor:
    url: "https://vibedoctor.io/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "io-vibedoctor-vibedoctor": {
      "Transport": "http",
      "Url": "https://vibedoctor.io/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add io-vibedoctor-vibedoctor -t streamable-http -u 'https://vibedoctor.io/mcp'
```

### Other

```json
{
  "mcpServers": {
    "io-vibedoctor-vibedoctor": {
      "type": "http",
      "url": "https://vibedoctor.io/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## 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-16 (score 75, +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-10-14 (score 74, +1)

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

### 2026-10-12 (score 73, −1)

- [security] The server rewrote its instructions, which are the text every model session reads
- [functional regression] Schema quality: 250 → 307
- [functional] Schema quality: excellent → good
- [cosmetic] “vibedoctor_connect” added an optional parameter “server”

### 2026-10-10 (score 74, 0)

- [functional improvement] Stability: unverified → 0.03

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

First indexed and scored.

## MCP tools (1)

### `vibedoctor_connect` (~195 tokens)

Connect to VibeDoctor

Register this repository with VibeDoctor and get the command that connects this MCP server to it. Zero questions: BEFORE calling, run `git remote get-url origin` (pass it as repoUrl) and `git config user.email` (pass it as gitEmail). Returns a paste-ready re-point command, a GitHub connect link and next steps. Safe to call again: the same repo and email return the same project.

Input parameters:

- `gitEmail` (string): Output of `git config user.email`. Optional; a GitHub noreply address is fine.
- `repoUrl` (string, required): Output of `git remote get-url origin` (SSH or HTTPS form; GitHub only)
- `server` (string): The name your MCP client registered this server under. In Claude Code it is the <name> in mcp__<name>__vibedoctor_connect. Omit it if you cannot tell.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/io-vibedoctor-vibedoctor/vibedoctor#diagnostics

## Score history

- 2026-10-17: 75
- 2026-10-16: 75
- 2026-10-15: 74
- 2026-10-14: 74
- 2026-10-13: 73
- 2026-10-12: 73
- 2026-10-10: 74
- 2026-10-09: 74

## Common questions

### What is the VibeDoctor MCP server?

VibeDoctor is an MCP server listed in the public MCP registry as io.vibedoctor/vibedoctor. Lets coding agents check their own code for leaked secrets, risky dependencies and AI-code mistakes. This page covers its hosted endpoint (https://vibedoctor.io/mcp).

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

VibeDoctor scores 75 out of 100 on VerifyMCP. 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 VibeDoctor MCP server expose?

VibeDoctor exposes 1 tool: vibedoctor_connect. Their descriptions and schemas cost roughly 195 tokens of context every time the server is loaded.

### Does the VibeDoctor MCP server require authentication?

No. We connected to VibeDoctor without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the VibeDoctor MCP server still maintained?

VibeDoctor 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.

## Links

- Remote endpoint: https://vibedoctor.io/mcp
- Website: https://vibedoctor.io/
- Changelog RSS feed: https://verifymcp.io/servers/io-vibedoctor-vibedoctor/vibedoctor.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-vibedoctor-vibedoctor/vibedoctor.json
- HTML version of this page: https://verifymcp.io/servers/io-vibedoctor-vibedoctor/vibedoctor