io.github.kosiakMD/artillery-mcp

OCI · GHCR.IO/KOSIAKMD/ARTILLERY-MCP:0.1.7 · 3 COMPONENTS · SCANNED AUG 3

MCP server for Artillery 2.x — full flags, Fargate, raw-text parser, project launcher (MIT)

Available components

npm · @kosiakmd/artillery-mcp 46 oci · docker.io/kosiakmd/artillery-mcp:0.1.7 39 oci · ghcr.io/kosiakmd/artillery-mcp:0.1.7 37

−1 this week 37 37 Trust /100

Trust breakdown (6 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 →

Supply Chain Security0

Malware scan not yet available for this package.Unverified
CVE data not yet available for this package.Unverified
Install-script risk not yet assessed.Unverified
Dependency-health data not yet available.Unverified

Provenance & Transparency45

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 109 days ago).Pass
Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail

Schema Quality & AI Usability54

AI-judged instruction clarity (fair).Partial
Tool/resource definitions use about 1711 tokens (~95/item across 18 items; 18 tools + 0 resources), lean.Pass
Usage-examples check failed: none of the tools include examples. See how to fix → Fail

Stability & Change Management23

Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial

Tool Coverage90

100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
70% of tool parameters carry a description.Partial

Capabilities100

Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

Unverified: 1 category

A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

oci · ghcr.io/kosiakmd/artillery-mcp:0.1.7

Claude Codex opencode Hermes Other

# add to Claude Code

claude mcp add kosiakmd-artillery-mcp -- docker run --rm -i ghcr.io/kosiakmd/artillery-mcp:0.1.7

# add to Codex CLI

codex mcp add kosiakmd-artillery-mcp -- docker run --rm -i ghcr.io/kosiakmd/artillery-mcp:0.1.7

// opencode.json

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "kosiakmd-artillery-mcp": {
      "type": "local",
      "command": [
        "docker",
        "run",
        "--rm",
        "-i",
        "ghcr.io/kosiakmd/artillery-mcp:0.1.7"
      ],
      "enabled": true
    }
  }
}

# ~/.hermes/config.yaml

mcp_servers:
  kosiakmd-artillery-mcp:
    command: "docker"
    args: ["run", "--rm", "-i", "ghcr.io/kosiakmd/artillery-mcp:0.1.7"]

// mcp.json

{
  "mcpServers": {
    "kosiakmd-artillery-mcp": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/kosiakmd/artillery-mcp:0.1.7"
      ]
    }
  }
}

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.

2 Aug 26 +3
- Stability: unverified → 0.20 ▲ functional
31 Jul 26 −4
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
27 Jul 26 +27
- Tool coverage: unverified → 100 ▲ functional
- First check of Schema quality: pass functional
- First check of Tool coverage: 70 functional
- First check of Schema quality: fail functional
- First check of Schema quality: fair functional
26 Jul 26 11

First indexed and scored.
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional

Show 3 earlier entries Hide earlier entries

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 3 Aug 2026 · Analysed oci/ghcr.io/kosiakmd/artillery-mcp:0.1.7

Provenance none

Ecosystem: oci · Outcome: none

Reason: no_attestation

MCP tools — 18 exposed · ~1,711 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.

Tool Tokens

compare_results ~55

Compare two Artillery test results to detect performance regressions.

Input Output Examples

Name	Type	Req	Description
baselinePath	string	yes	Path to baseline JSON results
currentPath	string	yes	Path to current JSON results
thresholds	object	—	Custom thresholds

No output schema declared.

No examples provided.

delete_config ~28

Delete a saved Artillery configuration.

Input Output Examples

Name	Type	Req	Description
name	string	yes	Name of the config to delete

No output schema declared.

No examples provided.

get_config ~30

Retrieve a saved Artillery configuration by name.

Input Output Examples

Name	Type	Req	Description
name	string	yes	Name of the config to retrieve

No output schema declared.

No examples provided.

list_capabilities ~19

Report versions, detected features, and server limits.

Input Output Examples

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_configs ~28

List all saved Artillery configurations.

Input Output Examples

Name	Type	Req	Description
tag	string	—	Optional tag to filter configs by

No output schema declared.

No examples provided.

parse_results ~32

Parse Artillery JSON results and return summary.

Input Output Examples

Name	Type	Req	Description
jsonPath	string	yes	Path to Artillery JSON results file

No output schema declared.

No examples provided.

quick_test ~93

Run a quick HTTP test (if supported by Artillery).

Input Output Examples

Name	Type	Req	Description
body	string	—	Request body
count	number	—	Total request count
duration	string	—	Test duration (e.g., "1m")
headers	object	—	HTTP headers
method	string	—	HTTP method
rate	number	—	Requests per second
target	string	yes	URL to test

No output schema declared.

No examples provided.

read_artillery_output ~142

Read an Artillery stdout text dump (e.g. artillery-output.txt from CI) and extract summary block, counters, rates, nested latency metrics — without needing a JSON report. Optionally returns counterBreakdown when a project config with counterGroups is loaded.

Input Output Examples

Name	Type	Req	Description
block	string	—	Parse metrics from "summary" (last Summary report section) or "full" file. Default: summary.
maxBytes	number	—	Truncate rawText from the head if file exceeds this many bytes (default 65536). Counters/metrics are still parsed from the full file.
path	string	yes	Absolute path to the text output file

No output schema declared.

No examples provided.

run_fargate ~311

Launch an Artillery load test on AWS ECS/Fargate (run-fargate). Requires AWS credentials and an artilleryio cluster in the target region.

Input Output Examples

Name	Type	Req	Description
cluster	string	—	—
containerDnsServers	string	—	—
count	number	—	Number of Fargate workers
cpu	—	—	—
cwd	string	—	—
dotenv	string	—	—
env	object	—	—
environment	string	—	—
extraArgs	array	—	—
insecure	boolean	—	—
launchConfig	string	—	—
launchType	string	—	—
maxDuration	string	—	—
memory	—	—	—
name	string	—	—
noAssignPublicIp	boolean	—	—
note	string	—	—
outputJson	string	—	—
overrides	—	—	—
packages	string	—	—
path	string	yes	Path to Artillery config
payload	string	—	—
record	boolean	—	—
region	string	yes	AWS region, e.g. us-east-1
scenarioName	string	—	—
secret	array	—	—
securityGroupIds	string	—	—
spot	boolean	—	—
subnetIds	string	—	—
tags	string	—	—
target	string	—	—
taskEphemeralStorage	number	—	—
taskRoleName	string	—	—
variables	—	—	—

No output schema declared.

No examples provided.

run_preset_test ~118

Run a preset test type (smoke, baseline, soak, spike) with minimal configuration.

Input Output Examples

Name	Type	Req	Description
body	object	—	Request body for POST/PUT
env	object	—	Environment variables
method	string	—	HTTP method
outputJson	string	—	Path for JSON results
path	string	—	Endpoint path (default: /)
preset	string	yes	Test type preset
reportHtml	string	—	Path for HTML report
target	string	yes	Target URL to test

No output schema declared.

No examples provided.

run_report ~86

Convert an existing Artillery JSON results file to an HTML report via `artillery report`. Use when you have JSON (e.g. CI artifact) and want shareable HTML without re-running the test.

Input Output Examples

Name	Type	Req	Description
jsonPath	string	yes	Absolute path to Artillery JSON results file
outputHtml	string	—	Absolute path for generated HTML. Defaults to <jsonPath>.html

No output schema declared.

No examples provided.

run_saved_config ~84

Run an Artillery test using a previously saved configuration.

Input Output Examples

Name	Type	Req	Description
env	object	—	Environment variables
name	string	yes	Name of the saved config to run
outputJson	string	—	Path for JSON results output
reportHtml	string	—	Path for HTML report output
validateOnly	boolean	—	Only validate config, do not run

No output schema declared.

No examples provided.

run_test_from_file ~359

Run an Artillery test from a config file path (supports --record/--tags/--name/--note/-t/-e/--scenario-name/-v/--overrides/-p/--dotenv/-k/--count/-s).

Input Output Examples

Name	Type	Req	Description
count	number	—	--count: number of instances
cwd	string	—	Working directory
dotenv	string	—	--dotenv: env file
env	object	—	Environment variables
environment	string	—	-e: pick config.environments
extraArgs	array	—	Raw extra CLI args (escape hatch)
insecure	boolean	—	-k: allow insecure TLS
name	string	—	--name: run name in Cloud dashboard
note	string	—	--note: annotation
outputJson	string	—	Path for JSON results output
overrides	—	—	--overrides: JSON object or string
path	string	yes	Path to Artillery config file
payload	string	—	-p: CSV payload path
record	boolean	—	--record: stream to Artillery Cloud (uses ARTILLERY_CLOUD_API_KEY)
reportHtml	string	—	Path for HTML report output (generated via `artillery report` after run; requires outputJson)
scenarioName	string	—	--scenario-name
solo	boolean	—	-s / --solo: single VU
tags	string	—	--tags: comma-separated key:value tags
target	string	—	-t / --target: override target URL
validateOnly	boolean	—	Only validate config, do not run
variables	—	—	-v: JSON object or string

No output schema declared.

No examples provided.

run_test_inline ~91

Run an Artillery test from inline configuration text.

Input Output Examples

Name	Type	Req	Description
configText	string	yes	Artillery configuration as text
cwd	string	—	Working directory
env	object	—	Environment variables
outputJson	string	—	Path for JSON results output
reportHtml	string	—	Path for HTML report output
validateOnly	boolean	—	Only validate config, do not run

No output schema declared.

No examples provided.

save_config ~67

Save a new Artillery configuration or update an existing one.

Input Output Examples

Name	Type	Req	Description
content	string	yes	Artillery configuration as YAML or JSON string
description	string	—	Optional description
name	string	yes	Unique name for the config
tags	array	—	Optional tags for organization

No output schema declared.

No examples provided.

wizard_finalize ~78

Generate final Artillery config from completed wizard state. Optionally save and/or run it.

Input Output Examples

Name	Type	Req	Description
outputJson	string	—	Path for JSON results output
reportHtml	string	—	Path for HTML report output
runImmediately	boolean	—	If true, run the test immediately
state	object	yes	The completed wizard state

No output schema declared.

No examples provided.

wizard_start ~38

Start a new interactive wizard for building Artillery test configurations.

Input Output Examples

Name	Type	Req	Description
fromSavedConfig	string	—	Optional saved config name to use as starting point

No output schema declared.

No examples provided.

wizard_step ~52

Advance the wizard to the next step based on user input.

Input Output Examples

Name	Type	Req	Description
action	string	yes	The action to perform
state	object	yes	The current wizard state
value	—	yes	The value for the action

No output schema declared.

No examples provided.

On this page

Handy links

Scoring key

80+ high trust
60–79 medium
below 60 low

How we score

Score history · last 30 days

26 Jul 3 Aug

Day	Score
26 Jul	11
27 Jul	38
28 Jul	38
29 Jul	38
30 Jul	38
31 Jul	34
1 Aug	34
2 Aug	37
3 Aug	37