e2e
NPM · E2E
Open live web and mobile app sessions from an e2e project to inspect the app and try locators.
Available components
Last scanned (1 hour ago)
Scores higher than 78% 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 Security99
- 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
- 8 of 79 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 tester-army/e2e). View diagnostics → Pass
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 0 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability80
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1069 tokens (~82/item across 13 items; 4 tools + 9 resources), lean.Pass
- 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 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
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.
- 17 Oct 26 +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.
- 16 Oct 26 82
First indexed and scored.
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 17 Oct 2026 · Analysed npm/e2e@0.21.2
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 | tester-army/e2e |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/tester-army/e2e/.github/workflows/release.yml@refs/heads/main |
| Rekor log index | 3281960227 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:c3734d24b6eed30914846cb8e0edde9535e10cd7707adaef12156fa80d998d4c7e97e71c721215003a1dace5da3f615a075e58fe59d931b42b39d7d53 |
Background: How many MCP packages publish verified provenance →
Dependencies 79 packages
| Packages resolved | 79 |
|---|---|
| Stale | 8 |
| 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 →
call ~148
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | A catalog tool name, e.g. "observe", "tap", "locate", "screenshot" |
No output schema declared.
No examples provided.
close_session ~58
Close a live session: save a recording still running, end the attempt, dispose the engine, and stop the app processes the session started.
| Name | Type | Req | Description |
|---|---|---|---|
| session | string | – | Session id from open_session; may be omitted only while one session is open |
No output schema declared.
No examples provided.
open_session ~206
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"}.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 |
No output schema declared.
No examples provided.
tools ~139
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 |
No output schema declared.
No examples provided.
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.
npm · e2e
claude mcp add tester-army-e2e -- npx -y e2e
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.