connections-mcp

Name: connections-mcp
Author: Unknown

MCPcommunity

v2.191.4UnknownUNLICENSEDUpdated 6d agonpm

Connections Local MCP - a thin SELF-UPDATING loader that fetches its implementation from AWS at launch (push fixes to AWS, never re-publish). Local-execution companion (shell/git/files/ssh/browser) + browser sign-in for the remote Connections (Studio) MCP

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 →

4Downloads/wk

6d agoLast update

Package

AuthorUnknown

LicenseUNLICENSED

Version2.191.4

Sourcenpm+mcp-registry

npmconnections-mcp

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 surface—

Security scan✓ Cleanv2.191.4 · 5d agoHow well does this scan work?

EvalsNone

IndexedSep 30, 2026

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

Tools

No tool declarations found in the source5d ago

Forge read 4 source files from the published package tarball and matched no MCP tool registrations. Extraction is pattern-based over shipped source: a server that builds its tool list at runtime, or that ships only bundled or minified code, registers nothing this can see. Treat it as “not detected”, not as “exposes none”.

About

Keywords

mcp

Alternatives

Comparing tool surfaces…

connections-mcp

Tools

Dependency tree