com.light-cloud/mcp-server
NPM · @LIGHT-CLOUD/MCP-SERVER
Deploy and run web apps, APIs and databases on Light Cloud from your AI agent.
Available components
Last scanned (2 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 Security93
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known medium-severity CVE affects glob 10.5.0, reached via archiver > archiver-utils > glob. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 61 of 166 dependencies flagged as unhealthy (1 deprecated). View diagnostics → Partial
Provenance & Transparency48
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 7 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability79
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 8659 tokens (~78/item across 110 items; 110 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage89
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 67% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 13 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 111 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
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
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.
- 31 Oct 26 −1
- CVE-2026-118764 affects this package: medium ▼ security
- CVE-2026-118773 affects this package: medium ▼ security
- Known CVEs: pass → fail ▼ security
- 29 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 28 Oct 26 55
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/@light-cloud/mcp-server@1.6.2
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 2 findings
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-3g3m-2fjr-6pw4 | CVE-2026-118773 | medium | yes | |
| GHSA-g3hv-75wg-m249 | CVE-2026-118764 | medium | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 166 packages
| Packages resolved | 166 |
|---|---|
| Deprecated | 1 |
| Stale | 60 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
set-usage-alerts ~81
Set one extra usage-alert email at a dollar amount of usage this cycle (the 80% and 100% emails always send). Pass null to remove it. Alerts only email and never pause anything; a bigger plan includes more usage.
| Name | Type | Req | Description |
|---|---|---|---|
| alert_at_usd | – | yes | – |
| organisation_id | string | yes | The organization (workspace) ID |
No output schema declared.
No examples provided.
sign-out-device ~35
Sign one session out (from list-connected-devices). It stops working within fifteen minutes.
| Name | Type | Req | Description |
|---|---|---|---|
| session_id | string | yes | – |
No output schema declared.
No examples provided.
update-application ~231
Change an application's build settings: framework, build command, output directory, monorepo root, runtime, container port, default size and instance limits, auto-deploy branches, GitHub checks. Only the fields given change. Redeploy afterwards for a build change to take effect.
| Name | Type | Req | Description |
|---|---|---|---|
| application_id | string | yes | – |
| auto_delete_stale_envs | boolean | – | – |
| auto_deploy_branches | array | – | Branches that deploy on push |
| build_command | string | – | – |
| container_port | integer | – | – |
| cpu | string | – | – |
| framework | string | – | – |
| github_checks_enabled | boolean | – | – |
| github_pr_comments_enabled | boolean | – | – |
| max_instances | integer | – | – |
| memory | string | – | e.g. 512Mi, 1Gi |
| min_instances | integer | – | – |
| organisation_id | string | yes | The organization (workspace) ID |
| output_directory | string | – | – |
| root_directory | string | – | Repo-relative folder to build from (monorepos) |
| runtime | string | – | – |
No output schema declared.
No examples provided.
update-database ~101
Change a database's name, tier, region, storage or high availability. Only the fields given change; a tier or storage change may take a few minutes.
| Name | Type | Req | Description |
|---|---|---|---|
| database_id | string | yes | – |
| ha_enabled | boolean | – | – |
| name | string | – | – |
| organisation_id | string | yes | The organization (workspace) ID |
| region | string | – | – |
| storage_gb | integer | – | – |
| tier | string | – | – |
No output schema declared.
No examples provided.
update-environment ~166
Change one environment's settings: name, build command, output directory, container port, memory, cpu, instance limits, auto-deploy on push. Only the fields given change. For variables use set-environment-variables; for the password gate use set-password-protection.
| Name | Type | Req | Description |
|---|---|---|---|
| auto_deploy | boolean | – | Redeploy automatically on push to this environment's branch |
| build_command | string | – | – |
| container_port | integer | – | – |
| cpu | string | – | – |
| environment_id | string | yes | – |
| max_instances | integer | – | – |
| memory | string | – | – |
| min_instances | integer | – | – |
| name | string | – | – |
| organisation_id | string | yes | The organization (workspace) ID |
| output_directory | string | – | – |
No output schema declared.
No examples provided.
update-profile ~64
Change the signed-in user's name or time zone. Password and two-factor settings are changed in the console only.
| Name | Type | Req | Description |
|---|---|---|---|
| first_name | string | – | – |
| last_name | string | – | – |
| timezone | string | – | IANA zone, e.g. Europe/Warsaw |
No output schema declared.
No examples provided.
upload-and-deploy ~124
Complete workflow to package, upload, and deploy a local project
| Name | Type | Req | Description |
|---|---|---|---|
| application_id | string | – | Existing application ID to redeploy to |
| directory | string | – | Path to project directory. Defaults to current working directory. |
| name | string | – | Application name. Defaults to folder name for new apps. |
| organisation_id | string | yes | Organization to deploy to |
| password | string | – | Visitor password to gate the site behind (6-128 characters). Omit for a public site. On a redeploy the existing setting is kept unless this is given. |
No output schema declared.
No examples provided.
wait-for-deployment ~109
Block until an application's current deployment finishes, then return the live URL. Call this right after upload-and-deploy or create-application instead of polling status yourself. Returns early with status 'building' if the timeout passes — call it again.
| Name | Type | Req | Description |
|---|---|---|---|
| application_id | string | yes | The application ID |
| organisation_id | string | yes | The organization ID |
| timeout_seconds | integer | – | How long to wait before returning the in-progress status (default 50, keeps within client tool timeouts) |
No output schema declared.
No examples provided.
whoami ~16
Check authentication status and show current user
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
write-project-config ~132
Write/update .lightcloud config file in a project directory
| Name | Type | Req | Description |
|---|---|---|---|
| application_id | string | – | Application ID to save |
| application_name | string | – | Application name to save |
| deployment_type | string | – | Deployment type to save |
| directory | string | – | Path to project directory. Defaults to current working directory. |
| environment_id | string | – | Environment ID to save |
| framework | string | – | Framework id to save, validated by the backend registry (e.g. react, nextjs, sveltekit, django, fastapi) |
| organisation_id | string | – | Organization ID to save |
No output schema declared.
No examples provided.
How do I install the com.light-cloud/mcp-server server?
com.light-cloud/mcp-server runs locally as an npm package, launched with npx -y @light-cloud/mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @light-cloud/mcp-server
claude mcp add com-light-cloud-mcp-server -- npx -y @light-cloud/mcp-server
What is the com.light-cloud/mcp-server server?
com.light-cloud/mcp-server is listed in the public MCP registry as com.light-cloud/mcp-server. Deploy and run web apps, APIs and databases on Light Cloud from your AI agent. This page covers its npm package (@light-cloud/mcp-server).
Is the com.light-cloud/mcp-server server safe to use?
com.light-cloud/mcp-server scores 69 out of 100 on VerifyMCP. We recorded 2 known advisories against it as of 5 November 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 com.light-cloud/mcp-server server expose?
com.light-cloud/mcp-server exposes 110 tools: ping, login, logout, connect, connect-status, and 105 more. Their descriptions and schemas cost roughly 7,928 tokens of context every time the server is loaded.
Is the com.light-cloud/mcp-server server still maintained?
com.light-cloud/mcp-server 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 com.light-cloud/mcp-server server under?
com.light-cloud/mcp-server declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.