cloudpin
NPM · CLOUDPIN
Read-only checks that cloud CLI commands run on the accounts a project pins in .cloudpin.yml.
Available components
Last scanned (5 hours ago)
Scores higher than 36% of npm servers
Category Cloud Infrastructure
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. How we score → Why this is hard to score →
Supply Chain Security63
- No malware found by supply-chain analysis.Pass
- Known CVEs could not be checked: the version this server declares is not published in its registry.Unverified
- No install/post-install scripts declared.Pass
- Dependency health could not be checked: the version this server declares is not published in its registry.Unverified
Provenance & Transparency74
- 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. View diagnostics → Unverified
- Cryptographically verified build provenance (signed, bound to paureis/cloudpin). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 0 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability70
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
- Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 −15
- Known CVEs: pass → unverified ▼ security
- Provenance: pass → unverified ▼ security
- Dependency health: 0.84 → unverified ▼ functional
- Package version: 1.2.1 → 1.2.3 functional
- Package version: 1.2.1 → 1.2.2 functional
- 4 Nov 26 +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.
- 2 Nov 26 +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.
- 31 Oct 26 +16
- Malware scan: unverified → pass ▲ security
- 30 Oct 26 0
- Malware scan: unverified → pass ▲ security
- Stability: unverified → 0.03 ▲ functional
- Package version: 1.2.0 → 1.2.1 functional
- 29 Oct 26 65
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed npm/cloudpin@1.2.3
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | paureis/cloudpin |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/paureis/cloudpin/.github/workflows/release.yml@refs/tags/v1.2.3 |
| Rekor log index | 3692771330 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:690b99ea4826bfbb06d4223058981aabd2a8e360cf518e32b3608571782758353b6a46db13780ed4d0497c08aace80a4fc225d7a23e593333e429a070 |
Background: How many MCP packages publish verified provenance →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
cloudpin_check ~129
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.
| Name | Type | Req | Description |
|---|---|---|---|
| command | string | yes | 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. |
No output schema declared.
No examples provided.
cloudpin_status ~83
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.
| Name | Type | Req | Description |
|---|---|---|---|
| cwd | string | – | Project folder; defaults to the current one. |
No output schema declared.
No examples provided.
How do I install the cloudpin MCP server?
cloudpin runs locally as an npm package, launched with npx -y cloudpin. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · cloudpin
claude mcp add paureis-cloudpin -- npx -y cloudpin
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.