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.

Testorim

NPM · @TESTORIM/CLI · SCANNED SEP 26

AI browser tests from your coding agent: a verdict, failing steps, report, video and trace.

Available components

67 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 Security100
  • 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
  • No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency19
Schema Quality & AI Usability82
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 722 tokens (~120/item across 6 items; 6 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 Management3
  • Stability observed for 1 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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 7 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 Testorim MCP server?

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

npm · @testorim/cli

# add to Claude Code
claude mcp add sallar-ba-testorim -- npx -y @testorim/cli
// .cursor/mcp.json
{
  "mcpServers": {
    "sallar-ba-testorim": {
      "command": "npx",
      "args": [
        "-y",
        "@testorim/cli"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "sallar-ba-testorim": {
      "command": "npx",
      "args": [
        "-y",
        "@testorim/cli"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add sallar-ba-testorim -- npx -y @testorim/cli
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "sallar-ba-testorim": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@testorim/cli"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add sallar-ba-testorim --command npx --arg -y --arg @testorim/cli
# ~/.hermes/config.yaml
mcp_servers:
  sallar-ba-testorim:
    command: "npx"
    args: ["-y", "@testorim/cli"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "sallar-ba-testorim": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@testorim/cli"
      ]
    }
  }
}
# add to Vellum
assistant mcp add sallar-ba-testorim -t stdio -c npx -a -y @testorim/cli
// mcp.json
{
  "mcpServers": {
    "sallar-ba-testorim": {
      "command": "npx",
      "args": [
        "-y",
        "@testorim/cli"
      ]
    }
  }
}
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.

  • 26 Sept 26 +12
    • Tool safety: pass → unverified ▼ security
    • Known CVEs: unverified → pass ▲ 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.03 ▲ functional
    • Dependency health: unverified → pass ▲ functional
    • First check of Schema quality: unverified functional
    • Package version: 0.4.0 → 0.4.1 functional
  • 25 Sept 26 55

    First indexed and scored.

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 26 Sept 2026 · Analysed npm/@testorim/cli@0.4.1

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 0 packages
Packages resolved 0
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 6 exposed · ~506 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
cancel_run ~36

Stop a queued or running run. A cancelled run has no verdict.

NameTypeReqDescription
runIdstringyesRun id returned by run_test.

No output schema declared.

No examples provided.

create_project ~73

Create a project for a site so it can be tested. If the workspace already tests that address, the existing project is returned instead.

NameTypeReqDescription
baseUrlstringyesThe site's public address, for example https://staging.example.com.
namestring–A short name, for example the product's name.

No output schema declared.

No examples provided.

get_run ~38

Read a run's status, verdict, failing steps, report and evidence links.

NameTypeReqDescription
runIdstringyesRun id returned by run_test.

No output schema declared.

No examples provided.

list_projects ~30

List the projects (sites under test) in the API key's workspace, with each project's id and address.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_tests ~54

List the saved tests (procedures) of a project. A saved test replays its recorded steps without re-planning, so it is faster and repeatable.

NameTypeReqDescription
projectIdstringyesProject id from list_projects.

No output schema declared.

No examples provided.

run_test ~275

Run a test in a real browser and return the verdict, the failing steps with the reason for each, the written report and links to the evidence. Pass testId to replay a saved test, or description to test anything in plain English, for example: "Sign up with a new email address and check that the dashboard opens and says Welcome." Waits for the verdict unless wait is false.

NameTypeReqDescription
baseUrlstring–Run against this address instead of the project's own, for example a pull request's preview deployment. Must be publicly reachable.
descriptionstring–What a visitor should do and what must be true at the end, in plain English. Name the buttons, fields and text as they appear on the page.
expectationstring–Use fail for a negative test (for example, a wrong password must be refused). Default pass.
projectIdstring–Project id from list_projects. Optional when testId is given.
testIdstring–A saved test id from list_tests.
timeoutSecondsinteger–How long to wait for the verdict before returning the run as still in progress (default 600).
waitboolean–Wait for the verdict (default true). With false, returns the run id at once; read it later with get_run.

No output schema declared.

No examples provided.

Common questions

What is the Testorim MCP server?

Testorim is an MCP server listed in the public MCP registry as io.github.sallar-ba/testorim. AI browser tests from your coding agent: a verdict, failing steps, report, video and trace. This page covers its npm package (@testorim/cli).

Is the Testorim MCP server safe to use?

Testorim scores 67 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 Testorim MCP server expose?

Testorim exposes 6 tools: list_projects, list_tests, run_test, get_run, cancel_run, create_project. Their descriptions and schemas cost roughly 506 tokens of context every time the server is loaded.

Is the Testorim MCP server still maintained?

Testorim 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 Testorim MCP server under?

Testorim declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.