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

C
Emerging
74/100

yeti-agent

Automate browser tasks with an AI agent that monitors, tests, and runs production websites

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

⚡ 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

hunkdl

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 →

Install from

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 11 credentials: OPENAI_API_KEY, ANTHROPIC_API_KEY, GOOGLE_API_KEY, DEEPSEEK_API_KEY, GROK_API_KEY, NOVITA_API_KEY, AZURE_OPENAI_KEY, MISTRAL_API_KEY, AZURE_OPENAI_API_KEY, CEREBRAS_API_KEY, BROWSER_USE_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.
configBROWSER_USE_LOGGING_LEVEL
configBROWSER_USE_SETUP_LOGGING
configMODEL_PROVIDER
configMODEL
configREGION
🔐 secretOPENAI_API_KEY
configBROWSER_USE_HOME
configBROWSER_USE_SESSION
configBROWSER_USE_CLOUD_SYNC
configANONYMIZED_TELEMETRY
configBROWSER_USE_CLOUD_API_URL
configBROWSER_USE_CLOUD_UI_URL
configXDG_CACHE_HOME
configXDG_CONFIG_HOME
configBROWSER_USE_CONFIG_DIR
🔐 secretANTHROPIC_API_KEY
🔐 secretGOOGLE_API_KEY
🔐 secretDEEPSEEK_API_KEY
🔐 secretGROK_API_KEY
🔐 secretNOVITA_API_KEY
configAZURE_OPENAI_ENDPOINT
🔐 secretAZURE_OPENAI_KEY
configSKIP_LLM_API_KEY_VERIFICATION
configDEFAULT_LLM
configIN_DOCKER
configIS_IN_EVALS
configBROWSER_USE_VERSION_CHECK
configWIN_FONT_DIR
configLMNR_LOGGING_LEVEL
configBROWSER_USE_VERBOSE_OBSERVABILITY
configLIBRARY_VERSION
configBROWSER_USE_DISABLE_EXTENSIONS
configBROWSER_USE_SCREENSHOT_FILE
🔐 secretMISTRAL_API_KEY
configMISTRAL_BASE_URL
🔐 secretAZURE_OPENAI_API_KEY
🔐 secretCEREBRAS_API_KEY
🔐 secretBROWSER_USE_API_KEY
configBROWSER_USE_CALCULATE_COST
configPLAYWRIGHT_BROWSERS_PATH
configAZURE_OPENAI_DEPLOYMENT
configBROWSER_USE_LLM_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

16/16 tools missing one or more hints — browser_navigate (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); browser_click (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); browser_type (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +13 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 test coverage

Only 0/16 tools referenced in tests (0%)

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

Secrets never reach shell commands

1 secret value passed to a subprocess as an argument — no shell is invoked, so there is nothing to inject into

Never pass secrets through shell commands. Use library APIs that accept credentials as arguments.

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 4 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/hunkdl/yeti-agent)](https://m8ven.ai/mcp/hunkdl/yeti-agent)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 3048c7cabd1cae9ebbf2545c69f5ac49d22fc334
code hash: 11fde1ab8c076859c752028c04c378ba1485415ea573b00d83f9fc5ced3e4a23
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