Codex Bridge MCP (luojiateng/codex-bridge-mcp) is an MCP server listed on the M8ven Trust Index. It scores 74 out of 100, grade C. It declares 10 tools. No publisher has claimed this listing.

C
Caution
74/100

Codex Bridge MCP

Codex Bridge MCP is a local MCP orchestration service for a stable Claude Code x Codex CLI development workflow.

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

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

luojiateng

Source: Glama

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
⚠️
Known vulnerabilities in dependencies: 1 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.
🔐
You'll be asked for 1 credential: CODEX_BRIDGE_MCP_TOKEN
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// known CVEs in dependencies1 high1 low

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

highws@8.18.0GHSA-96hv-2xvq-fx4p

ws: Memory exhaustion DoS from tiny fragments and data chunks

ws: Uninitialized memory disclosure

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.
configCODEX_BRIDGE_ACP_ENGINES$env: = "kimi=kimi acp;gemini=gemini --experimental-acp"
configCODEX_BRIDGE_APP_SERVER_REQUEST_TIMEOUT_MS
configCODEX_BRIDGE_ATTENTION_HEARTBEAT_MS每次 npm run build 都会生成新的 Bridge build ID。stdio Adapter 发现端口上仍是旧 build 的 Core 时会明确报告 PID 和版本不兼容,不会静默复用旧代码或自动终止正在运行的任务;确认没有活跃任务后再重启该 Core。进度心跳默认每 15 秒发送一次,可用 调整。
configCODEX_BRIDGE_BUILD_ID_OVERRIDE
configCODEX_BRIDGE_CLAUDE_DEMO_PROJECT_ROOT
configCODEX_BRIDGE_CLAUDE_DEMO_TIMEOUT_MS
configCODEX_BRIDGE_CODEX_EFFORT
configCODEX_BRIDGE_CODEX_MODEL
configCODEX_BRIDGE_CODEX_SERVICE_TIER
configCODEX_BRIDGE_CODEX_SUMMARY
configCODEX_BRIDGE_CODEX_TUI_AUTO_RELAUNCH
configCODEX_BRIDGE_CODEX_TUI_MODE无可见 TUI 的引擎自动无窗口执行,不受 影响;
configCODEX_BRIDGE_CODEX_VERBOSITY
configCODEX_BRIDGE_CORE_START_TIMEOUT_MS
configCODEX_BRIDGE_DATA_DIR
configCODEX_BRIDGE_DB_PATH
configCODEX_BRIDGE_E2E_PROJECT_ROOT
configCODEX_BRIDGE_E2E_TIMEOUT_MS
configCODEX_BRIDGE_HTTP_HOST
configCODEX_BRIDGE_HTTP_PATH
configCODEX_BRIDGE_HTTP_PORT
configCODEX_BRIDGE_LOGS_DIR
🔐 secretCODEX_BRIDGE_MCP_TOKEN
configCODEX_BRIDGE_MCP_UPSTREAM_TIMEOUT_MS
configCODEX_BRIDGE_MCP_URL
configCODEX_BRIDGE_PORT_BASE
configCODEX_BRIDGE_PORT_SPAN
configCODEX_BRIDGE_RUNTIME_HOST_WINDOW
configCODEX_BRIDGE_RUNTIME_RECONNECT_TIMEOUT_MS
configCODEX_BRIDGE_RUNTIME_SCRIPTS_DIR
configCODEX_BRIDGE_RUNTIME_START_TIMEOUT_MS
configCODEX_BRIDGE_SHOW_CODEX_TUI
configCODEX_PERMISSION_PROFILE
// 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

10/10 tools missing one or more hints — task_open (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); task_send (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); task_await (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +7 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 inputs are validated

Only 0/10 tool handlers declare input schemas (0%)

Declare an inputSchema with zod/joi/yup on every tool definition.

Tool handlers catch errors

Only 3/10 tool handlers wrap calls in try/catch (30%)

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

License file

No license file

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

Tests exist

No test files found

Add tests that exercise each declared tool.

Shell command execution

5 child_process calls — runs shell commands

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

Production dependencies are patched

0 critical, 1 high severity in production deps — ws@8.18.0 (high), ws@8.18.0 (low)

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

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 8 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/luojiateng/codex-bridge-mcp?variant=verified)](https://m8ven.ai/mcp/luojiateng/codex-bridge-mcp)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: 29a53dc3840242f2b876fbe3c40ce0168bee38b7
code hash: 6b6420cbbf89c1bc4cf18ff64812d77dd35d70478469e22423aaf830db4d966b
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