← Home

@mmnto/mcp

MCP server for Totem — AI persistent memory and context layer

100
Versions
Apache-2.0
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures No source commit

Maintainers

satur8d

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance missing-githead AI (provenance): SLSA provenance attestation present; gitHead absence is superseded by Sigstore attestation for this package. ai
typosquat typosquat.levenshtein:yup AI (typosquat): Scoped package @mmnto/mcp is an MCP server for the Totem project; no intent to impersonate yup. ai

Versions (showing 100 of 146)

Version Deps Published
1.104.0 5 / 3
1.103.0 5 / 3
1.102.0 5 / 3
1.101.2 5 / 3
1.101.1 5 / 3
1.101.0 5 / 3
1.100.0 5 / 3
1.99.0 5 / 3
1.98.1 5 / 3
1.98.0 5 / 3
1.97.0 5 / 3
1.96.0 5 / 3
1.95.0 5 / 3
1.94.0 5 / 3
1.93.0 5 / 3
1.92.0 5 / 3
1.44.0 5 / 3
1.43.6 5 / 3
1.43.5 5 / 3
1.43.4 5 / 3
1.43.3 5 / 3
1.43.2 5 / 3
1.43.1 5 / 3
1.43.0 5 / 3
1.42.0 5 / 3
1.41.0 5 / 3
1.40.2 5 / 3
1.40.1 5 / 3
1.40.0 5 / 3
1.39.0 5 / 3
1.38.0 5 / 3
1.37.0 5 / 3
1.36.0 5 / 3
1.35.0 5 / 3
1.34.3 5 / 3
1.34.2 5 / 3
1.34.1 5 / 3
1.34.0 5 / 3
1.33.0 5 / 3
1.32.0 5 / 3
1.31.0 5 / 3
1.30.1 5 / 3
1.30.0 5 / 3
1.29.0 5 / 3
1.28.1 5 / 3
1.28.0 5 / 3
1.27.0 5 / 3
1.26.1 5 / 3
1.26.0 5 / 3
1.25.0 5 / 3
1.24.0 5 / 3
1.23.0 5 / 3
1.22.0 5 / 3
1.21.0 5 / 3
1.20.0 5 / 3
1.19.0 5 / 3
1.18.3 5 / 3
1.18.2 5 / 3
1.18.1 5 / 3
1.18.0 5 / 3
1.17.1 5 / 3
1.17.0 5 / 3
1.16.1 5 / 3
1.9.0 4 / 3
1.8.5 4 / 3
1.8.3 4 / 3
1.8.2 4 / 3
1.8.1 4 / 3
1.8.0 4 / 3
1.7.2 4 / 3
1.7.1 4 / 3
1.7.0 4 / 3
1.6.3 4 / 3
1.6.2 4 / 3
1.3.19 4 / 3
1.3.18 4 / 3
1.3.17 4 / 3
1.3.16 4 / 3
1.3.15 4 / 3
1.3.14 4 / 3
1.3.13 4 / 3
1.3.12 4 / 3
1.3.11 4 / 3
1.3.10 4 / 3
1.3.9 4 / 3
1.3.8 4 / 3
1.3.7 4 / 3
1.3.6 4 / 3
1.3.5 4 / 3
1.3.4 4 / 3
1.3.3 4 / 3
1.3.2 4 / 3
1.3.1 4 / 3
1.3.0 4 / 3
1.2.0 4 / 3
1.1.0 4 / 3
1.0.0 4 / 3
0.44.0 4 / 3
0.43.0 4 / 3
0.42.0 4 / 3
Showing 100 of 146 Next page →

v1.104.0

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v1.103.0

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v1.102.0

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v1.101.2

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v1.101.1

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v1.101.0

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v1.100.0

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v1.99.0

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v1.98.1

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v1.98.0

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v1.97.0

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v1.96.0

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v1.95.0

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v1.94.0

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v1.93.0

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v1.92.0

2 findings
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

INFO Publisher changed: satur8d → GitHub Actions (on 2026-07-10, now via trusted publisher with provenance) provenance

This version was published by a different npm account (GitHub Actions) than the most recent previously approved version (satur8d) on 2026-07-10, but it carries Sigstore provenance attestation. This means the package moved to a trusted publisher (CI/CD with OIDC, e.g. GitHub Actions) — a supply-chain integrity improvement, not a compromise, since a stolen npm token cannot forge provenance bound to the source repository. Recorded as INFO for audit trail.