mimi-seed-sdk (jeonghwanko/mimi-seed-sdk) is an MCP server listed on the M8ven Trust Index. It scores 74 out of 100, grade C. It declares 234 tools. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
C
Emerging
74/100

mimi-seed-sdk

Release Doctor: check Expo, React Native and Unity release risks before connecting app stores. CLI + MCP for Claude Code and Codex.

→ jeonghwanko/mimi-seed-sdk· listed on github_repo_search

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

jeonghwanko

Source: github_repo_search

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

GitHub

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
✅
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
✅
Open source with a license and README
Anyone can audit the code, the license is declared, and the publisher documents what it does.
🔐
You'll be asked for 4 credentials: ANTHROPIC_API_KEY, MIMI_SEED_GOOGLE_CLIENT_SECRET, MIMI_SEED_TOKEN, PRESEED_GOOGLE_CLIENT_SECRET
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// known CVEs in dependencies1 low

Disclosed vulnerabilities in this server's declared npm dependencies (via OSV). Whether each is reachable depends on the installed versions.

lowvitest@4.1.10GHSA-82fw-gwwq-j7x9

Vitest: Path Traversal / Arbitrary File Read via @vitest/mocker Redirect Mock

Depend on this server? Get alerted when its CVEs change.Watch this server free →
// 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.
🔐 secretANTHROPIC_API_KEY## AI 릴리즈 노트 생성 ( 필요)
configMIMI_SEED_FFMPEG_PATHFFmpeg/ffprobe가 PATH에 없을 때 실행 파일 경로 (선택)
configMIMI_SEED_FFPROBE_PATHFFmpeg/ffprobe가 PATH에 없을 때 실행 파일 경로 (선택)
configMIMI_SEED_GOOGLE_CLIENT_ID
🔐 secretMIMI_SEED_GOOGLE_CLIENT_SECRET
configMIMI_SEED_LANG
🔐 secretMIMI_SEED_TOKEN
configMIMI_SEED_WEB_BASE
configPRESEED_GOOGLE_CLIENT_ID환경변수 / PRESEED_GOOGLE_CLIENT_SECRET 계속 인식
🔐 secretPRESEED_GOOGLE_CLIENT_SECRET환경변수 PRESEED_GOOGLE_CLIENT_ID / 계속 인식
// 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

234/234 tools missing one or more hints — admob_list_accounts (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); admob_list_apps (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); admob_list_ad_units (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +231 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.

Tool inputs are validated

225/234 tool handlers declare input schemas (96%)

Declare an inputSchema with zod/joi/yup on every tool definition.

Tool test coverage

Only 8/234 tools referenced in tests (3%)

Write tests that reference each tool by name so every tool has at least one test.

Domain consistency

npm scope @yoonion doesn't match GitHub owner jeonghwanko

Use the same org name across GitHub, npm, and your homepage so users can verify the publisher.

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/jeonghwanko/mimi-seed-sdk)](https://m8ven.ai/mcp/jeonghwanko/mimi-seed-sdk)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: e281fa9521494fd3923e6c09dd52c41f03c2f3e1
code hash: e11acd7ad1c864b843b6c79f08e1aae5517401f45f106d417eb817be750d99a9
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