Scalix Cloud
REMOTE · API.SCALIX.WORLD · SCANNED SEP 20
The agent-native cloud: database, functions, AI, storage, computers. 50 tools, one API key.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security97
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability87
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 3933 tokens (~74/item across 53 items; 51 tools + 2 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management96
- Stability check failed: schema churn in the 30 days we've observed: 2 tool removals, 0 breaking changes, 0 auth/transport breaks, 0 additions. See how to fix → Fail
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
- All 8 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 52 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
How do I install the Scalix Cloud MCP server?
Scalix Cloud is a hosted endpoint at https://api.scalix.world/v1/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · api.scalix.world
claude mcp add --transport http world-scalix-cloud 'https://api.scalix.world/v1/mcp'
{
"mcpServers": {
"world-scalix-cloud": {
"url": "https://api.scalix.world/v1/mcp"
}
}
} {
"servers": {
"world-scalix-cloud": {
"type": "http",
"url": "https://api.scalix.world/v1/mcp"
}
}
} [mcp_servers.world-scalix-cloud] url = "https://api.scalix.world/v1/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"world-scalix-cloud": {
"type": "remote",
"url": "https://api.scalix.world/v1/mcp",
"enabled": true
}
}
} openclaw mcp add world-scalix-cloud --url 'https://api.scalix.world/v1/mcp' --transport streamable-http
mcp_servers:
world-scalix-cloud:
url: "https://api.scalix.world/v1/mcp" {
"McpServers": {
"world-scalix-cloud": {
"Transport": "http",
"Url": "https://api.scalix.world/v1/mcp"
}
}
} assistant mcp add world-scalix-cloud -t streamable-http -u 'https://api.scalix.world/v1/mcp'
{
"mcpServers": {
"world-scalix-cloud": {
"type": "http",
"url": "https://api.scalix.world/v1/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 13 Sept 26 0
- Stability: unverified → fail ▼ security
- Authorization: unverified → pass ▲ security
- Injection markers: unverified → pass ▲ security
- TLS certificate: unverified → pass ▲ security
- HSTS header: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- MCP protocol: unverified → fail ▼ functional
- Endpoint reachability: unreachable → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Schema quality: unverified → 100 ▲ functional
- 12 Sept 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- Stability: fail → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Authorization: pass → unverified ▼ security
- TLS certificate: pass → unverified ▼ security
- HSTS header: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Schema quality: 100 → unverified ▼ functional
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 85 to 96.
- 4 Sept 26 0
- A breaking change shipped without a version bump: still 1.4.1 ▼ security
- Tool “scalix_search” was removed ▼ security
- Tool “scalix_usage” was removed ▼ security
- “scalix_fn_deploy” reworded the description of “runtime” cosmetic
- 3 Sept 26 0
- Tool “scalix_ai_infer” rewrote its description, which is the text the model reads security
- Tool “scalix_ai_models” rewrote its description, which is the text the model reads security
- “scalix_ai_infer” reworded the description of “model” cosmetic
- 26 Aug 26 +3
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70.
- 23 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63.
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 20 Sept 2026 · Probed https://api.scalix.world/v1/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=scalix.world | CN=YR1,O=Let's Encrypt,C=US | 12 Sept 2026 | 11 Dec 2026 | RSA 2048 | SHA256-RSA | 586df21617e318373ebbb2023aaabe6ffae |
| SANs: *.auth.scalix.world, *.db.scalix.world, *.fn.scalix.world, *.run.scalix.world, *.store.scalix.world, api.scalix.world, console.scalix.world, docs.scalix.world, prime.scalix.world, scalix.world, www.scalix.world | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of api.scalix.world. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| world. | present | 13081 | 8 | Verified |
| scalix.world. | present | 42985 | 13 | Verified |
| api.scalix.world. | Verified address RRset verified with the apex keys |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer realm="https://docs.scalix.world/mcp", resource_metadata="https://api.scalix.world/.well-known/oauth-protected-resource/v1/mcp", error="invalid_token", error_description="authenticate with an OAuth grant or a Scalix API key"
Bearer realm="https://docs.scalix.world/mcp", resource_metadata="https://api.scalix.world/.well-known/oauth-protected-resource/v1/mcp", error="invalid_token", error_description="authenticate with an OAuth grant or a Scalix API key" | Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=() |
Protected resource metadata
| Document | https://api.scalix.world/.well-known/oauth-protected-resource/v1/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://api.scalix.world/v1/mcp |
| Authorisation server | https://api.scalix.world |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.scalix.world/v1/mcp | Verified | 200 | |
| http (plaintext) | http://api.scalix.world/v1/mcp | HTTPS enforced | 301 | https://api.scalix.world/v1/mcp |
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 →
scalix_ai_infer ~138
Run AI inference on Scalix AI. Sends a prompt and returns the model's response in the OpenAI-compatible chat-completions format; tokens are billed to the project's credit pool. Discover available model IDs with scalix_ai_models.
| Name | Type | Req | Description |
|---|---|---|---|
| max_tokens | integer | – | Maximum tokens to generate |
| model | string | – | Model ID (from scalix_ai_models — a scalix-auto/* tier or a scalix-gw/<vendor>/<model> catalog id) |
| prompt | string | yes | User prompt / message |
| system | string | – | System message |
| temperature | number | – | Sampling temperature (0-2) |
No output schema declared.
No examples provided.
scalix_ai_models ~38
List the AI models available to the project — virtual tiers and the pass-through catalog model IDs — for use in scalix_ai_infer.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
scalix_auth_configure ~116
Configure end-user authentication for the project — require MFA, require email confirmation, and set the allowed auth providers. Needs an admin API key: organization admin scope is never delegated to a connected app, so this tool fails on an OAuth connection.
| Name | Type | Req | Description |
|---|---|---|---|
| allowed_providers | array | – | Allowed auth providers (e.g., ["email", "google", "github"]) |
| mfa_enabled | boolean | – | Require multi-factor authentication |
| require_email_confirmation | boolean | – | Require users to confirm their email before a session is issued |
No output schema declared.
No examples provided.
scalix_build_create ~67
Create a new container image build from a Git repository or Dockerfile.
| Name | Type | Req | Description |
|---|---|---|---|
| branch | string | – | Git branch |
| dockerfile | string | – | Path to Dockerfile in repo |
| git_url | string | yes | Git repository URL |
| name | string | yes | Build name |
No output schema declared.
No examples provided.
scalix_build_status ~31
Get the status and logs of a build.
| Name | Type | Req | Description |
|---|---|---|---|
| build_id | string | yes | Build ID to check |
No output schema declared.
No examples provided.
scalix_computer_create ~318
Get or create a persistent Linux machine by name. Idempotent — calling it again with the same name returns the existing machine rather than creating another, so it is safe to retry. Unlike a sandbox, the disk survives stop/start and is only erased by scalix_computer_delete.
| Name | Type | Req | Description |
|---|---|---|---|
| disk_gb | integer | – | Root disk in GB, 5-200 (default 10). Fixed at create — disks do not grow. Ignored if the machine already exists. |
| memory_mb | integer | – | Memory in MB, 512-32768 (default 1024). Ignored if the machine already exists. |
| name | string | yes | Machine name: lowercase letters, digits and hyphens, max 63 characters. Unique to you. |
| ssh_keys | array | – | OpenSSH public keys to authorise for root, max 32, e.g. ["ssh-ed25519 AAAAC3Nz… you@laptop"]. Only needed if a human will ssh in — exec, write_file and read_file all work without one. Send the public… |
| vcpus | integer | – | vCPUs, 1-16 (default 1). Ignored if the machine already exists. |
No output schema declared.
No examples provided.
scalix_computer_delete ~50
Permanently delete a persistent Linux machine AND its disk. This cannot be undone — use scalix_computer_stop if you may want the files back.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Machine id |
No output schema declared.
No examples provided.
scalix_computer_exec ~146
Run a command inside a persistent Linux machine and wait for it to finish. Returns exit code, stdout and stderr. The machine must be running.
| Name | Type | Req | Description |
|---|---|---|---|
| args | array | – | Arguments, e.g. ["-lc", "npm test"] |
| command | string | yes | Program to run, e.g. bash |
| cwd | string | – | Working directory inside the machine |
| env | object | – | Environment variables for this command only |
| id | string | yes | Machine id from scalix_computer_create or scalix_computer_list |
| timeout_ms | integer | – | Give up after this many milliseconds, 1000-600000 (default 120000) |
No output schema declared.
No examples provided.
scalix_computer_list ~25
List your persistent Linux machines with their status, address and resource shape.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
scalix_computer_read_file ~44
Read a text file out of a persistent Linux machine.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Machine id |
| path | string | yes | Absolute path inside the machine |
No output schema declared.
No examples provided.
scalix_computer_set_ssh_keys ~128
Replace the ssh keys authorised for root on a persistent Linux machine. This is how you revoke: send the list without the key you want gone, and on a running machine it stops working immediately. Sending an empty list removes every key. Not a patch — whatever you send becomes the whole list, so read the current keys from scalix_computer_list first if you mean to add one.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Machine id |
| ssh_keys | array | yes | The complete list of OpenSSH public keys, max 32. Empty array removes all of them. |
No output schema declared.
No examples provided.
scalix_computer_start ~33
Start a stopped persistent Linux machine. Same disk, same address.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Machine id |
No output schema declared.
No examples provided.
scalix_computer_stop ~63
Stop a persistent Linux machine. The disk and the network address are kept, so starting it again returns the same files at the same address. Stop machines you are done with — a stopped machine costs only its disk.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Machine id |
No output schema declared.
No examples provided.
scalix_computer_write_file ~111
Write a text file into a persistent Linux machine. Use this instead of shelling out with cat/echo — no quoting to get wrong.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | File contents as text |
| id | string | yes | Machine id |
| mode | integer | – | Unix mode in decimal, e.g. 493 for 0755. Omit unless the file must be executable. |
| path | string | yes | Absolute path inside the machine, e.g. /root/app/main.py |
No output schema declared.
No examples provided.
scalix_crew_board_post ~231
Post a note to the crew's notice board for other members and the human to see. The board is news, not knowledge: set ttl_seconds so routine updates expire on their own, pin only what every future task must see, and set owner_member_id to hand work off to a specific member. Notes cannot be edited from here — post a correction instead.
| Name | Type | Req | Description |
|---|---|---|---|
| author_member_id | string | – | Your member id, so the note is attributed. Omit when posting as the human. |
| body | string | yes | The note, max 8000 chars. Write for a teammate who was not watching your work. |
| crew_id | string | yes | Crew id from scalix_crew_list |
| owner_member_id | string | – | Hand off: the member id now responsible for this item. |
| pinned | boolean | – | Keep this in front of everyone indefinitely. Default false; most notes should expire instead. |
| ttl_seconds | integer | – | Seconds until the note expires, 60 to 7776000 (90 days). Omit for no expiry — usually only right for pins. |
No output schema declared.
No examples provided.
scalix_crew_board_read ~90
Read a crew's notice board: every pinned note plus the newest unpinned ones, current as of this call. The board is the crew's shared coordination state — read it before starting work so you act on the latest news, and post what teammates need to know with scalix_crew_board_post.
| Name | Type | Req | Description |
|---|---|---|---|
| crew_id | string | yes | Crew id from scalix_crew_list |
No output schema declared.
No examples provided.
scalix_crew_list ~43
List your crews with their ids and names. A crew is a team of AI members that share a notice board; use the crew id with the board tools.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
scalix_cron_create ~82
Create a cron schedule to run a function or webhook on a timer.
| Name | Type | Req | Description |
|---|---|---|---|
| action_type | string | yes | Type of action to trigger |
| config | object | – | Action configuration (function_id or webhook URL) |
| expression | string | yes | Cron expression (e.g., '*/5 * * * *') |
| name | string | yes | Schedule name |
No output schema declared.
No examples provided.
scalix_db_migrate ~40
Apply a database migration by version number.
| Name | Type | Req | Description |
|---|---|---|---|
| tenant_id | string | yes | Tenant ID |
| version | string | yes | Migration version to apply |
No output schema declared.
No examples provided.
scalix_db_optimize ~40
Analyze a SQL query and return optimization suggestions including index recommendations and query rewrites.
| Name | Type | Req | Description |
|---|---|---|---|
| sql | string | yes | SQL query to analyze and optimize |
No output schema declared.
No examples provided.
scalix_db_pii ~24
List all columns classified as containing personally identifiable information (PII).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
scalix_db_query ~127
Execute a SQL query against the project database. Returns columns, rows, row count, and cost breakdown. Destructive statements (DROP/TRUNCATE/bulk DELETE) require a two-step confirmation: the first call returns code CONFIRMATION_REQUIRED with a confirmation_token — re-call with that value in confirm_token to execute.
| Name | Type | Req | Description |
|---|---|---|---|
| confirm_token | string | – | Confirmation token from a prior CONFIRMATION_REQUIRED response; required to execute destructive SQL (single-use, short TTL) |
| params | array | – | Bind parameters for the query |
| sql | string | yes | SQL query to execute |
No output schema declared.
No examples provided.
scalix_db_relationships ~24
Get the relationship map showing how tables are connected via foreign keys.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
scalix_db_schema ~26
Get the full database schema including all tables, columns, types, and relationships.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
scalix_db_search_columns ~37
Search for columns by name or type across all tables.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Search term to match column names or types |
No output schema declared.
No examples provided.
scalix_db_table ~38
Get detailed information about a specific database table including columns, indexes, and foreign keys.
| Name | Type | Req | Description |
|---|---|---|---|
| table | string | yes | Table name to inspect |
No output schema declared.
No examples provided.
scalix_db_text_to_sql ~131
Translate a plain-language question into a candidate SQL query using pattern-matching against the live schema (no AI model — simple questions only: counts, averages, filtered selects on a named table). Returns the SQL without executing it, with a confidence score; low confidence means the table was guessed. Review the statement and tables_used, then run it with scalix_db_query. For complex questions, read scalix_db_schema and write the SQL directly.
| Name | Type | Req | Description |
|---|---|---|---|
| question | string | yes | The question to answer from the database, in plain language (e.g. 'how many orders shipped last week?') |
No output schema declared.
No examples provided.
scalix_domain_add ~42
Add a custom domain to the project. Returns DNS records to configure.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Domain name to add (e.g., api.example.com) |
No output schema declared.
No examples provided.
scalix_domain_list ~21
List all custom domains and their SSL/verification status.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
scalix_domain_verify ~32
Verify DNS configuration for a custom domain and provision SSL certificate.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Domain to verify |
No output schema declared.
No examples provided.
scalix_events_publish ~85
Publish an event to a topic. Provide an event_type (a short name for the kind of event, e.g. 'user.created') and the data payload.
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | yes | Event payload (JSON) |
| event_type | string | yes | Event type/name, e.g. 'user.created' |
| topic_id | string | yes | Topic ID to publish to |
No output schema declared.
No examples provided.
scalix_events_topics ~53
List the event-bus topics in the project, with each topic's ID and name. Use this to find or verify a topic_id before publishing with scalix_events_publish; publishing to a non-existent topic fails.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
scalix_fn_deploy ~91
Deploy a Scalix Function — serverless, per-request billed, running in isolated microVMs — from a container image. Invoke it with scalix_fn_invoke once deployed.
| Name | Type | Req | Description |
|---|---|---|---|
| image | string | yes | Container image reference |
| name | string | yes | Function name |
| runtime | string | – | Runtime — `node` or `python` (exactly what the functions orchestrator accepts) |
No output schema declared.
No examples provided.
scalix_fn_invoke ~46
Invoke a deployed function with a JSON payload.
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | – | JSON payload to pass to the function |
| function_id | string | yes | Function ID to invoke |
No output schema declared.
No examples provided.
scalix_fn_list ~17
List all deployed serverless functions.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
scalix_kv_get ~75
Read a single value from the project's key-value store by exact key. Returns the stored value, or a not-found error if the key does not exist or its TTL has expired. Use scalix_kv_list to discover keys by prefix first.
| Name | Type | Req | Description |
|---|---|---|---|
| key | string | yes | Exact key to look up (case-sensitive) |
No output schema declared.
No examples provided.
scalix_kv_list ~35
List keys in the key-value store, optionally filtered by prefix.
| Name | Type | Req | Description |
|---|---|---|---|
| prefix | string | – | Filter keys by prefix |
No output schema declared.
No examples provided.
scalix_kv_set ~57
Set a key-value pair with optional TTL.
| Name | Type | Req | Description |
|---|---|---|---|
| key | string | yes | Key to set |
| ttl | integer | – | Time-to-live in seconds (0 = no expiry) |
| value | string | yes | Value to store |
No output schema declared.
No examples provided.
scalix_project_create ~95
Create a new project within an organization. Returns the project ID, name, and slug. Issue an API key for the new project separately. Needs an admin API key: organization admin scope is never delegated to a connected app, so this tool fails on an OAuth connection.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Project display name |
| org_id | string | yes | Organization ID |
| slug | string | yes | URL-safe project slug |
No output schema declared.
No examples provided.
scalix_project_list ~81
List every project in an organization, with each project's ID, name, and slug. Use this to resolve a project ID before calling project-scoped tools. Needs an admin API key: organization admin scope is never delegated to a connected app, so this tool fails on an OAuth connection.
| Name | Type | Req | Description |
|---|---|---|---|
| org_id | string | yes | Organization ID whose projects to list |
No output schema declared.
No examples provided.
scalix_run_delete ~98
Permanently delete a Scalix Run service. This cannot be undone: it stops the running instances, releases the public HTTPS URL, erases any attached volumes and discards every revision, so scalix_run_rollback cannot bring it back afterwards. To stop paying for an idle service without losing it, set min_instances to 0 with scalix_run_scale instead.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Service ID (from scalix_run_list) |
No output schema declared.
No examples provided.
scalix_run_deploy ~201
Deploy a long-running container service on Scalix Run from a container image. Creates a new service, or a new revision of an existing service with the same name, with health checks, a public HTTPS URL, and autoscaling between min_instances and max_instances (min 0 = scale-to-zero when idle). Billed per vCPU-hour while instances run. Roll back a bad revision with scalix_run_rollback.
| Name | Type | Req | Description |
|---|---|---|---|
| env | object | – | Environment variables as key-value pairs |
| image | string | yes | Container image from the Scalix registry ({registry}/{project_id}/{repo}:{tag}). External registries (Docker Hub, etc.) are NOT supported — build & push first with scalix_build_create. |
| max_instances | integer | – | Maximum instances |
| min_instances | integer | – | Minimum instances (0 = scale to zero) |
| name | string | yes | Service name |
| port | integer | – | Port the container listens on |
No output schema declared.
No examples provided.
scalix_run_list ~19
List all deployed container services in the project.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
scalix_run_rollback ~102
Roll a Scalix Run service back to an earlier revision — omit 'revision' to return to the immediately previous one. Traffic switches to the target revision; the replaced revision is kept and can be redeployed later. Use scalix_run_list to see services and their current revisions.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Service ID (from scalix_run_list) |
| revision | integer | – | Revision number to roll back to; omit for the immediately previous revision |
No output schema declared.
No examples provided.
scalix_run_scale ~119
Change the autoscaling bounds of an existing Scalix Run service without redeploying it. Raising min_instances keeps instances warm (no cold starts, higher cost); min_instances 0 enables scale-to-zero when idle. Takes effect immediately. Find service IDs with scalix_run_list.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Service ID (from scalix_run_list) |
| max_instances | integer | – | New maximum instance count the service may scale up to |
| min_instances | integer | – | New minimum instance count (0 = scale-to-zero when idle) |
No output schema declared.
No examples provided.
scalix_sandbox_run ~99
Execute code in an isolated sandbox. Supports Python, JavaScript, TypeScript, and Bash. Returns stdout/stderr.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | Source code to execute |
| files | object | – | Additional files (filename -> content) |
| language | string | yes | Programming language |
| packages | array | – | Packages to install (pip/npm) |
| timeout_seconds | integer | – | Max execution time in seconds (default: 30) |
No output schema declared.
No examples provided.
scalix_status ~25
Get the current health status of the Scalix Cloud platform including all service components.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
scalix_storage_create_bucket ~108
Create a new Scalix Storage bucket in the project (S3-compatible object storage). Bucket names must be unique within the project. Setting public=true makes every object in the bucket readable without authentication — leave it false (the default) and use presigned URLs for private sharing.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Bucket name, unique within the project |
| public | boolean | – | true = all objects publicly readable without auth; false (default) = private, share via presigned URLs |
No output schema declared.
No examples provided.
scalix_storage_download ~43
Download an object from storage. Returns the content as base64.
| Name | Type | Req | Description |
|---|---|---|---|
| bucket | string | yes | Bucket name |
| key | string | yes | Object key (path) |
No output schema declared.
No examples provided.
scalix_storage_list ~54
List storage buckets, or list objects in a specific bucket with optional prefix filter.
| Name | Type | Req | Description |
|---|---|---|---|
| bucket | string | – | Bucket name. If omitted, lists all buckets. |
| prefix | string | – | Filter objects by key prefix |
No output schema declared.
No examples provided.
What is the Scalix Cloud MCP server?
Scalix Cloud is an MCP server listed in the public MCP registry as world.scalix/cloud. The agent-native cloud: database, functions, AI, storage, computers. 50 tools, one API key. This page covers its hosted endpoint (https://api.scalix.world/v1/mcp).
Is the Scalix Cloud MCP server safe to use?
Scalix Cloud scores 94 out of 100 on VerifyMCP. 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 Scalix Cloud MCP server expose?
Scalix Cloud exposes 51 tools: scalix_db_relationships, scalix_db_search_columns, scalix_db_pii, scalix_db_optimize, scalix_db_text_to_sql, and 46 more. Their descriptions and schemas cost roughly 3,910 tokens of context every time the server is loaded.
Does the Scalix Cloud MCP server require authentication?
Yes. Scalix Cloud asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the Scalix Cloud MCP server still maintained?
Scalix Cloud is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.