io.github.garagon/aguara-mcp

Aguara MCP

Is the Aguara MCP server down? Yes. It has given no valid answer since 2026-10-27: not found.

Security scanner for AI agent skills and MCP servers

not found down since 2026-10-27 · probed 2026-11-15 · unchanged since 2026-11-03

command not found: server/aguara-mcp-linux-amd64

Bundle: https://github.com/garagon/aguara-mcp/releases/download/v0.2.0/aguara-mcp.mcpb (MCPB, for a client that installs bundles; probed in a container with the network off)
Host: github.com
Repository: https://github.com/garagon/aguara-mcp
Registry: active, updated 2026-02-26 · registry entry

More servers

Other registry entries on github.com, the ones next to this name; all of them.

Tachyon GPU monitor io.github.formray/tachyon · crashed on start
io.github.francisco-perez-sorrosal/cv · crashed on start
Inbox Benefits MCP io.github.fvegiard/inbox-benefits-mcp · not found
Ganter Lab io.github.ganterlab/ganter-lab · needs network
Secret Handoff io.github.geland/secrethandoff · alive
io.github.genesiscode2026/genesis-agent-mcp · alive
Verdict — Compliance for AI-Generated Code io.github.getverdict-ai/verdict · crashed on start
Flow Learning System io.github.ghlee0786/flow-learning-system · crashed on start

Servers that mention aguara or security or scanner.

Prefeitura MG Itaguara: Certidão Negativa de Econômico io.github.mcp-dir/pref_mg_itaguara_cne-mcp · alive
Aguara MCP io.github.garagon/mcp-aguara · alive
Arketo ai.arketo/arketo · needs auth
CertScore.ai MCP Light ai.certscore/mcp-light · alive
Helixar Security ai.helixar/mcp · needs auth
ai.kernora/agent-sec · alive
IntoDNS.ai DNS & Email Security Scanner ai.intodns/scanner · alive
SOAR Record Gateway ai.lateos/soar-record-gateway · needs auth

The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.

Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.

No valid answer since 2026-10-27, in every probe since then.
The endpoint answers HTTP 404. The registry entry points to a URL that is not an MCP endpoint any more. Publish a new version of the registry entry with the current URL.