Skip to content
ProtocolProbe
Explore

MCP servers › io.github.metadist › synaplan

MCP server · registry snapshot 2026-10-23

io.github.metadist/synaplan

Self-hosted AI workspace: semantic RAG document search, long-term memory, and AI chat via MCP. — the publisher's description

5 of 5 record checks metTopic: ai-and-ml · AI-classifiedPricing: freemium · AI-classifiedversion 5.5.2PHPstreamable HTTP

Summary

io.github.metadist/synaplan is a remote MCP server listed in the official MCP registry at version 5.5.2.

Record checks

5 of 5 record checks met · 4 do not apply

  • met: Registry entry is active and says how to run it
  • met: Source repository link opens
  • met: Repository is not archived
  • met: Code pushed to the repository in the 90 days before our check
  • met: Repository publishes a security policy (SECURITY.md)
  • not applicable: Package names its licence with a standard (SPDX) identifier
  • not applicable: The version the registry lists can be installed and is not withdrawn
  • not applicable: npm package carries build provenance (attestation)
  • not applicable: No known critical or high advisory in the package or its dependencies
  • Not ranked by downloads: a remote server publishes no download figure
  • #524 of 22,952 repositories by GitHub stars, tied with 2 others

From public records, not a safety rating. Each check with its reason · Is it safe to install?

Key facts

Runs
remote (hosted by the publisher)
Transport
streamable HTTP
Repository
public
Topic
ai-and-mlAI-classified
Pricing
freemiumAI-classified
Last tested
not tested

Add to your client

How fresh this is

Live-tested
no
Last tested
not tested
Latest version
5.5.2, published 2026-10-20 (registry, as of the 2026-10-23 snapshot)
First listed version
2026-10-20 (earliest version still in the registry; older removed versions would be earlier)
Version history
3 versions listed, all on 2026-10-20; 3 in the 90 days before the 2026-10-23 snapshot.
Most recent 3 versions
  • 5.5.2 · 2026-10-20
  • 5.5.1 · 2026-10-20
  • 5.5.0 · 2026-10-20
(versions still listed in the registry only)
Registry data
snapshot 2026-10-23
Package and repository
checked 2026-10-23

Changes since the last refresh

New in the registry: not in the list of 2026-10-04, listed on 2026-10-23 with version 5.5.2 (published 2026-10-20).

Source: the official MCP Registry list on 2026-10-04 and on 2026-10-23.

What it is

How do I add it to my client?

Config from the registry entry

From the remote endpoint (Streamable HTTP)

This entry needs values of your own (marked < > or { } in the config below), so there is no one-click link: paste the config and fill them in.

Claude Desktop or claude.ai
Settings → Connectors → Add custom connector, then paste:
https://web.synaplan.com/mcp

The entry also requires the header X-API-Key.
Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json
{
  "mcpServers": {
    "synaplan": {
      "url": "https://web.synaplan.com/mcp",
      "headers": {
        "X-API-Key": "<X-API-Key>"
      }
    }
  }
}
VS Code · .vscode/mcp.json
{
  "servers": {
    "synaplan": {
      "type": "http",
      "url": "https://web.synaplan.com/mcp",
      "headers": {
        "X-API-Key": "${input:x-api-key}"
      }
    }
  },
  "inputs": [
    {
      "type": "promptString",
      "id": "x-api-key",
      "description": "X-API-Key",
      "password": true
    }
  ]
}
Claude Code
claude mcp add --transport http synaplan https://web.synaplan.com/mcp --header "X-API-Key: <X-API-Key>"
Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+
npx @modelcontextprotocol/inspector@2.11.0 --server-url https://web.synaplan.com/mcp --transport http
  • Replace <X-API-Key> with your own header values; the entry marks X-API-Key as secret, so keep the file out of version control.
  • The server runs on the operator's infrastructure; it may ask you to sign in when you first connect.
  • The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real. The command above does not send the required header (X-API-Key).

Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.

Does the registry listing match what we found?

Feature #6

The registry verifies a package once, when it is published, and does not re-check it. A difference below is about the listing, not a judgement of the publisher.

Registry saysWe foundResultSource · date
Repository github.com/metadist/synaplanOpens publiclymatchesapi.github.com · 2026-10-23

Who made it?

Feature #7 · lineage

Facts about the publisher. We do not turn them into a trust score.

Namespace
io.github.metadist
GitHub owner
an organization (metadist)
Repository
github.com/metadist/synaplan
Stars
217
Repository age
over a year
Last push
0–30 days ago
Archived
no
Security policy
SECURITY.md

What its security policy says about security research

“We ask that you keep the details private until the advisory is published. We aim to get there in days, not months; if a fix needs longer, we say so in the report thread and agree a date with you. Good-faith research that follows this policy — no access to other people's data, no service disruption, no destructive testing against the hosted service — is welcome, and we will not take action against it.”

The publisher’s own words from its security policy (formatting removed; a long passage is cut and marked “…”). Read the full policy for its conditions. This is the publisher’s statement, not our assessment. We still do not call this server’s tools: our checks only read what it lists.

Source: the registry entry and api.github.com · 2026-10-23; security policy read from GitHub · 2026-10-23.

Publish this server? Run these checks against it yourself before release, from your own machine: a server the command starts, or your own server at its URL after a one-time proof that you control it: npx protocolprobe-selftest.

Choosing

Record checks

Public records · not a safety rating

5 of 5 record checks met · 4 do not apply

  • Not ranked by downloads: a remote server publishes no download figure
  • #524 of 22,952 repositories by GitHub stars, tied with 2 others
  • MetRegistry entry is active and says how to run itActive, with a package or a remote address.
  • MetSource repository link opensThe linked GitHub repository is public.
  • MetRepository is not archivedNot archived.
  • MetCode pushed to the repository in the 90 days before our checkLast push 0-30 days before our check.
  • MetRepository publishes a security policy (SECURITY.md)SECURITY.md found.
  • Does not applyPackage names its licence with a standard (SPDX) identifierRemote server: it ships no package.
  • Does not applyThe version the registry lists can be installed and is not withdrawnRemote server: it ships no package.
  • Does not applynpm package carries build provenance (attestation)Remote server: it ships no package.
  • Does not applyNo known critical or high advisory in the package or its dependenciesRemote server: it ships no package.

Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-10-23. No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating. How each check works · Leaderboards

Common questions about io.github.metadist/synaplan

Answered from the data above

Is io.github.metadist/synaplan safe to install?

We do not rate servers as safe or unsafe. 5 of its 5 applicable record checks are met (facts from public records, each listed on this page). What the records show: Its source repository opens publicly. Its repository had a push in the last 90 days. These are facts with their sources on this page, not a safety guarantee, and we did not run its tools.

Is io.github.metadist/synaplan free to use?

Its website (www.synaplan.com/pricing) describes a freemium pricing model. This is an AI-classified reading of the page on 2026-10-23, so check the page itself before relying on it.

Has io.github.metadist/synaplan been security tested?

Not yet. It requires a credential (a key or token) that the publisher marks as required. We never fill in credentials, so we did not start it.

Does io.github.metadist/synaplan publish a security policy?

Yes: its repository has a public security policy (github.com/metadist/synaplan/blob/HEAD/SECURITY.md). It includes a statement about security research, quoted in the publisher's own words on this page. That is the publisher's statement, not permission for us to test the server, and we call none of its tools.

Where is the source code of io.github.metadist/synaplan?

In github.com/metadist/synaplan, which opens publicly.

Found this page useful?

Anonymous · no sign-in

A quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.

Similar servers

Same topic · AI-read

Active servers whose topic is also “ai-and-ml”, most GitHub stars first. The topic and the tool kinds are an AI model's reading of the publishers' descriptions, not checked by hand. Similar is not a recommendation.

Compare with another server

Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.

Security testing

Has it been tested?

Feature #1

It requires a credential (a key or token) that the publisher marks as required. We never fill in credentials, so we did not start it. — the server's own choice

Required input the publisher declares: X-API-Key (secret).

Reference

How is it classified?

18 fields

One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.

TopicAI-classified
ai-and-ml
AI-classified (Gemini + Claude agreed) · 2026-10-23
Pricing modelAI-classified
freemium
read from www.synaplan.com/pricing · 2026-10-23

“Self-hosted, free forever”

Programming language
PHP
api.github.com · 2026-10-23
Hosting type
remote (hosted by the publisher)
registry · 2026-10-23
MCP capability
not checked
not read (no session)
Transport
streamable HTTP
registry · 2026-10-23
Required credentials
requires a secret
registry · no declaration is not a guarantee
Package registry
does not apply
remote-only server: no package is shipped, so there is no package registry
Freshness
0–30 days
registry updatedAt · 2026-10-23
Lifecycle status
active
registry · 2026-10-23
License class
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Integrity hash
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Signature / provenance
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Dependency advisories
does not apply
ships no package, so there are no dependencies to audit
Popularity
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Publisher signals
owner: an organization · repository age: over a year · stars: 100–999
api.github.com · 2026-10-23
Maintenance
active
api.github.com · 2026-10-23
Environment
the publisher's infrastructure
where it runs, from the hosting type

“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.

Cite or correct this page

Sources and corrections

Suggested citation

ProtocolProbe. “io.github.metadist/synaplan: MCP server record.” Data checked 2026-10-23. https://protocolprobe.com/mcp/servers/io.github.metadist/synaplan

Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.

As JSON: this record in the API · API documentation.

Badge for your README

ProtocolProbe: 5 of 5 record checks met

[![ProtocolProbe](https://protocolprobe.com/api/v1/badge/io.github.metadist/synaplan)](https://protocolprobe.com/mcp/servers/io.github.metadist/synaplan)

It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.

Something wrong, or is this yours?

If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here.

Write to hello@protocolprobe.com · corrections log · methodology