NeevCloud Sandbox

com.neevcloudPublished by neevcloud.comOfficial publisherv1.0.0Updated Oct 24, 2026

A NeevCloud sandbox as native tools: run commands, edit files, manage processes, snapshots.

VerifiedStreamable HTTPWeb executableCloud & InfrastructureDeveloper Tools

Overview

AI-generated overview

NeevCloud Sandbox exposes a remote NeevCloud sandbox to an assistant as native tools for running commands, editing files, managing processes and snapshots.

What you can do
  • Run commands inside a NeevCloud sandbox
  • Edit and manage files in the sandbox
  • Manage processes running in the sandbox
  • Work with sandbox snapshots
  • Target a specific sandbox per connection via the x-sandbox-name header
When to use it
Useful when an assistant needs an isolated remote environment to execute commands and change files rather than acting on the user's own machine, for example for coding or experimentation tasks inside a NeevCloud project.
Requirements
A remote streamable HTTP endpoint at the NeevCloud regional sandbox host; no local package. A NeevCloud project API key (sk-nc-...) with Resource Type Sandboxes, sent as a bearer token in the Authorization header. Optionally an x-sandbox-name header naming the sandbox (lowercase letters, digits, hyphens, up to 63 characters; defaults to 'default').
Before you install
The connection requires a NeevCloud project API key in the Authorization header, so treat it as a secret and scope it to the Sandboxes resource type. The tools run commands and edit files in the sandbox, which can change or delete data there; confirm which sandbox the x-sandbox-name header points to before use.

Installation

In SourceWeft

  1. Open NeevCloud Sandbox in the dashboard and add it to a workspace.
  2. Connect Authorization token credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v1.0.0LatestOct 13, 2026

Score

28% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.