← Home

@vaiftech/mcp

npm Repository Homepage

MCP server for VAIF Studio — connect Claude Code to your VAIF project

10
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

vaiftechnologies

Keywords

vaifmcpclaudeaibackend

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
typosquat typosquat.levenshtein:yup AI (typosquat): Scoped package @vaiftech/mcp is an MCP server, not a typosquat of yup; name similarity is coincidental. ai
phantom-deps phantom-dep:zod AI (phantom-deps): tsup bundles deps; direct import not visible in source but zod is a legitimate runtime dependency. ai
phantom-deps phantom-dep:@modelcontextprotocol/sdk AI (phantom-deps): tsup bundles deps; @modelcontextprotocol/sdk is a legitimate runtime dependency for this MCP server. ai

Versions (showing 10 of 10)

Version Deps Published
1.5.2 2 / 3
1.5.1 2 / 3
1.5.0 2 / 3
1.4.0 2 / 3
1.2.1 2 / 3
1.2.0 2 / 3
1.1.0 2 / 3
1.0.2 2 / 3
1.0.1 2 / 3
1.0.0 2 / 3

v1.5.1

1 finding
LOW No provenance attestation provenance

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

v1.5.0

1 finding
LOW No provenance attestation provenance

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

v1.4.0

1 finding
LOW No provenance attestation provenance

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

v1.2.1

2 findings
HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: vaiftechnologies.

LOW No provenance attestation provenance

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

v1.2.0

1 finding
LOW No provenance attestation provenance

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

v1.1.0

1 finding
LOW No provenance attestation provenance

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

v1.0.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.

v1.0.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.

v1.0.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.