Hosted remote MCP server (Streamable HTTP) adapter over the Synap public REST API.
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"maximem-synap-mcp-server","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# synap-mcp-server [](https://glama.ai/mcp/connectors/ai.maximem/synap) Hosted remote **MCP server** (Streamable HTTP) that re-fronts the existing Synap public REST operations as MCP tools, so no-code platforms (Gumloop, n8n) can give their agents persistent memory with nothing but a pasted **MCP URL** and a **Bearer token**. It is a **stateless adapter** — no new backend, storage, or pipeline. Each tool call maps to one existing REST operation, and the incoming `Bearer synap_<key>` token is forwarded verbatim to `synap-cloud`, which owns auth. - Public endpoint (prod): `https://synap-mcp.maximem.ai/mcp` - Health: `https://synap-mcp.maximem.ai/health` ## Tools | Tool | REST operation | Notes | |---|---|---| | `log_exchange` | `POST /api/v1/memories/create` (`mode=long-range`) | Forward every turn; extraction decides what persists. `user_id` scopes per end-user, `customer_id` is B2B only (see Scoping); optional `conversation_id`. | | `recall_context` | `POST /v1/context/{client\|user\|customer}/fetch` (`mode=fast`) | Hot path; no IDs ⇒ client scope. `customer` scope is B2B only. | | `list_recent_memories` | broad `/v1/context/.../fetch` (no query) | Debug / "test my memory". Same scoping rules. | | `check_memory_status` | `GET /api/v1/memories/status/{id}` | Takes no scope ids: the `ingestion_id` already identifies the write. | ## Scoping: one contract, two modes The REST API enforces this. It is not advice, and it has been live on production since 2026-08-26 07:07 UTC. | Instance mode (`user_context_isolation`) | What to send | What happens otherwise | |---|---|---| | `equals_customer` (**B2C**) | `user_id` and nothing else. The user id is the whole identity. | Any `customer_id` is rejected with **HTTP 400**. `/v1/context/customer/fetch` is not available at all. | | `strict` (**B2B**) | `customer_id` is **r…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.