Testing

Name: Testing
Author: rog0x

by rog0xversion 1.0.2i★ –iRuns on your computer

Registry nameio.github.rog0x/testing

Install

Overview

Description from the maker (original English)

Test generation, mocks, coverage analysis for AI agents

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs on your computer
Transport: stdio
Category: Other

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on your computer with your user’s permissions (files, network, apps).
The registry lists no key to fill in.

You need

npmNode.js installed (for the npx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

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

Run this in your terminal

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

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

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

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "testing": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@rog0x/mcp-testing-tools"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account rog0x, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
– Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
– Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
… Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Otheri

More stars than 0% of the other 32380 servers in this category
Published to the registry more recently than 4% of the other 32380 servers in this category
Basic checks equal to or better than 100% of the other 32380 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Testing safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (1.0.2) reached the registry 8 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, Dechonet MCP

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Spec Driven Development

by formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

Runs on your computer★ 440MITUpdated 14 months ago

Install

Remote Desktop Commander

by desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

Runs in the cloud★ 211Updated yesterday

Install

Dechonet MCP

by node-man

30 security tools for AI agents: phishing links, exposure maps, DNS, SSL, PQC, history, pivots.

Computer or cloudUpdated today

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

@rog0x/mcp-testing-tools

Testing and quality assurance tools for AI agents, exposed via the Model Context Protocol (MCP).

Tools

generate_tests

Generate test cases from a function signature. Produces four categories of tests as ready-to-run Jest or Vitest code:

Happy path -- valid inputs, expected outputs
Edge cases -- empty strings, zero values, null parameters
Error cases -- missing arguments, wrong types
Boundary values -- extreme numbers, large arrays, NaN

Parameters:

Name	Type	Required	Description
`signature`	string	Yes	Function signature, e.g. `async function fetchUser(id: number): Promise`
`framework`	string	No	`jest` or `vitest` (default: `vitest`)
`module_path`	string	No	Import path for the module under test (default: `./module`)

generate_mock_data

Generate realistic mock data for testing. Supported types:

name, email, address, date, uuid, phone, company, credit_card, ip

Parameters:

Name	Type	Required	Description
`type`	string	Yes	Data type to generate
`count`	number	No	Number of items (default: 10, max: 1000)
`locale`	string	No	`en` or `es` (default: `en`)
`types`	string[]	No	Generate mixed records with multiple field types

generate_api_mock

Generate mock API responses from a schema definition. Creates realistic JSON payloads for REST endpoints by inferring values from field names and types.

Parameters:

Name	Type	Required	Description
`endpoint`	string	Yes	API endpoint path
`method`	string	No	HTTP method (default: `GET`)
`fields`	object[]	Yes	Field schemas with `name`, `type`, optional `items`, `fields`, `nullable`, `enum`
`count`	number	No	Number of records (default: 1, max: 100)
`status_code`	number	No	HTTP status code (default: 200)
`wrap_in_envelope`	boolean	No	Wrap in `{ success, data, meta }` (default: true)

analyze_test_coverage

Analyze source code and test code to find untested functions. Prioritizes suggestions by:

Export status (public API surface)
Cyclomatic complexity estimate
Parameter count
Async functions (more error paths)

Parameters:

Name	Type	Required	Description
`source_code`	string	Yes	Source code to analyze
`test_code`	string	Yes	Existing test code
`source_file_name`	string	No	Filename label (default: `source.ts`)

generate_assertions

Generate detailed assertion code by comparing expected and actual values. Performs deep diff and produces per-field assertions with descriptive comments.

Parameters:

Name	Type	Required	Description
`expected`	string	Yes	Expected value as JSON string
`actual`	string	Yes	Actual value as JSON string
`label`	string	No	Description for the comparison
`framework`	string	No	`jest`, `vitest`, or `chai` (default: `jest`)
`deep`	boolean	No	Deep equality for objects/arrays (default: true)

Setup

npm install

npm run build

Usage with Claude Desktop

Add to your claude_desktop_config.json:

"mcpServers": { "testing-tools": { "command": "node", "args": ["path/to/mcp-testing-tools/dist/index.js"] } } }

License

MIT

Testing

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Otheri

Common questions

Alternatives

Spec Driven Development

Remote Desktop Commander

Dechonet MCP

README from the maker

@rog0x/mcp-testing-tools

Tools

generate_tests

generate_mock_data

generate_api_mock

analyze_test_coverage

generate_assertions

Setup

Usage with Claude Desktop

License