Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/ndcorder/claude-codex-teamWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/ndcorder/claude-codex-team/codex-bridge)<a href="https://agentmods.dev/mcp/ndcorder/claude-codex-team/codex-bridge"><img src="https://agentmods.dev/badge/mcp/ndcorder/claude-codex-team/codex-bridge/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/mcp/ndcorder/claude-codex-team/codex-bridge"><img src="https://agentmods.dev/badge/mcp/ndcorder/claude-codex-team/codex-bridge.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
codex-bridge scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{ "codex-bridge": { "command": "npx", "args": [ "-y", "@ndcorder/codex-bridge" ] } }
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 1mo ago First seen · 9 lines scan A e7771f1d8ad9
codex-bridge is an MCP server published in the GitHub repository ndcorder/claude-codex-team (2 stars, last pushed 5mo ago), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other mcp servers, from other repositories
brutalist
Deploy Claude Code, Codex & Antigravity (agy) CLI agents to demolish your work before users do. Real file analysis. Brutal honesty. Per-call model pinning, conversation continuation & intelligent pagination. Runs locally from the @brutalist/mcp npm package.
mcp-devils-advocate
MCP server "mcp-devils-advocate" as configured in AleBrito124356/mcp-devils-advocate. Runs locally from the mcp-devils-advocate Python package. Needs 1 environment variable to run.
code-security-mcp
A security MCP server for AI coding agents: each language via its native analyzer — Kotlin (detekt), Java (SpotBugs+FindSecBugs), Python (Bandit), C# (Roslyn), JS/TS (ESLint) — plus diff review and secure patterns. Runs locally from the code-security-mcp Python package.
codereview
Risk-scan a diff, flag AI-generated-code tells, find secrets. 5 of 7 tools need no account. Remote server at mcp.moltlinestudio.com.
code-reviewer-ai-mcp
Code Reviewer Ai MCP server. Tools: review code, check security, suggest improvements. Built by MEOK AI Labs. Runs locally from the code-reviewer-ai-mcp Python package.
src-mcp
MCP server for semantic code search and codebase analysis — Treesitter parsing, AST extraction, and embedding-based indexing for any LLM that supports MCP. Runs locally from the src-mcp npm package.