← Home

@grackle-ai/mcp

npm Repository Homepage

MCP (Model Context Protocol) server for Grackle — translates MCP tool calls to ConnectRPC

11
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

nickpape

Keywords

gracklemcpmodel-context-protocolai-agents

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
typosquat typosquat.levenshtein:yup AI (typosquat): Scoped package @grackle-ai/mcp is not a typosquat of yup; Levenshtein match is coincidental. ai
phantom-deps phantom-dep:@bufbuild/protobuf AI (phantom-deps): @bufbuild/protobuf is a legitimate declared dep used via generated protobuf code; phantom-dep heuristic fires on indirect usage patterns. ai

Versions (showing 11 of 211)

Version Deps Published
0.72.1 7 / 4
0.72.0 7 / 4
0.71.3 7 / 4
0.71.2 7 / 4
0.71.1 7 / 4
0.71.0 7 / 4
0.70.6 7 / 4
0.70.5 7 / 4
0.70.4 7 / 4
0.70.3 7 / 4
0.70.2 7 / 4

v0.72.1

1 finding
LOW No provenance attestation provenance

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

v0.72.0

1 finding
LOW No provenance attestation provenance

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

v0.71.3

1 finding
LOW No provenance attestation provenance

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

v0.71.2

1 finding
LOW No provenance attestation provenance

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

v0.71.1

1 finding
LOW No provenance attestation provenance

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

v0.71.0

1 finding
LOW No provenance attestation provenance

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

v0.70.6

1 finding
LOW No provenance attestation provenance

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

v0.70.5

1 finding
LOW No provenance attestation provenance

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

v0.70.4

1 finding
LOW No provenance attestation provenance

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

v0.70.3

1 finding
LOW No provenance attestation provenance

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

v0.70.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.