Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.Dave-London/test

NPM · @PARETOOLS/TEST · SCANNED SEP 20

Auto-detects test framework (pytest, jest, vitest) and returns structured results.

Available components

0 this week 93 Trust /100
Trust breakdown (7 categories)

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 96 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to Dave-London/Pare). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 32 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability70
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 289 tokens (~144/item across 2 items; 2 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management93
  • Stability observed for 28 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
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 3 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
Install

How do I install the io.github.Dave-London/test MCP server?

io.github.Dave-London/test runs locally as an npm package, launched with npx -y @paretools/test. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @paretools/test

# add to Claude Code
claude mcp add dave-london-test -- npx -y @paretools/test
// .cursor/mcp.json
{
  "mcpServers": {
    "dave-london-test": {
      "command": "npx",
      "args": [
        "-y",
        "@paretools/test"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "dave-london-test": {
      "command": "npx",
      "args": [
        "-y",
        "@paretools/test"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add dave-london-test -- npx -y @paretools/test
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dave-london-test": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@paretools/test"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add dave-london-test --command npx --arg -y --arg @paretools/test
# ~/.hermes/config.yaml
mcp_servers:
  dave-london-test:
    command: "npx"
    args: ["-y", "@paretools/test"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "dave-london-test": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@paretools/test"
      ]
    }
  }
}
# add to Vellum
assistant mcp add dave-london-test -t stdio -c npx -a -y @paretools/test
// mcp.json
{
  "mcpServers": {
    "dave-london-test": {
      "command": "npx",
      "args": [
        "-y",
        "@paretools/test"
      ]
    }
  }
}
Changelog

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.

  • 19 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.

  • 17 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.

  • 16 Sept 26 −3
    • Stability: pass → 0.80 functional
  • 15 Sept 26 0
    • Stability: 0.97 → pass security
  • 14 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

  • 12 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.

  • 10 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.

  • 9 Sept 26 −3
    • Stability: pass → 0.80 functional
Diagnostics

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 20 Sept 2026 · Analysed npm/@paretools/test@0.8.0

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo Dave-London/Pare
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/Dave-London/Pare/.github/workflows/release.yml@refs/heads/main
Rekor log index 949169124
Predicate type https://slsa.dev/provenance/v1
Subject digest sha512:5d6cc2560264deabfea175572887130f9ff35b819f4b5f190b7c51cd4f173a83b29eff0f9ebecddf7f656830b7b2182a4dc21f1bf871fcb9efd4f4397

Background: How many MCP packages publish verified provenance →

Dependencies 96 packages
Packages resolved 96
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 2 exposed · ~241 tokens

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 →

Tool Tokens
coverage ~86

Runs tests with coverage and returns structured coverage summary per file. Use instead of running test coverage commands in the terminal.

NameTypeReqDescription
compactbooleanAuto-compact when structured output exceeds raw CLI tokens. Set false to always get full schema.
frameworkstringForce a specific framework instead of auto-detecting
pathstringProject root path (default: cwd)
NameTypeReqDescription
filesarray
frameworkstringyes
summaryobjectyes
totalFilesnumber

No examples provided.

run ~155

Auto-detects test framework (pytest/jest/vitest/mocha), runs tests, returns structured results with failures. Use instead of running pytest/jest/vitest/mocha in the terminal.

NameTypeReqDescription
argsarrayAdditional arguments to pass to the test runner
compactbooleanAuto-compact when structured output exceeds raw CLI tokens. Set false to always get full schema.
filterstringTest filter pattern (file path or test name pattern)
frameworkstringForce a specific framework instead of auto-detecting
pathstringProject root path (default: cwd)
updateSnapshotsbooleanUpdate snapshots (vitest/jest only, adds -u flag)
NameTypeReqDescription
failuresarrayyes
frameworkstringyes
summaryobjectyes

No examples provided.

Common questions

What is the io.github.Dave-London/test MCP server?

io.github.Dave-London/test is an MCP server listed in the public MCP registry as io.github.Dave-London/test. Auto-detects test framework (pytest, jest, vitest) and returns structured results. This page covers its npm package (@paretools/test).

Is the io.github.Dave-London/test MCP server safe to use?

io.github.Dave-London/test scores 93 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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.Dave-London/test MCP server expose?

io.github.Dave-London/test exposes 2 tools: run, coverage. Their descriptions and schemas cost roughly 241 tokens of context every time the server is loaded.

Is the io.github.Dave-London/test MCP server still maintained?

io.github.Dave-London/test is still listed as active in the MCP registry. We last reached this channel on 20 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 io.github.Dave-London/test MCP server under?

io.github.Dave-London/test declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.