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

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

tutorial-genai

→ lovehyun/tutorial-genai· listed on github_code

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

lovehyun

Source: github_code

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

M8ven verifies MCPs across every public registry — install directly from whichever one you prefer.

// key findings
🚨
Secret credentials may flow to a network call
3 flows detected: OPENAI_API_KEY. We can’t prove the destination matches the brand the credential belongs to.
🔐
You'll be asked for 7 credentials: OPENAI_API_KEY, MYSQL_PASSWORD, MCP_API_TOKEN, SECRET_KEY, FLASK_SECRET, ANTHROPIC_API_KEY, SERPER_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.
configFLASK_API_URL
🔐 secretOPENAI_API_KEY
configDB_TYPE
configSQL_MAX_ROWS
configSQLITE_PATH
configPGHOST
configPGPORT
configPGUSER
configPGPASSWORD
configPGDATABASE
configMYSQL_HOST
configMYSQL_PORT
configMYSQL_USER
🔐 secretMYSQL_PASSWORD
configMYSQL_DATABASE
🔐 secretMCP_API_TOKEN
configPGSSLMODE
🔐 secretSECRET_KEY
configFLASK_DEBUG
configFLASK_PORT
configFLASK_HOST
configUSE_LOG_SAMPLE
configLOG_SAMPLE_PATH
🔐 secretFLASK_SECRET
configHEALTH_POLL_SEC
configPROBE_TIMEOUT
configLOG_LEVEL
configGRADING_RESULT_FILE
configAPP_BASE_URL
configUSD_RATE_THRESHOLD
configWATCH_TICKER
configSTOCK_BUY_BELOW
configSCAN_ROOT
configENV_PATH
configINDEX_DB
🔐 secretANTHROPIC_API_KEY
🔐 secretSERPER_API_KEY
Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.
deployPORT
deployDATABASE_URL
deployCLIENT_DSN
// 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

204/204 tools missing one or more hints — search (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); answer (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); resolve_library_id (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +201 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

196/197 tool handlers declare input schemas (99%)

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

License file

No license file

Add a LICENSE file (MIT, Apache-2.0, etc.).

Tool test coverage

Only 8/204 tools referenced in tests (4%)

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

Secrets stay with their owner

3 secrets sent to a request target we could not resolve (OPENAI_API_KEY → dynamic, OPENAI_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.

Secrets not logged

10 secret values sent to log/print

Redact or omit secret values from log output.

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 7 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/lovehyun/tutorial-genai)](https://m8ven.ai/mcp/lovehyun/tutorial-genai)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 29bde5769f92f0b1780c6ed8fca1c266981a17f6
code hash: 034af093c9c3f328bc1f8f43376d2d853933362c56744410c2a0a2d7a9449009
verified: 9/1/2026, 6:41:38 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