io.github.rog0x/testing
NPM · @ROG0X/MCP-TESTING-TOOLS · SCANNED AUG 3
Test generation, mocks, coverage analysis for AI agents
Available components
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 Security86
- No malware found by supply-chain analysis.Pass
- Only part of the dependency tree could be resolved (94 of 98), so this covers what we could see, not the whole tree.Partial
- No install/post-install scripts declared.Pass
- Only part of the dependency tree could be resolved (94 of 98), so this covers what we could see, not the whole tree. View diagnostics → Partial
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 134 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability74
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- 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 Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
npm · @rog0x/mcp-testing-tools
claude mcp add rog0x-testing -- npx -y @rog0x/mcp-testing-tools
codex mcp add rog0x-testing -- npx -y @rog0x/mcp-testing-tools
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"rog0x-testing": {
"type": "local",
"command": [
"npx",
"-y",
"@rog0x/mcp-testing-tools"
],
"enabled": true
}
}
} openclaw mcp add rog0x-testing --command npx --arg -y --arg @rog0x/mcp-testing-tools
mcp_servers:
rog0x-testing:
command: "npx"
args: ["-y", "@rog0x/mcp-testing-tools"] {
"mcpServers": {
"rog0x-testing": {
"command": "npx",
"args": [
"-y",
"@rog0x/mcp-testing-tools"
]
}
}
} 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.
- 3 Aug 26 +3
- Stability: unverified → 0.23 ▲ functional
- 2 Aug 26 +60
- Provenance: unverified → fail ▼ security
- Install scripts: unverified → pass ▲ security
- Known CVEs: unverified → partial ▲ security
- Malware scan: unverified → pass ▲ security
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- Schema quality: unverified → excellent ▲ functional
- License: unverified → pass ▲ functional
- Dependency health: unverified → partial ▲ functional
- Maintenance: unverified → pass ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Licence: MIT functional
- 1 Aug 26 −15
- Tool coverage: 100 → unverified ▼ functional
- 31 Jul 26 +14
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 −40
- Malware scan: pass → unverified ▼ security
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 27 Jul 26 46
First indexed and scored.
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 npm/@rog0x/[email protected]
Provenance none
Ecosystem: npm · Outcome: none
Dependencies 94 packages
94 packages in the resolved dependency tree · 94 deprecated · 29 stale.
The dependency tree was only partially resolved, so these counts may be incomplete.
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.
analyze_test_coverage ~96
Parse source code and test code to identify untested functions. Suggests which functions need tests most based on complexity, export status, and parameter count.
| Name | Type | Req | Description |
|---|---|---|---|
| source_code | string | yes | The source code to analyze for functions |
| source_file_name | string | — | Filename for the source (used in output, default: "source.ts") |
| test_code | string | yes | The test code to check which functions are already tested |
No output schema declared.
No examples provided.
generate_api_mock ~181
Generate mock API responses from a schema. Creates realistic JSON responses for REST endpoints based on field names and types.
| Name | Type | Req | Description |
|---|---|---|---|
| count | number | — | Number of records to generate (default: 1, max: 100) |
| endpoint | string | yes | API endpoint path, e.g. "/api/v1/users" |
| fields | array | yes | 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) |
No output schema declared.
No examples provided.
generate_assertions ~132
Given expected and actual values (as JSON strings), generate detailed assertion code with descriptive messages. Supports deep object comparison, array comparison, and type checking.
| Name | Type | Req | Description |
|---|---|---|---|
| actual | string | yes | The actual value as a JSON string (or plain string for primitives) |
| deep | boolean | — | Use deep equality for objects/arrays (default: true) |
| expected | string | yes | 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") |
No output schema declared.
No examples provided.
generate_mock_data ~150
Generate realistic mock data: names, emails, addresses, dates, UUIDs, phone numbers, company names, credit cards (fake), IP addresses. Configurable count and locale.
| Name | Type | Req | Description |
|---|---|---|---|
| count | number | — | Number of items to generate (default: 10, max: 1000) |
| locale | string | — | Locale for generated data: "en" or "es" (default: "en") |
| type | string | yes | 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. |
No output schema declared.
No examples provided.
generate_tests ~105
Generate test cases from a function signature. Produces happy path, edge cases, error cases, and boundary value tests as Jest/Vitest test code.
| Name | Type | Req | Description |
|---|---|---|---|
| framework | string | — | Test framework to generate for (default: vitest) |
| module_path | string | — | Import path for the module under test (default: "./module") |
| signature | string | yes | The function signature to generate tests for, e.g. "export async function fetchUser(id: number): Promise<User>" |
No output schema declared.
No examples provided.