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.
npx agentmods add mcp/rahuljava2807/claude-code-bridge-mcp/claude-bridge-mcpgit clone --depth 1 https://github.com/rahuljava2807/claude-code-bridge-mcpWrote 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/rahuljava2807/claude-code-bridge-mcp/claude-bridge-mcp)<a href="https://agentmods.dev/mcp/rahuljava2807/claude-code-bridge-mcp/claude-bridge-mcp"><img src="https://agentmods.dev/badge/mcp/rahuljava2807/claude-code-bridge-mcp/claude-bridge-mcp.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
claude-bridge-mcp 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 4d 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
{
"claude-bridge-mcp": {
"command": "npx",
"args": [
"-y",
"@rahulonramp2807/claude-bridge-mcp"
],
"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.
- 4d ago First seen · 10 lines scan A 8221e6efe23a
claude-bridge-mcp is an MCP server published in the GitHub repository rahuljava2807/claude-code-bridge-mcp (1 stars, last pushed 4mo 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
neon
Neon's hosted MCP server: lets the agent create and manage Neon Postgres projects, branches and databases and run SQL. Remote server at mcp.neon.tech.
iwe-knowledge
MCP server "iwe-knowledge", hosted remotely at mcp.aisystant.com, as configured in TserenTserenov/FMT-exocortex-template.
ext-railway
MCP server "ext-railway" as configured in TserenTserenov/FMT-exocortex-template. Launched with {{HOME_DIR}}/.secrets/mcp-railway.sh.
localkeep
Local memory banks you keep — a localhost Hub UI + MCP connector for Claude. You curate titled, dated memory banks on your machine; Claude recalls them via MCP. Runs locally from the localkeep Python package. Needs 2 environment variables to run.
picassoweb
PicassoWeb — MCP server that turns any website into a faithful replication kit: design tokens, real assets, animations, layout trees, section clones, screenshots, and pixel-diff verification. Runs locally from the picassoweb npm package.
github-triage-agent
MCP server "github-triage-agent" as configured in umeshmynampati3-cmd/github-triage-agent. Runs locally from the github-triage-agent Python package.