VibeDoctor
Server Details
Lets coding agents check their own code for leaked secrets, risky dependencies and AI-code mistakes
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 1 tool
With only one tool, there is no possibility of misselection or overlap. An agent cannot confuse vibedoctor_connect with anything else because nothing else exists.
The single name follows a clear snake_case pattern with a server prefix (vibedoctor_connect), which is readable and predictable. However, with only one tool there is no repeated pattern to demonstrate genuine consistency across the set.
A single tool is very thin for a server named VibeDoctor, which implies ongoing diagnostics, status, or health-check functionality. The surface is effectively one onboarding action, leaving the server barely scoped as a standalone integration.
The connect/registration step is covered, including idempotency and next steps, but there are no companion operations such as checking connection status, disconnecting, or retrieving doctor results. The lifecycle is a single dead-end call rather than a full surface.
Available Tools
1 toolvibedoctor_connectConnect to VibeDoctorAIdempotentInspect
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.
Inputs: repoUrl (required), server, gitEmail.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Checks AI-written code for leaked keys and made-up packages, on your machine. Never uploads code.
Scores your code across 12 areas, with findings, fix prompts, and re-assessment in your AI agent
Security reviews for coding agents: diffs checked against your org policy and live infrastructure.
Lints + auto-fixes how AI coding agents discover any new product. 24 rules, 6 tools, score 0-100.
Related MCP Servers
- AlicenseNot gradedqualityCmaintenanceEnables AI coding agents to scan projects or changed files for risky leftovers like hallucinated packages, exposed secrets, truncated code, and unfinished stubs, and to verify that packages exist before installing them.17 npmMIT
- AlicenseNot gradedqualityDmaintenanceLocal-first security check for AI coding agents — finds hardcoded secrets, exposed .env files, git-history leaks and vulnerable dependencies (OSV), entirely on your machine. Ask your agent "is this safe to ship?" and get a Launch Readiness score with a fix for every finding.MIT
- AlicenseNot gradedqualityCmaintenanceProvides security checks for AI agents, including secret scanning, CVE lookup, and dependency vulnerability scanning, all running locally except for CVE lookups.MIT
- AlicenseNot gradedqualityDmaintenanceEnables MCP-compatible AI agents to scan code for leaked secrets, copyleft licenses, unprotected routes, missing privacy policies, and risky card handling before committing or shipping.63 npmMIT
Glama MCP Gateway
Add one secure layer between your agents and this server.