SyncytiumMD
NPM · SYNCYTIUM-MD
One canonical context transpiled into Cursor, Claude, Copilot, Cline and more, with agent handoff.
Available components
Last scanned (15 hours ago)
Scores higher than 73% of npm servers
Category Developer Tools
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 Security80
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 39 of 107 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to mrcbrbn5361/SyncytiumMD). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 5 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability74
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1906 tokens (~82/item across 23 items; 23 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management53
- Stability observed for 16 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (43% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 24 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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.
- 21 Nov 26 +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.
- 19 Nov 26 +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.
- 16 Nov 26 +16
- Malware scan: unverified → pass ▲ security
- 15 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- Package version: 0.3.1 → 0.3.2 functional
- 14 Nov 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.
- 12 Nov 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.
- 11 Nov 26 +5
- Source repository: unverified → pass ▲ security
- 10 Nov 26 −4
- Provenance: pass → unverified ▼ security
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 21 Nov 2026 · Analysed npm/syncytium-md@0.3.2
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | mrcbrbn5361/SyncytiumMD |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/mrcbrbn5361/SyncytiumMD/.github/workflows/release.yml@refs/tags/v0.3.2 |
| Rekor log index | 3907611038 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:6d662798b234f7c3c1ac03a2f1e0fd5c461456047f94e9252aee34953e31a789d61ed75086ae7e7d801a18d05b34ddfde457f8e72a1b7b07fd5651583 |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 107 packages
| Packages resolved | 107 |
|---|---|
| Stale | 39 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
syncytium_create_rule ~154
Write. Add a new canonical rule to .syncytium/rules/ and regenerate every bridge file. Reversible with syncytium_remove_rule.
| Name | Type | Req | Description |
|---|---|---|---|
| alwaysApply | boolean | – | Force the rule into every session |
| body | string | yes | 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 | yes | Human-readable rule title |
No output schema declared.
No examples provided.
syncytium_diff ~53
Read-only. Check context drift between .syncytium/ and the generated bridge files. Returns a summary plus the drifted paths.
| Name | Type | Req | Description |
|---|---|---|---|
| targets | array | – | Restrict the drift check to specific adapter ids |
| Name | Type | Req | Description |
|---|---|---|---|
| drifted | array | yes | – |
| hasDrift | boolean | yes | – |
| summary | object | yes | – |
No examples provided.
syncytium_doctor ~49
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.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| checks | array | yes | – |
| overallStatus | string | yes | – |
| stats | object | yes | – |
No examples provided.
syncytium_get_context ~73
Read-only. Get project rules, architecture, architectural decisions (ADR), and the active handoff state. Use this first in any session.
| Name | Type | Req | Description |
|---|---|---|---|
| includeContent | boolean | – | Include full rule bodies instead of just id/title/description |
| topic | string | – | Optional filter; defaults to a compact overview |
No output schema declared.
No examples provided.
syncytium_get_graph ~70
Read-only. Get the project knowledge graph (rules, tags, ADRs, agents, adapters, bridge files) for visualisation.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Perspective to isolate before building the graph |
| compact | boolean | – | Hide file, directory and tag nodes for a smaller payload |
| Name | Type | Req | Description |
|---|---|---|---|
| edges | array | yes | – |
| nodes | array | yes | – |
| stats | object | yes | – |
No examples provided.
syncytium_get_history ~45
Read-only. Get the multi-agent handoff audit trail: past goals, completed tasks and baton passes.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Maximum handoff entries to return |
| Name | Type | Req | Description |
|---|---|---|---|
| count | number | yes | Number of returned records |
| items | array | yes | The returned records |
No examples provided.
syncytium_handoff ~163
Write. Pass the baton to the next AI agent or record progress on the shared blackboard. Run this before you finish your turn.
| Name | Type | Req | Description |
|---|---|---|---|
| activeAgent | string | yes | 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 |
No output schema declared.
No examples provided.
syncytium_import ~72
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.
| Name | Type | Req | Description |
|---|---|---|---|
| dryRun | boolean | – | Report what would be imported without writing (default). |
No output schema declared.
No examples provided.
syncytium_lint ~34
Read-only. Validate canonical rules, frontmatter and ADR schema. Returns a compact summary, not the full report.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| errorCount | number | yes | – |
| errors | array | yes | – |
| totalChecked | number | yes | – |
| valid | boolean | yes | – |
| warningCount | number | yes | – |
| warnings | array | yes | – |
No examples provided.
syncytium_list_decisions ~72
Read-only. List recorded ADRs (optionally filtered by status or free-text query).
| Name | Type | Req | Description |
|---|---|---|---|
| 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 |
| Name | Type | Req | Description |
|---|---|---|---|
| count | number | yes | Number of returned records |
| items | array | yes | The returned records |
No examples provided.
syncytium_list_rules ~45
Read-only. Search the canonical rule catalog by id, title, tag or body text.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | – | Free-text search; omit to list all rules |
| Name | Type | Req | Description |
|---|---|---|---|
| count | number | yes | Number of returned records |
| items | array | yes | The returned records |
No examples provided.
syncytium_list_trash ~65
Read-only. List recoverable deletions (archived rules and ADRs) with their archive timestamps, newest first.
| Name | Type | Req | Description |
|---|---|---|---|
| kind | string | – | Restrict to archived rules or archived ADRs |
| limit | number | – | Maximum number of entries to return |
| Name | Type | Req | Description |
|---|---|---|---|
| count | number | yes | Number of returned records |
| items | array | yes | The returned records |
No examples provided.
syncytium_lock_acquire ~91
Write. Take the exclusive workspace lease so other agents do not edit the same files concurrently.
| Name | Type | Req | Description |
|---|---|---|---|
| agent | string | yes | 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) |
No output schema declared.
No examples provided.
syncytium_lock_release ~58
Write. Release the workspace lease held by this agent (idempotent).
| Name | Type | Req | Description |
|---|---|---|---|
| agent | string | – | Only release the lease if it is held by this agent |
| force | boolean | – | Release a lease held by another agent |
No output schema declared.
No examples provided.
syncytium_lock_status ~26
Read-only. Report who currently holds the workspace lease and when it expires.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| acquiredAt | string | – | – |
| agent | string | – | – |
| expiresAt | string | – | – |
| goal | string | – | – |
| host | string | – | – |
| isExpired | boolean | yes | – |
| locked | boolean | yes | – |
No examples provided.
syncytium_record_decision ~108
Write. Record an Architectural Decision (ADR) shared across all AI agents.
| Name | Type | Req | Description |
|---|---|---|---|
| consequences | string | yes | Pros, cons and implications |
| context | string | yes | Background problem |
| decision | string | yes | The chosen solution |
| id | string | – | ADR id; auto-allocated when omitted (ADR-002, ADR-003, …) |
| status | string | – | Lifecycle status of the ADR |
| title | string | yes | Short imperative title of the decision |
No output schema declared.
No examples provided.
syncytium_remove_decision ~100
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.
| Name | Type | Req | Description |
|---|---|---|---|
| confirm | boolean | – | Must be true with dryRun:false to actually delete. |
| dryRun | boolean | – | Preview the impact without changing anything (default). |
| id | string | yes | ADR id to remove, e.g. ADR-003 |
No output schema declared.
No examples provided.
syncytium_remove_rule ~100
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.
| Name | Type | Req | Description |
|---|---|---|---|
| confirm | boolean | – | Must be true with dryRun:false to actually delete. |
| dryRun | boolean | – | Preview the impact without changing anything (default). |
| id | string | yes | Rule id to remove |
No output schema declared.
No examples provided.
syncytium_restore ~64
Write. Restore an archived rule or ADR from the recoverable trash and regenerate bridge files. Fails if the same id already exists.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Id of the archived rule or ADR |
| kind | string | yes | Kind of archived item to restore |
No output schema declared.
No examples provided.
syncytium_sync ~98
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.
| Name | Type | Req | Description |
|---|---|---|---|
| force | boolean | – | Override an active workspace lease |
| noPrune | boolean | – | Do not remove orphaned generated files. |
| targets | array | – | Restrict to specific adapter ids |
No output schema declared.
No examples provided.
syncytium_update_rule ~132
Write. Edit an existing canonical rule in place (title, description, body, globs, tags).
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Rule id to update |
| sync | boolean | – | Regenerate bridge files afterwards |
| tags | array | – | Replacement tag list |
| title | string | – | New human-readable title |
No output schema declared.
No examples provided.
syncytium_validate ~36
Read-only. Validate syncytium.config.json and every rule frontmatter against the zod schema and report issues without changing anything.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| issues | array | yes | – |
| valid | boolean | yes | – |
| warnings | array | yes | – |
No examples provided.
syncytium_validate_fix ~63
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.
| Name | Type | Req | Description |
|---|---|---|---|
| dryRun | boolean | – | Report the repairs that would be applied without writing them. |
No output schema declared.
No examples provided.
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.
npm · syncytium-md
claude mcp add mrcbrbn5361-syncytiummd -- npx -y syncytium-md mcp
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.