Synapse Layer — Trust Infrastructure for AI Agents
REMOTE · FORGE.SYNAPSELAYER.ORG · SCANNED SEP 26
MCP-native Trust Infrastructure for AI Agents. Persistent encrypted memory with Trust Quotient.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 13 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability62
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 3194 tokens (~245/item across 13 items; 13 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "neural_handover" implies "transfer" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 14 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the Synapse Layer — Trust Infrastructure for AI Agents MCP server?
Synapse Layer — Trust Infrastructure for AI Agents is a hosted endpoint at https://forge.synapselayer.org/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · forge.synapselayer.org
claude mcp add --transport http synapselayer-synapse-layer 'https://forge.synapselayer.org/api/mcp'
{
"mcpServers": {
"synapselayer-synapse-layer": {
"url": "https://forge.synapselayer.org/api/mcp"
}
}
} {
"servers": {
"synapselayer-synapse-layer": {
"type": "http",
"url": "https://forge.synapselayer.org/api/mcp"
}
}
} [mcp_servers.synapselayer-synapse-layer] url = "https://forge.synapselayer.org/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"synapselayer-synapse-layer": {
"type": "remote",
"url": "https://forge.synapselayer.org/api/mcp",
"enabled": true
}
}
} openclaw mcp add synapselayer-synapse-layer --url 'https://forge.synapselayer.org/api/mcp' --transport streamable-http
mcp_servers:
synapselayer-synapse-layer:
url: "https://forge.synapselayer.org/api/mcp" {
"McpServers": {
"synapselayer-synapse-layer": {
"Transport": "http",
"Url": "https://forge.synapselayer.org/api/mcp"
}
}
} assistant mcp add synapselayer-synapse-layer -t streamable-http -u 'https://forge.synapselayer.org/api/mcp'
{
"mcpServers": {
"synapselayer-synapse-layer": {
"type": "http",
"url": "https://forge.synapselayer.org/api/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 15 Sept 26 0
- “save_to_synapse” reworded the description of “importance” cosmetic
1 cosmetic change on this day. Switch on “Show cosmetic changes” to see it.
- 13 Sept 26 0
- Stability: fail → pass ▲ security
- 3 Sept 26 0
- Schema quality: 215 → 245 ▼ functional
- Schema quality: good → excellent functional
- “store_memory” added an optional parameter “subject” cosmetic
- “search” added an optional parameter “subject” cosmetic
- “save_to_synapse” added an optional parameter “subject” cosmetic
- “save_memory” added an optional parameter “subject” cosmetic
- “recall_memory” added an optional parameter “subject” cosmetic
- “recall” added an optional parameter “subject” cosmetic
- “list_memories” added an optional parameter “subject” cosmetic
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 18 Aug 26 0
- Schema quality: 186 → 215 ▼ functional
- “save_to_synapse” added an optional parameter “force_intent” cosmetic
- “save_to_synapse” added an optional parameter “intent_reason” cosmetic
- “store_memory” added an optional parameter “force_intent” cosmetic
- “store_memory” added an optional parameter “intent_reason” cosmetic
- “save_memory” added an optional parameter “force_intent” cosmetic
- “save_memory” added an optional parameter “intent_reason” cosmetic
- 17 Aug 26 0
- Tool “save_to_synapse” now declares an output schema ▲ functional
- Tool “slo_report” now declares an output schema ▲ functional
- Tool “store_memory” now declares an output schema ▲ functional
- Tool “recall” now declares an output schema ▲ functional
- Tool “process_text” now declares an output schema ▲ functional
- Tool “neural_handover” now declares an output schema ▲ functional
- Tool “memory_feedback” now declares an output schema ▲ functional
- Tool “list_memories” now declares an output schema ▲ functional
- Tool “initialize_context” now declares an output schema ▲ functional
- Tool “health_check” now declares an output schema ▲ functional
- Tool “recall_memory” now declares an output schema ▲ functional
- Tool “save_memory” now declares an output schema ▲ functional
- Tool “search” now declares an output schema ▲ functional
- “memory_feedback” added an optional parameter “session_id” cosmetic
- “memory_feedback” added an optional parameter “memory_id” cosmetic
- “memory_feedback” reworded the description of “sessionId” cosmetic
- “memory_feedback” reworded the description of “memoryId” cosmetic
- “memory_feedback” made “memoryId” optional cosmetic
- 14 Aug 26 0
- Stability: 0.60 → fail ▼ security
- A breaking change shipped without a version bump: still 2.4.6 ▼ security
- Tool “initialize_context” rewrote its description, which is the text the model reads security
- Tool “search” rewrote its description, which is the text the model reads security
- Schema quality: 165 → 182 ▼ functional
- “search” added a required parameter “reason”, so existing callers break ▼ functional
- “initialize_context” added an optional parameter “detail” cosmetic
- “initialize_context” added an optional parameter “reason” cosmetic
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 · Probed https://forge.synapselayer.org/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=forge.synapselayer.org | CN=WE1,O=Google Trust Services,C=US | 3 Aug 2026 | 1 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | 8817d69f6d9ea81c13c774e916b64fee |
| SANs: forge.synapselayer.org | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of forge.synapselayer.org. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| org. | present | 26974 | 8 | Verified |
| synapselayer.org. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | no-referrer |
| permissions-policy | camera=(), microphone=(), geolocation=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://forge.synapselayer.org/api/mcp | Verified | 200 | |
| http (plaintext) | http://forge.synapselayer.org/api/mcp | HTTPS enforced | 301 | https://forge.synapselayer.org/api/mcp |
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 →
health_check ~22
Check service availability, engine version, and storage health. Public method.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| dbLatencyMs | number | – | – |
| status | string | yes | – |
| version | string | yes | – |
No examples provided.
initialize_context ~159
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.
| Name | Type | Req | Description |
|---|---|---|---|
| detail | string | – | Detail level. "summary" (default) = redacted metadata only, no plaintext. "full" = plaintext content; REQUIRES the reason parameter and is audit-logged. |
| reason | string | – | REQUIRED only when detail="full" (10–200 chars). Audit policy: MEMORY_EXPORT_GOVERNANCE_V1. Human-readable justification for retrieving PLAINTEXT context. Without it, detail="full" WILL fail with cod… |
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | – | – |
| memories | array | – | – |
| scope | string | yes | – |
No examples provided.
list_memories ~185
List memory metadata with pagination and governance limits.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | – | Agent identifier (canonical or alias). Used only when scope="agent" or scope is inferred. |
| limit | number | – | Maximum memory metadata rows to return. Hard-capped: default 5, max 10. Values above 10 are silently reduced to 10. |
| scope | string | – | Explicit memory scope. "agent" (default, fail-closed) = lists memories for the given agent_id (or the token agent). "tenant" = lists memories across all agents of the authenticated tenant. |
| subject | string | – | ESCOPO1 (optional): opaque 8-128 char token ([A-Za-z0-9._:-]) that isolates memory to a single person within a shared connect-token. Omit for token-scoped behavior. Never include PII/email. |
| Name | Type | Req | Description |
|---|---|---|---|
| count | number | yes | – |
| memories | array | yes | – |
| total | number | – | – |
No examples provided.
memory_feedback ~122
Submit feedback to adjust trust scoring for stored memories.
| Name | Type | Req | Description |
|---|---|---|---|
| memoryId | string | – | Deprecated camelCase alias of memory_id — still accepted for backward compatibility. |
| memory_id | string | – | ID of the memory to provide feedback on (canonical snake_case name). |
| sessionId | string | – | Deprecated camelCase alias of session_id — still accepted for backward compatibility. |
| session_id | string | – | Optional session identifier for tracking (canonical snake_case name). |
| signal | string | yes | Feedback signal: used (auto), helpful (positive), irrelevant (negative), ignored. |
| Name | Type | Req | Description |
|---|---|---|---|
| memoryId | string | yes | – |
| signal | string | – | – |
| success | boolean | yes | – |
No examples provided.
neural_handover ~95
Transfer contextual state between agents with continuity controls.
| Name | Type | Req | Description |
|---|---|---|---|
| consuming_agent | string | – | Agent identifier consuming the handover (defaults to token agent). |
| reason | string | yes | REQUIRED (10–200 chars). Human-readable justification for consuming this handover. Example: "Receiving project context from Claude session." |
| token | string | yes | The handover token (64 hex chars). Generated by the source agent/user in Forge UI. |
| Name | Type | Req | Description |
|---|---|---|---|
| handoverId | string | – | – |
| status | string | yes | – |
No examples provided.
process_text ~95
Extract candidate memories from free-form text with governance filters and sanitization.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | – | Agent identifier. Defaults to "default". |
| project | string | – | Force a specific project (e.g., SYNAPSE_LAYER, OFFLY). Auto-detected if omitted. |
| source | string | – | Source identifier (default: mcp). |
| text | string | yes | Free-form text to scan for auto-save triggers. |
| Name | Type | Req | Description |
|---|---|---|---|
| extracted | array | yes | – |
| storedCount | number | yes | – |
No examples provided.
recall ~349
Retrieve relevant persisted memory using semantic, temporal, priority, or hybrid routing. Governance: requires reason (10–200 chars). Rate limit: 20/min.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | – | Agent identifier (canonical or alias). Used only when scope="agent" or scope is inferred. |
| limit | number | – | Maximum memories to return (1–50, default: 10). |
| mode | string | – | Recall routing mode. "temporal" = pure chronological, "semantic" = FTS + TQ ranking, "priority" = critical/high-TQ first, "hybrid" = weighted blend, "auto" = detect from query (default). |
| query | string | yes | What to recall — natural language query for memory retrieval. |
| reason | string | yes | REQUIRED (10–200 chars). Audit policy: MEMORY_EXPORT_GOVERNANCE_V1. Human-readable justification for retrieving PLAINTEXT memory. Without this parameter the call WILL fail with code -32602. Example:… |
| scope | string | – | Explicit memory scope. "agent" (default, fail-closed) = limits recall to the given agent_id (or the token agent). "tenant" = cross-agent recall within the authenticated tenant. If omitted with agent_… |
| subject | string | – | ESCOPO1 (optional): opaque 8-128 char token ([A-Za-z0-9._:-]) that isolates memory to a single person within a shared connect-token. Omit for token-scoped behavior. Never include PII/email. |
| Name | Type | Req | Description |
|---|---|---|---|
| count | number | yes | – |
| memories | array | yes | – |
| scope | string | yes | – |
No examples provided.
recall_memory ~266
Recall persisted memory by query. Alias of recall.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | – | Agent identifier (canonical or alias). Used only when scope="agent" or scope is inferred. |
| limit | number | – | Maximum memories to return (1–50, default: 10). |
| mode | string | – | Recall routing mode. |
| query | string | yes | What to recall — natural language query for memory retrieval. |
| reason | string | yes | REQUIRED (10–200 chars). Audit policy: MEMORY_EXPORT_GOVERNANCE_V1. Without this the call WILL fail with code -32602. Example: "Checking user project status." |
| scope | string | – | Explicit memory scope. "agent" (default, fail-closed) = limits recall to the given agent_id (or the token agent). "tenant" = cross-agent recall within the authenticated tenant. If omitted with agent_… |
| subject | string | – | ESCOPO1 (optional): opaque 8-128 char token ([A-Za-z0-9._:-]) that isolates memory to a single person within a shared connect-token. Omit for token-scoped behavior. Never include PII/email. |
| Name | Type | Req | Description |
|---|---|---|---|
| count | number | yes | – |
| memories | array | yes | – |
| scope | string | yes | – |
No examples provided.
save_memory ~243
Save a memory entry to the persistent store. Alias of save_to_synapse.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | – | Agent identifier for memory isolation. |
| content | string | yes | The memory content to store securely. |
| force_intent | string | – | MANUAL OVERRIDE ONLY — use apenas quando você (humano) quer forçar explicitamente a classificação de intenção. Valores reconhecidos: preference | fact | procedural | bio | critical | operational | st… |
| intent_reason | string | – | Auditable reason for forcing intent classification. Max 500 characters. Ignored if force_intent is absent. |
| subject | string | – | ESCOPO1 (optional): opaque 8-128 char token ([A-Za-z0-9._:-]) that isolates memory to a single person within a shared connect-token. Omit for token-scoped behavior. Never include PII/email. |
| tags | array | – | Tags for categorization. |
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
| scope | string | yes | – |
| stored | boolean | yes | – |
No examples provided.
save_to_synapse ~338
Persist memory with encryption at rest, sanitization, and deduplication controls.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | – | Agent identifier for memory isolation. Defaults to "default". |
| content | string | yes | The memory content to store securely. |
| force_intent | string | – | MANUAL OVERRIDE ONLY — use apenas quando você (humano) quer forçar explicitamente a classificação de intenção. Valores reconhecidos: preference | fact | procedural | bio | critical | operational | st… |
| importance | number | – | Accepted for compatibility; not enforced by the API. |
| intent_reason | string | – | Auditable reason for forcing intent classification. Max 500 characters. Ignored if force_intent is absent. |
| project | string | – | Project identifier (e.g., SYNAPSE_LAYER). |
| subject | string | – | ESCOPO1 (optional): opaque 8-128 char token ([A-Za-z0-9._:-]) that isolates memory to a single person within a shared connect-token. Omit for token-scoped behavior. Never include PII/email. |
| tags | array | – | Tags for categorization. |
| type | string | – | Event type: [MILESTONE], [DECISION], [ALERT], [AUTO-STRAT], [AUTO-OP], [AUTO-INSIGHT], [AUTO-DECISION], [AUTO-CONTEXT], [MANUAL]. |
| Name | Type | Req | Description |
|---|---|---|---|
| memory_id | string | yes | – |
| status | string | yes | – |
| trust_quotient | number | – | – |
No examples provided.
search ~283
Search persisted memory across agent scopes using full-text matching. Governance: requires reason (10–200 chars) because results contain plaintext content.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | – | Agent identifier (canonical or alias). Used only when scope="agent" or scope is inferred. |
| limit | number | – | Maximum results to return (1–50, default: 20). |
| query | string | yes | Search query — natural language or keywords. |
| reason | string | yes | REQUIRED (10–200 chars). Audit policy: MEMORY_EXPORT_GOVERNANCE_V1. Human-readable justification for retrieving PLAINTEXT memory. Without this parameter the call WILL fail with code -32602. Example:… |
| scope | string | – | Explicit search scope. "agent" (default, fail-closed) = limits search to the given agent_id (or the token agent). "tenant" = cross-agent search within the authenticated tenant. If omitted with agent_… |
| subject | string | – | ESCOPO1 (optional): opaque 8-128 char token ([A-Za-z0-9._:-]) that isolates memory to a single person within a shared connect-token. Omit for token-scoped behavior. Never include PII/email. |
| Name | Type | Req | Description |
|---|---|---|---|
| count | number | yes | – |
| results | array | yes | – |
| scope | string | yes | – |
No examples provided.
slo_report ~68
Return uptime and SLO metrics for the MCP service.
| Name | Type | Req | Description |
|---|---|---|---|
| admin_token | string | yes | Admin authentication token. Must match ADMIN_TOKEN environment variable. |
| window_hours | array | – | Time windows in hours for the report. Default: [24, 168] (24h + 7d). |
| Name | Type | Req | Description |
|---|---|---|---|
| errorRate | number | – | – |
| p50 | number | – | – |
| p95 | number | – | – |
| uptime | number | yes | – |
| window | string | – | – |
No examples provided.
store_memory ~241
Store structured memory with metadata and trust scoring.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | – | Agent identifier for memory isolation. Defaults to "default". |
| content | string | yes | The memory content to store securely. |
| force_intent | string | – | MANUAL OVERRIDE ONLY — use apenas quando você (humano) quer forçar explicitamente a classificação de intenção. Valores reconhecidos: preference | fact | procedural | bio | critical | operational | st… |
| intent_reason | string | – | Auditable reason for forcing intent classification. Max 500 characters. Ignored if force_intent is absent. |
| subject | string | – | ESCOPO1 (optional): opaque 8-128 char token ([A-Za-z0-9._:-]) that isolates memory to a single person within a shared connect-token. Omit for token-scoped behavior. Never include PII/email. |
| tags | array | – | Tags for categorization. |
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
| scope | string | yes | – |
| stored | boolean | yes | – |
No examples provided.
What is the Synapse Layer — Trust Infrastructure for AI Agents MCP server?
Synapse Layer — Trust Infrastructure for AI Agents is an MCP server listed in the public MCP registry as io.github.SynapseLayer/synapse-layer. MCP-native Trust Infrastructure for AI Agents. Persistent encrypted memory with Trust Quotient. This page covers its hosted endpoint (https://forge.synapselayer.org/api/mcp).
Is the Synapse Layer — Trust Infrastructure for AI Agents MCP server safe to use?
Synapse Layer — Trust Infrastructure for AI Agents scores 74 out of 100 on VerifyMCP. 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.
What tools does the Synapse Layer — Trust Infrastructure for AI Agents MCP server expose?
Synapse Layer — Trust Infrastructure for AI Agents exposes 13 tools: recall, save_to_synapse, process_text, search, health_check, and 8 more. Their descriptions and schemas cost roughly 2,466 tokens of context every time the server is loaded.
Does the Synapse Layer — Trust Infrastructure for AI Agents MCP server require authentication?
No. We connected to Synapse Layer — Trust Infrastructure for AI Agents without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Synapse Layer — Trust Infrastructure for AI Agents MCP server still maintained?
Synapse Layer — Trust Infrastructure for AI Agents is still listed as active 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.