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.

Endform

NPM · ENDFORM

Find failing, flaky, and slow Playwright tests on Endform and keep your suite healthy as it grows.

Available components

60 Trust /100

Last scanned (13 hours ago)

Scores higher than 35% of npm servers

Category Testing and QA

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 Security97
  • 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
  • 6 of 6 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency6
  • Repository check failed: no source repository is declared. See how to fix → View diagnostics → Fail
  • Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
  • Licence could not be checked: the licence is shipped as a file inside the package, not declared as a standard (SPDX) licence identifier, so we cannot tell whether it is OSI-approved.Unverified
  • Actively maintained (last published 3 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability66
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 2451 tokens (~204/item across 12 items; 12 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 Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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 12 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 13 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass

Unverified: 1 category

A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

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.

  • 15 Oct 26 +30
    • Injection markers: unverified → pass ▲ security
    • First check of Judged manipulation: pass security
    • Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
    • Tool coverage: unverified → 100 ▲ functional
    • MCP protocol: unverified → pass ▲ functional
    • First check of Schema quality: fail functional
    • First check of Schema quality: excellent functional
    • First check of Destructive annotations: pass functional
    • First check of Schema quality: fail functional
    • First check of Tool coverage: 100 functional
    • First check of Tool coverage: 100 functional
  • 14 Oct 26 30

    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 18 Oct 2026 · Analysed npm/endform@0.81.5

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 6 packages
Packages resolved 6
No linked repository 6
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 12 exposed · ~2,260 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
create_quarantine_rule ~207

Creates an Endform quarantine rule from exact values. Requires suiteId and at least one of testId, projectName, or branch. Use query_samples first and pass its persisted suite.id and, when needed, test.id; do not use Playwright worker IDs, test names, or file paths as testId.

NameTypeReqDescription
branchstring|null–Exact branch name. Omit to match all branches.
endsAtstring|null–Future RFC3339 expiry timestamp. Omit for no expiry.
organizationIdstring|null–Organization ID. Omit to infer from the active login.
projectNamestring|null–Exact Playwright project name. Omit to match all projects.
reasonstring|null–Optional reason for quarantining the matching tests.
suiteIdstringyesExact persisted suite.id from query_samples.
testIdstring|null–Exact persisted test.id. Omit to match all tests in the suite.
NameTypeReqDescription
rule–yes–

No examples provided.

deactivate_quarantine_rule ~82

Deactivates one Endform quarantine rule by its exact rule ID. Use list_quarantine_rules to retrieve the ID. Repeating the same request is safe and reports changed false.

NameTypeReqDescription
organizationIdstring|null–Organization ID. Omit to infer from the active login.
ruleIdstringyesExact rule ID from list_quarantine_rules.
NameTypeReqDescription
changedbooleanyes–
rule–yes–

No examples provided.

get_otel_trace ~82

Gets raw OpenTelemetry trace data for an Endform test attempt. Use query_samples to find an otelTraceId. The organization is normally inferred from the active login.

NameTypeReqDescription
organizationIdstring|null–Optional organization containing the trace. Omit this when the login has access to one organization.
traceIdstringyesOpenTelemetry trace ID.

Structured output declared, but exposes no named fields.

No examples provided.

list_organizations ~31

Lists organizations available to the active Endform login. Use this when another tool reports that organization selection is required.

Input schema present but exposes no named parameters.

NameTypeReqDescription
organizationsarrayyes–

No examples provided.

list_quarantine_rules ~89

Lists active Endform quarantine rules with exact rule IDs plus suite, test, project, branch, reason, expiry, and deactivation metadata. Set includeInactive to true to include expired and deactivated rules.

NameTypeReqDescription
includeInactiveboolean–Include expired and deactivated rules. Defaults to false.
organizationIdstring|null–Organization ID. Omit to infer from the active login.
NameTypeReqDescription
rulesarrayyes–

No examples provided.

live_test_run ~144

Runs JavaScript inside the paused checkpoint of a live session started with live_test_start. The code runs in the test's scope with access to fixtures such as page, and may use multiple statements and await. Returns stdout, stderr, exitCode, a fresh inline ARIA snapshot, and paths to artifacts such as screenshots. A non-zero exitCode means the code threw; the session remains paused and this tool can be called repeatedly.

NameTypeReqDescription
codestringyesJavaScript to execute inside the paused test scope. The code may use `await` and access test fixtures such as `page`.
sessionIdstringyesLive session ID returned by `live_test_start`.
NameTypeReqDescription
artifactPathsarrayyes–
exitCodeintegeryes–
sessionIdstringyes–
snapshotstring|null––
snapshotPathstring|null––
stderrstringyes–
stdoutstringyes–

No examples provided.

live_test_start ~353

Starts a live session paused inside one Playwright test on Endform's remote infrastructure. Test selection follows Playwright conventions and must match exactly one test; narrow it with testFileFilters, grep, grepInvert, or project. Playwright grep patterns match the full title chain. A testFileFilter may include file.spec.ts:LINE to select a test declaration. The separate line input is the 1-based source line to pause before and defaults to the first statement inside the selected test body. Returns a sessionId, checkpoint, paths, and an inline initial ARIA snapshot. Then use live_test_run and call live_test_stop when finished. Startup may take a few minutes; sessions end automatically after 15 minutes.

NameTypeReqDescription
configstring|null–Playwright configuration file or test directory, like Playwright `--config`.
greparray–Only selects tests whose full Playwright title chain matches these regular expressions, including the project, file, describe blocks, and test title.
grepInvertarray–Excludes tests with titles matching these regular expressions, like Playwright `--grep-invert`.
lineinteger|null–1-based source line to pause before. Defaults to the first statement inside the selected test body.
organizationIdstring|null–Endform organization ID. Defaults to the organization configured for the repository or active login.
projectarray–Only selects tests from these Playwright projects, like Playwright `--project`.
testFileFiltersarray–Filters test files using regular expressions matched against absolute paths, like Playwright positional test filters. A filter may include a test declaration line, for example `tests/checkout.spec.ts…
NameTypeReqDescription
checkpointFilestringyes–
checkpointLineintegeryes–
logPathstringyes–
resultsPathstringyes–
sessionIdstringyes–
snapshotstring|null––
snapshotPathstring|null––

No examples provided.

live_test_status ~71

Shows the state of a live session started with live_test_start: starting, paused (ready for live_test_run), running (code is executing), ended, or stale. A paused response includes a fresh inline ARIA snapshot.

NameTypeReqDescription
sessionIdstringyesLive session ID returned by `live_test_start`.
NameTypeReqDescription
errorstring|null––
hintstring|null––
resultsPathstring|null––
sessionIdstringyes–
snapshotstring|null––
snapshotPathstring|null––
status–yes–

No examples provided.

live_test_stop ~61

Stops a live session started with live_test_start and cleans up its client-side and runner resources. Call this when finished debugging instead of waiting for the 15-minute session limit.

NameTypeReqDescription
sessionIdstringyesLive session ID returned by `live_test_start`.
NameTypeReqDescription
errorstring|null––
sessionIdstringyes–
status–yes–

No examples provided.

query_analytics ~458

Compares Endform run counts, pass rates, and durations over time. Use this first to identify patterns, then use query_samples to inspect concrete matching executions and errors.

NameTypeReqDescription
dataset–yesWhether to aggregate suite-level or individual test-run records.
endingAtstring|null–Optional ISO 8601 timestamp at which the period ends. Defaults to request time.
groupBy––Optional grouping dimension. Suite runs cannot be grouped by test or project.
metric–yesAggregate to calculate: count, pass-rate, or average-duration.
organizationIdstring|null–Optional organization to query. Omit this when the login has access to one organization.
periodstring–Positive integer followed by H, D, W, or M. Defaults to 7D.
wherestring|null–Optional analytics filter expression. Filter expression: comma-separated `key operator value` clauses, for example `suite.repository = endformdev/endform, suite.directory = e2e`. Quote values contain…

Structured output declared, but exposes no named fields.

No examples provided.

query_samples ~474

Returns concrete matching Endform suite or test run executions, including ordered test attempts and errors. Use query_analytics first to narrow patterns, and use get_otel_trace when an attempt has an otelTraceId.

NameTypeReqDescription
cursorstring|null–Opaque cursor from nextCursor. Pagination preserves the original time window.
dataset–yesWhether to return suite-level or individual test-run records.
endingAtstring|null–Optional ISO 8601 timestamp at which the period ends. Defaults to request time.
limitinteger–Number of newest records to return. Defaults to 10 and cannot exceed 50.
organizationIdstring|null–Optional organization to query. Omit this when the login has access to one organization.
periodstring–Positive integer followed by H, D, W, or M. Defaults to 7D.
wherestring|null–Optional analytics filter expression. Filter expression: comma-separated `key operator value` clauses, for example `suite.repository = endformdev/endform, suite.directory = e2e`. Quote values contain…

Structured output declared, but exposes no named fields.

No examples provided.

update_quarantine_rule ~208

Replaces all editable settings of an active quarantine rule, preserving its ID and priority. Use list_quarantine_rules to retrieve its ID. The suite cannot change. Supply every editable field explicitly; null clears a restriction, reason, or expiry. At least one of testId, projectName, or branch must remain set. Inactive rules cannot be edited.

NameTypeReqDescription
branchstring|nullyesExact branch, or null to match all branches.
endsAtstring|nullyesFuture RFC3339 expiry, or null for no expiry.
organizationIdstring|null–Organization ID. Omit to infer from the active login.
projectNamestring|nullyesExact project name, or null to match all projects.
reasonstring|nullyesReason, or null to clear it.
ruleIdstringyesExact rule ID from list_quarantine_rules.
testIdstring|nullyesExact persisted test ID, or null to match all tests.
NameTypeReqDescription
rule–yes–

No examples provided.

Install

How do I install the Endform MCP server?

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

npm · endform

# add to Claude Code
claude mcp add dev-endform-mcp -- npx -y endform
Common questions

What is the Endform MCP server?

Endform is an MCP server listed in the public MCP registry as dev.endform/mcp. Find failing, flaky, and slow Playwright tests on Endform and keep your suite healthy as it grows. This page covers its npm package (endform).

Is the Endform MCP server safe to use?

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

Endform exposes 12 tools: create_quarantine_rule, deactivate_quarantine_rule, get_otel_trace, list_organizations, list_quarantine_rules, and 7 more. Their descriptions and schemas cost roughly 2,260 tokens of context every time the server is loaded.

Is the Endform MCP server still maintained?

Endform is still listed as active in the MCP registry. We last reached this channel on 18 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.