AW-1 Sovereign Circuit Breaker

by MvikMannersio.github.MvikManners/aw1-circuit-breakerv2.2.1

Deterministic sub-0.2ms AST security circuit breaker and agent containment engine.

  • Remote endpoint

Uptime

Checked  · every day

100%from 1 day of checks

Up without downtime on 1 of 1 day with data.

  • No downtime
  • Degraded
  • Down over 5 minutes
  • No data
  • Not checked yet

How far each check got

  • Reached the address 100%
  • Completed the handshake 0.0%
  • Listed its tools 0.0%
Every day
DayResultChecksMedian
4 Nov (today)No downtime1–

A failure counts as down time only when a second check five minutes later fails too. How we check

Connect to the publisher's own endpoint

Add to anythingllm_mcp_servers.json in the AnythingLLM storage plugins directory:

{
  "mcpServers": {
    "aw1-circuit-breaker": {
      "type": "sse",
      "url": "https://p20.laveto.net/wisdom/mcp/sse"
    }
  }
}
For agents: the install prompt

Every step above as one Markdown text, for an assistant installing it for you.

# Install the MCP server AW-1 Sovereign Circuit Breaker (`io.github.MvikManners/aw1-circuit-breaker`)

Its page: https://plug.directory/servers/io.github.MvikManners/aw1-circuit-breaker

It runs on the publisher's servers; the client connects to its URL.

Use the section for the person's client.

## Claude Desktop

Paste into Settings › Connectors › Add custom connector:

```text
https://p20.laveto.net/wisdom/mcp/sse
```

## Claude Code

Run in a terminal:

```sh
claude mcp add --transport sse aw1-circuit-breaker https://p20.laveto.net/wisdom/mcp/sse
```

## Cursor, Devin Desktop, LM Studio, Gemini CLI, oterm, ECA

Merge into the place for the person's client:

- Cursor: ~/.cursor/mcp.json
- Devin Desktop: ~/.config/devin/mcp_config.json
- LM Studio: mcp.json (Program › Install › Edit mcp.json)
- Gemini CLI: ~/.gemini/settings.json
- oterm: config.json in oterm's data folder (~/Library/Application Support/oterm on macOS, ~/.local/share/oterm on Linux, %APPDATA%\oterm on Windows)
- ECA: ~/.config/eca/config.json (global) or .eca/config.json in the project

```json
{
  "mcpServers": {
    "aw1-circuit-breaker": {
      "url": "https://p20.laveto.net/wisdom/mcp/sse"
    }
  }
}
```

## VS Code

Merge into .vscode/mcp.json:

```json
{
  "servers": {
    "aw1-circuit-breaker": {
      "type": "sse",
      "url": "https://p20.laveto.net/wisdom/mcp/sse"
    }
  }
}
```

## Zed

This server's endpoint speaks only SSE, which this client's documentation does not list among its transports; use another client for it.

## Cline, AnythingLLM, Augment Code

Merge into the place for the person's client:

- Cline: cline_mcp_settings.json (MCP Servers › Configure › Configure MCP Servers)
- AnythingLLM: anythingllm_mcp_servers.json in the AnythingLLM storage plugins directory
- Augment Code: Augment Settings Panel – MCP section – Import from JSON (VS Code extension)

```json
{
  "mcpServers": {
    "aw1-circuit-breaker": {
      "type": "sse",
      "url": "https://p20.laveto.net/wisdom/mcp/sse"
    }
  }
}
```

## Continue

Merge into ~/.continue/config.yaml:

```yaml
mcpServers:
  - name: "aw1-circuit-breaker"
    type: sse
    url: "https://p20.laveto.net/wisdom/mcp/sse"
```

## Goose

This server's endpoint speaks only SSE, which this client's documentation does not list among its transports; use another client for it.

## Codex

This server's endpoint speaks only SSE, which this client's documentation does not list among its transports; use another client for it.

## mcp-client-cli, TUUI, BoltAI, Bob Shell, Kiro, Kiro CLI

This server's endpoint speaks only SSE, which this client's documentation does not list among its transports; use another client for it.

## Agenvoy

This server's endpoint speaks only SSE, which this client's documentation does not list among its transports; use another client for it.

## Amp

Merge into ~/.config/amp/settings.json (user) or .amp/settings.json (workspace):

```json
{
  "amp.mcpServers": {
    "aw1-circuit-breaker": {
      "url": "https://p20.laveto.net/wisdom/mcp/sse"
    }
  }
}
```

Then restart the client, or reload its MCP servers, and ask it to list the server's tools to confirm it started.

From the publisher's entry in the Official MCP Registry (the registry entry). Report a problem