# io.github.rog0x/testing (npm · @rog0x/mcp-testing-tools)

Test generation, mocks, coverage analysis for AI agents

- Trust score: 68/100 (medium)
- Change this week: +22
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- npm · `@rog0x/mcp-testing-tools`: 68/100 (this document), [markdown](https://verifymcp.io/servers/rog0x-testing/rog0x-mcp-testing-tools.md), [page](https://verifymcp.io/servers/rog0x-testing/rog0x-mcp-testing-tools)

## Channel facts

- Registry: `npm`
- Package: `@rog0x/mcp-testing-tools`
- Version: `1.0.2`
- 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-08-03.

- **Supply Chain Security**: 86/100
  - No malware found by supply-chain analysis.
  - Only part of the dependency tree could be resolved (94 of 98), so this covers what we could see, not the whole tree.
  - No install/post-install scripts declared.
  - Only part of the dependency tree could be resolved (94 of 98), so this covers what we could see, not the whole tree.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 134 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 74/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 664 tokens (~132/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add rog0x-testing -- npx -y @rog0x/mcp-testing-tools
```

### Codex

```bash
codex mcp add rog0x-testing -- npx -y @rog0x/mcp-testing-tools
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add rog0x-testing --command npx --arg -y --arg @rog0x/mcp-testing-tools
```

### Hermes

```yaml
mcp_servers:
  rog0x-testing:
    command: "npx"
    args: ["-y", "@rog0x/mcp-testing-tools"]
```

### Other

```json
{
  "mcpServers": {
    "rog0x-testing": {
      "command": "npx",
      "args": [
        "-y",
        "@rog0x/mcp-testing-tools"
      ]
    }
  }
}
```

## 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-08-03 (score 68, +3)

- [functional improvement] Stability: unverified → 0.23

### 2026-08-02 (score 65, +60)

- [security regression] Provenance: unverified → fail
- [security improvement] Install scripts: unverified → pass
- [security improvement] Known CVEs: unverified → partial
- [security improvement] Malware scan: unverified → pass
- [security] Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window).
- [functional improvement] Schema quality: unverified → excellent
- [functional improvement] License: unverified → pass
- [functional improvement] Dependency health: unverified → partial
- [functional improvement] Maintenance: unverified → pass
- [functional improvement] MCP protocol: unverified → pass
- [functional improvement] Tool coverage: unverified → 100
- [functional] Licence: MIT

### 2026-08-01 (score 5, −15)

- [functional regression] Tool coverage: 100 → unverified

### 2026-07-31 (score 20, +14)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 6, −40)

- [security regression] Malware scan: pass → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional] First check of Schema quality: unverified

### 2026-07-27 (score 46)

First indexed and scored.

## MCP tools (5)

### `generate_tests` (~105 tokens)

Generate test cases from a function signature. Produces happy path, edge cases, error cases, and boundary value tests as Jest/Vitest test code.

Input parameters:

- `framework` (string): Test framework to generate for (default: vitest)
- `module_path` (string): Import path for the module under test (default: "./module")
- `signature` (string, required): The function signature to generate tests for, e.g. "export async function fetchUser(id: number): Promise<User>"

### `generate_mock_data` (~150 tokens)

Generate realistic mock data: names, emails, addresses, dates, UUIDs, phone numbers, company names, credit cards (fake), IP addresses. Configurable count and locale.

Input parameters:

- `count` (number): Number of items to generate (default: 10, max: 1000)
- `locale` (string): Locale for generated data: "en" or "es" (default: "en")
- `type` (string, required): Type of data to generate: name, email, address, date, uuid, phone, company, credit_card, ip
- `types` (array): Generate mixed records with multiple field types (alternative to single type). Each record will have all specified fields.

### `generate_api_mock` (~181 tokens)

Generate mock API responses from a schema. Creates realistic JSON responses for REST endpoints based on field names and types.

Input parameters:

- `count` (number): Number of records to generate (default: 1, max: 100)
- `endpoint` (string, required): API endpoint path, e.g. "/api/v1/users"
- `fields` (array, required): Array of field schemas. Each field has: name (string), type (string|number|boolean|date|array|object), optional items (for arrays), optional fields (for nested objects), optional nullable, optional e…
- `method` (string): HTTP method (default: GET)
- `status_code` (number): HTTP status code for the response (default: 200)
- `wrap_in_envelope` (boolean): Wrap response in { success, data, meta } envelope (default: true)

### `analyze_test_coverage` (~96 tokens)

Parse source code and test code to identify untested functions. Suggests which functions need tests most based on complexity, export status, and parameter count.

Input parameters:

- `source_code` (string, required): The source code to analyze for functions
- `source_file_name` (string): Filename for the source (used in output, default: "source.ts")
- `test_code` (string, required): The test code to check which functions are already tested

### `generate_assertions` (~132 tokens)

Given expected and actual values (as JSON strings), generate detailed assertion code with descriptive messages. Supports deep object comparison, array comparison, and type checking.

Input parameters:

- `actual` (string, required): The actual value as a JSON string (or plain string for primitives)
- `deep` (boolean): Use deep equality for objects/arrays (default: true)
- `expected` (string, required): The expected value as a JSON string (or plain string for primitives)
- `framework` (string): Assertion framework to generate for (default: jest)
- `label` (string): Descriptive label for the comparison (default: "value comparison")

## Diagnostics

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

## Score history

- 2026-08-03: 68
- 2026-08-02: 65
- 2026-08-01: 5
- 2026-07-31: 20
- 2026-07-30: 6
- 2026-07-28: 46
- 2026-07-27: 46

## Links

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