io.github.rog0x/testing
NPM · @ROG0X/MCP-TESTING-TOOLS
Test generation, mocks, coverage analysis for AI agents
Available components
Last scanned (5 hours ago)
Scores higher than 84% of npm 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 Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 30 of 92 dependencies flagged as unhealthy. 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 229 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability79
- 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 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
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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.
- 4 Nov 26 +1
- Stability: 0.97 → pass security
- 3 Nov 26 −1
- Stability: pass → 0.97 functional
- 28 Oct 26 +1
- Stability: 0.97 → pass security
- 27 Oct 26 −1
- Stability: pass → 0.97 functional
- 22 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- 21 Oct 26 +1
- Stability: 0.97 → pass security
- Security disclosure: fail → unverified ▼ functional
- 20 Oct 26 −1
- Stability: pass → 0.97 functional
- 17 Oct 26 +3
- Stability: 0.83 → pass security
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 6 Nov 2026 · Analysed npm/@rog0x/mcp-testing-tools@1.0.2
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 92 packages
| Packages resolved | 92 |
|---|---|
| Stale | 30 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
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.
How do I install the io.github.rog0x/testing MCP server?
io.github.rog0x/testing runs locally as an npm package, launched with npx -y @rog0x/mcp-testing-tools. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @rog0x/mcp-testing-tools
claude mcp add rog0x-testing -- npx -y @rog0x/mcp-testing-tools
What is the io.github.rog0x/testing MCP server?
io.github.rog0x/testing is an MCP server listed in the public MCP registry as io.github.rog0x/testing. Test generation, mocks, coverage analysis for AI agents. This page covers its npm package (@rog0x/mcp-testing-tools).
Is the io.github.rog0x/testing MCP server safe to use?
io.github.rog0x/testing scores 85 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 6 November 2026. It declares no install or post-install scripts. 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.rog0x/testing MCP server expose?
io.github.rog0x/testing exposes 5 tools: generate_tests, generate_mock_data, generate_api_mock, analyze_test_coverage, generate_assertions. Their descriptions and schemas cost roughly 664 tokens of context every time the server is loaded.
Is the io.github.rog0x/testing MCP server still maintained?
io.github.rog0x/testing is still listed as active in the MCP registry. We last reached this channel on 6 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.rog0x/testing MCP server under?
io.github.rog0x/testing declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the io.github.rog0x/testing MCP server?
VerifyMCP ran 16 checks on io.github.rog0x/testing, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.