io.github.rehmansherazi/syncbridge-mcp

Name: io.github.rehmansherazi/syncbridge-mcp
Author: io.github.rehmansherazi

MCPcommunity

v0.1.1io.github.rehmansheraziUnknownUpdated 4mo agonpm GitHub

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

You're 30 messages deep with Claude. The plan is solid. Now you need to build it in your editor. So you copy. You paste. You lose half the context. Your editor doesn't know what Claude knows. And next time you go back to Claude, it doesn't know what your editor did. Syncbridge fixes this — automatically, for free, no CLI required. Every developer using AI chat faces the same daily toil: AI gives…

Works in

ClaudeCursorCopilotGemini

Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →

4mo agoLast update

Package

Authorio.github.rehmansherazi

LicenseUnknown

Version0.1.1

Sourcemcp-registry

npmsyncbridge-mcp

GitHubrehmansherazi/syncbridge

SBOMCycloneDX 1.6 ↓

Trust Status

60/100Good

✓Listed in Forge index+10/10

—Publisher identity verified+0/20

→ Publisher: run `forge publish` from the package repo to claim ownership

—Ed25519 publish signature+0/5

→ Included automatically when the publisher runs `forge publish`

—Domain verification+0/5

→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }

—npm Trusted Publishing (Sigstore)+0/5

→ Publish from GitHub Actions with --provenance so the attestation binds this package to this repo

—npm maintainer match+0/5

→ Earned once your identity is verified above and that login is an npm maintainer of this package

✓CVE scan · clean+30/30

✓Static analysis · clean+20/20

Paste into Claude Code, Cursor, or any AI assistant to fix all gaps

StatusCommunity-indexed

PublisherUnverified

SignatureUnsigned

Domain—

Provenance—

Dependencies✓ 0 resolved · none vulnerable

Tool surface4 tools · none privileged

Security scan✓ Cleanv0.1.1 · 3mo agoHow well does this scan work?

EvalsNone

IndexedJun 13, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

4 tools · none privileged

Statically extracted from the published packagev0.1.1 · 3mo ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

update_stateNo description published

This tool published no description. Forge does not invent one.

read_instructionsNo description published

This tool published no description. Forge does not invent one.

get_contextNo description published

This tool published no description. Forge does not invent one.

clear_stateNo description published

This tool published no description. Forge does not invent one.

0 of 4 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

Keywords

mcp

Alternatives

Comparing tool surfaces…

io.github.rehmansherazi/syncbridge-mcp

Tools

Tools exposed

No dependency coverage