emisar MCP Server
AndrewDryga/emisar
[](https://agentrank-ai.com/tool/AndrewDryga--emisar/?utm_source=badge&utm_medium=readme&utm_campaign=agentrank_badge) Let AI agents investigate and operate infrastructure through declared actions, bounded by policy and host-side checks. Approvals when required, with an audit trail. By Protectorate.
claude mcp add agentrank -- npx -y agentrank-mcp-server Overview
AndrewDryga/emisar is a Elixir tool. Let AI agents investigate and operate infrastructure through declared actions, bounded by policy and host-side checks. Approvals when required, with an audit trail. By Protectorate. Topics: ai, devops, elixir, go, security, infrastructure, mcp, ai-agents, devsecops, infosec, infra, mcp-server, policy-as-code, remote-execution, self-hosted.
Ranked #2942 out of 24846 indexed tools.
Ecosystem
Score Breakdown
337 stars → growing community
Last commit 29d ago → recently updated
2/3 issues closed → decent issue management
2 contributors → solo project
No dependents → no downstream usage
Weights: Freshness 20% · Issue Health 20% · Dependents 22% · Stars 10% · Contributors 8% · How we score →
How to Improve
Matched Queries
From the README
# emisar **Leave the agent working. Keep production authority bounded.** emisar gives MCP-capable agents a catalog of declared infrastructure actions instead of a shell. Policy decides what runs, what waits for a person, and what is denied. A small outbound-only runner checks the action again on the host before it executes anything. Start with the public pack catalog, let emisar suggest the packs that match a host, and add your own actions without adding another MCP server to every client. ## Start with one host You need an [emisar account](https://emisar.dev/sign_up), a Linux host with systemd, and `sudo`. GitHub CLI with `gh attestation verify --bundle` checks the release signature; without it the installer asks, or warns and continues when run with `--yes`, on the checksum alone. Allow outbound HTTPS to `emisar.dev:443`, `registry.emisar.dev:443`, `tuf-repo-cdn.sigstore.dev:443`, and `tuf-repo.github.com:443`. The last two serve the public trust roots used to authenticate releaRead full README on GitHub →
Get the weekly AgentRank digest
Top movers, new tools, ecosystem insights — straight to your inbox.