Argus Console — AI Agent Test Lab

io.github.igor-viiPublished by GitHub account igor-viiv0.1.2Updated Nov 5, 2026

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

The publisher's own server: Argus: Belgian tender insights

VerifiedStreamable HTTPWeb executableFinanceSecurity & MonitoringAI & ML

Overview

AI-generated overview

Argus Console lets an assistant verify agent endpoints, run free simulated or paid real adversarial test batteries against money-moving AI agents, and fetch…

What you can do
  • Verify and list agents: check endpoint ownership via a well-known verify token, and list registered agents with their free-tier simulation usage.
  • Run free MOCK simulations: execute the full pipeline (money-guard gate plus fault probes) as a deterministic simulation that never contacts the agent endpoint.
  • Run the real engine battery: execute canonical and fault scenarios against a live client agent using paid quota, returning a run id.
  • Fetch run reports: retrieve money-guard outcome, verdict counts, per-probe verdicts and proven/violations/not-established lists.
When to use it
Useful when you are building or reviewing an AI agent that spends, receives or settles money and want adversarial checks and evidence-backed verdicts. Start with a free simulation to see how the pipeline behaves before spending paid quota on a live run.
Requirements
Remote streamable HTTP endpoint at console.argus-lab.tech; no package, environment variables or headers declared. Agents must be registered and verified by serving a verify token at a well-known path on the agent endpoint. Real engine runs consume paid quota and apply to client agents only.
Before you install
Real engine runs use paid quota and act against a live agent endpoint; agents that do not speak x402 fail the money-guard gate and are auto-refunded. Runs may take minutes. Verification requires exposing a token file on your endpoint. Free simulations are capped at 25 runs per 24 hours.

Installation

In SourceWeft

  1. Open Argus Console — AI Agent Test Lab in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.igor-vii%2Fargus-console/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "argus-console-ai-agent-test-lab": {
      "type": "http",
      "url": "https://console.argus-lab.tech/mcp"
    }
  }
}

README

Argus Agent Test Lab — public proof layer

[latest-seal] [site-build]

Adversarial testing for AI agents that move money · argus-lab.tech

The lab breaks AI agents that spend, receive and settle money — buyer and merchant agents, and the SDKs, protocols and rails that sign and settle on their behalf — then seals every verdict in a public, hash-chained registry.

This repository is the public proof layer of Argus: the sealed, hash-chained evidence registry, the verification tooling, and the source of argus-lab.tech. It exists so that every public claim the lab makes can be checked by anyone, without trusting anyone:

bash
git clone https://github.com/igor-vii/Argus-Agent-Test-Labcd Argus-Agent-Test-Labnode tools/registry/verify-registry.mjs# → registry intact: N records, chain head …

Verification uses only the Node.js standard library — no npm install, no network access, no trust in this README.

What is sealed here

Records in attestations/records/ are Ed25519-signed and hash-chained (prev_record_hash → chain head). Each record pins the sha256 of its evidence files. A seal attests run validity and findings completeness — never bug-freeness.

Repository boundary (record 0013)

As of sealed record #0013, the product layer — the testing engine, scenario library, SUT harnesses, rail adapters and engagement archives — is developed in a private repository. The public repository retains the proof layer only. The exact moment of the split and the last public snapshot are themselves sealed and hash-pinned:

The split is forward-only: no history rewrite, no force-push. Versions up to the snapshot commit remain public history, and everything referenced from public threads (e.g. docs/block-b/fixtures/S-BS-06/ on branch block-b/v1-scenarios, referenced from x402 issue #3866) stays public and byte-identical. Sealed evidence paths pinned by records #0000–#0012 are permanent and were retained.

Repository layout

attestations/        signed, hash-chained records + public key + indextools/registry/      sign / verify tooling (node stdlib only)tools/paypal-adapter/evidence/   sealed live-run evidence (records 0001–0002)site/                argus-lab.tech source (Next.js; prebuild re-verifies the registry)docs/block-b/        sealed fixtures and evidence (S-BS series, records 0003+)docs/inngest-battery/  sealed evidence + repro harness (record 0005)docs/t1-mcp-tool-idempotency/  sealed external verification (record 0009)sut-x402-pr3920/     sealed SUT evidence, x402 PR #3920 cycles (records 0008, 0012)src/tests/blockb/SBS19_BlockRunNano.test.ts   sealed evidence (record 0006).github/             CI: verify registry → OG cover → IndexNow → Vercel deploy

About Argus

Argus is an independent black-box testing laboratory for AI agents and agent-based payment systems. It runs controlled failure scenarios against observable systems under test (SUTs), captures evidence at protocol boundaries, evaluates explicit assertions, and produces evidence-backed verdicts — the public ones are the sealed records above.

Agent → Scenario → SUT → Evidence → Verdict

  • Sealed case work: x402 (#3866, PR #3920), Inngest (#5091), BlockRun (blockrun-nano-client #18), Nevermined, mcp-tool-idempotency
  • Commercial engagements (scenario conformance runs, release verification): argus-lab.tech

Argus lives in a repository separate from the systems it tests and interacts with SUTs through defined external interfaces and observable behavior only.

Status

Public case studies and production-capability claims are added only when supported by verified run evidence — the registry is the source of truth, not this README.

Source: README.md at commit db48768

Tools

5

argus_verify_agent

Verify ownership of an agent endpoint: checks that the verify token is served at https://<endpoint>/.well-known/argus-verify.txt. Run this before registering the agent in Argus Console.

Parameterstokenrequiredendpointrequired

argus_list_agents

List the user's registered agents (name, role, endpoint) and their free tier. MOCK simulation is FREE: no payment, nothing to deploy, rolling cap 25 runs / 24h (paid quota untouched). The response includes freeSimulation { used, limit, resetsAt }.

Takes no parameters.

argus_run_simulation

Run a free MOCK battery against a registered agent: the full pipeline (money guard gate + fault probes) as a deterministic simulation seeded by the endpoint. Simulation only — this is a stand demo, no request reaches the agent endpoint. Does not touch paid quota; rolling cap 25 runs / 24h. Waits for completion and returns the report.

Parametersagentrequiredbattery

argus_run_engine

Run the REAL Argus engine battery (canonical S8 + fault scenarios) against a live agent using paid quota. 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 to poll via argus_get_run_report.

Parametersagentrequiredbattery

argus_get_run_report

Fetch the report of a finished run: money guard outcome, verdict counts, per-probe verdicts, proven/violations/not-established lists.

Parametersrun_idrequired

Version history

2
  1. v0.1.2LatestNov 5, 2026
  2. v0.1.1Nov 5, 2026

Score

90% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.

Other Argus integrations