# Synaplan (remote · web.synaplan.com)

Self-hosted AI workspace: semantic RAG document search, long-term memory, and AI chat via MCP.

- Trust score: 78/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `web.synaplan.com`: 78/100 (this document), [markdown](https://verifymcp.io/servers/metadist-synaplan/web.md), [page](https://verifymcp.io/servers/metadist-synaplan/web)

## Channel facts

- Endpoint: `https://web.synaplan.com/mcp`
- Transports: `streamable-http`
- Auth: `required (not validated)`
- Version: `5.6.7`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 83/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 74/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 974 tokens (~97/item across 10 items; 10 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Synaplan MCP server?

Synaplan is a hosted endpoint at https://web.synaplan.com/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.

### Claude

```bash
claude mcp add --transport http metadist-synaplan 'https://web.synaplan.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "metadist-synaplan": {
      "url": "https://web.synaplan.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "metadist-synaplan": {
      "type": "http",
      "url": "https://web.synaplan.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.metadist-synaplan]
url = "https://web.synaplan.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "metadist-synaplan": {
      "type": "remote",
      "url": "https://web.synaplan.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add metadist-synaplan --url 'https://web.synaplan.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  metadist-synaplan:
    url: "https://web.synaplan.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "metadist-synaplan": {
      "Transport": "http",
      "Url": "https://web.synaplan.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add metadist-synaplan -t streamable-http -u 'https://web.synaplan.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "metadist-synaplan": {
      "type": "http",
      "url": "https://web.synaplan.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-04 (score 78, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-02 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-30 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-29 (score 75, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-28 (score 75, +42)

- [security improvement] Transport: unverified → pass
- [security improvement] Injection markers: unverified → pass
- [security] First check of Judged manipulation: pass
- [security] Authorization: Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token.
- [functional improvement] MCP protocol: unverified → pass
- [functional improvement] Tool coverage: unverified → 100
- [functional] First check of Schema quality: fail
- [functional] First check of Destructive annotations: 100
- [functional] First check of Schema quality: pass
- [functional] First check of Schema quality: good
- [functional] First check of Tool coverage: 100

### 2026-10-20 (score 33)

First indexed and scored.

## MCP tools (10)

### `synaplan_chat` (~185 tokens)

Synaplan chat

Send a message through Synaplan's full AI pipeline — intent classification, web search, RAG over the user's documents, long-term memories, and inference — and return the synthesized answer. This is richer than a raw model call: it uses the authenticated account's knowledge base and memories.

Input parameters:

- `agentId` (string|integer|null): Optional assistant id or slug (see list_assistants). Pins the reply to that assistant; fails when it is not published, not usable by you, or does not allow connected apps.
- `chat_id` (integer|null): Optional existing chat id (from list_chats) to continue a conversation. Omit to start a new chat.
- `message` (string, required): The message or question to send through Synaplan's full AI pipeline (classification, web search, RAG over the user's documents, memories, and inference).

### `rag_search` (~105 tokens)

RAG knowledge search

Semantic search across the authenticated user's vectorized documents and knowledge base. Returns the most relevant text chunks with similarity scores.

Input parameters:

- `group_key` (string|null): Optional document group key to scope the search to a single document/collection.
- `limit` (integer): Maximum number of chunks to return (1-50).
- `min_score` (number): Minimum similarity score (0-1) a chunk must reach to be returned.
- `query` (string, required): Natural-language search query.

### `memory_search` (~80 tokens)

User memory search

Search the authenticated user's stored long-term memories (preferences, facts, context) using semantic similarity.

Input parameters:

- `category` (string|null): Optional category filter (e.g. preferences, work, personal).
- `limit` (integer): Maximum number of memories to return (1-50).
- `query` (string, required): Natural-language query describing the memory to look up.

### `memory_add` (~92 tokens)

Add a user memory

Store a new long-term memory for the authenticated user — a durable fact or preference that Synaplan will recall in future conversations.

Input parameters:

- `category` (string, required): Category for the memory, e.g. preferences, work, personal, health.
- `key` (string, required): Short identifier for the memory (min 3 characters), e.g. tech_stack.
- `value` (string, required): The fact or preference to remember.

### `file_ingest` (~118 tokens)

Ingest a document for RAG

Add a text document to the authenticated user's knowledge base. The content is chunked, embedded, and stored so it becomes retrievable via rag_search.

Input parameters:

- `content` (string, required): The text content to ingest. It is chunked, embedded, and made retrievable via rag_search.
- `group_key` (string|null): Optional group key to scope the document. Pass the same value to rag_search to retrieve only this group; omit it to search the whole corpus.
- `name` (string, required): A human-readable name/title for the document.

### `rag_similar` (~78 tokens)

Find similar chunks

Find document chunks similar to a given source message/document id (the `message_id` returned by rag_search).

Input parameters:

- `limit` (integer): Maximum number of similar chunks to return (1-50).
- `message_id` (integer, required): The source document/message id to find similar chunks for (use a `message_id` returned by rag_search).

### `list_chats` (~37 tokens)

List chats

List the authenticated user's conversations (most recently updated first).

Input parameters:

- `limit` (integer): Maximum number of chats to return (1-200).

### `get_messages` (~66 tokens)

Get chat messages

Return the messages of one of the user's chats, in chronological order.

Input parameters:

- `chat_id` (integer, required): The id of the chat (from list_chats) to read messages from.
- `limit` (integer): Maximum number of (most recent) messages to return (1-100).

### `list_prompts` (~27 tokens)

List task prompts

List the user's available Synaplan task prompts (internal `tools:*` prompts excluded).

### `list_assistants` (~35 tokens)

List assistants

List assistants the authenticated user may use from a connected app. Each row includes slug, name, description, version and origin.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/metadist-synaplan/web#diagnostics

## Score history

- 2026-11-05: 78
- 2026-11-04: 78
- 2026-11-03: 77
- 2026-11-02: 77
- 2026-11-01: 76
- 2026-10-31: 76
- 2026-10-30: 76
- 2026-10-29: 75
- 2026-10-28: 75
- 2026-10-27: 33
- 2026-10-26: 33
- 2026-10-25: 33
- 2026-10-24: 33
- 2026-10-23: 33
- 2026-10-22: 33
- 2026-10-21: 33
- 2026-10-20: 33

## Common questions

### What is the Synaplan MCP server?

Synaplan is an MCP server listed in the public MCP registry as io.github.metadist/synaplan. Self-hosted AI workspace: semantic RAG document search, long-term memory, and AI chat via MCP. This page covers its hosted endpoint (https://web.synaplan.com/mcp).

### Is the Synaplan MCP server safe to use?

Synaplan scores 78 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 Synaplan MCP server expose?

Synaplan exposes 10 tools: synaplan_chat, rag_search, memory_search, memory_add, file_ingest, and 5 more. Their descriptions and schemas cost roughly 823 tokens of context every time the server is loaded.

### Does the Synaplan MCP server require authentication?

Yes. Synaplan asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

### Is the Synaplan MCP server still maintained?

Synaplan is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://web.synaplan.com/mcp
- Authorisation metadata: https://web.synaplan.com/.well-known/oauth-protected-resource/mcp
- Repository: https://github.com/metadist/synaplan
- Website: https://synaplan.com/
- Changelog RSS feed: https://verifymcp.io/servers/metadist-synaplan/web.xml
- Changelog JSON feed: https://verifymcp.io/servers/metadist-synaplan/web.json
- HTML version of this page: https://verifymcp.io/servers/metadist-synaplan/web