@northbound-run/matrix-agent-mcp
MCP server for Matrix messaging. Exposes Matrix rooms, messages, members, and media as MCP tools and resources so AI agents can read and write to Matrix over the [Model Context Protocol](https://modelcontextprotocol.io/).
Supply chain provenance
Status for the latest visible version.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:base64-decode | AI (semgrep): Decodes media payload for Matrix upload — legitimate MCP media tool pattern, not a malware indicator. | ai |
Versions (showing 19 of 19)
| Version | Deps | Published |
|---|---|---|
| 0.7.0 | 5 / 4 | |
| 0.6.1 | 5 / 4 | |
| 0.6.0 | 5 / 4 | |
| 0.5.1 | 5 / 4 | |
| 0.5.0 | 5 / 4 | |
| 0.4.0 | 5 / 4 | |
| 0.3.8 | 4 / 2 | |
| 0.3.7 | 3 / 2 | |
| 0.3.6 | 3 / 2 | |
| 0.3.5 | 3 / 2 | |
| 0.3.4 | 3 / 2 | |
| 0.3.3 | 3 / 2 | |
| 0.3.2 | 3 / 2 | |
| 0.3.1 | 3 / 2 | |
| 0.1.9 | 3 / 2 | |
| 0.1.8 | 3 / 2 | |
| 0.1.7 | 3 / 2 | |
| 0.1.4 | 3 / 2 | |
| 0.1.0 | 3 / 2 |
v0.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.