# SyncytiumMD (npm · syncytium-md)

One canonical context transpiled into Cursor, Claude, Copilot, Cline and more, with agent handoff.

- Trust score: 83/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- npm · `syncytium-md`: 83/100 (this document), [markdown](https://verifymcp.io/servers/mrcbrbn5361-syncytiummd/syncytium-md.md), [page](https://verifymcp.io/servers/mrcbrbn5361-syncytiummd/syncytium-md)

## Channel facts

- Registry: `npm`
- Package: `syncytium-md`
- Version: `0.3.2`
- Transport: `stdio`

## Trust breakdown

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. 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-21.

- **Supply Chain Security**: 80/100
  - No malware found by supply-chain analysis.
  - CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available.
  - No install/post-install scripts declared.
  - 39 of 107 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 100/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to mrcbrbn5361/SyncytiumMD).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 5 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 74/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 1906 tokens (~82/item across 23 items; 23 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 53/100
  - Stability observed for 16 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.
  - Structured output schemas are declared (43% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - All 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 24 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 SyncytiumMD MCP server?

SyncytiumMD runs locally as an npm package, launched with npx -y syncytium-md mcp. 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 mrcbrbn5361-syncytiummd -- npx -y syncytium-md mcp
```

### Cursor

```json
{
  "mcpServers": {
    "mrcbrbn5361-syncytiummd": {
      "command": "npx",
      "args": [
        "-y",
        "syncytium-md",
        "mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "mrcbrbn5361-syncytiummd": {
      "command": "npx",
      "args": [
        "-y",
        "syncytium-md",
        "mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add mrcbrbn5361-syncytiummd -- npx -y syncytium-md mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "mrcbrbn5361-syncytiummd": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "syncytium-md",
        "mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add mrcbrbn5361-syncytiummd --command npx --arg -y --arg syncytium-md --arg mcp
```

### Hermes

```yaml
mcp_servers:
  mrcbrbn5361-syncytiummd:
    command: "npx"
    args: ["-y", "syncytium-md", "mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "mrcbrbn5361-syncytiummd": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "syncytium-md",
        "mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add mrcbrbn5361-syncytiummd -t stdio -c npx -a -y syncytium-md mcp
```

### Other

```json
{
  "mcpServers": {
    "mrcbrbn5361-syncytiummd": {
      "command": "npx",
      "args": [
        "-y",
        "syncytium-md",
        "mcp"
      ]
    }
  }
}
```

## 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-21 (score 83, +1)

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

### 2026-11-19 (score 82, +1)

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

### 2026-11-16 (score 81, +16)

- [security improvement] Malware scan: unverified → pass

### 2026-11-15 (score 65, −15)

- [security regression] Malware scan: pass → unverified
- [functional] Package version: 0.3.1 → 0.3.2

### 2026-11-14 (score 80, +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.

### 2026-11-12 (score 79, +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-11 (score 78, +5)

- [security improvement] Source repository: unverified → pass

### 2026-11-10 (score 73, −4)

- [security regression] Provenance: pass → unverified

## MCP tools (23)

### `syncytium_get_context` (~73 tokens)

Read-only. Get project rules, architecture, architectural decisions (ADR), and the active handoff state. Use this first in any session.

Input parameters:

- `includeContent` (boolean): Include full rule bodies instead of just id/title/description
- `topic` (string): Optional filter; defaults to a compact overview

### `syncytium_handoff` (~163 tokens)

Write. Pass the baton to the next AI agent or record progress on the shared blackboard. Run this before you finish your turn.

Input parameters:

- `activeAgent` (string, required): Your name (e.g. Cursor, Claude Code, Antigravity)
- `completedWork` (array): Work finished in this session
- `force` (boolean): Ignore an active lease
- `goal` (string): Primary objective
- `nextAgent` (string): Designated next agent, or omit
- `notes` (string): Context, warnings or rationale for the next agent
- `pendingTasks` (array): Work the next agent must continue
- `status` (string): Current task state for the next agent
- `touchedFiles` (array): Files recently modified

### `syncytium_record_decision` (~108 tokens)

Write. Record an Architectural Decision (ADR) shared across all AI agents.

Input parameters:

- `consequences` (string, required): Pros, cons and implications
- `context` (string, required): Background problem
- `decision` (string, required): The chosen solution
- `id` (string): ADR id; auto-allocated when omitted (ADR-002, ADR-003, …)
- `status` (string): Lifecycle status of the ADR
- `title` (string, required): Short imperative title of the decision

### `syncytium_remove_decision` (~100 tokens)

Destructive, but safe by default: previews the impact unless dryRun is false, requires confirm: true to delete, and archives the ADR so syncytium_restore can undo it.

Input parameters:

- `confirm` (boolean): Must be true with dryRun:false to actually delete.
- `dryRun` (boolean): Preview the impact without changing anything (default).
- `id` (string, required): ADR id to remove, e.g. ADR-003

### `syncytium_list_decisions` (~72 tokens)

Read-only. List recorded ADRs (optionally filtered by status or free-text query).

Input parameters:

- `limit` (number): Maximum number of ADRs to return
- `query` (string): Free-text search over title, context and decision
- `status` (string): Filter by ADR lifecycle status

Output parameters:

- `count` (number): Number of returned records
- `items` (array): The returned records

### `syncytium_create_rule` (~154 tokens)

Write. Add a new canonical rule to .syncytium/rules/ and regenerate every bridge file. Reversible with syncytium_remove_rule.

Input parameters:

- `alwaysApply` (boolean): Force the rule into every session
- `body` (string, required): Markdown body of the rule
- `description` (string): One-line summary shown in bridge files
- `globs` (array): Makes the rule glob-scoped instead of always-applied
- `id` (string): kebab-case id; derived from the title when omitted
- `sync` (boolean): Regenerate bridge files afterwards
- `tags` (array): Tags used for grouping and search
- `title` (string, required): Human-readable rule title

### `syncytium_list_rules` (~45 tokens)

Read-only. Search the canonical rule catalog by id, title, tag or body text.

Input parameters:

- `query` (string): Free-text search; omit to list all rules

Output parameters:

- `count` (number): Number of returned records
- `items` (array): The returned records

### `syncytium_update_rule` (~132 tokens)

Write. Edit an existing canonical rule in place (title, description, body, globs, tags).

Input parameters:

- `alwaysApply` (boolean): Force the rule into every session
- `body` (string): New Markdown body
- `description` (string): New one-line summary
- `globs` (array): Replacement glob scope; pass [] to make the rule always-applied
- `id` (string, required): Rule id to update
- `sync` (boolean): Regenerate bridge files afterwards
- `tags` (array): Replacement tag list
- `title` (string): New human-readable title

### `syncytium_remove_rule` (~100 tokens)

Destructive, but safe by default: previews the impact unless dryRun is false, requires confirm: true to delete, archives the rule, and prunes only banner-tagged generated files. Undo with syncytium_restore.

Input parameters:

- `confirm` (boolean): Must be true with dryRun:false to actually delete.
- `dryRun` (boolean): Preview the impact without changing anything (default).
- `id` (string, required): Rule id to remove

### `syncytium_sync` (~98 tokens)

Regenerate all AI tool bridge files (CLAUDE.md, .cursor/rules/, AGENTS.md, GEMINI.md, …). Can prune orphaned banner-tagged generated files; pass noPrune:true to keep them.

Input parameters:

- `force` (boolean): Override an active workspace lease
- `noPrune` (boolean): Do not remove orphaned generated files.
- `targets` (array): Restrict to specific adapter ids

### `syncytium_get_history` (~45 tokens)

Read-only. Get the multi-agent handoff audit trail: past goals, completed tasks and baton passes.

Input parameters:

- `limit` (number): Maximum handoff entries to return

Output parameters:

- `count` (number): Number of returned records
- `items` (array): The returned records

### `syncytium_lint` (~34 tokens)

Read-only. Validate canonical rules, frontmatter and ADR schema. Returns a compact summary, not the full report.

Output parameters:

- `errorCount` (number)
- `errors` (array)
- `totalChecked` (number)
- `valid` (boolean)
- `warningCount` (number)
- `warnings` (array)

### `syncytium_validate` (~36 tokens)

Read-only. Validate syncytium.config.json and every rule frontmatter against the zod schema and report issues without changing anything.

Output parameters:

- `issues` (array)
- `valid` (boolean)
- `warnings` (array)

### `syncytium_validate_fix` (~63 tokens)

Write. Repair invalid config or rule frontmatter in place, then report what changed. Separate from syncytium_validate so a read-only scan can never mutate the workspace.

Input parameters:

- `dryRun` (boolean): Report the repairs that would be applied without writing them.

### `syncytium_diff` (~53 tokens)

Read-only. Check context drift between .syncytium/ and the generated bridge files. Returns a summary plus the drifted paths.

Input parameters:

- `targets` (array): Restrict the drift check to specific adapter ids

Output parameters:

- `drifted` (array)
- `hasDrift` (boolean)
- `summary` (object)

### `syncytium_doctor` (~49 tokens)

Read-only. Run the full workspace health check: config, adapters, rules, drift, lock, git hook and CI gate. Never fixes or executes anything; remediation strings are suggestions only.

Output parameters:

- `checks` (array)
- `overallStatus` (string)
- `stats` (object)

### `syncytium_lock_acquire` (~91 tokens)

Write. Take the exclusive workspace lease so other agents do not edit the same files concurrently.

Input parameters:

- `agent` (string, required): Your agent name, recorded as the lease holder
- `force` (boolean): Take over an existing lease
- `goal` (string): What you are working on while holding the lease
- `leaseMinutes` (number): Lease length in minutes (1-1440)

### `syncytium_lock_release` (~58 tokens)

Write. Release the workspace lease held by this agent (idempotent).

Input parameters:

- `agent` (string): Only release the lease if it is held by this agent
- `force` (boolean): Release a lease held by another agent

### `syncytium_lock_status` (~26 tokens)

Read-only. Report who currently holds the workspace lease and when it expires.

Output parameters:

- `acquiredAt` (string)
- `agent` (string)
- `expiresAt` (string)
- `goal` (string)
- `host` (string)
- `isExpired` (boolean)
- `locked` (boolean)

### `syncytium_get_graph` (~70 tokens)

Read-only. Get the project knowledge graph (rules, tags, ADRs, agents, adapters, bridge files) for visualisation.

Input parameters:

- `category` (string): Perspective to isolate before building the graph
- `compact` (boolean): Hide file, directory and tag nodes for a smaller payload

Output parameters:

- `edges` (array)
- `nodes` (array)
- `stats` (object)

### `syncytium_import` (~72 tokens)

Write. Reverse-migrate existing unmanaged AI rule files (CLAUDE.md, .cursorrules, …) into .syncytium/. Dry-run by default; it only creates rules and never deletes the originals.

Input parameters:

- `dryRun` (boolean): Report what would be imported without writing (default).

### `syncytium_list_trash` (~65 tokens)

Read-only. List recoverable deletions (archived rules and ADRs) with their archive timestamps, newest first.

Input parameters:

- `kind` (string): Restrict to archived rules or archived ADRs
- `limit` (number): Maximum number of entries to return

Output parameters:

- `count` (number): Number of returned records
- `items` (array): The returned records

### `syncytium_restore` (~64 tokens)

Write. Restore an archived rule or ADR from the recoverable trash and regenerate bridge files. Fails if the same id already exists.

Input parameters:

- `id` (string, required): Id of the archived rule or ADR
- `kind` (string, required): Kind of archived item to restore

## Diagnostics

Captured diagnostic sections: Provenance, Vulnerabilities, Dependencies. The full working is on the page: https://verifymcp.io/servers/mrcbrbn5361-syncytiummd/syncytium-md#diagnostics

## Score history

- 2026-11-21: 83
- 2026-11-20: 82
- 2026-11-19: 82
- 2026-11-18: 81
- 2026-11-17: 81
- 2026-11-16: 81
- 2026-11-15: 65
- 2026-11-14: 80
- 2026-11-13: 79
- 2026-11-12: 79
- 2026-11-11: 78
- 2026-11-10: 73
- 2026-11-09: 77
- 2026-11-08: 77
- 2026-11-07: 76
- 2026-11-06: 76
- 2026-11-05: 75

## Common questions

### What is the SyncytiumMD MCP server?

SyncytiumMD is an MCP server listed in the public MCP registry as io.github.mrcbrbn5361/syncytiummd. One canonical context transpiled into Cursor, Claude, Copilot, Cline and more, with agent handoff. This page covers its npm package (syncytium-md).

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

SyncytiumMD scores 83 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 21 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 SyncytiumMD MCP server expose?

SyncytiumMD exposes 23 tools: syncytium_get_context, syncytium_handoff, syncytium_record_decision, syncytium_remove_decision, syncytium_list_decisions, and 18 more. Their descriptions and schemas cost roughly 1,771 tokens of context every time the server is loaded.

### Is the SyncytiumMD MCP server still maintained?

SyncytiumMD 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 licence is the SyncytiumMD MCP server under?

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

### What did VerifyMCP test on the SyncytiumMD MCP server?

VerifyMCP ran 16 checks on SyncytiumMD, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- npm package: https://www.npmjs.com/package/syncytium-md
- Socket report: https://socket.dev/npm/package/syncytium-md
- Repository: https://github.com/mrcbrbn5361/SyncytiumMD
- Changelog RSS feed: https://verifymcp.io/servers/mrcbrbn5361-syncytiummd/syncytium-md.xml
- Changelog JSON feed: https://verifymcp.io/servers/mrcbrbn5361-syncytiummd/syncytium-md/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/mrcbrbn5361-syncytiummd/syncytium-md.json
- HTML version of this page: https://verifymcp.io/servers/mrcbrbn5361-syncytiummd/syncytium-md
