Argus Console — AI Agent Test Lab MCP server
io.github.igor-vii/argus-consoleigor-viistreamable-httpv0.1.2Scanned
Adversarial testing for AI agents that move money: engine battery, Ed25519-sealed verdict reports.
5 tools: 3 change things and 2 only read.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 1
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
3 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the Argus Console — AI Agent Test Lab MCP server can do
The Argus Console — AI Agent Test Lab MCP server is published by the GitHub account igor-vii. It has 5 tools. It can create or change data (3 tools: argus_verify_agent, argus_run_simulation and argus_run_engine), but cannot delete data. 2 tools only read.
1 tool can send data out of your system (argus_verify_agent).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in, and its tools changed 2 times since Anlyon Radar first saw them.
Last scanned Nov 19, 2026, version 0.1.2.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
5 tools
Changes things 3Claude Code: ask
argus_run_engineRun the REAL Argus engine battery (canonical S8 + fault scenarios) against a LIVE agent endpoint using paid quota.No findings
Why it is in this group
- The name "argus_run_engine" says "run": a word for a change.
Description, as the server wrote it 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.
argus_run_simulationRun 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 rea…No findings
Why it is in this group
- The name "argus_run_simulation" says "run": a word for a change.
Description, as the server wrote it 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.
argus_verify_agentVerify 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.Can send data outNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
What it can reach
- outboundThe input takes a URL (input.endpoint): a request to a URL can carry data to whoever runs it.
Description, as the server wrote it 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.
Only reads 2Show 2 read-only tools
argus_get_run_reportFetch a finished Argus run report: money-guard outcome, verdict counts, per-probe verdicts, and the proven / violations_found / not_established lists.No findings
Why it is in this group
- The name "argus_get_run_report" says "get": a word for reading.
Description, as the server wrote it 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.
argus_list_agentsList the user's registered Argus agents (name, role, endpoint) and their free-tier state.No findings
Why it is in this group
- The name "argus_list_agents" says "list": a word for reading.
Description, as the server wrote it 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.
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out1
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:22 UTC, unchanged since Nov 6, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 3
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 3 tools that change things (3 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://console.argus-lab.tech/mcp: tools/list returned 5 tools to an anonymous client, including argus_verify_agent (write), argus_run_simulation (write), argus_run_engine (write)
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools5 changed.~5 changedView diff
- Changed:argus_get_run_reportOnly readsdescription
- Changed:argus_list_agentsOnly readsdescription
- Changed:argus_run_engineChanges thingsdescription
- Changed:argus_run_simulationChanges thingsdescription
- Changed:argus_verify_agentChanges thingsdescription
Tools2 changed.~2 changedView diff
- Changed:argus_run_engineChanges thingsdescription
- Changed:argus_run_simulationChanges thingsdescription
Install
Pinned to version 0.1.2. Values in angle brackets are yours to fill in.
claude mcp add --transport http argus-console https://console.argus-lab.tech/mcpclaude mcp add --transport http argus-console https://console.argus-lab.tech/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__argus-console__argus_list_agents",
"mcp__argus-console__argus_get_run_report"
],
"ask": [
"mcp__argus-console__argus_verify_agent",
"mcp__argus-console__argus_run_simulation",
"mcp__argus-console__argus_run_engine"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as argus-console. Review it before you use it.
Capability tags behind 1 rule
- mcp__argus-console__argus_verify_agent outbound
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.github.igor-vii/argus-console/verify?hash=493d38f6ef18d6532649610407090b9667839f085f5d5cade3ebb6085cd7813e" | jq -e '.changed == false'Pinned hash 493d38f6ef18, from Nov 19, 2026, 11:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.igor-vii/argus-console/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.igor-vii/argus-console)Source: MCP Registry · repository. Synced Nov 5, 2026, 14:17 UTC.
Argus Console — AI Agent Test Lab MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Argus Console — AI Agent Test Lab MCP server safe?
- No scan can promise that. What its definitions show: 5 tools, 3 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Argus Console — AI Agent Test Lab MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Argus Console — AI Agent Test Lab MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the Argus Console — AI Agent Test Lab MCP server have?
- 5 tools: 3 write, 2 read. argus_verify_agent, argus_run_simulation, argus_run_engine, argus_list_agents and argus_get_run_report.
Does the Argus Console — AI Agent Test Lab MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Argus Console — AI Agent Test Lab MCP server send data to outside services?
- 1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): argus_verify_agent.
Has the Argus Console — AI Agent Test Lab MCP server changed its tools?
- Yes, 2 times since Anlyon Radar started tracking it, most recently on Nov 19, 2026. Every change is on this page and in its Atom feed.