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.

Synology Chat

OCI · GHCR.IO/LOUIS-LASTELLA/SYNOLOGY-CHAT-MCP

Read channels and posts, find users, send messages and files on any Synology Chat server.

+3 this week 39 Trust /100

Last scanned (20 hours ago)

Scores higher than 49% of OCI servers

Category Communication

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security0
  • No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
  • Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
  • Install-script risk not yet assessed.Unverified
  • Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
Provenance & Transparency45
Schema Quality & AI Usability62
  • AI-judged instruction clarity (fair).Partial
  • Tool/resource definitions use about 218 tokens (~36/item across 6 items; 6 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management33
  • Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
  • 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 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "send_message" implies "send" 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 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass

Unverified: 1 category

A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

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.

  • 23 Oct 26 +1

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

  • 21 Oct 26 +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.

  • 19 Oct 26 +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.

  • 17 Oct 26 +2
    • Stability: unverified → 0.10 ▲ functional
  • 14 Oct 26 +25
    • Injection markers: unverified → pass ▲ security
    • First check of Judged manipulation: pass security
    • Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
    • Tool coverage: unverified → 100 ▲ functional
    • MCP protocol: unverified → pass ▲ functional
    • First check of Tool coverage: 0 functional
    • First check of Schema quality: fail functional
    • First check of Schema quality: fair functional
    • First check of Destructive annotations: 0 functional
    • First check of Schema quality: pass functional
    • First check of Tool coverage: 100 functional
  • 13 Oct 26 9

    First indexed and scored.

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 24 Oct 2026 · Analysed oci/ghcr.io/louis-lastella/synology-chat-mcp@0.2.0

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem oci
Reason No attestation published

Background: How many MCP packages publish verified provenance →

MCP tools · 6 exposed · ~218 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
dm_channel_for_user ~41

Find (or None if none exists yet) the 1:1 DM channel_id for a given user_id.

NameTypeReqDescription
user_idintegeryes–
NameTypeReqDescription
result–yes–

No examples provided.

find_user ~34

Find users by (partial, case-insensitive) username, e.g. 'smith'.

NameTypeReqDescription
name_querystringyes–
NameTypeReqDescription
resultarrayyes–

No examples provided.

get_recent_posts ~36

Read the most recent messages/files in a channel or DM.

NameTypeReqDescription
channel_idintegeryes–
limitinteger––
NameTypeReqDescription
resultarrayyes–

No examples provided.

list_channels ~27

List all joined chat channels/DMs with id, name, type, last_post_at.

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultarrayyes–

No examples provided.

send_file ~47

Upload a file to a channel/DM, optionally followed by a text message.

NameTypeReqDescription
channel_idintegeryes–
file_pathstringyes–
messagestring––

Structured output declared, but exposes no named fields.

No examples provided.

send_message ~33

Post a text message to a channel/DM.

NameTypeReqDescription
channel_idintegeryes–
messagestringyes–

Structured output declared, but exposes no named fields.

No examples provided.

Install

How do I install the Synology Chat MCP server?

Synology Chat runs locally as a container image, launched with docker run --rm -i -e SYNOLOGY_CHAT_URL -e SYNOLOGY_CHAT_USER -e SYNOLOGY_CHAT_PASS -e SYNOLOGY_CHAT_VERIFY_SSL ghcr.io/louis-lastella/synology-chat-mcp:0.2.0. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.

oci · ghcr.io/louis-lastella/synology-chat-mcp

# add to Claude Code
claude mcp add louis-lastella-synology-chat-mcp -- docker run --rm -i -e SYNOLOGY_CHAT_URL -e SYNOLOGY_CHAT_USER -e SYNOLOGY_CHAT_PASS -e SYNOLOGY_CHAT_VERIFY_SSL ghcr.io/louis-lastella/synology-chat-mcp:0.2.0

This image reads SYNOLOGY_CHAT_URL, SYNOLOGY_CHAT_USER, SYNOLOGY_CHAT_PASS and SYNOLOGY_CHAT_VERIFY_SSL. Set them in your client's env block for this server; docker run -e passes each one through to the container.

Common questions

What is the Synology Chat MCP server?

Synology Chat is an MCP server listed in the public MCP registry as io.github.Louis-Lastella/synology-chat-mcp. Read channels and posts, find users, send messages and files on any Synology Chat server. This page covers its container image (ghcr.io/louis-lastella/synology-chat-mcp).

Is the Synology Chat MCP server safe to use?

Synology Chat scores 39 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 Synology Chat MCP server expose?

Synology Chat exposes 6 tools: list_channels, find_user, get_recent_posts, dm_channel_for_user, send_message, send_file. Their descriptions and schemas cost roughly 218 tokens of context every time the server is loaded.

Is the Synology Chat MCP server still maintained?

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

What licence is the Synology Chat MCP server under?

Synology Chat declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.