Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

ARGUS-3 MCP Server

NPM · @ALEXAR76/ARGUS3

ARGUS-3 stdio MCP with WARDEN firewall: argus_ask, argus_status, argus_capabilities.

Available components

+6 this week 74 Trust /100

Last scanned (13 hours ago)

Scores higher than 49% of npm servers

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security99
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 36 of 173 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency48
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 0 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability65
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 949 tokens (~316/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management33
  • Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (16)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 21 Nov 26 +16
    • Malware scan: unverified → pass ▲ security
    • Package version: 0.6.1 → 0.6.2 functional
  • 20 Nov 26 −15
    • Malware scan: pass → unverified ▼ security
    • Package version: 0.6.0 → 0.6.1 functional
  • 19 Nov 26 +1

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

  • 18 Nov 26 +6
    • CVE-2026-16633 no longer affects this package ▲ security
    • Known CVEs: fail → pass ▲ security
    • Package version: 0.4.0 → 0.6.0 functional
  • 16 Nov 26 +16
    • Malware scan: unverified → pass ▲ security
  • 15 Nov 26 −18
    • CVE-2026-16633 affects this package: high ▼ security
    • Malware scan: pass → unverified ▼ security
    • CVE-2023-54404 no longer affects this package ▲ security
    • Known CVEs: CVE check failed: a known high-severity CVE affects pdfjs-dist 5.6.205, a direct dependency. A fixed version is available. security
    • Package version: 0.3.6 → 0.4.0 functional
  • 14 Nov 26 +1

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

  • 12 Nov 26 +16
    • Malware scan: unverified → pass ▲ security
    • Stability: unverified → 0.03 ▲ functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Analysed npm/@alexar76/argus3@0.6.2

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 173 packages
Packages resolved 173
Stale 36
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 3 exposed · ~824 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
argus_ask ~475

Run one bounded natural-language task through the ARGUS-3 agent and return the final answer text. When to use: research, summarise, debug, or draft when you want a WARDEN-hardened agent (not a raw model completion). Prefer argus_status first if you only need liveness; prefer argus_capabilities for the tool/WARDEN catalog without spending LLM tokens. When NOT to use: interactive multi-turn chat (use Telegram/HTTP channels); tasks that need human approval for sensitive tools (stdio denies them); pasting secrets into `task`. Side effects / auth / limits: calls your configured LLM provider (API key from env/config); may invoke ARGUS-configured tools; third-party MCP tools run only after WARDEN gates (static scan → threat feed → LUMEN → def-pinning). Sensitive tools are deny-by-default on this channel (no interactive approver). Spend is bounded by ARGUS budget ceilings (stops rather than overspending). Not idempotent — each call is a new metered run. May use network (model + allowed tools). Returns: plain-text final answer. On failure or budget stop, text may still be returned with isError true. No streaming / partial events on this tool. Example: argus_ask({ task: "Summarise https://example.com in three bullets", response_format: "bullets" })

NameTypeReqDescription
focusstring–Optional one-line emphasis (≤500 chars) appended as a constraint, e.g. "security only" or "ELI5". Omit when the task is already specific enough.
response_formatstring–Optional output shape hint prepended to the task. `prose` = normal paragraphs; `bullets` = short bullet list; `json_hint` = ask for a single JSON object in the answer (still returned as text — not a…
taskstringyesRequired. Single clear goal for ARGUS (1..8000 chars). Include constraints (length, format, tone) and any URLs/paths. Do not embed secrets (API keys, private keys, passwords) — they may be logged or…

No output schema declared.

No examples provided.

argus_capabilities ~168

List ARGUS MCP tools and WARDEN security posture as JSON text (no LLM call). When to use: discovery — choose between argus_ask / argus_status / this catalog. When NOT to use: executing a user task (argus_ask) or a cheap ping (argus_status). Side effects: none. Read-only, idempotent, no provider auth required for this tool. Returns: JSON { agent, version, tools[{name, readOnly, summary}], warden, sensitiveToolsPolicy, channel }. Example: argus_capabilities({ include_schemas: false })

NameTypeReqDescription
include_schemasboolean–If true, include each tool's inputSchema in the JSON (larger payload). Default false — names + short summaries only.

No output schema declared.

No examples provided.

argus_status ~181

Return ARGUS-3 MCP runtime status as JSON text (no LLM call, no side effects). When to use: before heavy argus_ask calls, or to confirm version/channel/tools. When NOT to use: to run a task (use argus_ask) or to list WARDEN policy detail (use argus_capabilities). Auth / limits: none beyond MCP session. Idempotent and read-only. Returns: JSON with status, agent, version, channel, mode, tools, detail, wardenNote, sensitiveToolsPolicy (and extra fields when detail=full). Example: argus_status({ detail: "basic" })

NameTypeReqDescription
detailstring–Response depth. `basic` = liveness + version + tool names. `full` adds instructions excerpt, annotation summary, and MCP transport notes. Default basic.

No output schema declared.

No examples provided.

Install

How do I install the ARGUS-3 MCP Server server?

ARGUS-3 MCP Server runs locally as an npm package, launched with npx -y @alexar76/argus3 mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @alexar76/argus3

# add to Claude Code
claude mcp add alexar76-argus3 -- npx -y @alexar76/argus3 mcp
Common questions

What is the ARGUS-3 MCP Server server?

ARGUS-3 MCP Server is listed in the public MCP registry as io.github.alexar76/argus3. ARGUS-3 stdio MCP with WARDEN firewall: argus_ask, argus_status, argus_capabilities. This page covers its npm package (@alexar76/argus3).

Is the ARGUS-3 MCP Server server safe to use?

ARGUS-3 MCP Server scores 74 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. It declares no install or post-install scripts. 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-3 MCP Server server expose?

ARGUS-3 MCP Server exposes 3 tools: argus_ask, argus_status, argus_capabilities. Their descriptions and schemas cost roughly 824 tokens of context every time the server is loaded.

Is the ARGUS-3 MCP Server server still maintained?

ARGUS-3 MCP Server 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 licence is the ARGUS-3 MCP Server server under?

ARGUS-3 MCP Server declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

What did VerifyMCP test on the ARGUS-3 MCP Server server?

VerifyMCP ran 16 checks on ARGUS-3 MCP Server, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.