# Argus Console — AI Agent Test Lab (remote · console.argus-lab.tech)

Adversarial testing for AI agents that move money: engine battery, Ed25519-sealed verdict reports.

- Trust score: 82/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `console.argus-lab.tech`: 82/100 (this document), [markdown](https://verifymcp.io/servers/igor-vii-argus-console/console.md), [page](https://verifymcp.io/servers/igor-vii-argus-console/console)

## Channel facts

- Endpoint: `https://console.argus-lab.tech/mcp`
- Transports: `streamable-http`
- Auth: `required (not validated)`
- Version: `0.1.2`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Endpoint Security**: 89/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 70/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 945 tokens (~189/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 53/100
  - Stability observed for 16 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the Argus Console — AI Agent Test Lab MCP server?

Argus Console — AI Agent Test Lab is a hosted endpoint at https://console.argus-lab.tech/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http igor-vii-argus-console 'https://console.argus-lab.tech/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "igor-vii-argus-console": {
      "url": "https://console.argus-lab.tech/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "igor-vii-argus-console": {
      "type": "http",
      "url": "https://console.argus-lab.tech/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.igor-vii-argus-console]
url = "https://console.argus-lab.tech/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "igor-vii-argus-console": {
      "type": "remote",
      "url": "https://console.argus-lab.tech/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add igor-vii-argus-console --url 'https://console.argus-lab.tech/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  igor-vii-argus-console:
    url: "https://console.argus-lab.tech/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "igor-vii-argus-console": {
      "Transport": "http",
      "Url": "https://console.argus-lab.tech/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add igor-vii-argus-console -t streamable-http -u 'https://console.argus-lab.tech/mcp'
```

### Other

```json
{
  "mcpServers": {
    "igor-vii-argus-console": {
      "type": "http",
      "url": "https://console.argus-lab.tech/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-20 (score 82, +1)

No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-18 (score 81, +1)

No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-16 (score 80, +1)

No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-14 (score 79, +1)

No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-12 (score 78, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-10 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-07 (score 76, 0)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “argus_get_run_report” rewrote its description, which is the text the model reads
- [security] Tool “argus_list_agents” rewrote its description, which is the text the model reads
- [security] Tool “argus_run_engine” rewrote its description, which is the text the model reads
- [security] Tool “argus_run_simulation” rewrote its description, which is the text the model reads
- [security] Tool “argus_verify_agent” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: pass → fail
- [functional] Schema quality: good → excellent

### 2026-11-06 (score 76, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

## MCP tools (5)

### `argus_verify_agent` (~116 tokens)

Verify ownership of an agent endpoint before it can be registered in Argus Console: checks that the verify token is served at https://<endpoint>/.well-known/argus-verify.txt. Run once per endpoint, right after the user adds the agent in Argus Console and shares the verify token. Does not consume any quota.

Input parameters:

- `endpoint` (string, required): Public base URL of the agent, e.g. https://my-agent.replit.dev
- `token` (string, required): Verify token from Argus Console → Agents

### `argus_list_agents` (~136 tokens)

List the user's registered Argus agents (name, role, endpoint) and their free-tier state. ALWAYS call this first, before any run — it shows which agents exist and includes freeSimulation { used, limit, resetsAt } (MOCK simulation is FREE: rolling cap 25 runs / 24h, paid quota untouched). New accounts also hold 3 welcome engine runs (+30-run beta pack) for the real engine — visible in the console Billing page. If the target agent is missing, it must be registered in the Argus Console web UI first — tell the user; do not guess agent names or ids.

### `argus_run_simulation` (~132 tokens)

Run a FREE deterministic MOCK battery against a registered agent: the full Argus pipeline (money-guard gate + fault probes) simulated from the endpoint's seed — no request ever reaches the agent endpoint. Use this BEFORE any real engine run to preview verdicts, demo the flow, or sanity-check registration. Does not consume paid quota; rolling cap 25 runs / 24h. Waits for completion and returns the report.

Input parameters:

- `agent` (string, required): Agent name or id (see argus_list_agents)
- `battery` (string): Optional battery id; defaults to the role's starter battery

### `argus_run_engine` (~233 tokens)

Run the REAL Argus engine battery (canonical S8 + fault scenarios) against a LIVE agent endpoint using paid quota. Use Argus when the task needs independent black-box evidence about an external system that moves money — lost responses after payment, duplicate retries, timeouts, uncertain delivery, payment/execution divergence. Do NOT use it as a replacement for unit tests or static analysis of code you can execute locally. Free entry: every new account gets 3 welcome engine runs (+30-run beta pack), and a run that fails the canonical payment gate is refunded in full (net cost 0) — until the agent passes the gate, you pay nothing. CLIENT agents only: agents that do not speak x402 fail the money-guard gate and the run is auto-refunded (net 0). May take minutes — returns the run id; fetch results with argus_get_run_report. Run argus_run_simulation first if unsure.

Input parameters:

- `agent` (string, required): Agent name or id (see argus_list_agents)
- `battery` (string): Optional battery id; defaults to the role's starter battery

### `argus_get_run_report` (~111 tokens)

Fetch a finished Argus run report: money-guard outcome, verdict counts, per-probe verdicts, and the proven / violations_found / not_established lists. Requires the run id from argus_run_simulation or argus_run_engine. Treat proven violations as evidence you can show the user; 'not established' means the probe could not decide — it is not a pass.

Input parameters:

- `run_id` (string, required): Run id returned by argus_run_simulation / argus_run_engine

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/igor-vii-argus-console/console#diagnostics

## Score history

- 2026-11-21: 82
- 2026-11-20: 82
- 2026-11-19: 81
- 2026-11-18: 81
- 2026-11-17: 80
- 2026-11-16: 80
- 2026-11-15: 79
- 2026-11-14: 79
- 2026-11-13: 78
- 2026-11-12: 78
- 2026-11-11: 77
- 2026-11-10: 77
- 2026-11-09: 76
- 2026-11-08: 76
- 2026-11-07: 76
- 2026-11-06: 76
- 2026-11-05: 76

## Common questions

### What is the Argus Console — AI Agent Test Lab MCP server?

Argus Console — AI Agent Test Lab is an MCP server listed in the public MCP registry as io.github.igor-vii/argus-console. Adversarial testing for AI agents that move money: engine battery, Ed25519-sealed verdict reports. This page covers its hosted endpoint (https://console.argus-lab.tech/mcp).

### Is the Argus Console — AI Agent Test Lab MCP server safe to use?

Argus Console — AI Agent Test Lab scores 82 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Argus Console — AI Agent Test Lab MCP server expose?

Argus Console — AI Agent Test Lab exposes 5 tools: argus_verify_agent, argus_list_agents, argus_run_simulation, argus_run_engine, argus_get_run_report. Their descriptions and schemas cost roughly 728 tokens of context every time the server is loaded.

### Does the Argus Console — AI Agent Test Lab MCP server require authentication?

Yes. Argus Console — AI Agent Test Lab asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

### Is the Argus Console — AI Agent Test Lab MCP server still maintained?

Argus Console — AI Agent Test Lab is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the Argus Console — AI Agent Test Lab MCP server?

VerifyMCP ran 13 checks on Argus Console — AI Agent Test Lab, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://console.argus-lab.tech/mcp
- Repository: https://github.com/igor-vii/Argus-Agent-Test-Lab
- Website: https://argus-lab.tech/
- Changelog RSS feed: https://verifymcp.io/servers/igor-vii-argus-console/console.xml
- Changelog JSON feed: https://verifymcp.io/servers/igor-vii-argus-console/console/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/igor-vii-argus-console/console.json
- HTML version of this page: https://verifymcp.io/servers/igor-vii-argus-console/console
