# e2e (npm · e2e)

Open live web and mobile app sessions from an e2e project to inspect the app and try locators.

- Trust score: 83/100 (high trust)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-17

## Components

- npm · `e2e`: 83/100 (this document), [markdown](https://verifymcp.io/servers/tester-army-e2e/e2e.md), [page](https://verifymcp.io/servers/tester-army-e2e/e2e)

## Channel facts

- Registry: `npm`
- Package: `e2e`
- Version: `0.21.2`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-17.

- **Supply Chain Security**: 99/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 8 of 79 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 100/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to tester-army/e2e).
  - Clear OSI-approved license (Apache-2.0).
  - Actively maintained (last published 0 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 80/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 1069 tokens (~82/item across 13 items; 4 tools + 9 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 3/100
  - Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the e2e MCP server?

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

### Claude

```bash
claude mcp add tester-army-e2e -- npx -y e2e
```

### Cursor

```json
{
  "mcpServers": {
    "tester-army-e2e": {
      "command": "npx",
      "args": [
        "-y",
        "e2e"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "tester-army-e2e": {
      "command": "npx",
      "args": [
        "-y",
        "e2e"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add tester-army-e2e -- npx -y e2e
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "tester-army-e2e": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "e2e"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add tester-army-e2e --command npx --arg -y --arg e2e
```

### Hermes

```yaml
mcp_servers:
  tester-army-e2e:
    command: "npx"
    args: ["-y", "e2e"]
```

### Netclaw

```json
{
  "McpServers": {
    "tester-army-e2e": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "e2e"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add tester-army-e2e -t stdio -c npx -a -y e2e
```

### Other

```json
{
  "mcpServers": {
    "tester-army-e2e": {
      "command": "npx",
      "args": [
        "-y",
        "e2e"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-17 (score 83, +1)

No change was recorded against any check on this day. Stability & Change Management went from 0 to 3. That category is still filling its 30-day observation window: 0 days of observed history at the previous scan, 1 at this one. The score rises as the window fills, whether or not the server changes. Other categories moved too: Supply Chain Security fell 1.

### 2026-10-16 (score 82)

First indexed and scored.

## MCP tools (4)

### `open_session` (~206 tokens)

Open a live session on one target of an e2e project: loads the config, starts the app command the target declares (if any), boots the engine (a browser, a simulator), opens the app URL, and returns the session id, the catalog of tools it can run, and the first observation. Several sessions can be open at once, one per agent, each with its own engine: pass the returned session id to every later call. Then act with call and look with call {tool: "observe"}.

Input parameters:

- `config` (string): Path to an e2e config file, relative to the server's directory; default: the nearest e2e.config.ts
- `headed` (boolean): Show the browser or simulator, when the engine supports it; pass true when the user wants to watch. Default: headless, unless the server was started with --headed
- `target` (string): Target name from the config; required when the config declares several

### `tools` (~139 tokens)

List the tools a session can run through call: observe, the grammar its engine honors (one tool per action the engine declares, type_secret when a secret is configured, and screenshot and the point tools, which answer PIXEL_TAINTED once a secret has been filled), locate, start_recording and stop_recording when the engine records video, and the project's own tools. With tool, shows that tool's full description and the JSON Schema of its arguments.

Input parameters:

- `session` (string): Session id from open_session; may be omitted only while one session is open
- `tool` (string): A catalog tool name, for its full contract

### `call` (~148 tokens)

Run one tool of a session by name, with its arguments as an object: call {tool: "tap", args: {target: "n42"}, session: "<id>"}. The session's catalog (from open_session or tools) names the tools and their arguments. Actions report what changed on screen; node ids are valid only for the newest observation.

Input parameters:

- `args` (object): The tool's arguments; omit for a tool without any
- `session` (string): Session id from open_session; may be omitted only while one session is open
- `tool` (string, required): A catalog tool name, e.g. "observe", "tap", "locate", "screenshot"

### `close_session` (~58 tokens)

Close a live session: save a recording still running, end the attempt, dispose the engine, and stop the app processes the session started.

Input parameters:

- `session` (string): Session id from open_session; may be omitted only while one session is open

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/tester-army-e2e/e2e#diagnostics

## Score history

- 2026-10-17: 83
- 2026-10-16: 82

## Common questions

### What is the e2e MCP server?

e2e is an MCP server listed in the public MCP registry as io.github.tester-army/e2e. Open live web and mobile app sessions from an e2e project to inspect the app and try locators. This page covers its npm package (e2e).

### Is the e2e MCP server safe to use?

e2e scores 83 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 17 October 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 e2e MCP server expose?

e2e exposes 4 tools: open_session, tools, call, close_session. Their descriptions and schemas cost roughly 551 tokens of context every time the server is loaded.

### Is the e2e MCP server still maintained?

e2e is still listed as active in the MCP registry. We last reached this channel on 17 October 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 e2e MCP server under?

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

## Links

- npm package: https://www.npmjs.com/package/e2e
- Socket report: https://socket.dev/npm/package/e2e
- Repository: https://github.com/tester-army/e2e
- Website: https://e2e.tester.army/docs/reference/mcp
- Changelog RSS feed: https://verifymcp.io/servers/tester-army-e2e/e2e.xml
- Changelog JSON feed: https://verifymcp.io/servers/tester-army-e2e/e2e.json
- HTML version of this page: https://verifymcp.io/servers/tester-army-e2e/e2e