← Home

@applitools/mcp

npm Repository Homepage

Applitools MCP server for AI coding assistants

10
Versions
SEE LICENSE IN LICENSE
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

danielputermangearmamit.rokachroy.selaapplitools-adminapplitools-readonlyiasisappnoam.mendelarik-applitoolsyotammademdenis.styrtkyrylo.onufriievormedaclementbarryidosapplitoolsgofilordalex.burdeynyyronikar_applitoolsbenny.halberstadtgrayscale64fatihsolhan-applitoolsitaiz134dockermasteranandbagmarsergovapplitoolsfluxomni.iommilappnoam.gaashroeefranastasia.koifmanaretm_borodavkayonittzairilevyasundaram-applitoolsamir.groismanemasuarynaama.shohamadamcarmimulygottliebyoavnaveh-applitoolschaimaharonsonmovshonetta.bondyshirbinranhadardmytro-hrostyslav.pidburachynskyi.applitoolstaltool

Keywords

applitoolseyesmcpmodel-context-protocolplaywrightvisual-testingaicoding-assistantvisual regressionmodel context protocolui testingcross-browser testingultrafast gridtest automation

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:zod AI (phantom-deps): Transitive dependency; common pattern in framework packages. ai
dependencies unvetted-dep:@applitools/utils AI (dependencies): Same org scope (@applitools); internal dependency, expected for this package. ai
dependencies unvetted-dep:@applitools/logger AI (dependencies): Same org scope (@applitools); internal dependency, expected for this package. ai
typosquat typosquat.levenshtein:yup AI (typosquat): Scoped @applitools/mcp has no meaningful similarity to 'yup'; Levenshtein match is spurious. ai
phantom-deps phantom-dep:@applitools/utils AI (phantom-deps): Internal org-scoped dep; may be used transitively or bundled. ai
phantom-deps phantom-dep:cors AI (phantom-deps): cors is a declared runtime dep; likely bundled via rollup rather than directly imported in source. ai
phantom-deps phantom-dep:express AI (phantom-deps): express is a declared runtime dep; likely bundled via rollup rather than directly imported in source. ai

Versions (showing 10 of 10)

Version Deps Published
0.5.7 9 / 22
0.5.6 9 / 22
0.5.3 9 / 22
0.5.2 9 / 22
0.5.1 9 / 22
0.5.0 9 / 21
0.4.3 9 / 21
0.4.2 9 / 21
0.4.1 9 / 21
0.4.0 9 / 21

v0.5.7

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.5.6

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: danielputerman → movsho (on 2026-05-26, known maintainer) provenance

This version was published by a different npm account (movsho) than the most recent previously approved version (danielputerman) on 2026-05-26, but movsho is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v0.5.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.5.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.5.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.4.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.4.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.4.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.4.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.