Skip to content
VibeDoctor logo

VibeDoctor MCP server

Which servers in the official MCP registry are VibeDoctor's own, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-21

← Back to VibeDoctor

Whose server it is
  • Registry nameio.vibedoctor/vibedoctorverified in the MCP registry

The registry name sits under vibedoctor.io. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-21
  • Stateanswerschecked 2026-10-21
  • Tools1
  • Server calls itselfvibedoctor
  • Server version1.0.0
  • Protocol version2025-06-18

On 2026-10-21 the server answered initialize and tools/list without a sign-in. First answer in 215 ms.

Should an agent connect itSkip it
  • Its tools do none of the product's use cases we checked: Check deployed sites for SEO and accessibility gaps; Review AI-written code before merging pull requests.
  • Checked on 6 of the 7 days it takes to judge reliability.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

Measured dailydaily checks: 6, the first on 2026-10-21
  • INITE MCP scoreafter a weeka score needs 7 daily checks: 6 so far
  • What an agent can do with it0 of 2 use cases
  • Answeredmeasuring6 of the 7 daily checks it takes to print a share
  • Median first answer699 ms
  • Space in an agent's context≈ 271 tokensthe definitions of all its tools (1), which an agent carries on every turn
  • Tool definitionsA · 100 of 100
  • Typed results0 of 1 toolsdeclared outputSchema: results come typed, read once
  • Every tool passes all six checks.

What an agent can do with it

  • not sure · Find committed API keys and secrets in source code
  • cannot · Check deployed sites for SEO and accessibility gaps
  • cannot · Review AI-written code before merging pull requests

Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?

Worth a look

None of the five warning signs in these definitions.

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (30%), doing the product's job (25%), definitions (20%), context (10%) and use (15%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

Tools it offers1 tools · read 2026-10-21
  • vibedoctor_connect

    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)…

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

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

Add it

Claude Code, in a terminal

claude mcp add --transport http vibedoctor https://vibedoctor.io/mcp

Add to CursorAdd to VS Code

claude.ai, ChatGPT and other clients: add https://vibedoctor.io/mcp as a custom connector in the settings.

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.