vibecode-checker (Lex6won/vibecode-checker) is an MCP server listed on the M8ven Trust Index. It scores 74 out of 100, grade C. It declares 15 tools. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
C
Emerging
74/100
9 days ago

vibecode-checker

MCP server that enables AI coding tools to scan projects for security vulnerabilities, secret leaks, and compliance issues, generating Korean-language audit reports.

→ Lex6won/vibecode-checker· listed on glama

Emerging. No concerning findings. Grades remain capped until the project builds reputation through adoption. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we verified

Code Verified⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every pushwhy connect →

Who stands behind it

Lex6won

Source: Glama

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

⚡ Connect GitHub for Live Monitored

Install from

Glamanot scored here

The grade above is for the source repository. Registries can serve a different version, so we mark the ones we were not able to read.

// key findings
🚨
Secret credentials may flow to a network call
1 flow detected: NVD_API_KEY. We can’t prove the destination matches the brand the credential belongs to.
🔐
You'll be asked for 4 credentials: JWT_SECRET, GVSKB_REGISTRY_TOKEN, OPENAI_API_KEY, NVD_API_KEY
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// environment variables
To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.
🔐 secretJWT_SECRET
configGVSKB_RULES_DIR
configGVSKB_STRICT_RULES
configGVSKB_MODEGVSKB_MODE=offline 설정으로 외부 통신을 완전히 차단하고 동작합니다. 위협 정보(취약점·악성 패키지 목록)는 매일 자동 생성되는 반입 번들로 옮기며, sha256 해시로 변조를 검증합니다.
configGVSKB_CHECK_CONCURRENCY
configGVSKB_REGISTRY_URL
🔐 secretGVSKB_REGISTRY_TOKEN
configGVSKB_REGISTRY_TIMEOUT
configGVSKB_REGISTRY_SUBMIT
configGVSKB_REGISTRY_ALLOW_OFFLINE
configGVSKB_ENGINE_COMMIT
configGVSKB_AUDIT_DIR감사로그: 환경변수를 설정하면 스캔·차단·예외 승인·인텔 갱신 이력이 월별 JSONL로 기록됩니다. 원본 코드·개인정보는 저장하지 않고 해시와 마스킹된 증거만 남깁니다(기관 감사 증빙용, 기본 비활성).
configPYTHONIOENCODING
configPYTHONUTF8
configGVSKB_EXCEPTIONS_DIR
configGVSKB_VCPS_RULES
configGVSKB_POLICIES_DIR
configGVSKB_CONFIG_DIR
configGVSKB_ALLOW_PROPOSED
configGVSKB_SYNONYMS
🔐 secretOPENAI_API_KEY
configGVSKB_AUTO_UPDATE인터넷 PC: 별도 설정 없이 자동입니다. 서버 기동·검사 시점에 캐시 신선도를 확인하고 낡았으면 하루 1회 자동으로 받아옵니다(=off 로 끌 수 있음). 수동 갱신은 gvskb update-intel --all.
configGVSKB_AUTO_UPDATE_HOURS
configGVSKB_INTEL_DIR망분리 PC: [아래 절차](#망분리폐쇄망-환경에서-쓰기)대로 번들을 반입합니다. 관리자가 공유 폴더()에 번들을 놓아두면 각 PC가 자동 반영합니다.
configGVSKB_INTEL_URL
configGVSKB_INTEL_MAX_AGE_DAYS캐시가 기본 30일( 로 조정)을 넘으면 '이상 없음' 판정을 '판정 보류'로 낮춥니다 — 오래된 데이터가 최신처럼 보이지 않게 합니다.
configGVSKB_CACHE_DIR캐시 위치는 %USERPROFILE%\.gvskb\cache 입니다(환경변수 로 변경 가능).
configGVSKB_KEV_PROMOTE_SINCE_DAYS
configGVSKB_SEMGREP_RULES_DIR
configEPSS_DAYS
configGVSKB_EPSS_CACHE_MAX
🔐 secretNVD_API_KEY
configGVSKB_NVD_CACHE_MAX
configGVSKB_OSV_INCLUDE_NPM
// quality suggestions

Tool annotations

No tools have read-only/destructive annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

15/15 tools missing one or more hints — search_rules (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_rule (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); scan_code (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +12 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

No eval / new Function

2 eval() or new Function() calls — dynamic code execution

Replace eval / Function with explicit parsing or safer alternatives.

Shell command execution

1 call in production code run through a shell (eval_corpus/projects/b_express_api/server.js:19)

Prefer library functions over shell-outs. If you must shell out, ensure all inputs are properly escaped.

Secrets stay with their owner

1 secret sent to a request target we could not resolve (NVD_API_KEY → dynamic) — often a configured endpoint, not necessarily third-party

Audit where credentials are sent. A NOTION_TOKEN should only reach api.notion.com — never a third-party host.

Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.

// full audit trail
The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// improvement guidance — verified publishers only
We have 5 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Score](https://m8ven.ai/badge/mcp/lex6won/vibecode-checker)](https://m8ven.ai/mcp/lex6won/vibecode-checker)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 5e0137934aa9edc8a8226f727488349da09231c5
code hash: 0bdedc7e4a07b0230a34ce682d6ec07b82ea15609cb21b7d64e0991cfcf8ae62
verified: 9/2/2026, 8:02:19 PM
view raw JSON →
Check MCPs from inside your assistant
Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check
check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern
How to add it →Free · no account needed · works in any MCP client