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/spranab/swarmcode/agent-bridgegit clone --depth 1 https://github.com/spranab/swarmcodeGrade A, and why
agent-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 yesterday.
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
{
"agent-bridge": {
"command": "npx",
"args": [
"-y",
"mcp-agent-bridge",
"channel"
],
"env": {
"AGENT_BRIDGE_REDIS_URL": "redis://192.168.4.161:30379",
"AGENT_BRIDGE_WORKSPACE_ID": "agent-bridge-dev"
}
}
}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.
- yesterday First seen · 14 lines scan A fae871e6f24c
agent-bridge is an MCP server published in the GitHub repository spranab/swarmcode (8 stars, last pushed 13d 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
raxol
MCP server "raxol" as configured in DROOdotFOO/raxol. Launched with mix mcp.server. Needs 1 environment variable to run.
semahash
Content-addressed semantics for multi-agent coordination. When the hash is the word. Runs locally from the semahash Python package.
komnet
Lets AI coding agents coordinate asynchronously through a private git repository. No server. Runs locally from the komnet npm package.
komnet
MCP server "komnet" as configured in Komdosh/komnet. Launched with komnet mcp.
yaac
Messaging between concurrent AI coding sessions, across clients, over MCP. Zero infrastructure. (YAAC: Yet Another Agentic Chat.). Runs locally from the yet-another-agentic-chat Python package.
yet-another-agentic-chat
Messaging between concurrent AI coding sessions, across clients, over MCP. Zero infrastructure. (YAAC: Yet Another Agentic Chat.). Runs locally from the yet-another-agentic-chat Python package.