Skip to content

MCP servers › io.github.trajectiq-ai › E2E

MCP server · registry snapshot 2026-10-23 · last tested 2026-10-23

io.github.trajectiq-ai/E2E

Diagnose and fix failing Playwright tests: trace analysis, verified locator fixes, flaky ranking. — the publisher's description

8 of 9 record checks metRead-only · tools listed 2026-10-23Topic: developer-tools · AI-classifiedversion 0.2.2TypeScriptMITstandard input/output, streamable HTTP11 tools

Summary

io.github.trajectiq-ai/E2E is a remote and local MCP server listed in the official MCP registry at version 0.2.2. On 2026-10-23 ProtocolProbe started its published package in an isolated sandbox in read-only mode and read its inventory: 11 tools, 0 resources and 2 prompts.

Record checks

8 of 9 record checks met

  • met: Registry entry is active and says how to run it
  • met: Source repository link opens
  • met: Repository is not archived
  • met: Code pushed to the repository in the 90 days before our check
  • not met: Repository publishes a security policy (SECURITY.md)
  • met: Package names its licence with a standard (SPDX) identifier
  • met: The version the registry lists can be installed and is not withdrawn
  • met: npm package carries build provenance (attestation)
  • met: No known critical or high advisory in the package or its dependencies
  • #2,472 of 15,112 packages by monthly downloads, tied with 1 other (package shared with 1 other registry entry)
  • Not ranked by stars: 0 stars (ranked from 10)

From public records, not a safety rating. Each check with its reason · Is it safe to install?

Key facts

Runs
remote and local package
Transport
standard input/output, streamable HTTP
Package
npm · listed version behind the latest release
License
MIT
Dependencies
no known high or critical advisories
Repository
public
Tools
11
Described as changing data
5 of 11 toolsAI-classified
Mainly works on
files and code on the machine it runs on; a web browser or desktop applicationsAI-classified
Topic
developer-toolsAI-classified
Last tested
2026-10-23

Add to your client

Worth knowing before you connect it

  • 5 tools are described as changing something (run-test, suggest-fix, generate-e2e-test, …): our AI model's reading of the descriptions, not something we tested. We did not call them.
  • The registry lists 0.2.2; 0.4.2 is newer (6 releases).
  • Its package is signed and carries a build record naming its source.

Each line comes from a section below, with its source and date.

How fresh this is

Live-tested
yes, a real session (not a text-only review)
Last tested
2026-10-23
Mode
read-only (no tool calls)
Latest version
0.2.2, published 2026-10-09 (registry, as of the 2026-10-23 snapshot)
First listed version
2026-10-05 (earliest version still in the registry; older removed versions would be earlier)
Version history
8 versions listed, 2026-10-05 to 2026-10-09; 8 in the 90 days before the 2026-10-23 snapshot.
Most recent 8 versions
  • 0.2.2 · 2026-10-09
  • 0.2.1 · 2026-10-09
  • 0.2.0 · 2026-10-09
  • 0.1.4 · 2026-10-07
  • 0.1.3 · 2026-10-07
  • 0.1.2 · 2026-10-06
  • 0.1.1 · 2026-10-06
  • 0.1.0 · 2026-10-05
(versions still listed in the registry only)
Registry data
snapshot 2026-10-23
Package and repository
checked 2026-10-23
Engine
mcp-runtime-engine@0.1.0 · sdk@1.32.0

Changes since the last refresh

New in the registry: not in the list of 2026-10-04, listed on 2026-10-23 with version 0.2.2 (published 2026-10-09).

Source: the official MCP Registry list on 2026-10-04 and on 2026-10-23.

What it is

What does this server offer?

Observed inventory
11tools
0resources
2prompts

What it mainly works on, as our AI model read its tool descriptions: files and code on the machine it runs on; a web browser or desktop applications.

5 of 11 tools are described as changing something (creating, editing, deleting, sending or running). For 1 the reading was uncertain, so no mark is shown.

  • run-teston 1 other serverruns code or commandsdescribed as changing data

    “Run the project's Playwright tests: stats plus each failure's file:line, kind and message.”

    Publisher declares: read-only no · destructive yes · idempotent yes · open-world yes

    14 inputs
    • projectRootstring“Project directory; defaults to the server working directory”
    • testFilesarray“Test files/directories relative to the project root; "file:line" is supported.”
    • grepstring“Only run tests whose title matches this regex”
    • browserstring“Playwright project name to run (matched against playwright.config projects)”
    • headedboolean“Run with a visible browser window”
    • timeoutMsinteger“Hard wall-clock limit for the whole run; the process tree is killed past it (default 120000)”
    • testTimeoutMsinteger“Per-test timeout passed to Playwright”
    • workersinteger
    • retriesinteger
    • retryOnFailureboolean“Auto retry failing tests once before reporting failure (default true; ignored when retries is set)”
    • lastFailedboolean“Only re-run tests that failed in the previous run (Playwright --last-failed) — the fast fix → re-run loop”
    • configstring“playwright.config path or 1-based index when the project has several configs”
    • argsarray“Extra Playwright flags from an allowlist, as --flag or --flag=value (e.g.”
    • backgroundboolean“Return a run id at once; poll get-run-status”
  • get-run-statuson 1 other serverreads or searches

    “Progress (tests done/total, failures so far) or the final result of a run-test background run; the result becomes the last run for get-failure.”

    Publisher declares: read-only no · destructive no · idempotent yes · open-world no

    3 inputs
    • runIdstring
    • waitSecondsinteger“Wait up to this long for it to finish”
    • cancelboolean
  • get-failureon 1 other serverreads or searches

    “Analyze one failure from the most recent run-test execution: full message and code frame, expected vs actual, stack trace, failed network requests (4xx/5xx and dead endpoints), console errors, failur…”

    Publisher declares: read-only yes · idempotent yes · open-world no

    2 inputs
    • indexinteger“1-based failure index from the last run (default 1)”
    • projectRootstring“Only used to re-read the stored report”
  • suggest-fixon 1 other serverruns code or commandsdescribed as changing data

    “Patch a failure from the last run: a drifted locator is matched against the DOM at failure (trace, or live url) and replaced with one proven unique; changed copy gets the new expected text.”

    Publisher declares: read-only no · destructive yes · idempotent no · open-world yes

    10 inputs
    • indexinteger“1-based failure index (default 1)”
    • projectRootstring
    • urlstring“Heal against this live page instead of the trace snapshot”
    • storageStatestring“Logged-in session: storageState JSON inside the project, e.g.”
    • headersobject“Extra HTTP headers, e.g.”
    • applyboolean“Write the fix (default: diff only)”
    • verifyboolean“Re-run after applying; revert if still failing (default true)”
    • allowExpectationUpdateboolean“Allow applying changed expected text (can hide regressions)”
    • configstring“playwright.config path or 1-based index”
    • timeoutMsinteger“Verification run limit (default 120000)”
  • inspect-pageon 1 other serverreads or searches

    “Open a URL headlessly and return its elements with Playwright locators proven unique on the page (role + name first), CSS selectors, visibility, text and console messages.”

    Publisher declares: read-only yes · idempotent yes · open-world yes

    13 inputs, 1 required
    • urlstringrequired“Full URL of the page to open (http/https)”
    • projectRootstring“Project whose Playwright launches the browser (default: server root)”
    • selectorstring“CSS selector: inspect matches instead of the whole DOM”
    • viewstring“'locators': compact map of interactive elements (cheapest); 'elements' (default): DOM inventory”
    • waitForstring“Wait for this selector first”
    • storageStatestring“Logged-in session: storageState JSON inside the project, e.g.”
    • headersobject“Extra HTTP headers, e.g.”
    • actionsarray“Steps run after load to reach a state (modal, step 3)”
    • viewportobject
    • waitUntilstring“Navigation wait condition (default domcontentloaded)”
    • includeHtmlboolean“Include the rendered HTML (truncated)”
    • maxHtmlCharsinteger“HTML cap when includeHtml is set (default 20000)”
    • timeoutMsinteger“Overall inspection limit in ms (default 45000)”
  • list-testson 1 other serverreads or searches

    “List the Playwright tests available in the project (file, line, full title, projects), with optional filtering.”

    Publisher declares: read-only yes · idempotent yes · open-world no

    5 inputs
    • projectRootstring“Project directory; defaults to the server working directory”
    • configstring“playwright.config path or 1-based index when the project has several configs”
    • testDirstring“Restrict scanning to this directory (inside the project)”
    • filterstring“Case-insensitive substring filter on "file › title"”
    • limitinteger“Max tests to return (default 500)”
  • validate-selectoron 1 other serverreads or searches

    “Check a CSS selector, Playwright selector or locator (getByRole/getByTestId…, .first(), .filter()) on a live page: validity, match count (actions need exactly 1), sample matches and a sturdier verifi…”

    Publisher declares: read-only yes · idempotent yes · open-world yes

    8 inputs, 2 required
    • urlstringrequired“Full URL of the live page to test against (http/https)”
    • selectorstringrequired“Selector or locator, e.g.”
    • projectRootstring“Project whose Playwright launches the browser (default: server root)”
    • storageStatestring“Logged-in session: storageState JSON inside the project, e.g.”
    • headersobject“Extra HTTP headers, e.g.”
    • actionsarray“Steps run after load to reach a state (modal, step 3)”
    • viewportobject
    • timeoutMsinteger“Overall limit in ms (default 45000)”
  • generate-e2e-teston 1 other servergenerates contentdescribed as changing data

    “Scaffold a Playwright test from a description using the project's REAL selectors.”

    Publisher declares: read-only no · destructive yes · idempotent no · open-world yes

    9 inputs, 1 required
    • descriptionstringrequired“What the test should cover, e.g.”
    • pageUrlstring“Page the test starts on (default: baseURL from playwright.config)”
    • projectRootstring“Project directory; defaults to the server working directory”
    • configstring“playwright.config path or 1-based index”
    • testDirstring“Directory for the generated spec (default: detected testDir or tests/)”
    • filestring“Exact spec path (*.spec.ts / *.test.ts) inside the project instead of the default location”
    • writeboolean“Write the file to disk (default true)”
    • overwriteboolean“Replace an existing spec at the target path (only specs this tool generated)”
    • liveInspectboolean“Verify discovered selectors against the live page (default true when a URL is known)”
  • compare-visual-stateon 1 other servercreates or changes datadescribed as changing data

    “Visual regression check: screenshot a live page (or element), compare it to a stored baseline, and report how many pixels changed, WHERE they changed (bounding regions), and the average color shift (…”

    Publisher declares: read-only no · destructive yes · idempotent yes · open-world yes

    15 inputs, 2 required
    • urlstringrequired“Full URL of the page (or element target) to capture”
    • namestringrequired“Baseline id, e.g.”
    • projectRootstring“Project directory; defaults to the server working directory”
    • selectorstring“Capture only this element (selector or locator)”
    • fullPageboolean“Capture the full scrollable page (default false)”
    • waitUntilstring
    • waitForstring“Wait for this selector before capturing”
    • storageStatestring“Logged-in session: storageState JSON inside the project, e.g.”
    • headersobject“Extra HTTP headers, e.g.”
    • actionsarray“Steps run after load to reach a state (modal, step 3)”
    • viewportobject
    • timeoutMsinteger
    • actionstring“'baseline' overwrites the stored baseline; 'compare' (default) compares against it”
    • tolerancenumber“Percent of pixels that may differ before reporting a change (default 0.1)”
    • pixelThresholdinteger“Combined per-pixel channel delta considered different (default 60)”
  • diagnose-flakyon 1 other serverruns code or commandsdescribed as changing data

    “Run a failing test multiple times with retries disabled and return an evidence-based verdict: CONSISTENTLY FAILING (real bug), FLAKY (intermittent — includes pass/fail counts and error-signature vari…”

    Publisher declares: read-only no · destructive yes · idempotent yes · open-world yes

    8 inputs
    • projectRootstring“Project directory; defaults to the server working directory”
    • testFilesarray“Tests to diagnose ("file:line" supported).”
    • runsinteger“How many times to run the tests (default 3)”
    • browserstring“Playwright project name to run”
    • headedboolean“Run with a visible browser window”
    • workersinteger
    • timeoutMsinteger“Hard wall-clock limit per run (default 120000)”
    • configstring“playwright.config path or 1-based index when the project has several configs”
  • analyze-historyon 1 other serverreads or searches

    “Analyze the local run history (.playwright-e2e-mcp/history.jsonl, written by every run): 'flaky' ranks tests that flip pass/fail and lists broken or regressed ones; 'patterns' groups failures by caus…”

    Publisher declares: read-only yes · idempotent yes · open-world no

    5 inputs
    • viewstring“Default 'flaky'”
    • teststring“Filter: substring of file or title”
    • lastRunsinteger“Runs to analyze (default 30)”
    • limitinteger
    • projectRootstring

Each quoted sentence is the first sentence of the publisher’s own description. The kind of tool and the “changes data” mark are our AI model’s reading of that description, not something we tested: two differently worded runs had to agree, otherwise no label is shown, and nobody has checked them by hand. A tool without the “changes data” mark is described as only reading, searching or calculating, or the two runs did not agree. No tool was called. Read the publisher’s full description before relying on it. “Publisher declares” lists the hints the server itself sends with the tool (MCP annotations: read-only, destructive, idempotent, open-world); they are the publisher's claims, not checked by us. Inputs are the parameters in the tool's own input schema: name, declared type, whether it is required, and the first sentence of its description. Read 2026-10-23.

How well are its tools described?

Features #4 and #5

How clearly this server's own tool descriptions say what a tool does, and how consistent its tool list is. The first part is an AI model's yes/no reading of each description; the second part is counted. We do not turn it into a grade.

Descriptions

AI reading of each description

Says what the tool does
100% of 11 tools
Says what it returns
100% of 11 tools
States limits, defaults or errors
78% of 9 tools
Says when to use it
100% of 5 tools
Items covered per tool
3.8 of 4 on average

Counted from the listing

Parameters with a description
86% of 92
Tools with a description
100% of 11
Typical description length
289 characters

The tool set

Counted from the listing

Tools
11
Size of the list
about 4,564 tokens for an agent to load (characters ÷ 4)
Naming
11 of 11 names use kebab-case

AI reading: easy to mix up

No pair found.

The AI items cover 11 of 11 tools: for a tool where two differently worded runs disagreed, that item is left out. They were not checked by hand, and no tool was called. “Easy to mix up” means two tools whose names or descriptions overlap without saying how they differ; the AI found none. We do not rate whether the tool set is complete or whether side effects are spelled out, because our AI reading of those was not reliable enough.

How do I add it to my client?

Config from the registry entry

From the npm package playwright-e2e-mcp

Our sandbox started this package on 2026-10-23 (a read-only session: no tool was called).

Add to CursorAn install link in the format Cursor documents, holding the Cursor config below. The command runs the publisher’s code on your machine.

Claude Desktop · claude_desktop_config.json (Settings → Developer → Edit Config)
{
  "mcpServers": {
    "e2e": {
      "command": "npx",
      "args": [
        "-y",
        "playwright-e2e-mcp@0.2.2"
      ]
    }
  }
}
Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json
{
  "mcpServers": {
    "e2e": {
      "command": "npx",
      "args": [
        "-y",
        "playwright-e2e-mcp@0.2.2"
      ]
    }
  }
}
VS Code · .vscode/mcp.json
{
  "servers": {
    "e2e": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "playwright-e2e-mcp@0.2.2"
      ]
    }
  }
}
VS Code (command line) · Bash or zsh terminal (macOS, Linux)
code --add-mcp '{"name":"e2e","type":"stdio","command":"npx","args":["-y","playwright-e2e-mcp@0.2.2"]}'
Claude Code
claude mcp add --transport stdio e2e -- npx -y playwright-e2e-mcp@0.2.2
Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+
npx @modelcontextprotocol/inspector@2.11.0 -- npx -y playwright-e2e-mcp@0.2.2
  • This runs the publisher's code on your machine (npx). Read its README first.
  • The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.

From the remote endpoint (Streamable HTTP)

Add to CursorAn install link in the format Cursor documents, holding the Cursor config below.

Claude Desktop or claude.ai
Settings → Connectors → Add custom connector, then paste:
https://playwright-e2e-mcp.vercel.app/api/mcp
Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json
{
  "mcpServers": {
    "e2e": {
      "url": "https://playwright-e2e-mcp.vercel.app/api/mcp"
    }
  }
}
VS Code · .vscode/mcp.json
{
  "servers": {
    "e2e": {
      "type": "http",
      "url": "https://playwright-e2e-mcp.vercel.app/api/mcp"
    }
  }
}
VS Code (command line) · Bash or zsh terminal (macOS, Linux)
code --add-mcp '{"name":"e2e","type":"http","url":"https://playwright-e2e-mcp.vercel.app/api/mcp"}'
Claude Code
claude mcp add --transport http e2e https://playwright-e2e-mcp.vercel.app/api/mcp
Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+
npx @modelcontextprotocol/inspector@2.11.0 --server-url https://playwright-e2e-mcp.vercel.app/api/mcp --transport http
  • The server runs on the operator's infrastructure; it may ask you to sign in when you first connect.
  • The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.

Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.

Can it be installed, and is it up to date?

Version pin · advisories

Listed version

Registry lists
0.2.2
Latest stable
0.4.2
Status
behind the latest release (6 releases, 13 days)
Withdrawn
no

Source: registry.npmjs.org · 2026-10-23. About the version the registry lists; a manual install may resolve to a different one.

Dependency advisories

critical0high0moderate0low0

Counted in the full dependency tree as resolved on 2026-10-23 (npm audit). Bars share one scale. The package itself has no known vulnerability (OSV.dev).

Integrity, provenance, license

Integrity
sha512-bX5i4N8/fkQyuU29b…
Signature
signed and attested
License
MIT

Source: the package registry · 2026-10-23.

Usage

Downloads
1,053 in the last month

Source: api.npmjs.org · 2026-10-23.

Does the registry listing match what we found?

Feature #6

The registry verifies a package once, when it is published, and does not re-check it. A difference below is about the listing, not a judgement of the publisher.

Registry saysWe foundResultSource · date
Remote endpoint playwright-e2e-mcp.vercel.app/api/mcpEndpoint answered and asked for sign-inmatchesour test · 2026-10-23
No credential declared as requiredRequired sign-indiffersour test · 2026-10-23
Published package can be startedStarted and answeredmatchesour test · 2026-10-23
Version 0.2.2 on npmExists and can be installedmatchesnpm · 2026-10-23
Repository github.com/trajectiq-ai/E2EOpens publiclymatchesapi.github.com · 2026-10-23

Who made it?

Feature #7 · lineage

Facts about the publisher. We do not turn them into a trust score.

Namespace
io.github.trajectiq-ai
GitHub owner
a personal account (trajectiq-ai)
Build record
signed and attested
Repository
github.com/trajectiq-ai/E2E
Stars
0
Repository age
0–30 days
Last push
0–30 days ago
Archived
no
Security policy
none found (we looked for SECURITY.md in the repository and in its owner’s .github repository)

Source: the registry entry and api.github.com · 2026-10-23; security policy read from GitHub · 2026-10-23.

Publish this server? Run these checks against it yourself before release, from your own machine: a server the command starts, or your own server at its URL after a one-time proof that you control it: npx protocolprobe-selftest.

Choosing

Record checks

Public records · not a safety rating

8 of 9 record checks met

  • #2,472 of 15,112 packages by monthly downloads, tied with 1 other (package shared with 1 other registry entry)
  • Not ranked by stars: 0 stars (ranked from 10)
  • MetRegistry entry is active and says how to run itActive, with a package or a remote address.
  • MetSource repository link opensThe linked GitHub repository is public.
  • MetRepository is not archivedNot archived.
  • MetCode pushed to the repository in the 90 days before our checkLast push 0-30 days before our check.
  • Not metRepository publishes a security policy (SECURITY.md)No SECURITY.md in the places GitHub reads it from.
  • MetPackage names its licence with a standard (SPDX) identifierMIT
  • MetThe version the registry lists can be installed and is not withdrawnThe listed version exists; a newer one is out.
  • Metnpm package carries build provenance (attestation)Signed, with a build attestation naming the source and workflow.
  • MetNo known critical or high advisory in the package or its dependenciesNone known in the package or its dependency tree.

Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-10-23. No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating. How each check works · Leaderboards

Common questions about io.github.trajectiq-ai/E2E

Answered from the data above

Is io.github.trajectiq-ai/E2E safe to install?

We do not rate servers as safe or unsafe. 8 of its 9 applicable record checks are met (facts from public records, each listed on this page). What the records show: Its npm package carries a build-provenance attestation that names its source repository and build workflow. Its source repository opens publicly. Its repository had a push in the last 90 days. A newer stable release exists than the one listed. The package itself has no known vulnerability (OSV.dev). Its full dependency tree has no known advisory. 5 of its tools describe changing data (our AI model's reading of the descriptions). These are facts with their sources on this page, not a safety guarantee, and we did not run its tools.

Has io.github.trajectiq-ai/E2E been security tested?

Partly. 4 of the 13 checks that apply to it were exercised. We started the package in an isolated sandbox and read what it declares, but this test round was read-only, so its tools were not called. No security verdict is published before verification.

What can io.github.trajectiq-ai/E2E do?

It lists 11 tools. In our AI model's reading of their descriptions (two runs had to agree, nobody checked it by hand), they include tools that read or search, create or change data, run code or commands and generate content. We did not call any tool, so this describes the text, not the behaviour.

Can io.github.trajectiq-ai/E2E change or delete data?

5 of its tools say in their description that they create, edit, delete, send or run something (our AI model's reading). We did not call any tool, so we cannot say what actually happens.

Does io.github.trajectiq-ai/E2E publish a security policy?

We found no SECURITY.md in its repository (root, .github/ or docs/) or in its owner's .github repository.

Is the listed version current?

No. The registry lists 0.2.2; the latest stable release on npm is 0.4.2.

Where is the source code of io.github.trajectiq-ai/E2E?

In github.com/trajectiq-ai/E2E, which opens publicly.

Found this page useful?

Anonymous · no sign-in

A quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.

Similar servers

Same topic · AI-read

Active servers whose topic is also “developer-tools” and that have at least one tool of the same kind; most kinds in common first, then most GitHub stars. The topic and the tool kinds are an AI model's reading of the publishers' descriptions, not checked by hand. Similar is not a recommendation.

Compare with another server

Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.

Security testing

What did we test, and what did we leave out?

18 checks · features #1, #2

Not probed (read-only run)

We started the package in an isolated sandbox and read what it declares, but this test round was read-only, so its tools were not called. No security score is given; a check we did not run is never counted as passed.

The 18 checks at a glanceour test · 2026-10-23
  1. Inventory: exercised
  2. Hidden instructions: exercised
  3. Real execution: not run · our policy
  4. Secret leak: not run · nothing to check it against
  5. Internal addresses: not run · our policy
  6. Unconfirmed changes: not run · our policy
  7. Bad input: not run · our policy
  8. Model requests: not run · nothing to check it against
  9. Sensitive questions: not run · nothing to check it against
  10. Folder boundary: not run · our policy
  11. Log leaks: not run · nothing to check it against
  12. Hidden content: exercised
  13. Fake assistant turns: exercised
  14. Token passthrough: not applicable
  15. Token audience: not applicable
  16. Sign-in redirect: not applicable
  17. Consent handling: not applicable
  18. Sign-in metadata: not applicable

4 exercised9 not run (reason given)5 not applicable

Each check ends in exactly one state: exercised, not run (with the reason), or not applicable (with the reason). 4 of the 13 checks that apply to it were exercised. We do not publish security-check outcomes for named servers.

Exercised · 4
  • 1Inventory
    tool-list
    Reads the declared tools, resources and prompts.exercised
  • 2Hidden instructions
    description-poisoning
    Looks for hidden instructions in tool descriptions.exercised
  • 12Hidden content
    audience-hiding
    Checks resources that hide content from the user.exercised
  • 13Fake assistant turns
    fake-assistant-turn
    Checks prompts that pose as the assistant's own words.exercised
Not run, with the reason · 9
  • 3Real execution
    real-execution
    Calls a tool and checks what really happens.This check calls the package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.not run · our policy
  • 4Secret leak
    canary-leak
    Plants a fake secret and checks whether it leaks.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 5Internal addresses
    ssrf
    Checks whether a tool can be steered to internal addresses.This check calls the package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.not run · our policy
  • 6Unconfirmed changes
    write-without-confirmation
    Checks whether tools that change data act without asking.This check calls the package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.not run · our policy
  • 7Bad input
    error-handling
    Sends bad input and watches how the server answers.This check calls the package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.not run · our policy
  • 8Model requests
    sampling
    Checks whether the server asks the client's model to act for it.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 9Sensitive questions
    elicitation-sensitive-data
    Checks whether the server asks users for sensitive data.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 10Folder boundary
    root-boundary
    Checks whether the server reaches outside the folders it was given.This check calls the package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.not run · our policy
  • 11Log leaks
    logging-side-channel
    Checks whether log messages carry data they should not.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
Does not apply to this server · 5
  • 14Token passthrough
    token-passthrough
    Checks whether the server forwards a user's token to other services.The server runs locally over standard input/output, so there is no sign-in flow to check.not applicable
  • 15Token audience
    token-audience-validation
    Checks whether tokens meant for another service are accepted.The server runs locally over standard input/output, so there is no sign-in flow to check.not applicable
  • 16Sign-in redirect
    open-redirect
    Checks the sign-in redirect for abuse.The server runs locally over standard input/output, so there is no sign-in flow to check.not applicable
  • 17Consent handling
    confused-deputy
    Checks consent handling when one service acts for another.The server runs locally over standard input/output, so there is no sign-in flow to check.not applicable
  • 18Sign-in metadata
    oauth-url-scheme
    Checks the published sign-in metadata for unsafe URLs.The server runs locally over standard input/output, so there is no sign-in flow to check.not applicable

Source: our own test in an isolated sandbox, 2026-10-23, mcp-runtime-engine@0.1.0. Which checks count and why follows our published scoring model. This server also has a remote test (1 of 18 applicable checks exercised).

What happened during the test?

Feature #8

The steps in order, as the test record holds them.

  1. 0 msStarted the published package in an isolated sandbox (read-only mode)
  2. 3,530 msConnected after 0 redirects.
  3. Read the inventory: 11 tools, 0 resources, 2 prompts.
  4. 4,640 msFinished: 4 checks exercised.

Reference

How is it classified?

18 fields

One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.

TopicAI-classified
AI-classified · 2026-10-23
Pricing modelAI-classified
no value
The website listed in the registry is a code-hosting, package or marketplace page, not the product's own site.
Programming language
api.github.com · 2026-10-23
Hosting type
registry · 2026-10-23
MCP capability
prompts, tools
our test · 2026-10-23
Transport
standard input/output, streamable HTTP
registry · 2026-10-23
Required credentials
none declared
registry · no declaration is not a guarantee
Package registry
registry · 2026-10-23
Freshness
0–30 days
registry updatedAt · 2026-10-23
Lifecycle status
registry · 2026-10-23
License class
package registry · 2026-10-23
Integrity hash
declared (sri)
package registry · 2026-10-23
Signature / provenance
package registry · 2026-10-23
Dependency advisories
none known
npm audit · 2026-10-23
Popularity
1,053 downloads a month
package registry · 2026-10-23
Publisher signals
owner: a personal account · repository age: 0–30 days · stars: 0–9 · build record: signed and attested
api.github.com · 2026-10-23
Maintenance
api.github.com · 2026-10-23
Environment
either (remote or your machine)
where it runs, from the hosting type

“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.

Cite or correct this page

Sources and corrections

Suggested citation

ProtocolProbe. “io.github.trajectiq-ai/E2E: MCP server record.” Data checked 2026-10-23. https://protocolprobe.com/mcp/servers/io.github.trajectiq-ai/E2E

Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.

As JSON: this record in the API · API documentation.

Badge for your README

ProtocolProbe: 8 of 9 record checks met

[![ProtocolProbe](https://protocolprobe.com/api/v1/badge/io.github.trajectiq-ai/E2E)](https://protocolprobe.com/mcp/servers/io.github.trajectiq-ai/E2E)

It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.

Something wrong, or is this yours?

If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here.

Write to hello@protocolprobe.com · corrections log · methodology