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/grizzly2005/bidirectional-bridge-claude-codexWrote 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/grizzly2005/bidirectional-bridge-claude-codex/bridge)<a href="https://agentmods.dev/mcp/grizzly2005/bidirectional-bridge-claude-codex/bridge"><img src="https://agentmods.dev/badge/mcp/grizzly2005/bidirectional-bridge-claude-codex/bridge.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
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 7d 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
{
"bridge": {
"type": "stdio",
"command": "node",
"args": [
"${CLAUDE_PROJECT_DIR:-.}/scripts/native-bridge-mcp.mjs",
"--caller",
"claude",
"--delegation",
"allow",
"--workspace",
"${CLAUDE_PROJECT_DIR:-.}"
],
"env": {}
}
}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.
- 7d ago First seen · 16 lines scan A 3bb14aa78844
bridge is an MCP server published in the GitHub repository grizzly2005/bidirectional-bridge-claude-codex (1 stars, last pushed 25d 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
dos-kernel
Dispatch Operating System — the domain-free trust substrate for fleets of autonomous agents (verdict spine, ship oracle, structured refusal, lane arbiter, correlation spine). Runs locally from the dos-kernel Python package. Needs 1 environment variable to run.
wiff
MCP server "wiff" as configured in xxxoooxoxo/wiff. Runs ./src/server.mjs with node.
wiff
Deterministic, resumable multi-agent workflows across Codex, Claude, Cursor, and Kimi. Runs locally from the @xxxoooxoxo/wiff npm package.
take-ur-turn
TUT (Take Ur Turn): multi coding-agent collaboration via a local Context Hub — append-only shared memory, derived task state, human approval gates. Runs locally from the take-ur-turn npm package.
forge-think
MCP server "forge-think" as configured in halflifezyf2680/forge-think. Runs /absolute/path/to/forge-think/server.py with python.
cascade-orchestrator
Cascade — agent task orchestration platform combining Leantime's strategic coherence with AgentRQ's agent orchestration. Runs locally from the cascade-orchestrator Python package.