Skip to content

Synapse Layer — Trust Infrastructure for AI Agents MCP server

io.github.SynapseLayer/synapse-layerSynapseLayerstreamable-httpv2.4.6Scanned

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

13 tools: 1 do something that can't be undone, 8 change things and 4 only read.

Tools: 0 delete, 1 irreversible, 8 write, 4 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here does something that can't be undone. Govern it.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Synapse Layer — Trust Infrastructure for AI Agents MCP server can do

The Synapse Layer — Trust Infrastructure for AI Agents MCP server is published by the GitHub account SynapseLayer. It has 13 tools. It can do things that cannot be undone, such as sending, paying or publishing (neural_handover) and create or change data (8 tools: save_to_synapse, process_text, health_check, initialize_context and 4 more), but cannot delete data. 4 tools only read.

None of its tools reads private data, brings in text other people write, or sends data out.

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.

Last scanned Nov 16, 2026, version 2.4.6.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

13 tools

Can't be undone 1Claude Code: ask
  • neural_handoverTransfer contextual state between agents with continuity controls.No findings

    Why it is in this group

    • The description's first verb is "transfer": a word for a change that another call does not undo.
    Description, as the server wrote it
    Transfer contextual state between agents with continuity controls.

    Annotations the server declares

    • title: Neural Handover
    • readOnlyHint: false
    • openWorldHint: false
Changes things 8Claude Code: ask
  • health_checkCheck service availability, engine version, and storage health.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Check service availability, engine version, and storage health. Public method.

    Annotations the server declares

    • title: Health Check
    • readOnlyHint: true
    • openWorldHint: false
  • initialize_contextInitialize a persistent memory context for a conversation or agent session.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Initialize Context
    • readOnlyHint: true
    • openWorldHint: false
  • memory_feedbackSubmit feedback to adjust trust scoring for stored memories.No findings

    Why it is in this group

    • The description's first verb is "submit": a word for a change.
    Description, as the server wrote it
    Submit feedback to adjust trust scoring for stored memories.

    Annotations the server declares

    • title: Memory Feedback
    • readOnlyHint: false
    • openWorldHint: false
  • process_textExtract candidate memories from free-form text with governance filters and sanitization.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Extract candidate memories from free-form text with governance filters and sanitization.

    Annotations the server declares

    • title: Process Text
    • readOnlyHint: false
    • openWorldHint: false
  • recall_memoryRecall persisted memory by query.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Recall persisted memory by query. Alias of recall.

    Annotations the server declares

    • title: Recall Memory
    • readOnlyHint: true
    • openWorldHint: false
  • save_memorySave a memory entry to the persistent store.No findings

    Why it is in this group

    • The name "save_memory" says "save": a word for a change.
    Description, as the server wrote it
    Save a memory entry to the persistent store. Alias of save_to_synapse.

    Annotations the server declares

    • title: Save Memory
    • readOnlyHint: false
    • idempotentHint: true
    • openWorldHint: false
  • save_to_synapsePersist memory with encryption at rest, sanitization, and deduplication controls.No findings

    Why it is in this group

    • The name "save_to_synapse" says "save": a word for a change.
    Description, as the server wrote it
    Persist memory with encryption at rest, sanitization, and deduplication controls.

    Annotations the server declares

    • title: Save to Synapse
    • readOnlyHint: false
    • idempotentHint: true
    • openWorldHint: false
  • store_memoryStore structured memory with metadata and trust scoring.No findings

    Why it is in this group

    • The name "store_memory" says "store": a word for a change.
    Description, as the server wrote it
    Store structured memory with metadata and trust scoring.

    Annotations the server declares

    • title: Store Memory
    • readOnlyHint: false
    • idempotentHint: true
    • openWorldHint: false
Only reads 4Show 4 read-only tools
  • list_memoriesList memory metadata with pagination and governance limits.No findings

    Why it is in this group

    • The name "list_memories" says "list": a word for reading.
    Description, as the server wrote it
    List memory metadata with pagination and governance limits.

    Annotations the server declares

    • title: List Memories
    • readOnlyHint: true
    • openWorldHint: false
  • recallRetrieve relevant persisted memory using semantic, temporal, priority, or hybrid routing.No findings

    Why it is in this group

    • The description's first verb is "retrieve": a word for reading.
    Description, as the server wrote it
    Retrieve relevant persisted memory using semantic, temporal, priority, or hybrid routing. Governance: requires reason (10–200 chars). Rate limit: 20/min.

    Annotations the server declares

    • title: Recall Memory
    • readOnlyHint: true
    • openWorldHint: false
  • slo_reportReturn uptime and SLO metrics for the MCP service.No findings

    Why it is in this group

    • The description's first verb is "return": a word for reading.
    Description, as the server wrote it
    Return uptime and SLO metrics for the MCP service.

    Annotations the server declares

    • title: SLO Report
    • readOnlyHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:00 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
9
Protocol version
2025-11-25
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 9 tools that change things (1 irreversible, 8 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://forge.synapselayer.org/api/mcp: tools/list returned 13 tools to an anonymous client, including neural_handover (irreversible), save_to_synapse (write), process_text (write), health_check (write), initialize_context (write) and 4 more

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools11 changed.~11 changedView diff

Install

Pinned to version 2.4.6. Values in angle brackets are yours to fill in.

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

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__synapse-layer__recall",
      "mcp__synapse-layer__search",
      "mcp__synapse-layer__list_memories",
      "mcp__synapse-layer__slo_report"
    ],
    "ask": [
      "mcp__synapse-layer__save_to_synapse",
      "mcp__synapse-layer__process_text",
      "mcp__synapse-layer__health_check",
      "mcp__synapse-layer__initialize_context",
      "mcp__synapse-layer__save_memory",
      "mcp__synapse-layer__store_memory",
      "mcp__synapse-layer__recall_memory",
      "mcp__synapse-layer__memory_feedback",
      "mcp__synapse-layer__neural_handover"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as synapse-layer. Review it before you use it.

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.github.SynapseLayer/synapse-layer/verify?hash=9ccd44a05775372a84defec351b743ae82c8519543cce8010b0d37d806ed1bd4" | jq -e '.changed == false'

Pinned hash 9ccd44a05775, from Nov 16, 2026, 06:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.github.SynapseLayer/synapse-layer/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.SynapseLayer/synapse-layer
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.SynapseLayer/synapse-layer.svg)](https://radar.anlyon.com/servers/io.github.SynapseLayer/synapse-layer)

Source: MCP Registry · repository. Synced Oct 21, 2026, 18:21 UTC.

Synapse Layer — Trust Infrastructure for AI Agents MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Synapse Layer — Trust Infrastructure for AI Agents MCP server safe?

No scan can promise that. What its definitions show: 13 tools, 9 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Synapse Layer — Trust Infrastructure for AI Agents MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Synapse Layer — Trust Infrastructure for AI Agents MCP server do things that cannot be undone?

Yes. 1 tool can send, pay, publish or merge: neural_handover.

What tools does the Synapse Layer — Trust Infrastructure for AI Agents MCP server have?

13 tools: 1 irreversible, 8 write, 4 read. neural_handover, save_to_synapse, process_text, health_check, initialize_context, save_memory, store_memory, recall_memory and 5 more.

Does the Synapse Layer — Trust Infrastructure for AI Agents MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Synapse Layer — Trust Infrastructure for AI Agents MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Synapse Layer — Trust Infrastructure for AI Agents MCP server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Nov 2, 2026. Every change is on this page and in its Atom feed.