Synapse Layer — Trust Infrastructure for AI Agents MCP Server

by synapselayer Your server? Claim it

answering

Synapse Layer — Trust Infrastructure for AI Agents is answering right now. Last checked 4 min ago. It exposes 13 tools. Last commit 22 Oct 2026.

MCP-native Trust Infrastructure for AI Agents. Persistent encrypted memory with Trust Quotient.

Uptime history 91 days of history · worst day 58%

91 days agonow

100.0%

Uptime 24h

91 of 91 checks

Tools

read from the server

686 ms

Response time

average over 24h

Stars

last commit 22 Oct 2026

What changed 42

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 14 August 2026. No other catalogue keeps this.

29 Oct 11 tools changed the parameters they ask for22 times that day initialize_context, list_memories, memory_feedback and 8 more

10 Oct a tool changed the parameters it asks for process_text

14 Sep a tool changed the parameters it asks for save_to_synapse

2 Sep 7 tools changed the parameters they ask for list_memories, recall, recall_memory and 4 more

18 Aug 3 tools changed the parameters they ask for6 times that day save_memory, save_to_synapse, store_memory

17 Aug a tool changed the parameters it asks for memory_feedback

14 Aug 2 tool descriptions were rewritten initialize_context, search

14 Aug 2 tools changed the parameters they ask for initialize_context, search

and 14 more, back to 14 August 2026

Nothing serious here today

Today is the operative word: we check Synapse Layer — Trust Infrastructure for AI Agents every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 4 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add synapse-layer --transport http https://forge.synapselayer.org/api/mcp

Settings → Connectors → Add custom connector, then paste this address

https://forge.synapselayer.org/api/mcp

~/.codex/config.toml

[mcp_servers.synapse-layer]
url = "https://forge.synapselayer.org/api/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "synapse-layer": {
      "url": "https://forge.synapselayer.org/api/mcp"
    }
  }
}

.vscode/mcp.json

{
  "servers": {
    "synapse-layer": {
      "type": "http",
      "url": "https://forge.synapselayer.org/api/mcp"
    }
  }
}

Available tools 13

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

recall

recall

Retrieve relevant persisted memory using semantic, temporal, priority, or hybrid routing. Governance: requires reason (10–200 chars). Rate limit: 20/min.

recall_memory

Recall persisted memory by query. Alias of recall.

save

save_memory

Save a memory entry to the persistent store. Alias of save_to_synapse.

save_to_synapse

Persist memory with encryption at rest, sanitization, and deduplication controls.

health

health_check

Check service availability, engine version, and storage health. Public method.

initialize

initialize_context

Initialize a persistent memory context for a conversation or agent session. Returns REDACTED metadata by default (detail="summary"). Use detail="full" with a reason (10–200 chars) to retrieve plaintext content under MEMORY_EXPORT_GOVERNANCE_V1.

memories

list_memories

List memory metadata with pagination and governance limits.

memory

memory_feedback

Submit feedback to adjust trust scoring for stored memories.

neural

neural_handover

Transfer contextual state between agents with continuity controls.

process

process_text

Extract candidate memories from free-form text with governance filters and sanitization.

search

Search persisted memory across agent scopes using full-text matching. Governance: requires reason (10–200 chars) because results contain plaintext content.

slo

slo_report

Return uptime and SLO metrics for the MCP service.

store

store_memory

Store structured memory with metadata and trust scoring.

Endpoints

URL	Transport	State	Latency	Checked
https://forge.synapselayer.org/api/mcp	streamable-http	answering	611 ms	4 min ago

Alternatives to Synapse Layer — Trust Infrastructure for AI Agents

same job, measured the same way

MemoraEU

by pquattro

Zero-knowledge persistent memory layer for AI agents. Encrypted client-side, hosted in France.

local only

Ori Memory

by aayoawoyemi

Persistent memory infrastructure for AI agents. Identity, knowledge graph, and search.

136 installs/wk local only

Openfuse MCP

by openfused

Encrypted mail, shared memory, and persistent context for AI agents.

90 installs/wk local only

WARM

by writerslogic

Local persistent memory for AI agents with recall, search, forgetting, and encrypted storage.

377 installs/wk local only

Agentverse Memory

by fetchai

Graph-native persistent memory for AI agents — 33 MCP tools, zero-LLM writes.

answering

Engram

by hbarefoot

Local-first persistent memory for AI agents — SQLite + local embeddings, MCP-native, no cloud.

53 installs/wk local only

LinkLore

by linklore

AI-native structured memory for agents (MCP). Built for agents, not humans.

163 installs/wk local only

Agtrepo Memory

by agtrepo

Encrypted, pay-per-use persistent memory storage for AI agents, gated by x402 payments on Base.

6 tools answering

Synapse Layer — Trust Infrastructure for AI Agents — questions

Answers built from our own checks of this server.

What can Synapse Layer — Trust Infrastructure for AI Agents do?

It exposes 13 tools, read directly from the server on our last check. Among them: health_check, initialize_context, list_memories, memory_feedback, neural_handover, process_text and 7 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

What is Synapse Layer — Trust Infrastructure for AI Agents mostly used for?

Its tools cluster around recall and save. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.

Is Synapse Layer — Trust Infrastructure for AI Agents working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 686 ms. The bar chart above shows every period we have measured.

How do I connect Synapse Layer — Trust Infrastructure for AI Agents?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does Synapse Layer — Trust Infrastructure for AI Agents need an API key?

No. Synapse Layer — Trust Infrastructure for AI Agents completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 13 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is Synapse Layer — Trust Infrastructure for AI Agents?

It answers our handshake in 686 ms on average, which is faster than 14% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.

Is Synapse Layer — Trust Infrastructure for AI Agents open source?

The code is open source: it is published under the Apache-2.0 licence, written in Python, 13 stars on GitHub and 1 open issue. The licence covers the code in the repository, not the hosted service at forge.synapselayer.org, which runs on its operator's own terms.