tk9v2 (thinhkhuat/tk9v2) is an MCP server listed on the M8ven Trust Index. M8ven has not graded it: we have no way to read this server ourselves. No publisher has claimed this listing.

C
Emerging
74/100
14 days ago

tk9v2

TK9 - upgraded to v2 - with sophisticated UI and much more

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

thinhkhuat

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 →

Install from

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

// key findings
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
🔐
You'll be asked for 10 credentials: SUPABASE_SERVICE_KEY, OPENAI_API_KEY, GOOGLE_API_KEY, ANTHROPIC_API_KEY, TAVILY_API_KEY, BRAVE_API_KEY, SUPABASE_ANON_KEY, GOOGLE_CSE_API_KEY, GOOGLE_CX_KEY, JWT_SECRET
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.
configPRIMARY_LLM_PROVIDER
configPRIMARY_LLM_MODEL
configPRIMARY_SEARCH_PROVIDER
configRESEARCH_LANGUAGE
configSUPABASE_URL
🔐 secretSUPABASE_SERVICE_KEY
configALLOWED_ORIGINS
🔐 secretOPENAI_API_KEY
🔐 secretGOOGLE_API_KEY
🔐 secretANTHROPIC_API_KEY
🔐 secretTAVILY_API_KEY
🔐 secretBRAVE_API_KEY
configLOG_LEVEL
configSTAGE
configAWS_REGION
configSERVICE_NAME
configRETRIEVER_ENDPOINT
configRETRIEVER
configGRPC_VERBOSITY
configGRPC_ENABLE_FORK_SUPPORT
configGRPC_PYTHON_LOG_LEVEL
🔐 secretSUPABASE_ANON_KEY
configTRANSLATION_TIMEOUT
configLLM_TEMPERATURE
configLLM_MAX_TOKENS
configSEARCH_MAX_RESULTS
configSEARCH_DEPTH
configFALLBACK_LLM_PROVIDER
configFALLBACK_LLM_TEMPERATURE
configFALLBACK_LLM_MAX_TOKENS
configFALLBACK_SEARCH_PROVIDER
configFALLBACK_SEARCH_MAX_RESULTS
configFALLBACK_SEARCH_DEPTH
configLLM_STRATEGY
configSEARCH_STRATEGY
configENABLE_CACHING
configCOST_TRACKING
configPROVIDER_TIMEOUT
configPROVIDER_MAX_RETRIES
🔐 secretGOOGLE_CSE_API_KEY
configGOOGLE_CSE_ID
🔐 secretGOOGLE_CX_KEY
configSEARCH_LANGUAGE
configSEARCH_COUNTRY
configBRAVE_UI_LANG
🔐 secretJWT_SECRET
configENVIRONMENT
configNO_COLOR
configFORCE_COLOR
configTERM
configTERM_PROGRAM
configSMART_LLM
configENABLE_JSON_OUTPUT
configAGENT_JSON_MIGRATION
Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.
deployREDIS_URL
// 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

3/3 tools missing one or more hints — deep_research (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); health_check (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); system_info (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint). 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.

License file

No license file

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

Tool test coverage

1/3 tools referenced in tests (33%)

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

Secrets not logged

5 secret values sent to console.log

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 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/thinhkhuat-tk9v2-m3duc5)](https://m8ven.ai/mcp/thinhkhuat-tk9v2-m3duc5)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: e6fd5c62b62ac675879602e36a4c0bfafc535c4b
code hash: 7a250a07caf7cab4a70ab5bc0eddac4f541f7ff0bbe67d80707eecd1abc2cc40
verified: 8/17/2026, 7:29:51 AM
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