← Home

@danainnovations/directory-mcp

npm

MCP server for Sonance employee directory — gives AI tools access to real employee data

4
Versions
UNLICENSED
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

tcpalm-relliotta1130silaswrv

Keywords

mcpmodel-context-protocolsonancedirectoryemployee

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance no-provenance AI (provenance): Internal/proprietary package; provenance attestation not expected for this org's tooling. ai
license uncommon-license:UNLICENSED AI (license): Intentionally proprietary/internal package; UNLICENSED is appropriate. ai

Versions (showing 4 of 4)

Version Deps Published
0.3.0 3 / 2
0.2.1 3 / 2
0.2.0 3 / 2
0.1.0 3 / 2

v0.2.1

1 finding
INFO No provenance attestation provenance

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

v0.2.0

1 finding
INFO No provenance attestation provenance

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

v0.1.0

1 finding
INFO No provenance attestation provenance

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