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/muchiny/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/plugins/muchiny/bridge-mcp/plugin)<a href="https://agentmods.dev/plugins/muchiny/bridge-mcp/plugin"><img src="https://agentmods.dev/badge/plugins/muchiny/bridge-mcp/plugin/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/plugins/muchiny/bridge-mcp/plugin"><img src="https://agentmods.dev/badge/plugins/muchiny/bridge-mcp/plugin.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
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 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
{
"name": "bridge-mcp",
"version": "4.0.2",
"description": "476-tool SSH bridge for secure remote server management. Execute commands on air-gapped Linux, Windows, Docker, Kubernetes hosts via SSH from Claude Code.",
"author": {
"name": "muchiny",
"url": "https://github.com/muchiny"
},
"homepage": "https://github.com/muchiny/bridge-mcp",
"repository": "https://github.com/muchiny/bridge-mcp",
"license": "MIT",
"keywords": ["ssh", "remote", "devops", "docker", "kubernetes", "linux", "windows"],
"skills": "./skills/",
"mcpServers": "./.mcp.json",
"hooks": "./hooks/hooks.json",
"userConfig": {
"config_path": {
"type": "file",
"title": "Config path",
"description": "Path to your bridge-mcp config.yaml (default: ~/.config/bridge-mcp/config.yaml)",
"sensitive": false
}
}
}
What it installs
The manifest is a name and a version. 1 skill, 1 hook, 1 MCP server travel with it, and installing the plugin installs all of them — 101 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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 Changed f2883a4fd9b5
- 1mo ago First seen · 25 lines scan A 7b39e5a2d316
bridge-mcp is a plugin published in the GitHub repository muchiny/bridge-mcp (10 stars, last pushed today), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
gpu-server-setup
Prepare a Linux server with NVIDIA or Intel Arc GPUs for LLM and neural-network workloads: NVIDIA driver + CUDA from the official repo or the in-tree Intel i915/xe driver with distro firmware, Docker Engine with verified GPU access (NVIDIA Container Toolkit or /dev/dri passthrough) as the mandatory base, staged…
xonovex-platform
Configure Moon tasks and build and operate Docker images, Kubernetes workloads, and Terraform infrastructure.
homelab-ops
Operational runbooks for infrastructure state, maintenance, and recovery: monitoring-first checks, Proxmox VE cluster operations, DNS ingress convergence, secrets-engine identity bring-up, Terrakube operations, PXE netboot installs, LLM router operations, workstation off-box backup, Dell iDRAC BMC operations, and…
easypanel-mcp-server marketplace
Full control of Easypanel from Claude Code, Cursor and Claude Desktop — deploy (app & compose), runtime logs, container exec, env vars, domains, databases, volumes, ports, resource limits, Docker maintenance and monitoring. 57 tools with built-in safety guards, optional read-only mode, plus an easypanelraw escape hatc.
synapse
MCP server and CLI for host and container operations: Docker and Compose control, SSH, host inspection, logs, ZFS, and safe file transfer.
synapse
MCP server and CLI for host and container operations: Docker and Compose control, SSH, host inspection, logs, ZFS, and safe file transfer.