io.github.kosiakMD/artillery-mcp
OCI · DOCKER.IO/KOSIAKMD/ARTILLERY-MCP:0.1.7 · 3 COMPONENTS
MCP server for Artillery 2.x — full flags, Fargate, raw-text parser, project launcher (MIT)
Last scanned (7 minutes ago)
Scores higher than 85% of OCI servers
Category Testing and QA
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 Security0
- No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
- Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Build provenance not yet verified. View diagnostics → Unverified
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 204 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability76
- AI-judged instruction clarity (good).Pass
- 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
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
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "delete_config" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 18 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
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.
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.
- 5 Nov 26 0
- Provenance: fail → unverified ▼ security
- 1 Nov 26 0
- Stability: 0.97 → pass security
- 31 Oct 26 0
- Stability: pass → 0.97 functional
- 17 Oct 26 +1
- Stability: 0.87 → pass security
- 16 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Oct 26 −2
- Stability: pass → 0.83 functional
- 14 Oct 26 0
- Stability: 0.97 → pass security
- 13 Oct 26 +1
- Security disclosure: unverified → fail ▼ functional
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 5 Nov 2026 · Analysed oci/docker.io/kosiakmd/artillery-mcp:0.1.7
Provenance Inconclusive
We could not complete the check, so nothing is claimed either way. This is a gap on our side, not a finding about the package.
| Result | Inconclusive |
|---|---|
| Ecosystem | oci |
| Reason | Attestation not fetched |
Background: How many MCP packages publish verified provenance →
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 →
compare_results ~55
Compare two Artillery test results to detect performance regressions.
| 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.
| 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.
| 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 schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_configs ~28
List all saved Artillery configurations.
| 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.
| 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).
| 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.
| 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.
| 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.
| 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.
| 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.
| 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).
| 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.
| 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.
| 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.
| 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.
| 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.
| 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.
How do I install the io.github.kosiakMD/artillery-mcp server?
io.github.kosiakMD/artillery-mcp runs locally as a container image, launched with docker run --rm -i -e ARTILLERY_CLOUD_API_KEY -e ARTILLERY_MCP_CONFIG docker.io/kosiakmd/artillery-mcp:0.1.7. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.
oci · docker.io/kosiakmd/artillery-mcp:0.1.7
claude mcp add kosiakmd-artillery-mcp -- docker run --rm -i -e ARTILLERY_CLOUD_API_KEY -e ARTILLERY_MCP_CONFIG docker.io/kosiakmd/artillery-mcp:0.1.7
This image reads ARTILLERY_CLOUD_API_KEY and ARTILLERY_MCP_CONFIG. Set them in your client's env block for this server; docker run -e passes each one through to the container.
What is the io.github.kosiakMD/artillery-mcp server?
io.github.kosiakMD/artillery-mcp is listed in the public MCP registry as io.github.kosiakMD/artillery-mcp. MCP server for Artillery 2.x, full flags, Fargate, raw-text parser, project launcher (MIT). This page covers its container image (docker.io/kosiakmd/artillery-mcp:0.1.7).
Is the io.github.kosiakMD/artillery-mcp server safe to use?
io.github.kosiakMD/artillery-mcp scores 52 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 io.github.kosiakMD/artillery-mcp server expose?
io.github.kosiakMD/artillery-mcp exposes 18 tools: run_test_from_file, run_test_inline, quick_test, list_capabilities, parse_results, and 13 more. Their descriptions and schemas cost roughly 1,711 tokens of context every time the server is loaded.
Is the io.github.kosiakMD/artillery-mcp server still maintained?
io.github.kosiakMD/artillery-mcp is still listed as active in the MCP registry. We last reached this channel on 5 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 io.github.kosiakMD/artillery-mcp server under?
io.github.kosiakMD/artillery-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.