Synapse Layer — Zero-Knowledge Memory
PYPI · SYNAPSE-LAYER · SCANNED SEP 26
Zero-Knowledge Context™ & Neural Handover™ for AI Agents. The Trust Layer for AI Memory.
Available components
Deprecated
This server is marked deprecated in the MCP registry.
The registry records this reason: duplicate/superseded by io.github.SynapseLayer/synapse-layer 2.4.6.
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security50
- Malware scan not yet available for this package.Unverified
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs setuptools.build_meta at install time, a recognised native-build step with no shell scripting around it. View diagnostics → Pass
- 0 of 17 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency48
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 79 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability0
- Schema quality not yet verified: our sandbox could not run this package, so we have no schema to assess.Unverified
Stability & Change Management0
- Stability not yet verified: our sandbox could not run this package, so we have no schema to compare.Unverified
Tool Coverage0
- Tool coverage not yet verified: our sandbox could not run this package, so we have no tool definitions to assess.Unverified
Tool Safety0
- Tool safety not yet verified: our sandbox could not run this package, so we have no tool text to scan.Unverified
Capabilities0
- Protocol version not yet verified: our sandbox could not run this package, so we never saw its MCP handshake.Unverified
Unverified: 5 categories
Categories scored 0 because our sandbox could not run this package, so we have no schema for these checks to read. That is a gap on our side rather than a finding about the package, and we only credit what we can confirm, so the score stands at 0 until we can run it. How we score packages →
How do I install the Synapse Layer — Zero-Knowledge Memory MCP server?
Synapse Layer — Zero-Knowledge Memory runs locally as a PyPI package, launched with uvx synapse-layer. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · synapse-layer
claude mcp add synapselayer-synapse-secure-memory -- uvx synapse-layer
{
"mcpServers": {
"synapselayer-synapse-secure-memory": {
"command": "uvx",
"args": [
"synapse-layer"
]
}
}
} {
"servers": {
"synapselayer-synapse-secure-memory": {
"command": "uvx",
"args": [
"synapse-layer"
]
}
}
} codex mcp add synapselayer-synapse-secure-memory -- uvx synapse-layer
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"synapselayer-synapse-secure-memory": {
"type": "local",
"command": [
"uvx",
"synapse-layer"
],
"enabled": true
}
}
} openclaw mcp add synapselayer-synapse-secure-memory --command uvx --arg synapse-layer
mcp_servers:
synapselayer-synapse-secure-memory:
command: "uvx"
args: ["synapse-layer"] {
"McpServers": {
"synapselayer-synapse-secure-memory": {
"Transport": "stdio",
"Command": "uvx",
"Arguments": [
"synapse-layer"
]
}
}
} assistant mcp add synapselayer-synapse-secure-memory -t stdio -c uvx -a synapse-layer
{
"mcpServers": {
"synapselayer-synapse-secure-memory": {
"command": "uvx",
"args": [
"synapse-layer"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 26 Sept 26 −12
- Malware scan: pass → unverified ▼ security
- License: fail → pass ▲ functional
- Licence: Apache 2.0 → Apache-2.0 functional
- 25 Sept 26 +15
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 17 Sept 26 −15
- Malware scan: pass → unverified ▼ security
- 16 Sept 26 +15
- Malware scan: unverified → pass ▲ security
- 14 Sept 26 −15
- Malware scan: pass → unverified ▼ security
- 13 Sept 26 +15
- Malware scan: unverified → pass ▲ security
- 9 Sept 26 −15
- Malware scan: pass → unverified ▼ security
- 8 Sept 26 +15
- Malware scan: unverified → pass ▲ security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 26 Sept 2026 · Analysed pypi/synapse-layer@1.0.7
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | setuptools.build_meta |
Background: Why install scripts are a supply-chain risk →
Dependencies 17 packages
| Packages resolved | 17 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
Tools for package channels are captured by running the package in an isolated sandbox. Our sandbox could not run this package, so no tool list has been captured. That is a gap on our side, not a finding about the package.
What is the Synapse Layer — Zero-Knowledge Memory MCP server?
Synapse Layer — Zero-Knowledge Memory is an MCP server listed in the public MCP registry as io.github.SynapseLayer/synapse-secure-memory. Zero-Knowledge Context™ & Neural Handover™ for AI Agents. The Trust Layer for AI Memory. This page covers its PyPI package (synapse-layer).
Is the Synapse Layer — Zero-Knowledge Memory MCP server safe to use?
Synapse Layer — Zero-Knowledge Memory scores 25 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 26 September 2026. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
Is the Synapse Layer — Zero-Knowledge Memory MCP server still maintained?
Synapse Layer — Zero-Knowledge Memory is marked deprecated in the MCP registry. We last reached this channel on 26 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Synapse Layer — Zero-Knowledge Memory MCP server under?
Synapse Layer — Zero-Knowledge Memory declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.