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.

io.github.rehmansherazi/syncbridge-mcp

NPM · SYNCBRIDGE-MCP

Bridges AI chat interfaces with Claude Code CLI via shared markdown control files.

Available components

−3 this week 79 Trust /100

Last scanned (7 hours ago)

Scores higher than 61% of npm servers

Category Developer Tools

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 Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency45
Schema Quality & AI Usability81
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 119 tokens (~29/item across 4 items; 4 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management77
  • Stability observed for 23 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
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
  • Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
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.

  • 5 Nov 26 −3
    • Stability: pass → 0.77 functional
  • 3 Nov 26 0
    • Security disclosure: unverified → fail ▼ functional
  • 2 Nov 26 0
    • Security disclosure: fail → unverified ▼ functional
  • 31 Oct 26 0
    • Security disclosure: unverified → fail ▼ functional
  • 30 Oct 26 0
    • Stability: 0.97 → pass security
    • Security disclosure: fail → unverified ▼ functional
  • 29 Oct 26 0
    • Stability: pass → 0.97 functional
  • 23 Oct 26 0
    • Stability: 0.97 → pass security
  • 22 Oct 26 0
    • Stability: pass → 0.97 functional
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 5 Nov 2026 · Analysed npm/syncbridge-mcp@0.1.1

Provenance No attestation

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

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 0 packages
Packages resolved 0
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 4 exposed · ~119 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
clear_state ~27

Reset Syncbridge state for a new session

NameTypeReqDescription
projectstringyesActive project name

No output schema declared.

No examples provided.

get_context ~26

Get full merged context for active project

NameTypeReqDescription
projectstringyesActive project name

No output schema declared.

No examples provided.

read_instructions ~27

Pull latest AI instructions from Syncbridge

NameTypeReqDescription
projectstringyesActive project name

No output schema declared.

No examples provided.

update_state ~39

Push current Claude Code CLI state to Syncbridge

NameTypeReqDescription
projectstringyesActive project name
statestringyesCurrent CLI state content

No output schema declared.

No examples provided.

Install

How do I install the io.github.rehmansherazi/syncbridge-mcp server?

io.github.rehmansherazi/syncbridge-mcp runs locally as an npm package, launched with npx -y syncbridge-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 · syncbridge-mcp

# add to Claude Code
claude mcp add rehmansherazi-syncbridge-mcp -- npx -y syncbridge-mcp
Common questions

What is the io.github.rehmansherazi/syncbridge-mcp server?

io.github.rehmansherazi/syncbridge-mcp is listed in the public MCP registry as io.github.rehmansherazi/syncbridge-mcp. Bridges AI chat interfaces with Claude Code CLI via shared markdown control files. This page covers its npm package (syncbridge-mcp).

Is the io.github.rehmansherazi/syncbridge-mcp server safe to use?

io.github.rehmansherazi/syncbridge-mcp scores 79 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. 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 io.github.rehmansherazi/syncbridge-mcp server expose?

io.github.rehmansherazi/syncbridge-mcp exposes 4 tools: update_state, read_instructions, get_context, clear_state. Their descriptions and schemas cost roughly 119 tokens of context every time the server is loaded.

Is the io.github.rehmansherazi/syncbridge-mcp server still maintained?

io.github.rehmansherazi/syncbridge-mcp 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.

What licence is the io.github.rehmansherazi/syncbridge-mcp server under?

io.github.rehmansherazi/syncbridge-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.