# Connections (npm · connections-mcp)

AWS, GitHub and connected services from your agent, no keys to paste, plus local shell and browser.

- Trust score: 67/100 (medium)
- Change this week: +8
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-17

## Components

- npm · `connections-mcp`: 67/100 (this document), [markdown](https://verifymcp.io/servers/lunarwerx-connections/connections-mcp.md), [page](https://verifymcp.io/servers/lunarwerx-connections/connections-mcp)

## Channel facts

- Registry: `npm`
- Package: `connections-mcp`
- Version: `2.240.0`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-17.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 6/100
  - Repository check failed: no source repository is declared.
  - Provenance check failed: no build-provenance attestation is published.
  - Licence could not be checked: the licence is shipped as a file inside the package, not declared as a standard (SPDX) licence identifier, so we cannot tell whether it is OSI-approved.
  - Actively maintained (last published 4 days ago).
  - Security-disclosure policy not yet verified: we couldn't inspect the source repository.
- **Schema Quality & AI Usability**: 68/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1145 tokens (~572/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 60/100
  - Stability observed for 18 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 86/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 59% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the Connections MCP server?

Connections runs locally as an npm package, launched with npx -y connections-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add lunarwerx-connections -- npx -y connections-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "lunarwerx-connections": {
      "command": "npx",
      "args": [
        "-y",
        "connections-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "lunarwerx-connections": {
      "command": "npx",
      "args": [
        "-y",
        "connections-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add lunarwerx-connections -- npx -y connections-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "lunarwerx-connections": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "connections-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add lunarwerx-connections --command npx --arg -y --arg connections-mcp
```

### Hermes

```yaml
mcp_servers:
  lunarwerx-connections:
    command: "npx"
    args: ["-y", "connections-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "lunarwerx-connections": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "connections-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add lunarwerx-connections -t stdio -c npx -a -y connections-mcp
```

### Other

```json
{
  "mcpServers": {
    "lunarwerx-connections": {
      "command": "npx",
      "args": [
        "-y",
        "connections-mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-16 (score 67, +1)

No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-14 (score 66, +35)

- [security improvement] Injection markers: unverified → pass
- [functional regression] MCP protocol: unverified → fail
- [functional improvement] Tool coverage: 53% → 59%
- [functional improvement] Schema quality: 1186 → 572
- [functional improvement] Tool coverage: unverified → 100
- [functional improvement] Stability: unverified → 0.50
- [functional improvement] Schema quality: unverified → 100
- [functional] Schema quality: excellent → good
- [functional] Package version: 2.191.4 → 2.240.0

### 2026-10-13 (score 31, 0)

- [functional] Package version: 2.191.4 → 2.240.0

### 2026-10-12 (score 31, −28)

- [security regression] Tool safety: pass → unverified
- [security] Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet.
- [functional regression] Capabilities: fail → unverified
- [functional regression] License: fail → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional regression] Schema quality: 100 → unverified
- [functional] Licence: UNLICENSED
- [functional] Package version: 2.191.4 → 2.240.0
- [functional] Package version: 2.191.4 → 2.231.0

### 2026-09-30 (score 59, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-09-29 (score 44)

First indexed and scored.

## MCP tools (2)

### `connections_search_catalog` (~265 tokens)

Search your local tools and the Connections catalog

Find something to run: your LOCAL tools on this machine (browser/shell/git/deploy/ssh/architect/…) and every API endpoint this workspace's company can call (first-party + connected third-party). A local tool's exact name → that one tool, catalog not searched. An endpoint's or Script Vault instrument's exact tool_name → that row first, ahead of every fuzzy hit (an instrument with its full description). Auto browser sign-in if needed (no key to paste).

Input parameters:

- `limit` (integer): Your CONTEXT budget - bounds the whole response, not just the endpoint list (default 8, max 25).
- `query` (string): What to find; blank → your full local-tool inventory.
- `service` (string)
- `use_case` (string): What you are trying to get done, in a sentence (e.g. 'deploy the pay lambda and check its logs'). Sharpens the local-tool ranking; alone it is the query. The top local hit lists the tools usually run…
- `verbose` (boolean): false (default): endpoint hits list param names only, local tools and Script Vault instruments a one-line summary. true: each hit's full parameter schema and description.

### `connections_execute` (~424 tokens)

Run a local tool or a catalog endpoint

Run something found with connections_search_catalog. (1) A LOCAL tool on this machine: { local:true, tool_name, params }; runs here, no sign-in. (2) A catalog API ENDPOINT: { endpoint_id } (or service+tool_name); runs as this workspace's company with the vaulted credential injected server-side (value-blind; auto browser sign-in if needed, no key to paste). Target a connected account with `instance`.

Input parameters:

- `company` (string): Run this call as another company you belong to (companyId, projectId or exact name from connections_list_companies), e.g. email_action inbox.threads for its inbox. Refused if you are not a member. Om…
- `endpoint_id` (string)
- `files` (object): Catalog endpoints only: { "<params field>": "<file path>" }; this machine reads each file into that params field as base64 (dotted, e.g. "data_base64"), so the bytes never pass through you. Never bas…
- `instance` (string)
- `jmespath` (string): Optional JMESPath applied to the JSON answer, e.g. body.items[*].id (grammar: connections_briefing).
- `local` (boolean): true → run tool_name as a LOCAL tool instead of a catalog endpoint.
- `params` (object)
- `params_file` (string): A JSON object file (relative to this workspace or absolute) read into params on this machine. Give params OR params_file, never both.
- `project` (string): Which COMPANY/workspace THIS call runs against: a company id, project id or ref (Studio's ?project= on a catalog call; a one-call pin on a local tool, refused if you are not a member, and the reply n…
- `service` (string)
- `tool_name` (string)
- `workflow`

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/lunarwerx-connections/connections-mcp#diagnostics

## Score history

- 2026-10-17: 67
- 2026-10-16: 67
- 2026-10-15: 66
- 2026-10-14: 66
- 2026-10-13: 31
- 2026-10-12: 31
- 2026-10-04: 59
- 2026-10-03: 59
- 2026-10-02: 59
- 2026-10-01: 59
- 2026-09-30: 59
- 2026-09-29: 44

## Common questions

### What is the Connections MCP server?

Connections is an MCP server listed in the public MCP registry as io.github.Lunarwerx/connections. AWS, GitHub and connected services from your agent, no keys to paste, plus local shell and browser. This page covers its npm package (connections-mcp).

### Is the Connections MCP server safe to use?

Connections scores 67 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 17 October 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 Connections MCP server expose?

Connections exposes 2 tools: connections_search_catalog, connections_execute. Their descriptions and schemas cost roughly 689 tokens of context every time the server is loaded.

### Is the Connections MCP server still maintained?

Connections is still listed as active in the MCP registry. We last reached this channel on 17 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- npm package: https://www.npmjs.com/package/connections-mcp
- Socket report: https://socket.dev/npm/package/connections-mcp
- Website: https://studio.connectionsapi.com/mcp
- Changelog RSS feed: https://verifymcp.io/servers/lunarwerx-connections/connections-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/lunarwerx-connections/connections-mcp.json
- HTML version of this page: https://verifymcp.io/servers/lunarwerx-connections/connections-mcp