CodexClaw (MackDing/CodexClaw) is an MCP server listed on the M8ven Trust Index. M8ven has not graded it yet. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
D
Caution
58/100

CodexClaw

Telegram bot for Claude Code and Codex CLI with MCP routing, multi-agent orchestration, cron jobs, and access controls.

→ MackDing/CodexClaw· listed on github_topic

Caution. Specific findings reduced this grade. They are listed on the page. 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

MackDing

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

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
⚠️
Known vulnerabilities in dependencies: 5 high
Affects packages this MCP installs at runtime. Upgrade or remove the affected dependency.
✅
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 1 credential: GITHUB_TOKEN
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// known CVEs in dependencies5 high8 low

Disclosed vulnerabilities in this server's declared npm dependencies (via OSV). Whether each is reachable depends on the installed versions.

highsimple-git@3.33.0GHSA-hffm-xvc3-vprc

simple-git is vulnerable to Remote Code Execution

highundici@7.24.5GHSA-4cwx-7wf7-3272

undici vulnerable to cross-user information disclosure and parse-time crash via degenerate private cache directives

highundici@7.24.5GHSA-hm92-r4w5-c3mj

undici vulnerable to cross-origin request routing via SOCKS5 proxy pool reuse

highundici@7.24.5GHSA-vmh5-mc38-953g

undici vulnerable to TLS certificate validation bypass via dropped requestTls in SOCKS5 ProxyAgent

highundici@7.24.5GHSA-vxpw-j846-p89q

undici WebSocket client vulnerable to denial of service via fragment count bypass

Depend on this server? Get alerted when its CVEs change.Watch this server free →
// 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.
configALLOWED_USER_IDSWhitelist-only access () is mandatory
configCODEX_ARGS
configCODEX_BACKENDOn =sdk, Telegram streams structured Codex SDK events and persists thread IDs per project
configCODEX_COMMANDCodex not producing output: verify CODEX_BACKEND, , and CODEX_WORKDIR
configCODEX_SDK_ADDITIONAL_DIRECTORIES
configCODEX_SDK_APPROVAL_POLICY
configCODEX_SDK_CONFIG
configCODEX_SDK_NETWORK_ACCESS_ENABLED
configCODEX_SDK_REASONING_EFFORT
configCODEX_SDK_SANDBOX_MODEIf is unset, the bot now defaults SDK threads to Full Access: danger-full-access with approvalPolicy=never. Set it explicitly to workspace-write or read-only only if you want a more restricted mode.
configCODEX_SDK_SKIP_GIT_REPO_CHECK
configCODEX_SDK_WEB_SEARCH_MODE
configCODEX_WORKDIRKeep scoped to a safe workspace root
configCRON_DAILY_SUMMARYDaily summary schedule: (default 0 9 )
configCRON_TIMEZONE
configE2E_TEST_COMMAND
configGITHUB_DEFAULT_BRANCH
configGITHUB_DEFAULT_WORKDIR
🔐 secretGITHUB_TOKENGitHub API failures: verify scope (repo) and account permissions
configMCP_SERVERS
configPROACTIVE_USER_IDSTarget users:
configSHELL_ALLOWED_COMMANDS
configSHELL_DANGEROUS_COMMANDSIf you allow write commands, mark high-risk prefixes in and require /sh --confirm ...
configSHELL_ENABLED
configSHELL_MAX_OUTPUT_CHARS
configSHELL_READ_ONLYKeep =true unless you have a strong reason to allow write commands
configSHELL_TIMEOUT_MS
configSTATE_FILERuntime state is persisted to , so /mcp enabledisable, /skill onoff, /language, /verbose, and per-project Codex conversation slots survive bot restarts
configSTREAM_BUFFER_CHARS
configSTREAM_THROTTLE_MSThrottle: controlled by (default 1200)
configTELEGRAM_API_BASETelegram API blocked: set TELEGRAM_PROXY_URL (HTTP proxy like http://127.0.0.1:7890) or run a local Bot API server and set
configTELEGRAM_PROXY_URLTelegram API blocked: set (HTTP proxy like http://127.0.0.1:7890) or run a local Bot API server and set TELEGRAM_API_BASE
configWORKSPACE_ROOT/repo - list switchable git projects under
// quality suggestions

Production dependencies are patched

0 critical, 5 high severity in production deps — simple-git@3.33.0 (high), undici@7.24.5 (high)

Run npm audit fix, or upgrade the affected packages to a non-vulnerable version.

Dependency freshness

1/12 production deps stale: lodash.throttle@2022-06-19 (4.2y)

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 1 concrete improvement 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/mackding/codexclaw?variant=verified)](https://m8ven.ai/mcp/mackding/codexclaw)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: b62ac154313d3d00a64d6f5851d9307088195ea2
code hash: 4480cad4d89b8218dc31e7a236f94507b19f8e12c82e10f5c362eb001b4aef95
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