← Home

@microsoft/agentmesh-mcp-proxy

npm Repository Homepage

Public Preview — Security proxy for MCP servers: The Firewall for Model Context Protocol

12
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

microsoft1esmicrosoft-oss-releases

Keywords

mcpmodel-context-protocolsecurityproxyai-safetyagentmeshfirewallpolicy-engine

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:winston AI (phantom-deps): Declared runtime dependency; used for logging in security proxy. ai
phantom-deps phantom-dep:crypto-js AI (phantom-deps): Declared runtime dependency; used for cryptographic operations in security proxy. ai
phantom-deps phantom-dep:@modelcontextprotocol/sdk AI (phantom-deps): Declared runtime dependency; core MCP SDK for this proxy implementation. ai

Versions (showing 12 of 12)

Version Deps Published
4.0.0 6 / 4
3.7.0 6 / 4
3.6.0 6 / 4
3.5.0 6 / 4
3.4.0 6 / 4
3.3.0 6 / 4
3.2.2 6 / 4
3.2.1 6 / 4
3.2.0 6 / 4
3.1.0 6 / 4
3.0.2 6 / 4
1.0.0 6 / 4

v4.0.0

1 finding
LOW No provenance attestation provenance

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

v3.7.0

1 finding
LOW No provenance attestation provenance

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

v3.6.0

1 finding
LOW No provenance attestation provenance

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

v3.5.0

1 finding
LOW No provenance attestation provenance

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

v3.4.0

1 finding
LOW No provenance attestation provenance

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

v3.3.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.

v3.2.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.

v3.2.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.

v3.2.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.

v3.1.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.

v3.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.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.