# cloudpin (npm · cloudpin)

Read-only checks that cloud CLI commands run on the accounts a project pins in .cloudpin.yml.

- Trust score: 68/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- npm · `cloudpin`: 68/100 (this document), [markdown](https://verifymcp.io/servers/paureis-cloudpin/cloudpin.md), [page](https://verifymcp.io/servers/paureis-cloudpin/cloudpin)

## Channel facts

- Registry: `npm`
- Package: `cloudpin`
- Version: `1.2.3`
- 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-11-05.

- **Supply Chain Security**: 63/100
  - No malware found by supply-chain analysis.
  - Known CVEs could not be checked: the version this server declares is not published in its registry.
  - No install/post-install scripts declared.
  - Dependency health could not be checked: the version this server declares is not published in its registry.
- **Provenance & Transparency**: 74/100
  - Repository presence not verified: we could not reach the forge to check. This is a gap on our side, not a finding about the repository.
  - Cryptographically verified build provenance (signed, bound to paureis/cloudpin).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 0 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 70/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 367 tokens (~183/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**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% 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.
  - We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

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

cloudpin runs locally as an npm package, launched with npx -y cloudpin 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 paureis-cloudpin -- npx -y cloudpin mcp
```

### Cursor

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

### VS Code

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

### Codex

```bash
codex mcp add paureis-cloudpin -- npx -y cloudpin mcp
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add paureis-cloudpin --command npx --arg -y --arg cloudpin --arg mcp
```

### Hermes

```yaml
mcp_servers:
  paureis-cloudpin:
    command: "npx"
    args: ["-y", "cloudpin", "mcp"]
```

### Netclaw

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

### Vellum

```bash
assistant mcp add paureis-cloudpin -t stdio -c npx -a -y cloudpin mcp
```

### Other

```json
{
  "mcpServers": {
    "paureis-cloudpin": {
      "command": "npx",
      "args": [
        "-y",
        "cloudpin",
        "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-11-05 (score 68, −15)

- [security regression] Known CVEs: pass → unverified
- [security regression] Provenance: pass → unverified
- [functional regression] Dependency health: 0.84 → unverified
- [functional] Package version: 1.2.1 → 1.2.3
- [functional] Package version: 1.2.1 → 1.2.2

### 2026-11-04 (score 83, +1)

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

### 2026-11-02 (score 82, +1)

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

### 2026-10-31 (score 81, +16)

- [security improvement] Malware scan: unverified → pass

### 2026-10-30 (score 65, 0)

- [security improvement] Malware scan: unverified → pass
- [functional improvement] Stability: unverified → 0.03
- [functional] Package version: 1.2.0 → 1.2.1

### 2026-10-29 (score 65)

First indexed and scored.

## MCP tools (2)

### `cloudpin_status` (~83 tokens)

Which cloud accounts each CLI (az, aws, gcloud, vercel, gh, kubectl, helm, supabase, wrangler) is using here, what this project's .cloudpin.yml pins, which environment applies, and which agent hooks are installed. Call it before cloud work.

Input parameters:

- `cwd` (string): Project folder; defaults to the current one.

### `cloudpin_check` (~129 tokens)

Would cloudpin allow this shell command, as an agent's? Returns each cloud CLI call in it, the account it would use and why, and the verdict (allow, block or ask) with the reason and the fix. Nothing is run.

Input parameters:

- `command` (string, required): The full command line, e.g. "cd web && vercel deploy --prod".
- `cwd` (string): Folder the command would run in; defaults to the current one.
- `shell` (string): The shell that would run it: powershell for a PowerShell tool's command; defaults to bash.

## Diagnostics

Captured diagnostic sections: Provenance. The full working is on the page: https://verifymcp.io/servers/paureis-cloudpin/cloudpin#diagnostics

## Score history

- 2026-11-05: 68
- 2026-11-04: 83
- 2026-11-03: 82
- 2026-11-02: 82
- 2026-11-01: 81
- 2026-10-31: 81
- 2026-10-30: 65
- 2026-10-29: 65

## Common questions

### What is the cloudpin MCP server?

cloudpin is an MCP server listed in the public MCP registry as io.github.paureis/cloudpin. Read-only checks that cloud CLI commands run on the accounts a project pins in .cloudpin.yml. This page covers its npm package (cloudpin).

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

cloudpin scores 68 out of 100 on VerifyMCP. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 cloudpin MCP server expose?

cloudpin exposes 2 tools: cloudpin_status, cloudpin_check. Their descriptions and schemas cost roughly 212 tokens of context every time the server is loaded.

### Is the cloudpin MCP server still maintained?

cloudpin 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 cloudpin MCP server under?

cloudpin declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

### What did VerifyMCP test on the cloudpin MCP server?

VerifyMCP ran 13 checks on cloudpin, covering Malware scan, Install scripts, Provenance, License and 9 more. 3 items could not be completed, a gap on our side rather than a finding about cloudpin: Known CVEs, Dependency health and Provenance. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- npm package: https://www.npmjs.com/package/cloudpin
- Socket report: https://socket.dev/npm/package/cloudpin
- Repository: https://github.com/paureis/cloudpin
- Website: https://github.com/paureis/cloudpin/blob/main/docs/mcp.md
- Changelog RSS feed: https://verifymcp.io/servers/paureis-cloudpin/cloudpin.xml
- Changelog JSON feed: https://verifymcp.io/servers/paureis-cloudpin/cloudpin/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/paureis-cloudpin/cloudpin.json
- HTML version of this page: https://verifymcp.io/servers/paureis-cloudpin/cloudpin