Jarroba Tools · Test audit
NPM · @JARROBA/MCP-TESTS · SCANNED SEP 26
Audits tests instead of writing them: what each one really asserts. 4 tools, local.
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 → 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
- 31 of 97 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
- Repository check failed: the declared repository URL returned HTTP 404. See how to fix → View diagnostics → Fail
- 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 9 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability66
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 793 tokens (~198/item across 4 items; 4 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 Management47
- Stability observed for 14 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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 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
How do I install the Jarroba Tools · Test audit MCP server?
Jarroba Tools · Test audit runs locally as an npm package, launched with npx -y @jarroba/mcp-tests. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @jarroba/mcp-tests
claude mcp add invarato-jarroba-tools-tests -- npx -y @jarroba/mcp-tests
{
"mcpServers": {
"invarato-jarroba-tools-tests": {
"command": "npx",
"args": [
"-y",
"@jarroba/mcp-tests"
]
}
}
} {
"servers": {
"invarato-jarroba-tools-tests": {
"command": "npx",
"args": [
"-y",
"@jarroba/mcp-tests"
]
}
}
} codex mcp add invarato-jarroba-tools-tests -- npx -y @jarroba/mcp-tests
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"invarato-jarroba-tools-tests": {
"type": "local",
"command": [
"npx",
"-y",
"@jarroba/mcp-tests"
],
"enabled": true
}
}
} openclaw mcp add invarato-jarroba-tools-tests --command npx --arg -y --arg @jarroba/mcp-tests
mcp_servers:
invarato-jarroba-tools-tests:
command: "npx"
args: ["-y", "@jarroba/mcp-tests"] {
"McpServers": {
"invarato-jarroba-tools-tests": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@jarroba/mcp-tests"
]
}
}
} assistant mcp add invarato-jarroba-tools-tests -t stdio -c npx -a -y @jarroba/mcp-tests
{
"mcpServers": {
"invarato-jarroba-tools-tests": {
"command": "npx",
"args": [
"-y",
"@jarroba/mcp-tests"
]
}
}
} 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.
- 26 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 +15
- Malware scan: unverified → pass ▲ security
- 16 Sept 26 −14
- Malware scan: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Stability: unverified → 0.13 ▲ functional
- First check of Schema quality: unverified functional
- Schema quality: excellent → good functional
- Package version: 0.1.2 → 0.1.4 functional
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 26 Sept 2026 · Analysed npm/@jarroba/mcp-tests@0.1.4
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 97 packages
| Packages resolved | 97 |
|---|---|
| Stale | 31 |
| 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 →
test_audit ~216
Audit a test file and say, case by case, what it ACTUALLY checks: which ones assert about a value, which only check that something exists, which assert nothing at all, and which are disabled. Returns the EVIDENCE behind each verdict (the assertions it found) so you can check the checker. TypeScript, JavaScript, Python, Java and Go. Executes nothing. Run it on the tests you just wrote, BEFORE you hand them over: told to "make the tests pass", widening a matcher is cheaper than fixing the bug, and this is what notices.
| Name | Type | Req | Description |
|---|---|---|---|
| dialects | array | – | Your own assertion helpers. If your team has a home-made expect(), declare it here and it will stop coming back as "indeterminate". |
| language | string | – | Required if you pass `text` without `path`. |
| path | string | – | Path to the test file. The language is inferred from the extension. |
| text | string | – | The test file as text. Alternative to `path`. |
No output schema declared.
No examples provided.
test_cases ~188
From a TYPE to the cases worth testing, with no model involved: equivalence partitions and boundary values derived from a TypeScript signature or a JSON Schema. For each parameter it returns the TECHNIQUE that applies and why — boundary values only mean something where there is an ordering, so they are NOT applied to a boolean or an enum. It adds the properties that can be asserted without knowing the domain, plus a fast-check test ready to paste. Use it BEFORE writing the tests, so you do not miss the cases everyone misses.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | – | Function name for the generated code. Inferred from the signature if you pass one. |
| schema | string | – | JSON Schema (an object with `properties`). Alternative to `signature`. |
| signature | string | – | TypeScript signature, e.g. function calculate(price: number, kind: 'A' | 'B'): number |
No output schema declared.
No examples provided.
test_debt ~148
A project's DISABLED-test debt, WITH ITS AGE. Walks the folder, finds every `it.skip`, `xit`, `@Ignore`, `@pytest.mark.skip` or `t.Skip`, and dates it with `git blame`. None of those cases appears in a coverage report, because as far as the runner is concerned they do not exist: this is the debt nobody measures and the one that lasts longest — disabled 'to fix later', and later never comes. Sorted oldest first, which is what makes it actionable.
| Name | Type | Req | Description |
|---|---|---|---|
| folder | string | yes | Root of the project (or subtree) to review. |
| maxFiles | integer | – | Cap on how many test files to read. |
No output schema declared.
No examples provided.
test_diff_audit ~183
Compare TWO versions of the same test file and say whether the change STRENGTHENED or WEAKENED the safety net: widened matchers (toBe -> toContain -> toBeGreaterThan), assertions that disappeared, and cases that stopped running. Call it on your own work after touching tests, and above all after fixing a red suite: reaching green by softening an assertion is cheaper than fixing the bug, and this is what catches it. Executes nothing.
| Name | Type | Req | Description |
|---|---|---|---|
| after | string | – | New version, as text. |
| afterPath | string | – | Path to the new version. |
| before | string | – | Previous version, as text. |
| beforePath | string | – | Path to the previous version (e.g. what `git show HEAD:file` produced). |
| language | string | – | Required if you pass the texts without paths. |
No output schema declared.
No examples provided.
What is the Jarroba Tools · Test audit MCP server?
Jarroba Tools · Test audit is an MCP server listed in the public MCP registry as io.github.Invarato/jarroba-tools-tests. Audits tests instead of writing them: what each one really asserts. 4 tools, local. This page covers its npm package (@jarroba/mcp-tests).
Is the Jarroba Tools · Test audit MCP server safe to use?
Jarroba Tools · Test audit scores 70 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 26 September 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 Jarroba Tools · Test audit MCP server expose?
Jarroba Tools · Test audit exposes 4 tools: test_audit, test_diff_audit, test_cases, test_debt. Their descriptions and schemas cost roughly 735 tokens of context every time the server is loaded.
Is the Jarroba Tools · Test audit MCP server still maintained?
Jarroba Tools · Test audit is still listed as active in the MCP registry. We last reached this channel on 26 September 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 Jarroba Tools · Test audit MCP server under?
Jarroba Tools · Test audit declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.