F
Warning
5/100
10 days ago

Warning. Serious findings were identified. Review the full report before connecting. 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

akim-dev

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
🚨
Secret credentials may flow to a network call
1 flow detected: LOG_TOKENS. We can’t prove the destination matches the brand the credential belongs to.
🚨
Reads files from sensitive locations
Touches: /.dockerenv
🚨
Code appears obfuscated
2 files are unreadable to a human reviewer. Cannot audit what they do.
🔐
You'll be asked for 13 credentials: DOTENV_KEY, REPLICATE_API_TOKEN, ANTHROPIC_API_KEY, HF_TOKEN, HUGGINGFACE_API_KEY, OLLAMA_API_KEY, BASETEN_API_KEY, OPENAI_API_KEY, ACTIONS_ID_TOKEN_REQUEST_TOKEN, WEBHOOK_SECRET, LITELLM_CONFIG_BUCKET_OBJECT_KEY, UI_PASSWORD, OPENID_CLIENT_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.
🔐 secretDOTENV_KEY
configGITHUB_ACTIONS
configGRACEFUL_FS_PLATFORM
configLOG_STREAM
configLOG_TOKENS
configMAX_LOG_LENGTH
configPLAYWRIGHT_INPUT_FILE_TEXTBOX
configPLAYWRIGHT_SKIP_BROWSER_GC
configPLAYWRIGHT_SKIP_NAVIGATION_CHECK
configPROGRAMFILES
configPROGRAMFILES(X86)
configPWTEST_CLI_AUTO_EXIT_WHEN
configPWTEST_CLI_EXECUTABLE_PATH
configPWTEST_CLI_HEADLESS
configPWTEST_CLI_IS_UNDER_TEST
configPWTEST_SERVER_WS_HEADERS
configPW_CLI_DISPLAY_VERSION
configPW_DEBUG_CONTROLLER_HEADLESS
configPW_EXTENSION_MODE
configPW_LANG_NAME
configPW_LIVE_TRACE_STACKS
configPW_TEST_CDN_THAT_SHOULD_WORK
configPW_TEST_SCREENSHOT_NO_FONTS_READY
configSELENIUM_REMOTE_URL
configSYSTEMROOT
configTEST_GRACEFUL_FS_GLOBAL_PATCH
configTEST_INSPECTOR_LANGUAGE
configWS_NO_BUFFER_UTIL
configWS_NO_UTF_8_VALIDATE
configXDG_CACHE_HOME
config__IS_WSL_TEST__
🔐 secretREPLICATE_API_TOKEN
🔐 secretANTHROPIC_API_KEY
🔐 secretHF_TOKEN
🔐 secretHUGGINGFACE_API_KEY
configDATABRICKS_API_BASE
🔐 secretOLLAMA_API_KEY
🔐 secretBASETEN_API_KEY
configOPENAI_BASE_URL
configOPENAI_API_BASE
configOPENAI_ORGANIZATION
🔐 secretOPENAI_API_KEY
configACTIONS_ID_TOKEN_REQUEST_URL
🔐 secretACTIONS_ID_TOKEN_REQUEST_TOKEN
configAZURE_FEDERATED_TOKEN_FILE
configSPACE_ID
🔐 secretWEBHOOK_SECRET
configSPACE_HOST
configSERVER_ROOT_PATH
configDOCS_TITLE
configLITELLM_CONFIG_BUCKET_NAME
configDOCS_FILTERED
configPROXY_BASE_URL
configAZURE_KEY_VAULT_URI
🔐 secretLITELLM_CONFIG_BUCKET_OBJECT_KEY
configLITELLM_CONFIG_BUCKET_TYPE
configLITELLM_LICENSE
configWORKER_CONFIG
configLITELLM_DONT_SHOW_FEEDBACK_BOX
configLITELLM_LOG
configPROMETHEUS_URL
configUI_USERNAME
🔐 secretUI_PASSWORD
configPROXY_ADMIN_ID
configUI_LOGO_PATH
configSLACK_WEBHOOK_URL
configOPENID_BASE_URL
configOPENID_CLIENT_ID
🔐 secretOPENID_CLIENT_SECRET
Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.
deployDATABASE_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

2/2 tools missing one or more hints — mcp_server_tool_call (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); listmcptoolsrestapiresponseobject (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.

Tool handlers catch errors

Only 0/1 tool handlers wrap calls in try/catch (0%)

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.

No access to sensitive paths

Reads sensitive paths: /.dockerenv

Remove reads of sensitive system paths. If you genuinely need them, document why in the README.

No eval / new Function

5 eval() or new Function() calls — dynamic code execution

Replace eval / Function with explicit parsing or safer alternatives.

Shell command execution

29 child_process calls — runs shell commands

Prefer library functions over shell-outs. If you must shell out, ensure all inputs are properly escaped.

Readable source code

2 files appear obfuscated

Ship unminified, readable source.

Secrets stay with their owner

1 secret/sensitive value flow into network calls (LOG_TOKENS → dynamic)

Audit where credentials are sent. A NOTION_TOKEN should only reach api.notion.com — never a third-party host.

Secrets never reach shell commands

2 secret values passed to shell commands — possible command injection

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

Secrets not written to files

1 secret value 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 11 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 Verified](https://m8ven.ai/badge/mcp/akim-dev-krawel-1djqrf?variant=verified)](https://m8ven.ai/mcp/akim-dev-krawel-1djqrf)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: b2e6bcb1a887bc09f18ae0f56a278b4afe496605
code hash: cc1fe1a7309c9dc02e965227dae6cd4b13dda072af67cfc376256a957801bd2c
verified: 8/9/2026, 7:18:31 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