@cloudgrid-io/mcp
npm
v0.21.17
Source verified
Published by cloudgrid-io — publish provenance cryptographically ties this package to that repository. That is proof of origin, not an official vendor package.
MCP access to CloudGrid — the live runtime environment where the user's apps run WITH the infrastructure they need out of the box: managed MongoDB, Redis (cache/queues/pub-sub), a pgvector store, persistent disk, and built-in AI with no API keys, in any l
The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.
1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:
The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.
2. Client adoption risk — 100 − 6 = 94. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:
| Points | Adoption-risk factor |
|---|---|
| −6 | capability blast radius (high) — client exposure if the model is manipulated |
Capability observations and info notes are shown under Findings but never scored.
Open any row's finding below for the file, line and evidence behind a deduction.
In the server's implementation (`src/tools/cli.js:5`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: { execFile } from "node:child_process"; import { promisify } from "node:util"; import { readFileSync, existsSync, statSy
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server src/tools/cli.js
Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.
| Version | Score | Findings | Engine | Scanned |
|---|---|---|---|---|
v0.21.17 latest |
A 94/100 | 1 | 1.13.0 | 2026-09-07 |
v0.21.14 |
A 94/100 | 1 | 1.13.0 | 2026-08-31 |
v0.21.10 |
A 94/100 | 1 | 1.13.0 | 2026-08-30 |
v0.21.9 |
A 94/100 | 1 | 1.13.0 | 2026-08-27 |
v0.21.7 |
A 94/100 | 1 | 1.13.0 | 2026-08-25 |
v0.21.5 |
A 94/100 | 1 | 1.12.1 | 2026-08-24 |
v0.21.2 |
A 93/100 | 1 | 1.12.1 | 2026-08-23 |
v0.21.1 |
A 94/100 | 1 | 1.12.1 | 2026-08-21 |
v0.21.0 |
A 94/100 | 1 | 1.12.1 | 2026-08-17 |
v0.20.56 |
A 94/100 | 1 | 1.12.1 | 2026-08-16 |
Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.
The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.
npx mcptrustchecker scan @cloudgrid-io/mcp --online
Adapters for the FrontMCP framework
Transcend MCP Server — Admin tools.
Transcend MCP Server — Assessments tools.
MCP Server for Bling
MCP Server for Blogger API
Official MCP server for Brilliant Directories — manage members, posts, leads, reviews, and more.