# Stratz (npm · @pipeworx/mcp-stratz)

STRATZ Dota 2 MCP.

- Trust score: 77/100 (medium)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `gateway.pipeworx.io`: 76/100, [markdown](https://verifymcp.io/servers/pipeworx-io-stratz/stratz-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-stratz/stratz-mcp)
- npm · `@pipeworx/mcp-stratz`: 77/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-stratz/pipeworx-mcp-stratz.md), [page](https://verifymcp.io/servers/pipeworx-io-stratz/pipeworx-mcp-stratz)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-stratz`
- Version: `0.2.0`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-stratz).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 6 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 67/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1350 tokens (~112/item across 12 items; 12 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 82/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 46% of tool parameters carry a description.
- **Tool Safety**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "graphql" implies "send" and declares no destructiveHint at all, which the MCP spec reads as destructive by default.
  - An AI judge read all 13 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

**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

### How do I install the Stratz MCP server?

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

### Claude

```bash
claude mcp add pipeworx-io-stratz -- npx -y @pipeworx/mcp-stratz
```

### Cursor

```json
{
  "mcpServers": {
    "pipeworx-io-stratz": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-stratz"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "pipeworx-io-stratz": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-stratz"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add pipeworx-io-stratz -- npx -y @pipeworx/mcp-stratz
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "pipeworx-io-stratz": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@pipeworx/mcp-stratz"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add pipeworx-io-stratz --command npx --arg -y --arg @pipeworx/mcp-stratz
```

### Hermes

```yaml
mcp_servers:
  pipeworx-io-stratz:
    command: "npx"
    args: ["-y", "@pipeworx/mcp-stratz"]
```

### Netclaw

```json
{
  "McpServers": {
    "pipeworx-io-stratz": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@pipeworx/mcp-stratz"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add pipeworx-io-stratz -t stdio -c npx -a -y @pipeworx/mcp-stratz
```

### Other

```json
{
  "mcpServers": {
    "pipeworx-io-stratz": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-stratz"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-02 (score 77, 0)

- [functional regression] Security disclosure: unverified → fail

### 2026-11-01 (score 77, 0)

- [functional regression] Security disclosure: fail → unverified

### 2026-10-30 (score 77, 0)

- [functional regression] Security disclosure: unverified → fail

### 2026-10-29 (score 77)

First indexed and scored.

## MCP tools (12)

### `graphql` (~177 tokens)

Send an arbitrary GraphQL query (with optional variables) directly to the STRATZ API at api.stratz.com/graphql. Use when no named tool covers the data you need. Field names are camelCase and must match the STRATZ schema exactly (e.g. numLastHits, goldPerMinute, constants { gameModes }); a query naming an unknown field fails with "Cannot query field", so introspect the type (`{ __type(name: "MatchPlayerType") { fields { name } } }`) before guessing. Requires a STRATZ Bearer token.

Input parameters:

- `_apiKey` (string, required): Your own STRATZ API token (BYO — Pipeworx does not supply one). Free at https://stratz.com/api after Steam sign-in.
- `query` (string, required)
- `variables` (object)

### `hero` (~111 tokens)

Fetch a single Dota 2 hero's full detail by numeric hero id — display name, short name, roles, and base/gain stats (armor, strength, agility, intelligence, primary attribute, attack type/range/rate, starting damage, move speed, vision range).

Input parameters:

- `_apiKey` (string, required): Your own STRATZ API token (BYO — Pipeworx does not supply one). Free at https://stratz.com/api after Steam sign-in.
- `id` (number, required)

### `heroes` (~83 tokens)

Fetch the complete list of all Dota 2 heroes from STRATZ, returning each hero's numeric id, name, displayName, and shortName. No arguments required.

Input parameters:

- `_apiKey` (string, required): Your own STRATZ API token (BYO — Pipeworx does not supply one). Free at https://stratz.com/api after Steam sign-in.

### `hero_stats` (~119 tokens)

Fetch daily win-rate and pick-rate statistics for a Dota 2 hero by numeric hero_id, optionally filtered to a rank bracket (e.g. HERALD, ARCHON, LEGEND, DIVINE, IMMORTAL). Returns matchCount and winCount per day.

Input parameters:

- `_apiKey` (string, required): Your own STRATZ API token (BYO — Pipeworx does not supply one). Free at https://stratz.com/api after Steam sign-in.
- `hero_id` (number, required)
- `rank` (string)

### `match` (~107 tokens)

Fetch full details of a single Dota 2 match by numeric match id — duration, start time, Radiant/Dire teams, game mode, lobby type, and per-player stats (heroId, K/D/A, GPM, XPM, level).

Input parameters:

- `_apiKey` (string, required): Your own STRATZ API token (BYO — Pipeworx does not supply one). Free at https://stratz.com/api after Steam sign-in.
- `id` (number, required)

### `player` (~89 tokens)

Fetch a Dota 2 player's profile by Steam account id — Steam name, profile URL, avatar, total match count, and win count via STRATZ.

Input parameters:

- `_apiKey` (string, required): Your own STRATZ API token (BYO — Pipeworx does not supply one). Free at https://stratz.com/api after Steam sign-in.
- `steam_account_id` (number, required)

### `player_matches` (~143 tokens)

Fetch a Dota 2 player's recent match history by Steam account id. Returns one row per match: match id, duration, start time, game mode, Radiant win flag, plus this player's heroId, side, win/loss, K/D/A, last hits, GPM/XPM, level and IMP. Supports pagination via take/skip.

Input parameters:

- `_apiKey` (string, required): Your own STRATZ API token (BYO — Pipeworx does not supply one). Free at https://stratz.com/api after Steam sign-in.
- `skip` (number)
- `steam_account_id` (number, required)
- `take` (number)

### `player_heroes` (~110 tokens)

Fetch the top heroes played by a Dota 2 player (by Steam account id), ranked by match count — returns heroId, matchCount, and winCount for up to `take` heroes (default 20).

Input parameters:

- `_apiKey` (string, required): Your own STRATZ API token (BYO — Pipeworx does not supply one). Free at https://stratz.com/api after Steam sign-in.
- `steam_account_id` (number, required)
- `take` (number)

### `live_matches` (~83 tokens)

Fetch all currently live Dota 2 matches from STRATZ, returning matchId, radiantTeamId, direTeamId, and current game time. No arguments required.

Input parameters:

- `_apiKey` (string, required): Your own STRATZ API token (BYO — Pipeworx does not supply one). Free at https://stratz.com/api after Steam sign-in.

### `tournament` (~86 tokens)

Fetch details for a single Dota 2 tournament (league) by numeric id — display name, description, tier, start/end dates, and prize pool.

Input parameters:

- `_apiKey` (string, required): Your own STRATZ API token (BYO — Pipeworx does not supply one). Free at https://stratz.com/api after Steam sign-in.
- `id` (number, required)

### `tournaments` (~111 tokens)

List Dota 2 tournaments (leagues) from STRATZ, most recent start date first (up to 50) — id, name, tier, start/end dates and prize pool. Pass only_premium=true to restrict to MAJOR and INTERNATIONAL tier events.

Input parameters:

- `_apiKey` (string, required): Your own STRATZ API token (BYO — Pipeworx does not supply one). Free at https://stratz.com/api after Steam sign-in.
- `only_premium` (boolean)

### `meta` (~79 tokens)

Fetch current Dota 2 meta constants from STRATZ: the list of game versions (patches) with their id and name. No arguments required.

Input parameters:

- `_apiKey` (string, required): Your own STRATZ API token (BYO — Pipeworx does not supply one). Free at https://stratz.com/api after Steam sign-in.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/pipeworx-io-stratz/pipeworx-mcp-stratz#diagnostics

## Score history

- 2026-11-05: 77
- 2026-11-04: 77
- 2026-11-03: 77
- 2026-11-02: 77
- 2026-11-01: 77
- 2026-10-31: 77
- 2026-10-30: 77
- 2026-10-29: 77

## Common questions

### What is the Stratz MCP server?

Stratz is an MCP server listed in the public MCP registry as io.github.pipeworx-io/stratz. STRATZ Dota 2 MCP. This page covers its npm package (@pipeworx/mcp-stratz).

### Is the Stratz MCP server safe to use?

Stratz scores 77 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 Stratz MCP server expose?

Stratz exposes 12 tools: graphql, hero, heroes, hero_stats, match, and 7 more. Their descriptions and schemas cost roughly 1,298 tokens of context every time the server is loaded.

### Is the Stratz MCP server still maintained?

Stratz 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 Stratz MCP server under?

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

## Links

- npm package: https://www.npmjs.com/package/@pipeworx/mcp-stratz
- Socket report: https://socket.dev/npm/package/@pipeworx/mcp-stratz
- Repository: https://github.com/pipeworx-io/mcp-stratz
- Website: https://pipeworx.io/packs/stratz
- Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-stratz/pipeworx-mcp-stratz.xml
- Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-stratz/pipeworx-mcp-stratz.json
- HTML version of this page: https://verifymcp.io/servers/pipeworx-io-stratz/pipeworx-mcp-stratz