devops-deploy-guard-mcp-server
Related Servers
Alternatives to devops-deploy-guard-mcp-server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to inspect and safely operate a Linux VPS through typed DevOps tools governed by YAML allowlists, read-only defaults, dry-run plans, secret redaction, and tamper-evident auditing.MIT
- FlicenseNot gradedqualityBmaintenanceEnables AI coding agents to run shell commands, spawn persistent background tasks, and read/write files inside isolated remote container sandboxes on a VPS. It also provides project workspace listing, task attach/kill controls, and a searchable knowledge graph for memory continuity across sessions.-
- AlicenseNot gradedqualityBmaintenanceEnables a cloud-hosted AI agent to execute shell commands, manage background jobs, and drive interactive persistent terminals on a remote Linux VPS with native root privileges over MCP and HTTPS — no SSH, tunnel, or local runtime required. It also provides bearer-key authentication, key revocation, and a LAN-restricted dashboard for sessions and audit logs.MIT
- AlicenseNot gradedqualityDmaintenanceProvision KYC-free, crypto-paid Nordic VPS and dedicated servers from any AI agent. Enables natural language hosting workflows including comparison, top-up, and provisioning of anonymous servers.MIT

mcp-fracteraofficial
AlicenseNot gradedqualityBmaintenanceZero-Ops deploy of a private AI coding workspace to your own VPS, straight from your AI chat. Registers the user, recommends a VPS, and runs and monitors the full deployment.69MIT- AlicenseAqualityCmaintenanceEnables AI agents to deploy applications and manage servers over SSH using natural language commands, with built-in tools for Python bots, Docker Compose, and SSL setup.6MIT
TDQS
Scored across 20 tools
Each tool targets a distinct operation: inspection, environment setup, deployment planning, execution, rollback, etc. There is no overlap; even the two planning tools are differentiated (dynamic vs Docker).
All tool names follow a consistent verb_noun pattern with imperative verbs (inspect, resume, rollback, analyze, generate, verify, etc.). No mixed conventions.
20 tools cover the full DevOps deployment lifecycle without being excessive. Each tool serves a clear and necessary purpose within the domain.
The tool set covers inspection, provisioning, environment setup, deployment planning, execution, rollback, recovery, health checks, and cleanup. No obvious gaps for the stated purpose.