Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Synapse Layer — Trust Infrastructure for AI Agents

REMOTE · FORGE.SYNAPSELAYER.ORG

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

0 this week 76 Trust /100

Last scanned (12 hours ago)

Scores higher than 65% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Memory and Knowledge

Trust breakdown (7 categories)

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 Security63
Transport & Reachability100
Schema Quality & AI Usability58
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 3363 tokens (~258/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
What we tested

Checks we ran (12)

  • TLS certificate
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 6 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 11 Nov 26 0
    • Stability: 0.97 → pass security
  • 10 Nov 26 0
    • Stability: pass → 0.97 functional
  • 9 Nov 26 0
    • Stability: 0.97 → pass security
  • 8 Nov 26 0
    • Stability: pass → 0.97 functional
  • 7 Nov 26 0
    • Stability: 0.97 → pass security
  • 6 Nov 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
  • 5 Nov 26 0
    • Stability: 0.97 → pass security
  • 4 Nov 26 0
    • Stability: pass → 0.97 functional
Diagnostics

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 21 Nov 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 1 Oct 2026 31 Dec 2026 ECDSA 256 ECDSA-SHA256 246c65f786741bf40e30b39b7318428e
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. DS published 725 8 Verified
synapselayer.org. No DS 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
strict-transport-security max-age=15552000; includeSubDomains
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
MCP tools · 13 exposed · ~2,810 tokens

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 →

Tool Tokens
health_check ~22

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

Input schema present but exposes no named parameters.

NameTypeReqDescription
dbRealLatencyMsnumber––
latencyMsnumber––
statusstringyes–
versionstringyes–

No examples provided.

initialize_context ~181

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.

NameTypeReqDescription
detailstring–Detail level. "summary" (default) = redacted metadata only, no plaintext. "full" = plaintext content; REQUIRES the reason parameter and is audit-logged.
project_idstring–Optional project ID. Required for Corporate context unless the token is project-bound.
reasonstring–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…
NameTypeReqDescription
agent_idstring––
countnumber––
errorstring––
initializedboolean––
memoriesarray––
scopestring––

No examples provided.

list_memories ~207

List memory metadata with pagination and governance limits.

NameTypeReqDescription
agent_idstring–Agent identifier (canonical or alias). Used only when scope="agent" or scope is inferred.
limitnumber–Maximum memory metadata rows to return. Hard-capped: default 5, max 10. Values above 10 are silently reduced to 10.
project_idstring–Optional project ID. Required for Corporate context unless the token is project-bound.
scopestring–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.
subjectstring–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.
NameTypeReqDescription
countnumberyes–
memoriesarrayyes–
totalnumber––

No examples provided.

memory_feedback ~148

Submit feedback to adjust trust scoring for stored memories.

NameTypeReqDescription
memoryIdstring–Deprecated camelCase alias of memory_id — still accepted for backward compatibility.
memory_idstring–ID of the memory to provide feedback on (canonical snake_case name).
project_idstring–Project ID for authorization and memory isolation. Required for Corporate context unless the token is project-bound.
sessionIdstring–Deprecated camelCase alias of session_id — still accepted for backward compatibility.
session_idstring–Optional session identifier for tracking (canonical snake_case name).
signalstringyesFeedback signal: used (auto), helpful (positive), irrelevant (negative), ignored.
NameTypeReqDescription
memoryIdstringyes–
signalstring––
successbooleanyes–

No examples provided.

neural_handover ~121

Transfer contextual state between agents with continuity controls.

NameTypeReqDescription
consuming_agentstring–Agent identifier consuming the handover (defaults to token agent).
project_idstring–Project ID for authorization and memory isolation. Required for Corporate context unless the token is project-bound.
reasonstringyesREQUIRED (10–200 chars). Human-readable justification for consuming this handover. Example: "Receiving project context from Claude session."
tokenstringyesThe handover token (64 hex chars). Generated by the source agent/user in Forge UI.
NameTypeReqDescription
fromAgentstring––
handoverIdstringyes–
memoriesarray––
memoryCountnumber––
successbooleanyes–

No examples provided.

process_text ~132

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

NameTypeReqDescription
agent_idstring–Agent identifier. Defaults to "default".
projectstring–Force a specific project namespace. Auto-detected if omitted.
project_idstring–Project ID for authorization and memory isolation. Required for Corporate context unless the token is project-bound.
sourcestring–Source identifier (default: mcp).
textstringyesFree-form text to scan for auto-save triggers.
visibilitystring–private (default) or project (visible to active members of this project).
NameTypeReqDescription
extractedarrayyes–
storedCountnumberyes–

No examples provided.

recall ~371

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

NameTypeReqDescription
agent_idstring–Agent identifier (canonical or alias). Used only when scope="agent" or scope is inferred.
limitnumber–Maximum memories to return (1–50, default: 10).
modestring–Recall routing mode. "temporal" = pure chronological, "semantic" = FTS + TQ ranking, "priority" = critical/high-TQ first, "hybrid" = weighted blend, "auto" = detect from query (default).
project_idstring–Optional project ID. Required for Corporate context unless the token is project-bound.
querystringyesWhat to recall — natural language query for memory retrieval.
reasonstringyesREQUIRED (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:…
scopestring–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_…
subjectstring–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.
NameTypeReqDescription
countnumberyes–
memoriesarrayyes–
scopestringyes–

No examples provided.

recall_memory ~288

Recall persisted memory by query. Alias of recall.

NameTypeReqDescription
agent_idstring–Agent identifier (canonical or alias). Used only when scope="agent" or scope is inferred.
limitnumber–Maximum memories to return (1–50, default: 10).
modestring–Recall routing mode.
project_idstring–Optional project ID. Required for Corporate context unless the token is project-bound.
querystringyesWhat to recall — natural language query for memory retrieval.
reasonstringyesREQUIRED (10–200 chars). Audit policy: MEMORY_EXPORT_GOVERNANCE_V1. Without this the call WILL fail with code -32602. Example: "Checking user project status."
scopestring–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_…
subjectstring–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.
NameTypeReqDescription
countnumberyes–
memoriesarrayyes–
scopestringyes–

No examples provided.

save_memory ~290

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

NameTypeReqDescription
agent_idstring–Agent identifier for memory isolation.
contentstringyesThe memory content to store securely.
force_intentstring–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_reasonstring–Auditable reason for forcing intent classification. Max 500 characters. Ignored if force_intent is absent.
project_idstring–Project ID for authorization and memory isolation. Required for Corporate context unless the token is project-bound.
subjectstring–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.
tagsarray–Tags for categorization.
visibilitystring–private (default) or project (visible to active members of this project).
NameTypeReqDescription
intentstring––
memory_idstringyes–
pipelineobject––
privacy_appliedboolean––
quotaobject––
sanitizedboolean––
statusstringyes–
trust_quotientnumber––

No examples provided.

save_to_synapse ~385

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

NameTypeReqDescription
agent_idstring–Agent identifier for memory isolation. Defaults to "default".
contentstringyesThe memory content to store securely.
force_intentstring–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…
importancenumber–Accepted for compatibility; not enforced by the API.
intent_reasonstring–Auditable reason for forcing intent classification. Max 500 characters. Ignored if force_intent is absent.
projectstring–Project identifier (e.g., SYNAPSE_LAYER).
project_idstring–Project ID for authorization and memory isolation. Required for Corporate context unless the token is project-bound.
subjectstring–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.
tagsarray–Tags for categorization.
typestring–Event type: [MILESTONE], [DECISION], [ALERT], [AUTO-STRAT], [AUTO-OP], [AUTO-INSIGHT], [AUTO-DECISION], [AUTO-CONTEXT], [MANUAL].
visibilitystring–private (default) or project (visible to active members of this project).
NameTypeReqDescription
memory_idstringyes–
statusstringyes–
trust_quotientnumber––

No examples provided.

search ~309

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

NameTypeReqDescription
agent_idstring–Agent identifier (canonical or alias). Used only when scope="agent" or scope is inferred.
limitnumber–Maximum results to return (1–50, default: 20).
project_idstring–Project ID for authorization and memory isolation. Required for Corporate context unless the token is project-bound.
querystringyesSearch query — natural language or keywords.
reasonstringyesREQUIRED (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:…
scopestring–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_…
subjectstring–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.
NameTypeReqDescription
countnumberyes–
resultsarrayyes–
scopestringyes–

No examples provided.

slo_report ~68

Return uptime and SLO metrics for the MCP service.

NameTypeReqDescription
admin_tokenstringyesAdmin authentication token. Must match ADMIN_TOKEN environment variable.
window_hoursarray–Time windows in hours for the report. Default: [24, 168] (24h + 7d).
NameTypeReqDescription
generatedAtstringyes–
statusstringyes–
versionstring––
windowsarray––

No examples provided.

store_memory ~288

Store structured memory with metadata and trust scoring.

NameTypeReqDescription
agent_idstring–Agent identifier for memory isolation. Defaults to "default".
contentstringyesThe memory content to store securely.
force_intentstring–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_reasonstring–Auditable reason for forcing intent classification. Max 500 characters. Ignored if force_intent is absent.
project_idstring–Project ID for authorization and memory isolation. Required for Corporate context unless the token is project-bound.
subjectstring–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.
tagsarray–Tags for categorization.
visibilitystring–private (default) or project (visible to active members of this project).
NameTypeReqDescription
intentstring––
memory_idstringyes–
pipelineobject––
privacy_appliedboolean––
quotaobject––
sanitizedboolean––
statusstringyes–
trust_quotientnumber––

No examples provided.

Install

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

# add to Claude Code
claude mcp add --transport http synapselayer-synapse-layer 'https://forge.synapselayer.org/api/mcp'
Common questions

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 76 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,810 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 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the Synapse Layer — Trust Infrastructure for AI Agents MCP server?

VerifyMCP ran 12 checks on Synapse Layer — Trust Infrastructure for AI Agents, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about Synapse Layer — Trust Infrastructure for AI Agents: Authorization. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.