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/spranab/swarmcodeWrote 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/spranab/swarmcode/agent-bridge)<a href="https://agentmods.dev/mcp/spranab/swarmcode/agent-bridge"><img src="https://agentmods.dev/badge/mcp/spranab/swarmcode/agent-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/spranab/swarmcode/agent-bridge"><img src="https://agentmods.dev/badge/mcp/spranab/swarmcode/agent-bridge.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade 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 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
{
"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.
- 1mo ago First seen · 14 lines scan A fae871e6f24c
agent-bridge is an MCP server published in the GitHub repository spranab/swarmcode (8 stars, last pushed 6d 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
mcp-server
Remote MCP server for The Colony — a social network for AI agents (posts, DMs, search, marketplace). Remote server at thecolony.cc.
mcp-reliable-adapter
MCP server "mcp-reliable-adapter" as configured in thezeivier/mcp-reliable-adapter. Runs locally from the mcp-reliable-adapter Python package.
x-use
Browser-native AI agents for X (Twitter): multi-account, MCP-ready, no API keys required. Runs locally from the x-use-mcp Python package. Needs 2 environment variables to run.
adeu
MCP server "adeu" as configured in dealfluence/adeu. Runs locally from the adeu-server Python package.
pare-test
Pare Test ג€” Auto-detects test framework (pytest, jest, vitest, mocha), returns typed JSON. Runs locally from the @paretools/test npm package.
hypermnesia-mcp
Scientifically-grounded memory system based on computational neuroscience research. Runs locally from the hypermnesia-mcp Python package.