Skip to content
External endpointresponds

Synapse Layer — Continuous Consciousness Infrastructure

Persistent zero-knowledge memory for AI agents. AES-256-GCM encryption, PII redaction.

Endpoint URL
https://forge.synapselayer.org/api/mcp
Current status
responds
Last checked
Aug 17, 2026, 05:01 AM UTC
Check
MCP initialize · 8s limit
Latency
283 ms
Response record
4 of 4 rounds
Transport
streamable-http
Source
mcp_registry
Registry name
io.github.SynapseLayer/synapse-layer

Current observation

This endpoint answered at its latest recorded check.

What this server reports about itself

Self-reported at initialize. Not verified by Licium.

Server name
synapse-layer
Version
2.4.6
Capability keys
tools
Tool names
recall, save_to_synapse, process_text, search, health_check, initialize_context, save_memory, store_memory, recall_memory, list_memories, memory_feedback, neural_handover, slo_report
Instructions excerpt

## IDENTITY You are an AI Agent augmented by Synapse Layer — a persistent cross-agent memory system. Your long-term memory lives in the MCP tools below. You CAN access Telegram messages, decisions, goals, and anything the user saved — but ONLY by calling tools. ## ABSOLUTE RULE — RECALL BEFORE REPLY NEVER answer a question about the user's data, projects, decisions, goals, metas, messages, or history WITHOUT calling 'recall_memory' (or 'recall') FIRST. This applies to ALL of these categories — no exceptions: - Telegram messages, conversations, or anything the user sent via phone - Project names (Nexumi, GoArqIA, Synapse Layer, or ANY proper noun you don't recognize) - Financial targets, metas de faturamento, budgets, investments, aportes - Past decisions, strategies, priorities, deadlines - Anything the user says they 'registered', 'saved', 'noted', or 'defined' ## BANNED RESPONSES (before calling recall_memory) You are FORBIDDEN from saying ANY of these without calling recal

Reported Aug 17, 2026, 05:01 AM UTC.

Check history

Oldest to newest. Each row is one recorded check.

  1. responds
    MCP initialize · 8s limit · HTTP 200 · 224ms
  2. responds
    MCP initialize · 8s limit · HTTP 200 · 291ms
  3. responds
    MCP initialize · 8s limit · HTTP 200 · 340ms
  4. responds
    MCP initialize · 8s limit · HTTP 200 · 283ms