io.github.Servosity/connectwise-control-mcp

MCPcommunity
v0.1.4io.github.ServosityUnknownUpdated 25d agoGitHub

Manage ConnectWise Control (ScreenConnect) remote support and access sessions from one CLI or agent.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
25d agoLast update
Needs 1 credential before it runs
  • CONNECTWISE_CONTROL_PASSWORDAPI keyrequired

    Your ConnectWise Control instance password (HTTP Basic auth).

Declared by the author in the official MCP registry. Forge does not store, broker, or ever see these values — the config below is scaffolded with placeholders you fill in locally.

Package
Authorio.github.Servosity
LicenseUnknown
Version0.1.4
Sourcemcp-registry
GitHubservosity/msp-skills
SBOMCycloneDX 1.6 ↓
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/30
→ Publisher: run `forge publish` from the repo to claim ownership
—Domain verification+0/10
→ Not currently available for this listing type — the domain-verification check only runs for npm-backed packages today, so this row cannot be earned here yet regardless of what's hosted at the domain.
✓Prompt-injection scan · clean+30/30
✓Obfuscation / exfil scan · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
DependenciesNot audited
Tool surface—
Security scan✓ CleanvHEAD · 1mo agoHow well does this scan work?
EvalsNone
IndexedJun 17, 2026

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

Tools

Source not readable1mo ago

The repository archive could not be read at scan time (tarball exceeds size cap), so no tool declarations could be extracted from it. Nothing here is a statement about what this exposes.

About

Manage ConnectWise Control (ScreenConnect) remote support and access sessions from one CLI or agent.

Keywords
mcp
Alternatives
Comparing tool surfaces…

No dependency coverage

This entry publishes no npm package, so Forge has no dependency tree for it. That is a gap in coverage — not a statement that it has no dependencies.