mcp server
emisar
Let AI operate servers without SSH. Choose actions, approve risky changes, and audit every step.
Description as published by the maintainer. Source
- version 0.36.0
- active
active — Most recent push to the repository was 2026-08-06.
Signals
These are separate measurements of different things. They are deliberately not combined into one score, because a popularity number that mixes website traffic with saves and stars cannot be checked or acted on.
| Signal | Value | What it measures | Window | Observed | Source |
|---|---|---|---|---|---|
| GitHub stars | 421 | Number of GitHub accounts that bookmarked this repository since it was created. It is a bookmark count, not installs, not active users and not quality. | cumulative, all time | GitHub | |
| Last commit | 2026-08-06 | Date of the most recent push to any branch. This is the strongest cheap indicator of whether the project is still maintained. | point in time | GitHub | |
| Open issues | 0 | Open issues plus open pull requests, as GitHub counts them together. A high number can mean an active project or an abandoned one. | as of fetch | GitHub | |
| Latest published version | 0.36.0 | Latest version string the maintainer published to the registry. | as of fetch | Model Context Protocol | |
| Registry record last updated | 2026-07-31 | When the registry record was last updated by its maintainer. | point in time | Model Context Protocol | |
| First listed in the MCP Registry | 2026-07-31 | Date this server was first published to the official MCP Registry. Not a usage or quality measure. | point in time | Model Context Protocol | |
| repository status | active | The repository exists on GitHub and is not archived. This says nothing about how recently it was worked on. | as of fetch | GitHub |
Where to get it
Related, by what their authors tagged them
-
ControlKeel
— last commit 2026-08-06, shares devsecops, elixir, policy-as-code
Governed MCP workflows with policy validation, findings tracking, and review gates.
-
dev.avakit/avalanche
— last commit 2026-08-06, shares infra
Act on Avalanche from your agent: scaffold a dapp, deploy a contract, mint, and read chain state.
-
Aegis — AI Agent Governance
— last commit 2026-05-05, shares policy-as-code
Policy-based governance for AI agent tool calls. YAML policy, approval gates, audit logging.
-
SentinelX
— last commit 2026-08-01, shares devops, infrastructure
Operate your Linux servers from your LLM. Every action runs through an auditable allowlist.
-
Control Plane
— last commit 2026-08-05, shares devops, infrastructure
Control Plane (controlplane.com): deploy and operate workloads across AWS, GCP, Azure, and more.
-
MikroMCP
— last commit 2026-07-21, shares devops, infrastructure
MCP server for MikroTik RouterOS: typed tools, dry-run, RBAC, audit logs, and rollback.
-
io.github.davidlandais/ovh-api-mcp
— last commit 2026-06-15, shares devops, infrastructure
MCP server for the OVH API. Explore and call any OVH endpoint via sandboxed JS.
-
io.github.den-indance/network-diagram-mcp
— last commit 2026-05-25, shares devops, infrastructure
Network topology editor — Claude builds diagrams via MCP. nmap/CSV import, one-click SSH.
-
DC Hub — Data Center & Power Intelligence
— last commit 2026-08-06, shares infrastructure
Data-center, grid, fiber & gas infrastructure intelligence for AI agents — query and cite.
-
com.opsmill/infrahub-mcp
— last commit 2026-08-06, shares infrastructure
An MCP server connects your AI assistants to Infrahub using the open MCP standard.
These share tags the maintainers applied themselves, such as devsecops, elixir, policy-as-code, security. Common tags like "mcp" or "ai" are ignored for this: agreeing with six hundred other projects is not a similarity.
This is not a recommendation and not a test result. It is a map of what the authors said their work is about.
How the author describes it
Topics the maintainer set on GitHub: ai, ai-agents, devops, devsecops, elixir, go, infosec, infra, infrastructure, mcp, mcp-server, policy-as-code, remote-execution, security, self-hosted.
Bring your own setup
We take apart real AI setups every week and show what broke, what cost too much, and what the trace actually said. If you run agents on real work, that is where the useful conversation is.
Join ZBS AI Practice Lab