Command Cloud MCP Server

command-cloud-mcp npm v1.0.0

Published by bripple89 — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.

Trust grade
A
99/100
Last scanned get badge →
Trust
A · 99/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
Minimal
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
A Why this grade threat 100 − adoption risk = 99/100

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 − 1 = 99. 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:

PointsAdoption-risk factor
−1 publisher verification (public source) — no provenance, but the source is public and inspectable

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.

Findings 0

✓ No findings. The scan raised nothing on this surface — see Coverage for how deep it could look.

Tools 53

Each tool and what it can reach — statically extracted from the published source.

  • cloud_auth_statusno sensitive capability
  • cloud_healthno sensitive capability
  • cloud_set_max_responseno sensitive capability
  • cloud_usageno sensitive capability
  • dismiss_alertno sensitive capability
  • get_billableno sensitive capability
  • get_billing_settingsno sensitive capability
  • get_customerno sensitive capability
  • get_customer_scorecardno sensitive capability
  • get_invoiceno sensitive capability
Show 43 more tools ↓
  • get_jobno sensitive capability
  • get_locationno sensitive capability
  • get_mixno sensitive capability
  • get_orderno sensitive capability
  • get_productno sensitive capability
  • get_ticketno sensitive capability
  • list_alertsno sensitive capability
  • list_batch_resultsno sensitive capability
  • list_billablesno sensitive capability
  • list_billing_lrrno sensitive capability
  • list_carriersno sensitive capability
  • list_contactsno sensitive capability
  • list_customersno sensitive capability
  • list_driversno sensitive capability
  • list_entitiesno sensitive capability
  • list_inventory_balance_historyno sensitive capability
  • list_inventory_balancesno sensitive capability
  • list_inventory_demandno sensitive capability
  • list_inventory_transaction_historyno sensitive capability
  • list_inventory_transactionsno sensitive capability
  • list_invoicesno sensitive capability
  • list_jobsno sensitive capability
  • list_loadsno sensitive capability
  • list_locationsno sensitive capability
  • list_mixesno sensitive capability
  • list_order_historyno sensitive capability
  • list_order_requestsno sensitive capability
  • list_ordersno sensitive capability
  • list_payment_methodsno sensitive capability
  • list_payment_termsno sensitive capability
  • list_price_adjustmentsno sensitive capability
  • list_price_booksno sensitive capability
  • list_productsno sensitive capability
  • list_projectsno sensitive capability
  • list_prospectsno sensitive capability
  • list_quotesno sensitive capability
  • list_tax_codesno sensitive capability
  • list_test_resultsno sensitive capability
  • list_ticket_inventory_statusno sensitive capability
  • list_ticketsno sensitive capability
  • list_usersno sensitive capability
  • list_vehiclesno sensitive capability
  • list_vendorsno sensitive capability

What this scan could not see

Versions 1

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.

VersionScoreFindingsEngineScanned
v1.0.0 latest A 99/100 0 1.9.0 2026-07-24

Embed this score

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.

MCP Trust Score: A · 99/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/command-cloud-mcp/badge.svg)](https://mcptrustchecker.com/registry/command-cloud-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/command-cloud-mcp"><img src="https://mcptrustchecker.com/registry/command-cloud-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/command-cloud-mcp/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

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 command-cloud-mcp --online

Use the free API → How scoring works

More in Developer Tools