Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Vibe Doctor

REMOTE · VIBE-DOCTOR.ZEROONE.IT.KR

Check a deployed web app for security headers, SEO, accessibility and performance, with a grade.

+4 this week 74 Trust /100

Last scanned (9 hours ago)

Scores higher than 66% of remote servers

Reachable. Last reached 25 Oct 2026.

Category Testing and QA

Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Endpoint Security63
Transport & Reachability100
Schema Quality & AI Usability64
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 172 tokens (~57/item across 3 items; 3 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management83
  • Stability observed for 25 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 25 Oct 26 +1

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

  • 23 Oct 26 +1

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

  • 21 Oct 26 +1

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

  • 19 Oct 26 +1

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

  • 16 Oct 26 +1

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

  • 14 Oct 26 +1

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

  • 13 Oct 26 0
    • Server version: 3.3.1 → 3.3.2 functional
  • 12 Oct 26 +1
    • Server version: 3.3.0 → 3.3.1 functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 25 Oct 2026 · Probed https://vibe-doctor.zeroone.it.kr/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=vibe-doctor.zeroone.it.kr CN=YR2,O=Let's Encrypt,C=US 30 Sept 2026 29 Dec 2026 RSA 2048 SHA256-RSA 58dcd1f8456b8c25cfc84c1b9cd7056294f
SANs: vibe-doctor.zeroone.it.kr
CN=YR2,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA 4ebd24947e24d394802d84a52fd5b319
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of vibe-doctor.zeroone.it.kr. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
kr. present 64641 13 Verified
it.kr. present 56019 13 Verified
zeroone.it.kr. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=31536000; includeSubDomains
content-security-policy default-src 'self'; script-src 'self' 'unsafe-inline' https://challenges.cloudflare.com https://static.cloudflareinsights.com https://js.tosspayments.com https://www.googletagmanager.com; style-src 'self' 'unsafe-inline' https://cdn.jsdelivr.net; img-src 'self' data: blob: https://challenges.cloudflare.com https://www.googletagmanager.com https://*.google-analytics.com; font-src 'self' data: https://cdn.jsdelivr.net; connect-src 'self' https://challenges.cloudflare.com https://*.tosspayments.com https://www.googletagmanager.com https://*.google-analytics.com https://*.google.com; frame-src https://challenges.cloudflare.com https://*.tosspayments.com; object-src 'none'; base-uri 'self'; form-action 'self' https://*.tosspayments.com; frame-ancestors 'none'; upgrade-insecure-requests
x-content-type-options nosniff
x-frame-options DENY
referrer-policy no-referrer
permissions-policy camera=(), microphone=(), geolocation=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://vibe-doctor.zeroone.it.kr/mcp Verified 200
http (plaintext) http://vibe-doctor.zeroone.it.kr/mcp HTTPS enforced 308 https://vibe-doctor.zeroone.it.kr/mcp
MCP tools · 3 exposed · ~149 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
vibe_doctor_explain_finding ~56

검사에서 나온 항목 하나의 관찰 근거, 수정 방법, 재검증 방법과 공식 참고 링크를 설명합니다.

NameTypeReqDescription
itemIdstringyes–
scanIdstringyes–

No output schema declared.

No examples provided.

vibe_doctor_get_scan ~36

같은 MCP 세션에서 시작한 검사 결과와 관찰 한계를 조회합니다.

NameTypeReqDescription
scanIdstringyes–

No output schema declared.

No examples provided.

vibe_doctor_start_scan ~57

공개 HTTPS URL 한 개를 현재 무료 스캔 범위에서 검사합니다. 내부망·로그인·저장소는 검사하지 않습니다.

NameTypeReqDescription
requestIdstringyes–
urlstringyes–

No output schema declared.

No examples provided.

Install

How do I install the Vibe Doctor MCP server?

Vibe Doctor is a hosted endpoint at https://vibe-doctor.zeroone.it.kr/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.

remote · vibe-doctor.zeroone.it.kr

# add to Claude Code
claude mcp add --transport http kr-it-zeroone-vibe-doctor-vibe-doctor 'https://vibe-doctor.zeroone.it.kr/mcp'
Common questions

What is the Vibe Doctor MCP server?

Vibe Doctor is an MCP server listed in the public MCP registry as kr.it.zeroone.vibe-doctor/vibe-doctor. Check a deployed web app for security headers, SEO, accessibility and performance, with a grade. This page covers its hosted endpoint (https://vibe-doctor.zeroone.it.kr/mcp).

Is the Vibe Doctor MCP server safe to use?

Vibe Doctor scores 74 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 Vibe Doctor MCP server expose?

Vibe Doctor exposes 3 tools: vibe_doctor_start_scan, vibe_doctor_get_scan, vibe_doctor_explain_finding. Their descriptions and schemas cost roughly 149 tokens of context every time the server is loaded.

Does the Vibe Doctor MCP server require authentication?

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

Is the Vibe Doctor MCP server still maintained?

Vibe Doctor is still listed as active in the MCP registry. We last reached this channel on 25 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.