sample-genai-on-eks-starter-kit (aws-samples/sample-genai-on-eks-starter-kit) is an MCP server listed on the M8ven Trust Index. It scores 89 out of 100, grade B. It declares 7 tools. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
B
Emerging
89/100
1 month ago

sample-genai-on-eks-starter-kit

A comprehensive toolkit for deploying production-ready Generative AI infrastructure on Amazon EKS. Includes pre-configured components for: 🚀 AI Gateway (LiteLLM) 🤖 LLM Serving (vLLM, SGLang, Ollama) 📊 Vector Databases, 🔍 Embedding Models (TEI) 📈 Observability (Langfuse, Phoenix) etc. Fast-track your GenAI deployment with Kubernetes

→ aws-samples/sample-genai-on-eks-starter-kit· listed on github_topic

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

aws-samples

Source: github_topic

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
✅
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 7 credentials: HF_TOKEN, LITELLM_API_KEY, LITELLM_UI_PASSWORD, MLFLOW_PASSWORD, OPENWEBUI_ADMIN_PASSWORD, PHOENIX_API_KEY, GATEWAY_MODEL_ACCESS_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.
configAWS_REGION
configDOMAIN? Enter value for :
configEKS_CLUSTER_NAME✔ Enter value for : genai-on-eks
configEKS_MODEEKS mode, auto (default) or standard
🔐 secretHF_TOKENHugging Face [user access token](https://huggingface.co/docs/hub/en/security-tokens)
🔐 secretLITELLM_API_KEY
🔐 secretLITELLM_UI_PASSWORD
configLITELLM_UI_USERNAME
🔐 secretMLFLOW_PASSWORD
configMLFLOW_USERNAME
configOPENWEBUI_ADMIN_EMAIL
🔐 secretOPENWEBUI_ADMIN_PASSWORD
🔐 secretPHOENIX_API_KEY
configPLATFORM
configREGION✔ Enter value for : us-west-2
🔐 secretGATEWAY_MODEL_ACCESS_KEY
configGATEWAY_URL
configMCP_ADDRESS_VALIDATOR
configMCP_EMPLOYMENT_VALIDATOR
configMCP_IMAGE_PROCESSOR
configS3_BUCKET_NAME
// 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

7/7 tools missing one or more hints — validate_address (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); perform_address_fraud_check (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); verify_address_ownership (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +4 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 handlers catch errors

Only 2/7 tool handlers wrap calls in try/catch (29%)

Wrap each tool handler body in try/catch and return a structured error response.

Tests exist

No test files found

Add tests that exercise each declared tool.

Secrets not written to files

11 secret values written to files

Avoid persisting secrets to disk. Keep them in memory or your secret manager.

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/aws-samples/sample-genai-on-eks-starter-kit)](https://m8ven.ai/mcp/aws-samples/sample-genai-on-eks-starter-kit)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 18c6bfbecf89ebb2fc38ea67a8c4118526737d46
code hash: ad25a5725b49bd0932de8f851d91a327a810fc192a956ca262e16bc40fa9e3c0
verified: 8/7/2026, 2:18:08 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